United Kingdom · guide · 5 October 2026
Reading groundwater monitoring findings on a CAR
Landfill, waste treatment and industrial sites with groundwater permit conditions may receive CAR non-compliance rows about missing borehole samples, exceeded trigger levels, broken monitoring wells, or incomplete monitoring reports. Operators read those lines to prioritise responses and pull permit schedules — not to reinterpret hydrogeology from a blog.
Free CAR check · £19.99 Full CARBrief · £49.99 Permit + CAR Review
Where groundwater rows sit on the form
- Monitoring data — monitoring data findings.
- Leachate management — leachate management findings.
- Containment and bunds — bund and drainage findings.
- Pollution incidents — pollution incident response findings.
Common breach descriptions
| CAR wording pattern | Plain-English reading |
|---|---|
| Monitoring not undertaken at required frequency | Sampling schedule breach |
| Trigger level exceeded | May require notification action — read deadline |
| Monitoring borehole damaged / inaccessible | Infrastructure maintenance finding |
| Quarterly report not submitted | Documentation / management system row |
| Inadequate groundwater risk assessment | May overlap management system findings |
Link to permit conditions
Match cited conditions on the Public Register — linking CAR findings to permit conditions, how to read a permit, improvement conditions on permits.
Scores and categories
Read printed C1–C4 categories per row — what CCS scores mean, what C2 means, what C3 means. Do not merge groundwater and surface water rows mentally.
Response deadlines and follow-up
Note officer actions — CAR response deadlines, what happens after a CAR, what evidence to keep.
Worked example — two rows on one CAR
A landfill CAR might print:
- Row A: “Quarterly groundwater monitoring not undertaken for Q2.” Cited condition on sampling frequency.
- Row B: “Ammonia trigger level exceeded at borehole BH3.” Cited condition on trigger notification.
Literacy: Row A is a schedule breach; Row B may trigger notification and investigation actions with different deadlines — list separately on your tracker; read categories on CCS scores guide.
Common misreadings
- Desktop CAR assumed to mean no groundwater risk. Desktop reviews can still cite missing reports — check assessment type on the form header.
- Single borehole exceedance treated as site-wide failure without reading condition text. The CAR may name specific boreholes only.
- Leachate row merged mentally with groundwater monitoring. Split rows — see leachate management findings.
- Permit improvement programme ignored when repeat misses appear. Cross-read improvement conditions.
CAR row triage checklist
| Field to copy | Why |
|---|---|
| Non-compliance wording verbatim | Evidence trail |
| Cited permit condition | Pull schedule from register |
| Category / points | Per-row scoring |
| Action deadline | See response deadlines guide |
| Borehole ID if named | Scope remedial work |
Why groundwater rows drive urgent responses
Trigger exceedances can require notification to regulators within tight windows printed on the CAR — separate from longer-term remediation programmes in your permit. Operators prioritise by reading the officer action column first, then mapping each line to permit monitoring tables. CARBrief highlights deadlines as printed; it does not advise which consultant to instruct.
Repeat monitoring misses on sites under enforcement scrutiny may appear alongside site warning themes — still read each row’s category independently.
Landfill vs treatment site context
Landfill permissions often embed long-term groundwater regimes with quarterly or monthly sampling — breach rows may reference missed quarters rather than single spill events. Treatment sites may instead tie triggers to bund integrity — cross-read sealed surface and drainage findings when both appear on one CAR. CARBrief extracts each printed line; it does not predict plume behaviour.
Desktop vs site inspection
Some groundwater findings arise from record review on a desktop assessment — note assessment type on the CAR header before prioritising field work. Site inspection rows may include photographs of damaged borehole headworks — cite the CAR page reference on your tracker.
Linking to competence findings
Missed monitoring sometimes appears under competence and training findings when the officer attributes gaps to management systems — still extract the groundwater-specific row if both exist.
Export each row to your compliance tracker with the CAR publication date; follow-up visits may reference earlier breaches by date. Match borehole IDs to your site plan labels before briefing field teams.
Reading checklist
- List each groundwater-related non-compliance with cited condition.
- Separate sampling, reporting and infrastructure rows.
- Pull permit monitoring frequency and trigger tables.
- Record category/points per row on your tracker.
- Flag whether the finding is documentation-only or cites field exceedance.
Questions
Where do groundwater findings appear on a CAR?
Under monitoring data, pollution incident, leachate or containment rows when the CAR cites permit conditions about boreholes, sampling frequency or trigger levels.
Are groundwater rows the same as surface water breaches?
Not always. Permit schedules may treat groundwater and surface water separately. Read each non-compliance line and cited condition on its own.
Will CARBrief interpret hydrogeology reports?
No. CARBrief reads published CAR wording. Technical hydrogeology advice is for your environmental consultant.
Does a missed quarterly sample always score the same category?
No. Read the printed C1–C4 label and points on each CAR row — category depends on the officer’s assessed impact, not the calendar miss alone.
Should trigger level exceedances be merged with leachate findings?
Only in your action tracker after you have read each line. On the CAR they may be separate non-compliances with different cited conditions and deadlines.
All guides: /guides/. Related: gas management landfill findings, monitoring data findings.