United Kingdom · guide · 14 October 2026

Reading monitoring equipment calibration findings on a CAR

Informational only. Not legal advice. Not enforcement strategy.

Emissions, noise and flow monitoring CARs often cite expired calibration certificates, missing asset labels and sealed analyser faults. Operators read those rows to schedule metrology work — informational only.

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

Why calibration rows appear on CARs

Emissions monitoring, ambient air kits, noise meters and flow gauges often appear on CARs when calibration certificates expired, labels were missing or instruments failed spot checks.

Environmental teams read those rows to prioritise metrology spend before the next officer revisit.

Cross-read emissions monitoring findings, noise monitoring findings, and monitoring data findings.

Common calibration finding patterns

Officer themeTypical CAR languageInternal action
Calibration certificate expiredProvide valid cert within 28 daysContractor booking
Instrument not labelled with due dateUpdate asset tagAsset register
Broken seal on analyserRepair and recertifyService ticket
Reference gas cylinders out of dateReplace cylindersLab supply order
Monitoring schedule missed while instrument faultyDual breach rowData completeness guide

Desktop vs site inspection visits

Desktop assessments may cite missing calibration paperwork while site inspections note physical seal damage. Visit type changes evidential weight — read desktop assessment guide.

CAR response deadlines guide helps when calibration fixes must be reported before revisit.

See desktop assessment vs site inspection and CAR response deadlines.

Worked example

CAR row: “Stack analyser calibration certificate expired 14/03/2026; no monitoring shall rely on this instrument until recalibrated and certificate submitted.” Notes:

Common misreadings

Reading checklist

  1. List instruments named in calibration rows.
  2. Collect certificate expiry dates as printed.
  3. Cross-read monitoring data completeness on same visit.
  4. Map rows to permit condition numbers.
  5. Plan contractor visit before response deadline.

Stack limits and groundwater crossover

Stack emission limits findings may follow calibration failures when data gaps prevent limit comparison.

Groundwater monitoring findings use different kits — read groundwater guide when borehole instruments cited.

See stack emission limits findings and groundwater monitoring findings.

Competence and management system rows

Competence training findings may cite staff awareness of monitoring procedures without fixing calibration certificates — list separate actions.

Management system CAR findings may reference ISO schedules — metrology evidence still needs its own folder.

See competence and training findings and management system findings.

Permit variation context

When calibration failures persist, operators may consider permit variation — read when to vary your permit guide before assuming CAR closure equals compliance.

Standard rules vs bespoke permits guide helps locate monitoring schedules that calibration rows reference.

See when to vary your permit and standard rules vs bespoke permits.

Rainfall and ambient monitoring crossover

Rainfall monitoring findings use separate tipping bucket gauges — do not assume stack analyser calibration fixes rainfall gaps.

Odour dust noise findings may cite monitoring pauses while instruments are offline — read odour dust noise guide for amenity context.

Find permit online literacy helps pull monitoring schedules when CAR rows cite condition numbers without repeating limits.

What evidence to keep guide lists document types operators should retain after calibration remedials.

See rainfall monitoring findings and find permit online.

Category score literacy

What does C1 mean and what does C4 mean guides interpret scored rows when calibration breaches carry compliance categories.

Can scores increase fees guide explains charging implications separate from fixing instruments.

Pollution incident response findings may reference monitoring gaps discovered after calibration failures — read response guide for drill evidence.

Linking CAR findings to permit conditions guide helps attach calibration remedials to the correct schedule clause.

See what does C1 mean and linking CAR findings to permit conditions.

How to read a CAR refresher

How to read a CAR guide frames where calibration rows sit within section headings and action lists on multi-page forms.

Car assessment status codes guide helps when calibration visits carry overall site status labels beyond individual rows.

See how to read a CAR and CAR assessment status codes.

Contractor coordination

Book metrology contractors using expiry dates copied verbatim from CAR rows — paraphrasing dates causes mismatches with officer records.

Pause production monitoring when CAR text prohibits reliance on uncertified instruments until certificates are resubmitted.

Track calibration fixes on the same spreadsheet as monitoring data gaps so revisit officers see closed loops.

Desktop assessment follow-ups may accept certificates without repeat site visit — read officer action text carefully.

Questions

Do calibration findings always reference MCERTS or equivalent schemes?

Officer text varies — some rows cite scheme names while others simply state calibration overdue. Quote printed wording.

Is calibration the same as monitoring data completeness on a CAR?

No. Data completeness rows concern missing readings; calibration rows concern instrument accuracy. Read both guides when visits cite monitoring failures.

Will CARBrief recalibrate instruments?

No. CARBrief reads published CAR forms. Metrology remains your contractor's task.

Can stack emission and noise monitoring share calibration rows?

Sometimes one row covers multiple instruments — separate follow-up actions per permit schedule.

Does a C2 score always mean calibration failure?

Read what does C2 mean alongside officer narrative — scores complement free text.

Order CARBrief See sample

All guides: /guides/.