Write your awesome label here.
Read a software water number, know what it covers, and know when it cannot be compared.
Six short modules in plain language: why water reaches every software role, the four layers of software water, consumption versus withdrawal, how to read a water number and state what it leaves out, why a litre in one place is not a litre in another, and the small things each role can do. No prerequisites and no calculation required.
2h 50m
6
12 question
80%
Certification
Software Water Essentials
How the course works
Basic on purpose
Plain language throughout, no opinions, no arithmetic to perform. The outcome is to recognize, interpret and question a water number, not to calculate a full SWI.
Draft status stated everywhere
The Software Water Intensity specification is draft v0.1.0, a work in progress and subject to change. Every module says so where it cites the spec.
One worked example, carried through
Northbridge, the same constructed organization used across the catalogue, so the figures stay consistent from module to module.
What this course helps with
The dimension most teams have not started on
Carbon has a ratified standard and years of practice behind it. Water is newer, the specification is still in draft, and most software teams have never been asked the question. This course is the entry point.
Numbers that arrive without a basis
One service reports 12 mL per request, another 9 mL. Module 4 walks that comparison and reaches the honest answer: not comparable as stated, and here is exactly why.
A liter is not a liter
The same volume means something different in a water-stressed basin. Module 5 explains stress adjustment, and why the AWARE and Aqueduct scales cannot be swapped for one another.
Who this is for
- Every software role — developers, testers, architects, data and platform engineers, product and delivery
- Sustainability practitioners adding water to work that so far covers only carbon
- Anyone who has been handed a water figure and asked whether it can be used
- No prerequisites and no engineering seniority assumed
Related courses:
This is a cross-role feeder course. For producing footprint figures rather than reading them, see SCI for AI Practitioner: The Measurement Lab. For the placement and capacity decisions that change a water number, see Green and Efficient Architect and GreenOps Practitioner.
What you will work with
The four layers
Building, electricity, hardware and the stress conversion — the structure everything else in the course hangs from.
The Northbridge worked entry
1,000 kWh in a month at a WUE of 0.3 L/kWh gives 300 L direct; a grid factor of 1.5 L/kWh gives 1,500 L indirect; across 100,000 requests that is roughly 18 mL per request. Illustrative figures — and quantified operational water only, embodied not yet quantified, so a partial result rather than a complete SWI.
The reading card
Eight questions to ask of any water figure, from how much and which kind to what is missing, ending with whether it can be compared or filled in for the Northbridge entry.
What you will be able to do
Course Lessons
The full course
01
Why Water, and Why You
Software feels dry, but the buildings it runs in use water for cooling, the electricity it consumes was made using water, and the hardware was manufactured with it. This module shows those three connections and closes the gap between the people who can see the water and the people who change the software.
module-01
02
The Four Layers: building, electricity, hardware, and the stress conversion
This module gives the three ways software uses water their proper names, as the draft SWI specification uses them, and adds a fourth layer that converts litres into how much each litre matters. It ends with the only line of arithmetic in the course.
module-02
03
Consumption and Withdrawal: used up vs borrowed
Water figures come in two kinds, and confusing them is the most common mistake in reading them. This module teaches the distinction between water used up and water borrowed and returned, and the rule that the two are never added together.
module-03
04
Reading a Water Number
This module teaches no calculations. It teaches how to look at any water figure, whether a provider report, a news headline or a colleague’s slide, and know what it does and does not say.
module-04
05
Stress-Adjusted Water: a liter is not a liter
The same liter counts for more where water is scarce and for less where it is plentiful. This module turns that idea into arithmetic using a published factor per place, giving the conversion layer its full treatment at foundation depth.
module-05
06
Small Things That Save Water
The earlier modules built a vocabulary; this one turns it into actions small enough to take this week, organised by role. None of them needs a water meter, a budget or permission to run a project.
module-06
07
Final Assessment
A final assessment of 12 questions - 80% to pass, 30 minutes, retake available.
Final Assessment
Assessment & Certification
Time to complete