Water & Compliance 7 min read Published 16 June 2026

Effluent monitoring and DWS compliance in South Africa

By Frank Guo · Technology & Product Leadership, addanode

TL;DR — If you discharge effluent under a DWS water-use licence, compliance comes down to three things: measuring the right parameters, proving you measured them continuously, and reporting in the expected format. Manual grab-samples leave gaps a breach can hide in. Continuous online monitoring of pH, COD, conductivity, turbidity, flow and temperature at the discharge point — logged to a platform with edge buffering and breach alerts — turns compliance from a monthly scramble into a dashboard and an automatic report, and lets you fix an excursion before it becomes a reportable, finable incident.

Who this is for

Environmental and plant managers at South African factories, mines, abattoirs, food & beverage plants and treatment works that hold a Department of Water and Sanitation (DWS) water-use licence and have to report on the quality of what they discharge.

Why grab-samples aren't enough anymore

The traditional approach — a technician takes a sample, sends it to a lab, files the result monthly — has two problems. It's a snapshot, so a breach between samples is invisible (until the regulator's own sample catches it), and it's reactive, so by the time a bad result comes back, the non-compliant water is long gone downstream. Continuous monitoring closes both gaps: you see the discharge all the time, and you can act the moment it drifts.

The compliance shift: the question is no longer just "what was the reading?" but "can you prove what it was, continuously, and show you acted when it moved?" Continuous logging answers all three.

The question is no longer only what the reading was A grab sample is a snapshot and a slow one: a breach between samples is invisible until the regulator's own sample finds it, and a bad result arrives long after the water has gone downstream. The compliance question has three parts now — what the reading was, whether you can prove it, and whether you can show you acted — and only a continuous log answers all three. A monthly grab sample A continuous record “What was the reading?” The reading on the day the technician came Every reading, including the ones nobody asked for “Can you prove what it was?” For that sample, and for nothing between samples For the whole period, with timestamps “Can you show you acted when it moved?” Not from a monthly file — by then the water is downstream The drift, the alert, and what was done about it A breach between samples Invisible, until the regulator's own sample catches it An event with a time on it What the process is Reactive: the result arrives after the fact Continuous: the drift is acted on while it is still a drift
The question is no longer only what the reading was What it was, whether you can prove it, and whether you acted — three parts, one log. “What was the reading?” Grab sample The reading on the day the technician came Continuous record Every reading, including the ones nobody asked for “Can you prove what it was?” Grab sample For that sample, and for nothing between samples Continuous record For the whole period, with timestamps “Can you show you acted when it moved?” Grab sample Not from a monthly file — by then the water is downstream Continuous record The drift, the alert, and what was done about it A breach between samples Grab sample Invisible, until the regulator's own sample catches it Continuous record An event with a time on it What the process is Grab sample Reactive: the result arrives after the fact Continuous record Continuous: the drift is acted on while it is still a drift
The three questions above, asked of both regimes. Only the third one is new, and it is the one a monthly file cannot answer at all — by the time a bad result comes back, the water it describes is downstream.

What to measure

Your water-use licence is the definitive list, but effluent monitoring at the discharge point typically covers:

  • pH — the most common and fastest-moving compliance parameter
  • COD (chemical oxygen demand) — organic load, critical for food, beverage and abattoir effluent
  • Conductivity / TDS — dissolved salts
  • Turbidity / suspended solids
  • Flow — volume discharged, often a licence condition in its own right
  • Temperature — and, depending on process, dissolved oxygen, ammonia or specific ions

How to put it in place

The sequence we follow on a DWS compliance project:

  • 1. Read the licence. Extract the exact parameters, limits and reporting frequency for your discharge point — don't monitor more or less than required.
  • 2. Instrument the discharge. Install online sensors for the licensed parameters at the final discharge point.
  • 3. Log continuously. Stream readings to a platform that time-stamps and stores them, with edge buffering so load shedding doesn't create gaps in your record.
  • 4. Alert on breach. Threshold alerts to WhatsApp or email, so an out-of-limit reading triggers action before it becomes an incident.
  • 5. Automate the report. Generate the periodic compliance report straight from the logged data, in the format DWS expects.

Why load-shedding resilience matters for compliance

A gap in your monitoring record is a problem, not a neutral absence — it's exactly when a regulator asks "what was happening here?" If your monitoring goes dark every time the grid does, your compliance record is full of holes. Edge buffering — logging locally and syncing when power returns — keeps the record continuous through outages, which is why we treat it as a compliance requirement, not a nice-to-have, on South African sites.

This is the backbone of our water management solution and a core reason water utilities and industrial dischargers work with us. It runs on the addaNet platform, so effluent compliance sits alongside flow, energy and the rest of your operation.

One more distinction: where does your effluent go?

This guide covers discharge to the environment — a river, wetland or land — under a DWS water-use licence. If your effluent instead goes to the municipal sewer, you're under the local authority's bylaw and a trade-effluent permit, billed on volume and COD load, with a different (and separately monitored) set of limits — see trade-effluent monitoring. And if you're on the regulator's side of this data rather than the discharger's, see regulatory & catchment oversight.

The General Authorisation limits — general vs special

For discharge to a water resource under the 2013 General Authorisation (GN 665, Table 2.1), the limits that a continuous record is measured against are published. The special limits apply to listed sensitive resources; the notice states the values are subject to review as classification and resource quality objectives progress, so confirm the current condition on your licence or authorisation.

ParameterGeneral limitSpecial limit
Faecal coliforms (per 100 mL)1,0000
Chemical oxygen demand (mg/L)7530
pH5.5 – 9.55.5 – 7.5
Ammonia as N (mg/L)62
Nitrate/nitrite as N (mg/L)151.5
Free chlorine (mg/L)0.250
Suspended solids (mg/L)2510
Electrical conductivity+70 mS/m above intake, max 150+50 mS/m above background, max 100
Ortho-phosphate as P (mg/L)101 (median), 2.5 (max)
Soap, oil or grease (mg/L)2.50
Dissolved iron / manganese (mg/L)0.3 / 0.10.3 / 0.1
Dissolved zinc / copper (mg/L)0.1 / 0.010.04 / 0.002

Source: GN 665, Government Gazette 36820, 6 September 2013, Table 2.1 (selected parameters; the notice also lists arsenic, cadmium, chromium VI, cyanide, lead, mercury, selenium, fluoride and boron).

Frequently asked questions

What parameters does DWS require us to monitor?

It's defined by your specific water-use licence and discharge type, but effluent compliance commonly covers pH, COD, conductivity, turbidity, flow and temperature, sometimes with additional process-specific parameters. Always work from the parameters and limits stated in your own licence.

Can continuous monitoring replace lab grab-samples entirely?

It replaces the blind spots between samples and gives you real-time control, but most licences still require periodic accredited-lab verification. The practical model is continuous online monitoring for control and reporting, with lab samples for calibration and verification.

How does automated reporting actually work?

Because every reading is time-stamped and stored, the platform compiles the periodic compliance report directly from the data — values, exceedances and actions — in the format you submit, instead of someone rebuilding it from spreadsheets each month.

What happens if a parameter breaches a limit?

A threshold alert goes to the responsible person immediately via WhatsApp or email, so you can intervene — adjust dosing, divert flow, stop a process — before the excursion becomes a reportable incident, and the event and your response are logged.

Will the monitoring keep working during load shedding?

Yes, when it's designed for it. Edge devices buffer readings locally and sync when power and connectivity return, so your compliance record stays continuous through outages instead of showing gaps.

Turn DWS compliance into a dashboard.

Send us your water-use licence conditions. We'll scope the sensors and the automated reporting to match exactly what the regulator asks of you.