Legal and Compliance Register
A register is a living list of safety-related obligations that apply to your operations — what they require, who owns them, and where the evidence sits. It is an internal map so nothing important is owned by “everyone”.
Why This Matters
Organisations get surprised by obligations they never listed: licence conditions, customer clauses, internal rules that became mandatory, or standards they publicly committed to follow.
A register makes obligations visible, owned, and reviewable. It supports planning and honest gap management.
Keep it usable. A two-hundred-row register nobody opens is worse than thirty high-impact rows with real owners.
Key Ideas
Plain-language obligation statements beat legal quotations alone.
Evidence must be retrievable, not theoretical.
Status should be honest: gap is allowed if actioned.
Step-by-Step Process
- Identify sources applicable to your activities and sites.
- Translate each into a plain obligation line.
- Assign a single owner.
- Link controls and evidence.
- Set review dates.
- Track gaps with actions.
- Retire obsolete lines with a note.
What to Capture
Worked Scenario: New Activity Line
A site adds a coating process. The register review adds obligations related to ventilation checks, waste handling, and emergency spill response. Owners are named before first production, not after the first customer audit.
Evidence folders are created empty on day one so the team knows what good looks like. Ninety days later, sampling shows two evidence links broken — fixed before external scrutiny.
Common Pitfalls
- Copying another company’s register blindly
- Owners who do not know they own lines
- Evidence links that 404 in real life
- No process when activities change
- Hiding gaps instead of actioning them
Practical Depth: People, Time, and Pressure
Processes fail when designed for ideal conditions: full staffing, no rush, perfect information, and calm weather. Design for the Tuesday night version of the job — short-handed, behind schedule, and dealing with a surprise defect.
Name the human factors openly: fatigue, unfamiliarity, language differences, production incentives, and fear of reporting delays. Controls that ignore those factors are decorative.
Build stop-work authority into the process in plain words. People need to know they will be backed when they pause a job for a real hazard, even if the pause is inconvenient.
Records That Match Reality
Short, accurate records beat long fictional ones. If a form takes longer to complete than the control it describes, people will invent shortcuts or tick boxes blindly.
Every record should answer who, what, when, and what happens next. Orphan notes without owners become archaeological artefacts after the next incident.
Sample records in the field. If the paperwork says a barrier was placed and the barrier is not there, fix both the behaviour and the process friction that encouraged the fiction.
Learning Loops
After misses, near misses, and successful recoveries, run a brief structured conversation: What did we expect? What happened? What factors were present? What will we change by when?
Share lessons across shifts within a week using plain language and photos where helpful. Delayed learning is almost the same as no learning.
Track whether corrective actions stay closed at thirty and ninety days. Reopened actions are normal; silent drift back to the old state is not.
Leadership Behaviours That Make It Real
Leaders teach priorities by what they ask about on walkarounds. Ask about open actions, last drill findings, temporary changes, and whether permits were suspended for the right reasons.
Never celebrate “zero reports” without checking whether reporting channels feel safe. Silence is not the same as safety.
Resource the process. If owners have no time or materials to close actions, the organisation has chosen acceptance of risk — it should do so consciously, not by backlog.
Implementation Notes for Busy Sites
Start with the highest-risk subset of work, not the entire universe of possible forms. A thin process used on the right jobs beats a perfect process used on none.
Pilot on one area or one shift for thirty days. Collect friction points from the people using it. Adjust the form length and the gates before a wider rollout.
Appoint a single process steward who keeps definitions consistent, trains new supervisors, and reports leading indicators to the leadership team each month.
Document the minimum standard on one page: when required, who authorises, what must be recorded, and how close-out is proven. Keep detailed annexes available without forcing everyone through them every time.
When you expand to more areas, carry the lessons of the pilot rather than restarting from a blank design. Consistency across the organisation reduces contractor confusion and shift-handover errors.
Putting This Into Practice on a Real Site
Start where risk and friction are highest, not where paperwork is easiest. Choose one area, one crew, or one job type and run the process properly for thirty days. During the pilot, capture every point of confusion: unclear ownership, missing inputs, forms that take too long, and steps people skip under time pressure. Those friction points are design requirements for the next revision.
Train with stories from your own workplace rather than generic slides alone. Walk the physical locations where controls must appear. Ask new supervisors to explain the process back to you in their own words before they authorise live work. If they cannot explain it simply, the process is not yet ready for unsupervised use.
Build a weekly fifteen-minute review: what was opened, what closed, what blocked progress, and what nearly went wrong. Keep the conversation factual and free of humiliation. The goal is faster learning, not theatre. Escalate chronic blockers to someone who can change resources, scheduling, or design — local owners cannot fix capacity problems with better handwriting.
Define what “good” looks like with three to five leading indicators that match this process. Examples include on-time close-out, percentage of jobs with a completed walk-down where required, reopen rate after near misses, and sample quality scores from leadership walkarounds. Review indicators without turning them into a blame scoreboard. If numbers improve while field reality worsens, your measures are wrong.
After ninety days, decide deliberately: standardise, adjust, or stop. Write the minimum standard on a single page so contractors and new starters can follow it. Keep deeper annexes available without forcing every user through every detail every time. Consistency across shifts matters more than ornamental complexity.
Finally, connect this process to its neighbours. Change control should reopen risk assessments. Permits should reflect real isolations. Emergency plans should match headcount methods. Incident learning should update procedures and briefings. A strong site is a network of simple processes that talk to each other, not a collection of isolated campaigns that fade after the launch poster comes down.
Supervision, Handover, and Fatigue
Many failures occur at boundaries: shift handover, crew change, contractor swap, or the moment a temporary control is left “for the next person.” Write handover expectations into the process. What must be said out loud? What must be shown in the field? What must be signed or logged before responsibility transfers?
Fatigue and unfamiliarity deserve explicit attention. If a control only works when people are fresh and experienced, it will fail during overtime, shutdowns, and peak seasons. Consider additional checks, simpler steps, or staffing rules when those conditions are present. Do not rely on slogans about staying alert as the primary control.
Supervisors need time and skill to verify, not only to sign. If the schedule assumes zero verification time, the organisation has designed verification out of existence. Protect a small amount of time for walks, sampling, and coaching — it is cheaper than investigation after harm.