Is Water Use in Development Really Underestimated?

When a developer stands before a city commission and pitches a project, the numbers in that presentation are supposed to reflect reality. What happens when they don't? According to critics of at least one recent development proposal, projected water use was "woefully underestimated" — and the developer's pitch to the city commission "plainly misrepresents" actual consumption. That's not a rounding error; that's a credibility problem with real consequences for the communities and ecosystems downstream.

Water is the constraint that most infrastructure projects don't take seriously until it's too late.

Understanding Water Use in Development Projects

Water use in infrastructure is deceptively complex. A development's water footprint isn't just what comes out of taps — it includes cooling systems, landscaping irrigation, construction-phase water, stormwater management, and, in some cases, process water for industrial or data center applications. Each of these categories requires separate modeling, and each carries its own set of assumptions that can drift dramatically from reality if the underlying data is weak or — worse — deliberately conservative.

Accurate water forecasting isn't a bureaucratic box to check. It's the foundation on which municipalities make binding decisions about resource allocation for decades.

For residential developments, consumption models typically rely on per-unit averages drawn from regional utility data. For commercial or mixed-use projects, those models become more complicated quickly. Data centers, for instance, can consume millions of gallons per day in cooling alone. Solar farms with panel-washing requirements, battery storage facilities with thermal management systems, and large-scale agricultural operations all have water profiles that look nothing like standard residential benchmarks. When developers apply the wrong baseline or cherry-pick favorable assumptions, the resulting projections are fiction dressed up as engineering.

The consequences of that fiction fall almost entirely on the public.

When Developer Claims Don't Hold Up

The phrase "plainly misrepresents" in any regulatory or public hearing context is damning. It means reviewers — whether engineers, city staff, or outside consultants — ran the numbers and found that what was presented doesn't square with what would actually happen on the ground.

This isn't uncommon. The incentive structure for developers favors optimistic projections. Lower projected water demand can mean faster permitting, reduced mitigation requirements, fewer environmental hurdles, and lower infrastructure connection fees. A project that honestly projected, say, 500,000 gallons per day in consumption might face a fundamentally different approval process than one that claims 150,000. The delta between those figures isn't just an academic disagreement; it represents real stress on municipal water systems, aquifers, and watersheds.

The pattern of underreporting water demand mirrors what happened with traffic studies a generation ago: developers learned that low-balling projections got projects approved, and regulators rarely had the resources to push back effectively.

What's changed — or what should change — is that communities now have access to better independent modeling tools, more sophisticated environmental review requirements in many jurisdictions, and a growing body of case law around misrepresentation in permitting applications. When a project's actual water draw materially exceeds what was promised, the legal and political exposure for everyone involved increases substantially.

What Underestimation Actually Costs

The impact of miscalculated water use in development projects extends well beyond the project boundary. Groundwater aquifers don't respect property lines. When a large development draws more than its permitted share, neighboring wells can fail, stream flows can drop, and ecosystems that depend on baseflow from those aquifers — wetlands, riparian corridors, cold-water fisheries — can degrade or collapse.

For municipal water systems, the math is similarly unforgiving. Utilities plan infrastructure capacity — treatment plants, storage tanks, distribution mains — based on projected demand. A development that consumes twice its projected water share can push a system past capacity years ahead of schedule, forcing ratepayers to fund emergency upgrades that nobody budgeted for.

There's also a sustainability dimension that doesn't get enough attention in approval hearings. Infrastructure water management isn't just about having enough water today; it's about maintaining that supply through droughts, population growth, and climate variability. A project that strains water resources in good years becomes a crisis in bad ones.

Communities that approve projects based on underestimated water projections are, in effect, mortgaging their resource security against an optimistic scenario that may never materialize.

And in regions already facing water stress — the American Southwest, parts of the Southeast, drought-prone agricultural areas — that gamble is increasingly reckless.

Regulatory Teeth: What the Rules Actually Require

Most jurisdictions require some form of water availability analysis as part of environmental review for major development projects. In states with strong water law frameworks — Colorado, Arizona, California — developers must demonstrate that adequate water supply exists before a project can be approved. Other states have weaker requirements, and the gap shows.

Federal environmental review under NEPA (National Environmental Policy Act) requires disclosure of water impacts for projects with federal nexus, but the quality of that disclosure varies enormously. The regulation requires honesty; it doesn't always enforce it.

When a developer's claims are found to misrepresent water demand, the regulatory consequences depend heavily on when the misrepresentation is discovered. Caught during the review process, the project may face additional conditions, delays, or outright denial. Caught after approval — when actual consumption data from metering tells a different story than the application — the remedies are murkier. Regulators can impose penalties, require mitigation, or, in extreme cases, pursue legal action, but unraveling an already-approved and partially built project is politically and legally messy.

This is why front-end scrutiny matters. Municipalities with technical staff capable of independently reviewing water projections — or with the budget to hire outside hydrologists who will push back on developer assumptions — catch these discrepancies before they become entrenched problems. Many smaller communities don't have that capacity, which is exactly where misrepresentation tends to thrive.

Getting the Numbers Right: What Responsible Forecasting Looks Like

The good news is that accurate water forecasting isn't technically out of reach. The tools and methodologies exist. What's often missing is the will to use them rigorously.

For developers who want to build durable, approvable projects — and avoid the legal and reputational exposure that comes with challenged projections — a few practices separate serious water analysis from wishful thinking:

Use peer-reviewed consumption coefficients, not internal estimates. Organizations like the American Water Works Association publish consumption benchmarks by land use type that can be applied transparently and audited by third parties. Deviating from those benchmarks should require explicit, documented justification.

Model multiple scenarios. A single-point estimate for water use is almost always wrong. Responsible forecasting includes a base case, a high-demand scenario, and a stress-test scenario that reflects drought conditions or occupancy/utilization peaks. If a project is only viable under the most optimistic water assumption, that's material information for decision-makers.

Engage hydrologists early, not late. Bringing in water resource professionals after the project design is locked in produces defensive analysis. Integrating water constraints into early-stage project design often surfaces solutions — reclaimed water systems, closed-loop cooling, drought-tolerant landscaping — that reduce actual demand rather than just improving how demand gets reported.

Commit to metered monitoring and adaptive management. The most credible projects include post-approval monitoring requirements and binding commitments to reduce consumption if actual use exceeds projected thresholds. This converts a one-time promise into an ongoing accountability mechanism.

For regulators and community members evaluating developer claims, the key question is always: who ran these numbers, and what were their incentives? A water study produced exclusively by a firm hired and paid by the developer deserves more scrutiny than one conducted or independently verified by a third party. That's not cynicism; it's basic analytical hygiene.

The stakes around water use in development projects are only going up. As more infrastructure — energy, data, housing, agriculture — concentrates in water-stressed regions, the gap between what developers claim and what projects actually consume will face more scrutiny, more legal challenges, and more political resistance from communities that have watched their wells run dry while approvals kept getting stamped.

The developers and project sponsors who get ahead of this — who bring rigorous, transparent, independently verifiable water analysis to the table before anyone asks — will have a meaningful competitive advantage. Not just in getting permits, but in building the kind of community trust that makes long-term infrastructure projects viable.

The ones who keep low-balling the numbers are borrowing time they don't have.

Explore our marketplace for more insights on responsible development practices.

[INTERNAL LINK: water forecasting]

[INTERNAL LINK: environmental review requirements]

[INTERNAL LINK: sustainable development practices]