Short answer: Brewing is a water-intensive process, and the gap between a well-run facility and an average one is large enough to represent both a meaningful cost line and a credible ESG commitment — but closing that gap requires sub-process metering, not just facility-level reporting.
Why Water Is Brewing’s Most Visible Environmental Lever
Beer is largely water. Yet for every liter that ends up in a can or keg, breweries consume considerably more — for mashing, cooling, cleaning-in-place (CIP), steam generation, and packaging rinses. Industry benchmarks suggest a wide range across facility types and vintages, with best-in-class operations achieving ratios well below the sector average. That spread is not random: it maps almost directly to the quality of a brewery’s measurement infrastructure and the frequency with which process teams act on what they measure.
For sustainability leads and CFOs, the framing matters. Water is simultaneously a cost input, a regulatory exposure (particularly in water-stressed regions), and an increasingly scrutinized ESG disclosure item under frameworks such as GRI 303 and the CDP Water Security questionnaire. Analytics is the mechanism that converts raw meter readings into actionable reduction targets.
Building the Sub-Metering Foundation
Aggregate water meters tell you what you spent; sub-process meters tell you where to cut. A credible water-analytics program typically layers three tiers:
- Process-level metering: separate readings for the brewhouse, fermentation/conditioning cooling circuits, CIP systems, and packaging lines.
- Wastewater characterization: volume and biological oxygen demand (BOD) load, because high-strength discharge often signals product loss, not just water waste.
- Batch linkage: tying water consumption to individual production orders by style, batch size, and operator, so that outliers surface automatically rather than being averaged away.
Without this foundation, machine-learning models have little to work with. With it, even simple regression tools can flag which styles, which shifts, or which CIP programs are driving the facility’s liters-per-liter ratio upward.
Analytics Use Cases Worth Prioritizing
CIP optimization is usually the highest-yield target. Cleaning cycles are necessary for food safety but frequently over-engineered — longer than conductivity data would justify, using more water than the soil load requires. Sensor-driven CIP systems that end a cycle when clean rather than when a timer expires routinely demonstrate double-digit water reductions in pilot deployments.
Cooling tower and glycol circuit monitoring surfaces leak and bleed-off inefficiencies that are invisible without trend analysis. Evaporation losses are expected; anomalous spikes in make-up water are not.
Predictive scheduling can reduce the number of partial-batch CIP cycles triggered by unplanned changeovers — a cascading operational improvement with a direct water-efficiency benefit.
Non-Alcoholic Beer: A Nuanced Picture
Non-alcoholic beer has become a growth category with genuine ESG relevance, primarily through the social pillar — moderation, health outcomes, and inclusive hospitality. The water story is more complicated. Dealcoholization technologies add process steps that consume water and energy. Breweries scaling NA portfolios should model the incremental footprint per hectoliter rather than assuming a sustainability dividend exists automatically. The honest answer is that NA beer’s ESG case is strong, but it rests on social and governance foundations more than on environmental ones — at least until process engineering matures further. See also the fuller NA discussion at /2025/non-alcoholic-beer-esg-story/.
From Data to Disclosure
Water reduction targets are only credible when anchored to a measured baseline, a defined reduction pathway, and a transparent methodology for what is and is not counted (process water vs. irrigation vs. employee facilities). GRI 303-3 asks for withdrawal by source; CDP Water asks for risk-adjusted targets. Both reward specificity. Breweries that invest in sub-metering before they write their sustainability report are in a materially better position than those who attempt disclosure and then work backward.
Honest caveat: Water-intensity benchmarks published by industry associations vary in methodology and sample composition. Treat any single figure as directional rather than definitive, and build your reduction case on your own audited baseline.
Part of the ESG track — browse all.
Frequently asked questions
How much water does a typical brewery use per liter of beer produced? Benchmarks vary widely by facility size, technology, and process design — ranges often cited in industry literature span from roughly three to ten or more liters of water per liter of beer. World-class operations cluster toward the lower end; older or smaller sites often sit considerably higher. Auditing your own ratio is always the essential first step.
What data does a brewery need to run water-efficiency analytics? At minimum: metered sub-process data (brewing, cleaning-in-place, cooling, packaging), wastewater volume and load, and a production log tied to batch size and beer style. Without sub-metering, analytics can only point to the facility level rather than the process causing waste.
Does non-alcoholic beer require less water to produce than full-strength beer? Not automatically. Dealcoholization steps — membrane filtration or vacuum evaporation — add water and energy load. However, NA beer’s sustainability story lies more in the social pillar (moderation, health) than in a straightforward water-per-liter advantage. Some producers are actively engineering lower-footprint NA processes, but comparable published data remains limited.