United Kingdom · guide · 7 October 2026

Reading rainfall monitoring findings on a CAR

Informational only. Not legal advice. Not enforcement strategy.

Quarries, landfills, industrial sites and sewage treatment works often require rainfall gauging, storm-event sampling or telemetry-linked weather records. CAR non-compliance rows may cite missing gauge readings, incomplete monthly returns, or effluent exceedances during storm events. Operators read those lines to map permit tables — not to calibrate instruments from a guide.

Free CAR check  ·  £19.99 Full CARBrief  ·  £49.99 Permit + CAR Review

Where rainfall rows sit on the form

Common breach descriptions

CAR wording patternPlain-English reading
Rain gauge not maintained / unreadableInfrastructure availability finding
Rainfall records incomplete for reporting periodDocumentation breach
Storm event sampling not triggeredProcedure breach — read cited condition
Discharge exceeded during rainfall eventPerformance finding — note averaging in text
Telemetry failure on weather stationContinuous monitoring row

Permit conditions

Match cited conditions using linking findings to permit conditions and improvement conditions on permits.

Standard rules permits may embed rainfall monitoring in schedule tables — read how to read a permit for table literacy.

See linking findings to permit conditions, improvement conditions, and how to read a permit.

Scores and escalation

Read category and points per row — CCS scores and what C1 means on a CAR. Site warning letters may follow repeat monitoring gaps.

See CCS scores, what C1 means, and site warning explained.

Worked example

A treatment site CAR might list:

Row 1 is documentation; Row 2 is performance during rainfall — actions and deadlines may differ.

Common misreadings

CAR row triage checklist

CaptureNotes
Gauge ID / locationPermit schedule alignment
Reporting period citedMatch internal logs
Storm vs daily monitoringDifferent breach types
Category and pointsPer row on tracker
Officer action dateSee car response deadlines

CARBrief mirrors row granularity in sourced readings rather than collapsing monitoring into a single fail summary.

After documentation breaches, follow-up visits may be scheduled — see what happens after a CAR for process literacy.

Read CAR response deadlines and what happens after a CAR.

Batch vs continuous monitoring

Permits may require manual gauge reads while telemetry covers automated alerts — a CAR row about missing monthly totals is not automatically a discharge exceedance row.

When both appear, list separate actions and deadlines on your compliance tracker.

See how to read a CAR and sealed surface drainage findings when rainfall links to containment performance.

Management system overlap

Incomplete rainfall returns may be classified under management system findings rather than surface water sections — search the whole CAR PDF before assuming row location.

Trade effluent and combined events

Sites with co-located effluent treatment may carry trade effluent findings on the same visit — do not merge remedial tasks without reading each cited condition.

Rainfall-triggered sampling may appear beside ammonia or pH limits distinct from groundwater trigger levels.

See trade effluent discharge findings and monitoring data findings.

Reading checklist (extended)

  1. Search PDF for gauge, storm, rainfall and telemetry phrases.
  2. Separate infrastructure failures from exceedance events.
  3. Pull permit monitoring frequency for each outfall.

Leachate and landfill overlap

Landfill and quarry permissions may tie rainfall data to leachate level triggers. A missed gauge read can therefore relate to groundwater protection — cross-read leachate management findings when cited.

Keep raw rainfall logs with CAR row citations for responder teams.

See leachate management findings and groundwater monitoring findings.

Odour and amenity during storms

Heavy rainfall can trigger odour complaints separately from gauge paperwork breaches. Amenity rows may cite different conditions — read odour dust noise findings when neighbours complained after storms.

Emissions monitoring rows may still stand alone — do not collapse weather-related findings into one summary line.

See odour, dust and noise findings and emissions monitoring findings.

Standard rules permits

Standard rules sets embed rainfall or storm monitoring in schedule tables — use standard rules vs bespoke permits literacy when linking rows to permit PDFs.

Improvement conditions may require upgraded telemetry after repeat gauge failures.

See standard rules vs bespoke permits and improvement conditions on permits.

CARBrief reads published CAR wording only; it does not calibrate gauges or design storm sampling programmes for your site.

Keep storm event dates beside officer quotes when you build remedial timelines for directors.

Questions

Where do rainfall monitoring findings appear on a CAR?

Under surface water, groundwater or management system rows when the CAR cites permit monitoring schedules, gauge maintenance or incomplete rainfall records.

Are missed rain gauge readings always high category scores?

Category depends on the printed CAR line — read C1–C4 labels per row.

Will CARBrief calibrate rain gauges?

No. CARBrief reads published CAR wording. Instrument maintenance is for your environmental consultant.

Is rainfall data treated the same as effluent sampling on a CAR?

Often separate rows with different cited conditions — read each independently.

Do trigger level breaches always appear under groundwater sections?

Headings vary by site — search the PDF for rainfall, gauge and storm event phrases.

Order CARBrief See sample

All guides: /guides/.