All resources
Guides

Dewatering discharge limits in practice: pH, TSS and turbidity

c.
claused. team
July 20268 min read

Every excavation eventually fills with water, and every full excavation eventually needs to be emptied. What happens in the ten minutes before someone starts the pump is one of the highest-stakes moments in site environmental management. Get it right and nobody ever thinks about it again. Get it wrong and you have put turbid or contaminated water into a creek, which is the kind of event that triggers incident notifications, regulator attention and, in the worst cases, prosecution.

This guide covers why dewatering permits exist, what the common water quality criteria are and where they come from, and the workflow disciplines that separate sites that dewater safely for years from sites that have one very bad afternoon.

Why dewatering permits exist

The core problem with dewatering is that the person holding the pump hose is rarely the person who understands the receiving environment. Water sitting in an excavation or a sediment basin can look acceptable and still be well outside safe limits: fine clays hold turbidity that the eye underestimates, groundwater in some soils is naturally acidic, and disturbed acid sulfate soils or curing concrete can push pH to extremes in either direction. None of that is visible from the top of a trench.

A dewatering permit is the control that closes the gap. It forces three questions to be answered before any water moves: where is the water going, does its quality meet the criteria for that destination, and who has confirmed both? On most projects the permit requirement comes from the CEMP or a water management sub-plan, often backed by conditions in the EPL or planning approval. If you are not sure which instrument governs discharges on your site, our guide to understanding EPA licence conditions is a good place to start.

The common criteria: pH, TSS and turbidity

Three parameters do most of the work on construction sites, because they can be tested quickly in the field and they capture the most common failure modes.

  • pH, commonly 6.5 to 8.5. This range appears on a large share of Australian approvals as the acceptable window for discharge to surface waters. Low pH points to acid sulfate soil influence or groundwater chemistry; high pH almost always means contact with concrete, grout or stabilised material. Both are toxic to aquatic life well before the water looks unusual.
  • Total suspended solids, commonly below 50 mg/L.TSS is the direct measure of sediment load. It normally needs a laboratory result, which is why many sites use it for periodic verification while relying on turbidity for the go/no-go decision at the point of discharge.
  • Turbidity, commonly below 60 NTU. Turbidity is the field-friendly proxy for suspended sediment, readable in seconds with a handheld meter. Some approvals instead frame the limit relative to the receiving water, for example no more than a set increase above upstream background, which requires a background reading as well.

Treat all three figures as common defaults, not law. The limits that bind your site are the ones written into your approval, licence or CEMP, and they vary with the sensitivity of the receiving environment. A discharge to a saltmarsh or a drinking water catchment can carry much tighter criteria, and some approvals add parameters such as oil and grease, conductivity or specific contaminants where site history justifies it. The variation between jurisdictions is real too; see our overview of environmental monitoring requirements by state. Check your documents, then write the actual numbers into the permit form so the person at the pump never has to remember them.

The two-actor workflow

The single most effective structural control in a dewatering procedure is separating the person who tests from the person who approves.

  • The field tester, typically a supervisor, foreman or environmental technician, samples the water, runs the field tests, records the results and photographs the water and the meter readings.
  • The approver, typically the environmental advisor or site environmental manager, reviews the results against the permit criteria, checks the discharge path and receiving environment, and signs the permit before the pump starts.

The point is not bureaucracy, it is judgement under pressure. The person running the pump is usually also the person whose program is blocked by the water. Asking them to test, interpret and approve their own discharge puts schedule pressure and environmental judgement in the same head. A second set of eyes, with authority to say no and no stake in the pour going ahead, is what makes marginal results get treated as failures instead of rounding errors.

On smaller sites the two actors might be a supervisor and a remote environmental advisor approving from a photo of the meter and the water. That still works, provided the approval happens before discharge and is recorded.

Test before discharge, every time

The discipline that fails most often is sequence. Testing after the pump has started is not a control, it is a confession with good record keeping. A workable pre-discharge routine looks like this:

  • Sample representatively. Test the water that will actually be pumped, at pump intake depth, not the clearer surface layer. If the excavation stratifies, the first hour of pumping can look nothing like the sample.
  • Calibrate the meter. A turbidity or pH meter that has not been calibrated on schedule produces numbers that will not survive scrutiny. Log the calibration date on the permit.
  • Record before you approve. Results go on the permit form first, then the approver signs. Photos of the meter display alongside the sample container are cheap insurance.
  • Re-test on long discharges. Water quality changes as the level drops and the pump gets closer to the sediment at the base. Most procedures require periodic re-testing during extended dewatering, and the interval should be on the permit.

Stop on fail, and mean it

A failed test is not a negotiation. If the water is outside criteria, the options are treat, redirect or wait: dose or aerate to correct pH, flocculate and settle to drop turbidity, pump to a sediment basin or tank for treatment, discharge to sewer under a trade waste arrangement where one exists, or simply leave the water until it settles. What is never on the list is discharging anyway because the pour is at 6am.

The stop-on-fail rule also applies mid-discharge. If a re-test or a visual check shows the water deteriorating, the pump stops, and the stoppage gets recorded with the same care as the approval. Sites that discharge out-of-spec water into receiving waters are exposed to pollution offences that carry serious penalties, for corporations and in some cases for individuals personally. Our explainer on POEO Act penalties sets out how steep that exposure can be.

Record keeping that survives an audit

Dewatering records are among the first things a regulator or auditor asks for after any water quality complaint, because they show whether discharge control was systematic or improvised. A complete permit record includes:

  • The permit itself: location, source of water, destination, criteria, and the treatment applied if any.
  • Test results with times, the instrument used and its calibration status, plus photos.
  • Both signatures, tester and approver, with the approval timestamp before the discharge start time. That ordering is exactly what an auditor will check.
  • Discharge details: start and finish, approximate volume or pump rate, and any re-tests during the discharge.
  • Failures and stoppages, including what was done with water that did not pass. A record showing occasional failed tests handled correctly is far more credible than one showing a hundred consecutive passes.

Keep the records linked to the condition they discharge. When the audit comes, the question will not be "do you have dewatering records?" but "show me the evidence against condition X", and a folder of loose PDFs answers the first question, not the second.

Running it without the paper chase

All of this works on a triplicate pad until it rains, the advisor is on another site, and the permit book is in a ute. claused. runs the whole sequence digitally: the field tester raises the permit and logs results and photos from the field app, the approver reviews and signs from wherever they are, the system enforces test-before-approve-before-discharge ordering, and every permit is auto-tagged to the EPL or CEMP condition it evidences, so the audit pack builds itself. You can try the workflow end to end in the live demo workspace, or get early access to set it up for your project.

The short version

Know the criteria on your approval, and expect them to sit near pH 6.5 to 8.5, TSS below 50 mg/L and turbidity below 60 NTU unless the receiving environment demands tighter. Split the roles: one person tests, another approves. Test the water that will actually be pumped, before the pump starts, with a calibrated meter. Stop when a test fails, treat or wait, and record everything, including the failures. The discharge nobody remembers is the goal; the record is how you prove it.

All resources
Last updated July 2026
Try claused.

Every obligation on site, held in one register.

Inspections, corrective actions, permits and incidents, captured in the field and filed as audit evidence. Early access is free while we build it with the first sites on board.

c.

claused. team

Built by people who've tracked conditions on real Australian construction projects.