Prepare for CWEP by practicing water-balance reasoning: split metered use into end uses, estimate savings with explicit units and assumptions, compare measures with a decision table, and pressure-test recommendations against seasonal patterns and operating constraints. Two worked scenarios, a self-check rubric, and a four-week sequence structure the review.
Building a defensible water baseline from billing and meter records
A baseline is not just annual total consumption; it is consumption resolved by month, by meter, and by estimated end use, so seasonal uses and large intermittent demands become visible instead of hidden inside an average.
Start with the billing record and convert every line to one unit, then plot monthly values rather than computing a single annual figure. Averaging across twelve months smooths away exactly the signals an efficiency professional needs: summer irrigation peaks, cooling season spikes, and step changes that suggest leaks or occupancy shifts. In a paper scenario, annotate each month with a plausible driver so the pattern has an explanation you can state out loud.
Next, reconcile meters to end uses. Indoor fixture demand tracks occupancy and is roughly stable across the year; landscape irrigation and evaporative cooling track weather. When a scenario gives you monthly data plus an employee count or irrigated area, use the stable component as an anchor and treat the seasonal residual as the weather-driven portion. Writing the anchor-and-residual logic on paper forces the assumptions into the open, which is what makes a baseline defensible rather than convenient.
Indoor fixture measures: why flow rates, volume, and behavior produce different estimates
Fixture savings come from three distinct levers: lower flow or flush rates, shorter duration or fewer events, and leak elimination. Each lever uses different input data, and mixing them is the classic way an estimate becomes internally inconsistent.
Trace one example end to end. If a scenario replaces standard lavatory aerators with lower-flow units, savings per use equals the flow-rate difference multiplied by the duration of each use, then multiplied by uses per person per day, then by population. If it replaces flushometer toilets, the driver is gallons per flush times flush frequency. Writing the chain as a sentence with units at each step, for example gallons per use times uses per person-day times workdays, keeps the arithmetic honest.
Distinguish this from behavioral measures, which change duration or frequency instead of equipment ratings. A fixture retrofit holds its savings as long as the device is installed; a behavior-dependent saving decays and is harder to verify. Also separate leak savings: a running fixture or a failed flush valve can consume continuously, so its baseline is hours per day rather than events per day. Comparing a per-event estimate with a continuous-loss estimate side by side on paper makes the structural difference impossible to unsee.
Cooling tower water: why cycles of concentration changes are easy to overstate
Raising cycles of concentration reduces blowdown, but evaporation stays essentially the same, so the saving is the change in blowdown alone. Candidates who compute savings from total makeup overstate the opportunity substantially.
Worked example, labeled as a simplified teaching case: a tower evaporates 40,000 gallons per month. Blowdown at steady state is roughly evaporation divided by (cycles minus 1). At 3 cycles, blowdown is 40,000 / 2 = 20,000 gallons, and makeup is 60,000. At 5 cycles, blowdown is 40,000 / 4 = 10,000, and makeup is 50,000. The saving is 10,000 gallons per month, not the 20,000 someone would claim by subtracting makeup totals incorrectly or assuming all makeup is recoverable.
The better decision in a scenario is therefore to state the evaporation assumption explicitly and check the operating constraint before recommending higher cycles: dissolved solids, scale, and corrosion limits set how far cycles can rise, and water quality determines that limit. A recommendation that names the water-chemistry dependency and the resulting bounded saving is stronger than a larger unbounded number. This mirrors AWE's published research interest in cooling technologies, so practicing tower arithmetic on paper is directly on-scope study material.
Outdoor use and landscape measures: separating irrigation from the metered total
Irrigation is usually embedded in a mixed-use meter, so landscape analysis starts by isolating the seasonal component and estimating an irrigation requirement from area, plant water needs, and application efficiency before any smart-controller saving is claimed.
In a scenario, compare winter-month indoor baselines with summer-month totals; the difference is a first approximation of outdoor use. Then sanity-check it against the irrigated area: if the implied seasonal depth of application is implausibly high or low, revisit whether the winter baseline includes other seasonal loads, such as cooling. AWE's landscape resources, including its residential landscape best-practices work, frame this as matching applied water to plant need rather than simply reducing run times.
This matters because smart-controller savings are proportional to how much the existing schedule overwaters, not to total irrigation. If the scenario says the current schedule applies twice the estimated plant requirement, the ceiling for improvement is the over-application portion, capped by the plant need. A candidate answer that claims the whole irrigation volume as saving has ignored the physical requirement that the landscape still needs water. Stating the cap in the recommendation is the difference between a number and an argument.
Advanced metering and interval data: turning hourly patterns into findings
Interval data from advanced metering infrastructure shows when water moves, which supports leak detection, schedule diagnosis, and end-use disaggregation. Reading it well means looking for shape, minimum night flows, and consistency across days, not just totals.
AWE's research portfolio includes advanced metering infrastructure, and the professional skill it enables is pattern reading. In a paper exercise, take a hypothetical week of hourly data and ask three questions: is there a persistent overnight minimum that suggests a leak; do weekday and weekend shapes differ in a way consistent with occupancy; and do any single-day spikes appear that a monthly bill would have absorbed invisibly? Each observation converts raw data into a candidate finding with a named mechanism.
Now connect the pattern to a recommendation. A flat 24-hour flow in a building that should close overnight points toward leak repair, and its saving estimate comes from the minimum night flow rate extrapolated over the leak duration. A peaking irrigation-only meter with a misaligned schedule points to scheduling, and its estimate comes from the excess run time. Because the same data supports both, the exam-style skill is choosing the interpretation that matches the shape and stating the diagnostic evidence, not producing the largest possible number.
Worked scenarios: two decisions where the tempting answer is the wrong one
Scenario practice builds judgment by showing how a plausible first answer fails a check. These two cases, written as paper exercises, each contain a mistake, a better decision, and the reason the difference matters.
Scenario one: a 200-person office campus uses 1,200,000 gallons per year, with summer months about double winter months. A first-pass answer targets restrooms because fixtures feel like the obvious efficiency lever and estimates a large retrofit saving. The better decision builds the monthly split first: if fixtures anchored to occupancy account for roughly 600,000 gallons and the 600,000-gallon seasonal residual is split between irrigation and cooling, the cooling and irrigation portions are each comparable to the entire plausible fixture saving. The reason it matters: prioritization changes with the split, and a defensible plan may lead with cooling tower and irrigation measures while fixtures remain a secondary measure.
Scenario two: a hospital proposes cutting cooling tower blowdown in half and claims makeup savings equal to the full blowdown volume. The better decision recomputes with the blowdown relationship from the earlier example: blowdown falls by only the increment between cycles, evaporation is unchanged, and the achievable cycles are bounded by water chemistry. The claim shrinks from the full blowdown volume to a smaller, explicitly derived figure. The reason it matters: an overstated proposal that exceeds chemistry limits would trade water savings for scale and corrosion risk, so the bounded answer is both more accurate and more professionally responsible, which is the reasoning style a scenario-based credential rewards.
- In both scenarios, write the estimate chain with units before computing any total.
- Name one explicit assumption per estimate, such as evaporation volume or winter baseline.
- State the constraint that bounds the recommendation, such as plant water need or dissolved-solids limits.
A four-week practice sequence with a self-check rubric
Structure preparation as escalating exercises: week one, baselines; week two, fixture and leak estimates; week three, cooling and irrigation cases; week four, integrated recommendation memos scored against a rubric.
Week one, take any published monthly consumption series and produce a seasonal split with a one-sentence driver for each month. Week two, write three fixture-chain estimates and one leak estimate from a minimum night flow, keeping units visible. Week three, redo the cooling tower and irrigation scenarios in this guide with different numbers so the relationships, not the answers, are what you retain. Week four, draft a one-page recommendation for a composite campus scenario: target, estimated saving, bounding assumption, and verification signal.
Score each week-four memo against a self-check rubric where a learning milestone, not a passing prediction, is the goal. Full credit means: units cancel correctly through the estimate chain; seasonal effects are acknowledged; one assumption is stated per number; the recommendation is bounded by an operating or physical constraint; and a verification signal, such as post-change metered flow, is named. If any row fails, return to the matching earlier week rather than rereading notes. For administrative details about the credential itself, consult the issuer, the Alliance for Water Efficiency, directly.
| Measure | Data needed to estimate savings | Most common overstatement risk | Verification signal |
|---|---|---|---|
| Fixture retrofit | Flow or flush rates, events per person-day, population | Counting duration or frequency changes the device does not deliver | Post-install metered indoor baseline drop |
| Cooling tower cycles increase | Evaporation estimate, current and achievable cycles, water chemistry | Treating all makeup as recoverable savings | Conductivity logs plus reduced makeup metering |
| Irrigation scheduling or smart control | Irrigated area, estimated plant requirement, current application depth | Claiming the full irrigation volume instead of the over-application | Seasonal residual versus new winter baseline comparison |
| Leak repair | Minimum night flow rate, hours of persistence | Assuming the leak was intermittent when it was continuous | Overnight minimum flow approaching zero |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.