Chapter 06
Regulatory and insurer conversations
How the captured base supports conversations with regulators, insurers, and other external safety stakeholders, including under reservation of rights.
01
The regulator at the gate
When a regulator arrives unannounced, the project's readiness is determined by what is already in the system. A compliance pack with the right structure means the inspection becomes a series of predictable conversations rather than a forensic exercise. The captured base supports the controls record: which controls were in place, when, on which activities. The findings register supports the audit trail: what was raised, how it was routed, when it closed. The closeout evidence supports the credibility of the whole record. A team that has been running the workflows for months has nothing to assemble in the half-hour before the regulator walks the site; they have something to present. The regulator is rarely looking for a perfect site — they are looking for evidence that the project knows what is happening on it and acts on what it sees. A compliance pack that demonstrates that posture changes the tone of the conversation. The regulator who can see the system working is much more likely to leave with advisory observations than enforcement notices.
02
After a regulator statement or notice
When a regulator issues an improvement or prohibition notice, or takes statements following an incident, the captured base supports the response in two ways. First, it lets the project answer the specific questions in the notice with evidence rather than narrative — what was happening on the activity at the time, who was on site, what controls were in place, what was logged in the safety system. Second, it supports the engineering of the corrective action plan, because the regulator wants to see not only that the immediate issue has been addressed but that the system is robust against recurrence. A project that can show its near-miss loop, its sampling discipline, and its closeout record makes a stronger case for the corrective action plan than a project that has to assemble evidence retrospectively. Statements taken from individuals are also strengthened by a record they can point to: a banksman whose account is supported by the captured view of the lift is in a different position to one whose recollection is contested.
03
The insurer survey and reservation of rights
Insurer surveys reward the same discipline. The captured base shows controls in place during high-risk activities. The findings and closeouts show that the safety system is functioning as designed. The retention policy shows that records survive the period the insurer cares about, which is typically longer than the project realises. A project that runs the workflows tends to find that insurance conversations move from defensive to factual, and that pricing tends to reflect the change over time. When an incident has triggered a notification, the insurer may write under reservation of rights while liability is being investigated. In that period, the captured base, the chain of custody, and the closeout record of any prior near-misses in the area become the basis on which the reservation is eventually withdrawn or maintained. The team that has the discipline tends to come out of the reservation period in a stronger position than the team that does not.
04
When something has gone wrong
When a serious incident has occurred, the conversation with regulators, insurers, and the client is hard regardless of preparation. The captured base does not make the conversation easy; it makes it shorter. Preserved records, defensible custody, a clear timeline, and the closeout trail of any prior near-misses in the area let the conversation focus on what happened and what the corrective plan is, rather than on whether the records can be relied on at all. The project that has the discipline tends to come out of the conversation with a clearer set of next steps, fewer follow-up requests, and a smaller exposure to the secondary disputes that often grow around a poorly evidenced incident.
05
Post-incident interview windows and what good looks like
In the days and weeks after a significant incident, the project will conduct interviews — the regulator with witnesses, the insurer with the project team, the client with the senior leadership, and the project itself with the people involved. The post-incident interview window is short and the recollections fade quickly. A captured base that the interviewer and interviewee can sit in front of changes the quality of the interview. The questions become specific, the answers become checkable, and the record of the interview is anchored to something both sides can see. What good looks like is a project where the regulator visit, the insurer survey, and the post-incident interview all start from the same body of evidence; where the chain of custody on that evidence is intact; and where the leadership can speak to the system that produced it without rehearsal. That is what site safety leadership looks like when the workflows have been run.
Practice
01. Build a regulator-readiness pack for your project. Cover controls record, findings register, closeout evidence, preservation policy, and the chain of custody on a sample of records. Aim for something a project director could open in front of an inspector tomorrow.
Look for: A pack with five named sections, each backed by a live link to the system. The pack should not require any new content — if it does, that gap is itself the most useful finding from the exercise.
02. Imagine an insurer survey is scheduled in six weeks. List the three things you would tighten in your safety workflow before the survey, and the evidence you would expect each one to produce.
Look for: Three concrete items. Common candidates: closing aged observations, formalising the sampling rule for high-risk activities, and writing the preservation policy. Each should produce a recorded artefact the insurer can read.
Checkpoint
For a hypothetical regulator visit next week, what would the first ten minutes of the meeting look like, and what would you put on the screen?
Recommended reading