Your 5-Step Water Resources Checklist for Reliable Supply System Design

A reliable water supply system is not built on a single calculation or a lucky guess. It emerges from a sequence of deliberate decisions, each with its own failure modes. This checklist distills the five steps we see most often mishandled in real projects—demand forecasting, source evaluation, treatment selection, storage sizing, and distribution layout. We wrote it for engineers, planners, and utility managers who want a practical reference, not a textbook chapter. Each step includes what to check, what can go wrong, and how to decide when data is incomplete.

1. Why a Structured Checklist Matters in Water Supply Design

The difference between a system that works for decades and one that fails within a year often comes down to process, not technology. In a typical municipal project, we have seen teams jump straight to pipe sizing without verifying the demand assumptions that drive every downstream decision. The result: a network that meets peak hour flow on paper but cannot fill a storage tank overnight because the pump curve was mismatched to the actual static head.

A checklist forces explicit review of each step before moving to the next. It also creates a shared language between disciplines—civil engineers, hydrologists, treatment specialists, and operators. When a project runs into trouble, the checklist helps pinpoint where the assumption chain broke. For example, if a system runs dry in summer, the checklist might reveal that the demand forecast used average annual growth instead of seasonal tourism spikes.

We recommend treating the checklist as a living document. Update it after each project with new failure modes or design standards. Over time, it becomes a record of institutional knowledge that outlasts any single team member.

Common Reasons Teams Skip the Checklist

Time pressure is the most common excuse. When a client wants a design in two weeks, it is tempting to reuse an old template and adjust a few numbers. But that shortcut often leads to costly change orders later. Another reason is overconfidence: senior engineers sometimes assume they have seen it all and do not need a written guide. Our experience is that even experienced designers benefit from a structured review—especially when the project includes unfamiliar conditions like high turbidity sources or intermittent power supply.

2. Step 1: Demand Forecasting—Getting the Numbers Right

Demand forecasting is the foundation of any supply system, yet it is frequently done with too little data or too much optimism. The goal is not to predict the exact flow for every hour of the next 20 years, but to bound the range of plausible conditions and design for the worst reasonable case.

Start with current consumption data from water bills or flow meters. If the system is new, use benchmarks from similar communities, adjusted for climate, income, and industrial activity. Do not rely on a single average daily demand figure. You need at least three numbers: average day, maximum day, and peak hour. Maximum day is typically 1.5 to 2.5 times average, depending on climate and customer type. Peak hour can be 3 to 5 times average in residential areas with small storage.

Seasonal and Growth Adjustments

A common mistake is using a flat growth rate without considering seasonal variation. In tourist regions, summer population may double, and irrigation demand can push maximum day to four times the winter average. We recommend building a monthly demand profile using at least three years of historical data if available. For growth, use a range—low, medium, and high—based on zoning plans and economic trends, not a single number from a developer's proposal.

Red Flag: Demand Exceeds Source Capacity

If your maximum day demand is close to or above your firm source yield, you have a problem that no amount of clever distribution design can fix. This is the point to consider demand management, additional sources, or both. Do not assume you can simply drill a new well later—permitting and construction can take years.

3. Step 2: Source Evaluation—Yield, Quality, and Reliability

Once demand is bounded, the next step is to evaluate potential sources. The checklist here has three dimensions: yield (how much water is available), quality (what treatment is needed), and reliability (how consistent the source is over time and under stress).

For surface water, yield is typically the 7-day, 10-year low flow (7Q10) or a similar drought statistic. Groundwater yield depends on aquifer transmissivity and sustainable pumping rate—not just the instantaneous capacity of the pump. Many projects have failed because they sized the pump to the well's short-term drawdown test without accounting for long-term aquifer depletion.

Water Quality as a Constraint

Source quality directly affects treatment cost and complexity. A river with high turbidity during monsoon season may require a sedimentation basin or dissolved air flotation before filtration, adding capital and operational expense. Groundwater with iron and manganese may need oxidation and filtration. We recommend collecting at least one year of monthly quality data before finalizing the source. If that is not possible, use data from nearby sources with similar geology or hydrology.

Reliability Under Climate Change

Historical data may no longer be a reliable guide. In many regions, droughts are becoming more frequent and severe. We suggest adding a climate resilience factor: design the system to meet maximum day demand with the source at its 20-year drought yield, not the historical average. This may mean over-sizing storage or planning for emergency interconnections.

4. Step 3: Treatment Selection—Matching Process to Raw Water

Treatment is often the most expensive part of a water supply system, both in capital and operation. The checklist here is to match the treatment train to the raw water quality and the finished water quality goals, not to the latest technology brochure.

Start with a clear water quality target. In most jurisdictions, this is set by national drinking water standards. But you may also need to meet utility-specific goals for corrosion control, disinfection byproducts, or aesthetic parameters like taste and odor. Once the target is defined, compare it to the raw water quality data from Step 2. The gap determines the required treatment processes.

Common Treatment Trains and Their Pitfalls

For low-turbidity surface water, direct filtration (coagulation, flocculation, filtration) is common but can be upset by sudden turbidity spikes. A conventional plant with sedimentation is more robust but costs more. For groundwater with iron, a simple aeration and filtration system often works, but if manganese is also present, you may need pH adjustment or chemical oxidation.

A mistake we see repeatedly is designing treatment for average raw water quality and then struggling during high-turbidity events. The checklist should include a contingency plan for extreme events—whether that means a bypass line, chemical dose adjustment, or a backup source.

5. Step 4: Storage Sizing—More Than Just a Tank

Storage serves three purposes: equalizing demand (balancing supply and consumption), providing emergency reserve (fire flow, power outage), and maintaining pressure. The checklist must account for all three, not just the volume needed to meet peak hour.

Equalization storage is typically the volume needed to meet the difference between the source pumping rate and the demand over the peak day. A common rule of thumb is 25% of average daily demand, but this varies widely. We recommend running a mass curve analysis using hourly demand data if available.

Fire Flow and Emergency Storage

Fire flow requirements are set by local codes and depend on building type and spacing. In many areas, the required fire flow is 1,000 to 3,000 gallons per minute for two hours. That is 120,000 to 360,000 gallons of dedicated storage. Do not assume you can draw from equalization storage during a fire—the tank may already be low at the time of the fire.

Emergency storage for power outages or source contamination is often neglected. We suggest a minimum of one day of average demand as emergency reserve, stored in a separate compartment or a dedicated tank. This can be a lifesaver when the pump station loses power for 12 hours.

6. Step 5: Distribution Network—Pressure, Velocity, and Redundancy

The distribution network is where design assumptions meet real-world hydraulics. The checklist here focuses on three parameters: pressure (minimum and maximum), velocity (to prevent sedimentation and water hammer), and redundancy (so a single pipe break does not shut down the system).

Minimum pressure is usually 20 to 30 psi under peak hour demand, but higher may be needed for fire hydrants. Maximum pressure should not exceed 80 to 100 psi to avoid pipe bursts. Pressure reducing valves may be needed in hilly areas. Velocity should be between 0.3 and 1.5 m/s—too slow and sediment settles, too fast and water hammer becomes a risk.

Looping vs. Dead-End Systems

Looping the network improves reliability and water quality by reducing stagnation. But loops are more expensive and require careful valve placement to isolate breaks. In practice, many systems are a mix: loops in high-density areas and dead-ends in low-density fringes. The checklist should include a valve exercise plan—valves that are never operated become inoperable.

Hydraulic Modeling Before Construction

We strongly recommend building a hydraulic model of the proposed network before breaking ground. Free tools like EPANET are sufficient for most projects. Run scenarios for maximum day, peak hour, fire flow, and a pipe break. If pressures drop below minimum in any scenario, the design needs revision. Do not rely on hand calculations alone—they miss the interaction between multiple demand nodes.

7. Common Mistakes and How to Avoid Them

Even with a checklist, certain errors recur. We list the most frequent ones here so you can catch them early.

Mistake 1: Using Average Daily Demand for Everything

Average daily demand is a useful planning number, but it is dangerous for design. Pipes sized for average flow will be undersized for peak hour. Storage sized for average day will run dry during a fire. Always use the appropriate demand scenario for each component.

Mistake 2: Ignoring Water Age in Storage Tanks

A tank that is too large for the demand will have long water age, leading to disinfection residual decay and bacterial regrowth. We have seen tanks designed for 2 days of storage that actually hold 5 days because the demand grew slower than expected. The solution is to design with baffles or multiple cells that can be taken offline when demand is low.

Mistake 3: Forgetting About Power Supply

A pump station with no backup power is a single point of failure. Even a small generator can keep the system running during a blackout. For critical systems, consider dual power feeds from different substations. This is often cheaper than building a second source.

8. Summary and Next Steps

This five-step checklist—demand, source, treatment, storage, distribution—provides a systematic way to design a reliable water supply system. The key is to treat each step as a decision gate: do not move forward until the current step is verified with data and a clear rationale.

Here are three specific actions you can take this week:

• Pull your current demand data and create a monthly profile for the last three years. Compare it to your design assumptions.
• Review your source yield calculation. Does it use a drought statistic or just average flow? If the latter, redo it with a 20-year low flow.
• Run a hydraulic model of your distribution network for fire flow at the farthest hydrant. If pressure drops below 20 psi, plan a loop or upsizing.

No system is perfect, but a structured checklist reduces the chance of missing a critical assumption. Share this with your team and adapt it to your local context. The goal is not to eliminate all risk—that is impossible—but to make risk visible and manageable.