A single project’s impact depends on its demand, supply source, local drought conditions, and the existing demands already competing for water. Cumulative development is often more important than one headline number.
Good analysis separates annual usage from hot-day peaks and planned buildout from present operations.
What to verify locally: This page helps readers ask about cumulative effects, conservation, and public reporting.
Assess cumulative demand
Use original public records whenever possible. A developer statement can explain an intent; an approval, permit, or utility filing is where enforceable details are more likely to appear.
Separate facts from forecasts
Record the date, document title, agency, page number, and project address. That turns a claim into something another reader can check.
Evidence standard: this guide avoids treating a proposal as a completed project, and avoids treating a missing record as proof that no impact exists.