What belongs in an obligations register, and who owns each line

Ask an organisation for its obligations register and you are usually handed one of two things. A list of regulations copied from a trade body’s website, or nothing at all. The first is worse than the second, because it looks like control.

A register is not a reading list. It answers four questions about every duty the organisation carries. A line that cannot answer all four is not finished.

What applies, precisely

Not “the Health and Safety at Work etc. Act 1974”, but the specific duty that lands on this organisation, on this site, given what it does. A regulation that applies to a process you do not run is noise, and noise is what stops people reading a register.

The sources are also wider than most registers admit. Statute and regulations, yes. Then the standards you have committed to, the conditions attached to your permits, the requirements written into customer contracts, and the warranties in your insurance policy. Insurance conditions in particular tend to sit outside the compliance function altogether. That is a poor place for them. They are the ones that void cover.

Who holds it

A duty with no name against it is a duty nobody performs. The name should be a role, not a person, because people leave. It has to be a role that exists on the organisation chart, and whose holder knows the duty is theirs. This is the question that most often produces a silence in the room. The silence is the finding.

Two failure patterns come up again and again. The first is a duty allocated to somebody with no authority to discharge it: an engineer who owns a duty that needs capital expenditure they cannot approve. The second is a duty allocated to a contractor in practice, but retained by the organisation in law, which covers most of them. You can contract out the work. You cannot contract out the duty.

What evidences it

Here is what separates a real register from a decorative one. What document, record or artefact would show a sceptical outsider that this duty has been discharged? Not “we do this”. The certificate, the log, the signed record, the calibration certificate, the training record, the inspection report.

Write down where it lives, too. A register that says an inspection certificate exists, without saying where, is a promise to go looking during the week before an audit.

How often

Some duties are continuous. Some are periodic. Some are triggered by an event: a modification, an incident, a change of occupier, a new substance on site. Periodic duties need the frequency and the last date. Triggered duties need the trigger written down, because those are the ones that lapse without anybody noticing. Nobody forgets the annual inspection. Everybody forgets the reassessment a process change was supposed to prompt.

What it costs to build, and what it finds

A register of this kind takes longer to build than people expect. Most of the time goes on establishing what is true, not on writing anything down. It is still the cheapest part of a compliance programme, and it decides whether the rest of the money is well spent. You cannot prioritise remedial work against a list of duties you have not established.

In our experience it nearly always turns up two or three duties nobody had allocated. Not through carelessness. Those duties arrived with a change: a new machine, a new substance, a new building, a new customer requirement. The change was managed as a project, not as an addition to what the organisation is obliged to do. That gap between “we changed something” and “our duties changed” is where most compliance failures start.