Asbestos re-inspections — schedule, scope and software
A management survey gives you a baseline register. Regulation 4 of CAR 2012 then requires the duty-holder to keep that register current as ACM condition changes. Re-inspection is the operational answer to that requirement. This guide covers schedule, scope and the role of software.
Re-inspection interval
CAR 2012 does not set a fixed interval, but HSE guidance and industry practice converge on a baseline of at least every 12 months for most ACMs. Damaged, high-risk or high-disturbance items are inspected more frequently — six-monthly or quarterly.
Trigger-based inspections sit alongside the schedule: any incident, any works in the vicinity of an ACM, or any change in building use should prompt an out-of-cycle inspection.
What a re-inspection covers
A re-inspection is not a fresh survey. It is a condition check against the existing register — same ACMs, same locations, updated condition and updated photo evidence.
- Walk to each ACM listed on the register
- Confirm it is still present (or note any removal)
- Re-assess condition and disturbance likelihood
- Photograph current state
- Update material assessment score where condition has changed
- Update recommended action if priority has shifted
- Log any new ACMs discovered (and trigger a separate sample if needed)
- Sign off the updated register with date and competent person
Where unstructured re-inspections go wrong
When the original register is a static PDF, re-inspection usually means producing a separate re-inspection report alongside it. Over a few cycles you end up with the original survey plus four or five re-inspection reports — and no single document is the current source of truth.
Drift compounds. Contractors get briefed against an out-of-date register. Air tests reference ACM IDs that no longer match. Items removed years ago still sit on the register marked 'manage'.
Where software helps
Structured software treats the register as the live record. Each re-inspection updates the same ACM row rather than producing a parallel document. Condition history is preserved per ACM, so you can see how a particular item has changed over time without trawling PDFs.
AsbestosSurveyPro is built around this model. The original survey produces the structured register. Each re-inspection updates condition and evidence against the same items, and the schedule for the next inspection is held against the property — not in a separate spreadsheet.
Operational checklist for re-inspections
A working pattern that holds up to audit.
- Re-inspection schedule visible per property
- Reminders fire ahead of the due date
- Each ACM has a condition history, not just a current value
- Photo evidence is dated and linked to the inspection
- Competent person signs off each cycle
- Out-of-cycle inspections recorded with trigger reason
Takeaway
Re-inspection works when the register is structured enough to update in place. A schedule without that structure produces drift; structured software keeps the register current, defensible and useful to contractors.