
A site without storage is a site that stops whenever a tanker is late. Storage is not really about water — it is about not having your programme depend on someone else’s traffic.
Why storage pays
- Lets you take large, cheaper loads instead of frequent small ones
- Removes the dependency on a tanker being present
- Buffers against peak-season delivery delays
On this page
Sizing site storage
Work from daily consumption, then add a buffer. A site using 5,000 gallons a day with a 10,000 gallon tank has two days of cover — enough to absorb a delayed delivery without stopping work.
| Daily use | Sensible storage | Delivery pattern |
|---|---|---|
| 1,000–2,500 gal | 5,000 gal | Every 2–3 days |
| 5,000 gal | 10,000 gal | Daily or alternate |
| 10,000 gal+ | 15,000 gal+ | Daily, sometimes multiple |
Separate storage for separate water
If the site uses both sweet water and TSE, they need separate, clearly labelled storage. Mixing them, or filling a potable tank from a TSE load, is a serious problem rather than an inconvenience.
Label tanks clearly and physically. Relying on people remembering which is which does not survive a shift change.
The economics
Storage converts your water buying from reactive to planned. Planned deliveries are routed efficiently and priced accordingly; urgent ones are not.
On a site running for months, that difference compounds into real money — usually far more than the cost of the tank.

Never fill potable storage from a TSE load
Cross-contamination of drinking water storage is the one site water mistake with genuine health consequences. Separate tanks, clear labels, no exceptions.
Sizing site storage against your delivery schedule
Site storage should be sized from two things: peak daily demand and how quickly a replacement load can arrive. Storage that covers only one day of use leaves no margin for a delivery that slips.
A common working rule is to hold two to three days of peak demand. That absorbs a missed slot, a Friday, or a demand spike on a pour day without stopping work.
Size for peak, not average
Average daily use across a month understates what a busy day needs. A site that averages 2,000 gallons a day may need 4,000 on a pour day, and that is the day storage has to cover.
Siting and setting up the tank
Put the tank where a tanker can reach it without crossing the working area. A tank positioned for convenience of use but awkward for delivery creates a daily obstruction as vehicles run hose across a live site.
Other practical points: a level, prepared base — a full tank is heavy and an uneven base will crack or tilt it; a sealed lid to keep dust and debris out; and shade if the water is for welfare use, because uncovered site tanks get very hot.
Where a site takes both potable and TSE, use separate tanks with clear labels and physically distinct fill points. This is the single most effective way to prevent a wrong-grade fill on a busy morning.
Frequently asked questions
Do construction sites need a water storage tank?
Practically, yes. Storage lets you take larger cheaper loads and stops work depending on a tanker being present.
How big should site water storage be?
Around two days of consumption is a sensible buffer, so a delayed delivery does not stop work.
Can one tank hold both sweet water and TSE?
No. They need separate, clearly labelled storage to avoid contaminating potable supply.
Does storage reduce water costs?
Yes, indirectly. It lets you buy planned bulk loads rather than urgent small ones.
What kind of tank do sites use?
Commonly poly tanks, GRP tanks or IBCs depending on volume and how long the site runs.
How big should a construction site water tank be?
Size it for two to three days of peak daily demand, not average use, so a missed delivery slot does not stop work.
Where should a site water tank be positioned?
On a level prepared base where a tanker can reach it without crossing the working area, with a sealed lid and separate labelled tanks for potable and TSE.
Setting up site water supply?
Tell us your daily volume on WhatsApp and we will propose storage and a delivery schedule.