CDM compliance tracking you do not have to remember to do
CDM compliance rarely fails at the policy level. It fails at the expiry level: a training card that lapsed in March, a RAMS pack written for a scaffold sequence the job stopped following in April, an F10 notification describing a programme nobody recognises by May. None of it is wilful. It is what happens when compliance depends on a person remembering, and the fix is a register that watches the dates so nobody has to.
The prize for fixing it is bigger than avoiding trouble. Prequalification questionnaires, framework applications and principal contractors' supply chain vetting all ask the same underlying question: can this firm show its compliance rather than assert it? A register that is visibly alive, with current cards, current assessments and a notification that matches reality, answers that question before it is asked. Clean records are a sales asset wearing a health and safety badge.
What does CDM 2015 actually require, and what is just habit?
Precision matters here, because a lot of site paperwork is industry custom rather than law, and knowing the difference tells you what your register genuinely has to defend. The duties come from the Construction (Design and Management) Regulations 2015, and HSE's CDM guidance is the plain-English companion to them.
| Item | Where the duty actually sits | How it fails in practice |
|---|---|---|
| Construction phase plan | CDM 2015 regulation 12, required on every project | Written for the tender, never revised when the sequence changes |
| F10 notification | CDM 2015 regulation 6, notifiable projects only | Submitted at the start, never updated as dates and numbers move |
| Skills, knowledge, training and experience | CDM 2015 regulation 8; the plastic card is habit, not law | Cards photographed at induction, expiry dates never watched again |
| Risk assessments and method statements | Risk assessment sits in wider health and safety law; the RAMS format is convention | Written once, the work changes, the pack quietly goes stale |
| Site induction | CDM 2015 regulation 13 | Done properly, recorded on paper that never leaves the cabin |
Two things follow from that table. First, some rituals are defensible custom rather than regulation, and pretending otherwise wastes credibility. CDM asks for appropriate skills, knowledge, training and experience; the card scheme is one way of evidencing that, not the duty itself. Second, and less comfortably: almost every duty in the table is continuous, while almost every record of it is a snapshot. The plan, the notification and the assessments were all true on the day they were written. CDM does not care about the day they were written.
Why does compliance fail at the expiry level?
Because expiry is invisible until something forces a look.
A training card does not announce that it lapsed on Tuesday. A RAMS pack does not flag that the job it describes changed when the client moved the crane position. The F10 does not know the programme slipped eight weeks. Each of these drifts silently, and the person nominally responsible is the same person running the job, pricing the next one and answering forty messages a day. Remembering dates is precisely the work humans are worst at and machines are flawless at.
The failure is then discovered at the worst possible moment: an incident, an inspection, an audit, or a prequalification submission where the evidence requested is the evidence that quietly expired. At that point the record gets reconstructed, and a reconstructed record is worth a fraction of a contemporaneous one, a point the humble site diary makes on every project that ends in an argument.
What does an automated register actually do?
Four boring things, continuously.
It holds the evidence in one place: cards, assessments, inductions, the plan, the notification, each with its date and its owner. It watches expiry: sixty days out it tells the office, thirty days out it tells the operative, and the day after lapse it tells the site manager who is booked in tomorrow. It prompts review when reality changes: if the diary and the site messages show the scaffold sequence changed, the RAMS covering it are flagged for a human to re-check, which works best where site WhatsApp traffic is already being captured as a record. And it keeps the audit trail of all of the above, so the answer to "how do you manage competence?" is a screenshot rather than a paragraph of assurance.
Note what stays human: judging whether a method statement is actually adequate, deciding whether work stops while it is revised, having the conversation with the subcontractor whose cards lapsed. The machine does the watching and the nagging. People do the judging.
What do clean compliance records win you?
Access, mostly. Principal contractors shortlist supply chains on evidence, frameworks score it, and the direction of travel is more of the same: the Building Safety Act's golden thread requirement is the same idea, a live and accurate record rather than a folder of snapshots, applied to higher-risk buildings, and Gateway 3 readiness is what it looks like at full stretch. A small contractor whose CDM records maintain themselves is practising, at modest scale, exactly the discipline the top of the market now demands.
There is a quieter win too. The evening hour spent hunting for card copies before an audit simply stops existing. AI Metric builds these registers for small firms, usually on top of tools they already own, and the honest summary is this: the regulations have not changed, your obligations have not changed, but the remembering can now be delegated to something that never forgets. The firms that delegate it will be the ones whose records are clean on the day it matters, and the day it matters is never announced in advance.