After an Incident

An incident on site produces an investigation, frequently a regulatory one, and the first thing anybody asks for is the records.

For teams turning after an incident into a repeatable record, task time tracking software provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside HSE construction guidance so the software choice remains grounded in site practice and applicable guidance.

The immediate questions

Who was present, and where.

Who was doing the work, and who engaged them.

Were they inducted, and when.

Were they competent for that work, with evidence.

Was a permit required, was one issued, and was it valid at that moment.

Five questions. A site that can answer all five from its records has a defensible position. One that can answer two is reconstructing.

Preserving what will be needed

Freeze the access records for the period before routine processes touch them.

The permit, in its physical or electronic form.

The induction record and its version — which content that person was briefed on.

The competence evidence as it stood that day, not as it stands after somebody renews a card.

And the site diary entry, photographs and any plant records.

Who investigates

The site, and usually the subcontractor, and possibly a regulator, and eventually an insurer.

Which means the same records are requested several times by parties with different interests.

Assemble the pack once, rather than answering each request separately, because inconsistent responses to the same question are the thing that turns a defensible position into a difficult one.

The question about the chain

Who engaged this person, and who engaged them.

Investigators ask it early because duties attach at each level, and an answer of "one of the groundworks subcontractors, we think" is the answer that extends an investigation.

Which is the practical reason the engaging company belongs as a required field on the register, rather than as a nice-to-have.

Where records usually fail

The person was on site under a temporary access with no expiry.

The induction was six months earlier, on a different phase.

The competence status was checked once and the card had since expired.

The permit was issued and never closed.

And the register showed forty people in an area that held eight.

Each of these is a finding in itself, independent of what caused the incident.

Regulatory reporting

General orientation, not legal advice.

Certain injuries and dangerous occurrences must be reported within prescribed periods, and the thresholds and timescales differ by jurisdiction.

The clock runs from the incident, not from the investigation.

Know which of your foreseeable incidents cross the threshold before one does, and who is responsible for making the report where several companies are involved — because each may assume another has done it.

Afterwards

Tell the workforce what happened and what changed, anonymised and promptly.

Because silence after an incident teaches that reporting achieves nothing, and the near-miss reporting stops with it.

And check whether the same conditions exist elsewhere on the site, which is the question that turns one investigation into a prevention.

Rehearsing it

Take a past incident, or an invented one, and assemble the pack as if it were requested tomorrow.

Time it.

The gaps are the findings, and they are the same gaps that would be found under pressure with a regulator waiting.

An afternoon, once a project, and it locates every weakness in the records before anybody else does.

What the pack should contain

The register for the period, with entries and exits.

The engaging company for each person involved.

Induction records with content versions.

Competence evidence as at the date.

Permits, open and closed, with times.

The diary entry and photographs.

And a short factual chronology, written by somebody who was there, the same day — which is the document everything else supports and the one most often missing.

Supporting the people involved

An incident affects the person it happened to, the person who found them, and frequently the operative who was working alongside.

None of whom may be your employees, and all of whom are on your site.

Offer support regardless of who employs them, which costs little and is noticed by everybody else on site far more than any policy statement.