What you will learn
- How restriction stages are defined and communicated
- What customer messaging works during a drought, and what backfires
- How rebate and fixture programs are managed
- How conservation is measured: usage, not enrolment
- What happens when restrictions end
What the project is
A drought program has stages, usually escalating from voluntary conservation to mandatory restrictions on outdoor watering, then to tighter limits and penalties. Each stage changes what customers may do, and the software communicates those rules, tracks compliance where it can, and manages the programs that help customers use less: rebates for efficient toilets and washing machines, turf replacement incentives, leak fix assistance, and free fixture distributions.
The measurement problem is central. Enrolment in a rebate program is not conservation; a toilet replaced is not water saved until usage falls. The software connects program participation to metered usage, so the utility can report, by area and by program, whether consumption actually dropped, and by how much. That evidence decides which programs expand and which stop.
Core features
Usage tracking is the feature that separates a drought program from a drought press release. Everything else is communication and administration on top of it.
- Restriction stage management: rules per stage, effective dates, and the customer-facing explanation of each stage.
- Customer messaging by area and stage, through email, SMS, and bill inserts, with delivery tracking.
- Rebate program management: applications, eligibility checks, approvals, and payment or credit handling.
- Fixture and turf program tracking: installations, inspections, and the usage baseline for each participating property.
- Usage analytics by area, customer class, and program participation, showing whether consumption is actually falling.
- Violation and variance handling: reported violations, warnings, and exemptions for medical or special needs.
- Stage exit handling: lifting restrictions, closing programs, and reporting the program's total effect.
How it is built
Build the usage measurement first, because a drought program without it cannot prove anything. Rebate administration can follow.
- Program design: define stages, rules, rebate offers, and the usage metrics that will judge the program.
- Usage baseline: establish per-area and per-class consumption baselines from billing and meter data before the program starts.
- Messaging and rebate build: stage communications, application flows, and approval workflows, tested with a small customer group.
- Measurement loop: connect participation to usage, report falling or stagnant consumption by area and program, and adjust offers.
- Exit and reporting: lift stages cleanly, close programs, and publish the total effect with the method behind it.
Tech considerations
The technical core is usage analytics linked to participation records. Messaging and rebate workflows are standard web work.
- Usage data integration from billing or smart metering, with baselines that survive rate and season changes.
- Customer segmentation by area, class, and participation, so messaging and measurement target the right groups.
- Rebate workflow with document upload, eligibility rules, and payment or bill-credit integration.
- Messaging integration for email and SMS, with delivery tracking and preference handling.
- Dashboards showing consumption trends against baselines, by area and program, updated as new reads arrive.
Challenges to plan for
Drought programs fail on fairness and on measurement. Customers who see neighbours ignoring restrictions stop complying, and programs that cannot show savings lose funding.
- Fairness perception: restrictions that hit gardens while large users seem untouched destroy public cooperation fast.
- Seasonal confusion: a usage drop in winter may be weather, not conservation, and baselines must account for season.
- Rebate fraud: applications for fixtures never installed waste money and discredit the program, so inspection matters.
- Restriction fatigue: long programs lose compliance over time, and messaging must change, not just repeat.
Who it is for, and honest limits
This fits utilities in drought-prone regions, systems facing supply constraints, and any utility whose regulator or council requires a drought plan. It fits less well for a utility with abundant supply and no shortage history, where a general conservation program without stages is a better fit.
It does not create water. It reduces demand and manages the shortage fairly. If supply itself is the constraint, the program buys time and reduces peak demand, but the long-term answer is supply, storage, or interconnection, not messaging.
Frequently asked questions
How are restriction stages decided?
By supply indicators the utility defines in advance: reservoir levels, groundwater levels, demand trends, and forecasts. Stages should be defined before a drought, not invented during one, because mid-crisis rule-making looks arbitrary.
Do rebates actually save water?
They can, when the fixture is installed and the old one removed. The program should verify installation and track the property's usage before and after, rather than counting applications as savings.
How are violations handled?
Usually with warnings first, then penalties defined by the utility's rules. Reporting channels should be simple, and exemptions for medical needs or new landscaping should be handled through a clear variance process.
What happens when the drought ends?
Stages are lifted in order, customers are notified, and programs close with a final report. Lifting cleanly matters: restrictions left in place after supply recovers breed cynicism about the next drought.
Can usage be compared fairly across areas?
Only with baselines that account for customer mix, season, and weather. A wealthy area with gardens and a dense apartment area will never use the same amount, and comparing them raw proves nothing.