Free CAR check · £19.99 Full CARBrief
United Kingdom · guide · 11 November 2026
Reading brewery and brewhouse effluent findings on a CAR
Plain-English guide to reading brewhouse effluent, COD and trade discharge findings on Environment Agency CAR forms. Not legal advice.
Why brewery and brewhouse effluent findings appear on CAR forms
Food and drink sites receive CAR comments on trade effluent strength, yeast sludge handling and consent sampling when brewhouse logs miss permit benchmarks.
Environmental leads map findings to water company consents, CIP chemical stores and ABV production records.
CARBrief translates officer wording into plain trackers without running brewhouse operations.
Start with trade effluent discharge findings, bund drainage containment findings and stormwater drainage integrity findings.
Common wording patterns
| Phrase | What to check | Note |
|---|---|---|
| COD/BOD exceedance | Lab | Consent limit |
| Yeast spill pathway | Drain seal | Housekeeping |
| CIP chemical store | Bund | Inventory |
| Flow vs production | Meter | Calibration |
| Sludge consignment | Waste note | Carrier |
Brewhouse-specific rows on your tracker
Craft brewers on industrial estates may share effluent treatment with unrelated tenants — split CAR narratives.
Visitor centres selling pints may trigger public complaints referenced on CAR forms.
Seasonal ale peaks may explain sampler gaps officers still cite as monitoring failures.
Canning lines may add cleaning chemicals absent from brewhouse-only permits.
Malt deliveries may generate dust findings separate from liquid effluent themes.
CO2 recovery units may introduce pressure-vessel maintenance rows beside effluent text.
Tank farms may share bund findings with distillery annexes on the same site.
Fermenter cleaning may produce pH spikes logged inconsistently across shifts.
Third-party toll brewing may blur permit holder duties on shared CAR paperwork.
Trade effluent meters may drift before officers compare production tonnage data.
Spent grain hauliers may leave yard staining cited as secondary housekeeping findings.
Nitrate consent limits may apply when brewers also bottle soft drinks on line.
Worked example
CAR cites missing effluent samples for March, yeast spill to surface water drain during transfer, and overdue CIP bund integrity checks. Tracker rows: sampler roster, drain valve maintenance, bund exam date, and consent breach notification letters.
Common misreadings
- Public sewer consent assumed to waive on-site monitoring cited on CAR.
- Brewery tours assumed out of scope when effluent originates in brewhouse cellars.
- Spent grain recycling assumed unrelated to liquid effluent non-compliance rows.
- Lab certificates from water companies assumed to replace brewer self-monitoring duties.
Triage checklist
- Consent number: CAR header — Mirror on tracker
- Sample slot missed: Named month — Lab reschedule
- Drain route photo: When quoted — Maintenance ticket
- CIP store bund: Separate — Exam PDF
- Corrective date: Footer — Owner initial
Consent and production alignment
Plot ABV output against effluent volume when officers question flow anomalies.
Separate CAR rows for canning hall cleaning even when brewhouse shares consent.
File yeast disposal consignment notes beside spill findings for close-out packs.
Coordinate water company audits with EA revisit dates after formal notices.
Train night brew crews on drain lockout procedures referenced in CAR narratives.
Archive CIP SDS updates whenever chemical suppliers change caustic strengths.
Brewhouse close-out habits
Mirror CAR dates on wall calendars beside brewhouse shift handover boards.
Share sample schedules with production planners so peak brew weeks still hit consent slots.
Tag bund photos with GPS when officers reference specific manhole routes on forms.
Keep water company consent PDFs pinned beside CAR trackers for joint audit visits.
Document visitor tour routes when CAR mentions public footpaths near yeast disposal skips.
Escalate repeat effluent findings to permit variation teams before formal warning letters stack.
Regulator correspondence
Attach production schedules when officers question sample timing against brew length.
Log tanker collection slots for spent yeast cited as housekeeping follow-ups.
Store photos of drain dye tests requested after CAR visits.
File abatement notices from water companies beside EA CAR paperwork.
Track CAPA owners when CAR lists duplicate themes from prior quarters.
Share close-out packs with solicitors when CAR wording references permit variation.
Mirror lab turnaround times on whiteboards when findings cite late results.
Archive staff training attendance for bund response drills mentioned on forms.
Note odour diary entries neighbours submit after CAR disclosures.
Keep meteorological notes when heavy rain follows yard spill findings.
Attach photos of bund valves when CAR narratives reference slow-closing drain seals.
Log CIP temperature charts when officers compare energy data with effluent strength spikes.
Store emails to water companies when consent breaches require statutory notifications.
Mirror CAR dates on brewhouse HACCP folders so production and environmental teams align.
File maintenance invoices for inline pH probes cited as calibration overdue on CAR forms.
Track visitor footpath incidents separately when CAR mentions public access near yeast skips.
Archive storm event logs when yard drains overflow following heavy rain after inspections.
Keep solicitor letters when repeat CAR themes trigger permit variation discussions.
Questions
Are brewery findings the same as maltings?
Read activity narratives — split codes on trackers.
Will CARBrief run kilns?
No. CARBrief reads published CAR wording only.
Do glaze booths always need LEV rows?
When CAR or permits cite them — mirror wording.
Should findings map to consent numbers?
Yes when officers quote them.
Are tile dust findings like foundry dust?
Different process — use ceramic-specific tracker labels.
Map brewery or tile CAR rows to consent logs
CARBrief reads published CAR forms into plain-English trackers.
All guides: /guides/.