After Something Happens

The measure of a lone worker programme is what happens on the one occasion it is needed, and what is learned from it.

When after something happens also depends on reliable work records, employee monitoring software can support time, attendance and workload review without being treated as the emergency response itself. Compare any workflow with NIOSH worker-safety resources and keep alarm ownership, escalation and dispatch responsibilities explicit.

The first hour

The person, first and entirely: medical care, safety, someone with them.

Not a debrief. Someone who has been assaulted or injured is not a witness yet.

Contact next of kin according to the rule that was agreed in advance, which avoids a decision at the worst moment.

Preserve the records: alert times, location data, audio if any, call logs. Routine deletion does not pause for an incident.

The days afterwards

Support rather than a return-to-work assumption.

Assault and serious near misses produce lasting effects, including in people who seem fine at the time.

A staged return, and a choice about returning to that client or that site, which should be theirs.

And practical help with any report to police or insurer, which the organisation should carry rather than the individual.

The review

Separate from any question about whether the worker did anything wrong, and started as one.

What was the hazard, and had it been assessed?

Did the alert fire, and how long did each step take?

Did the responder have what they needed — location, access, authority?

Was the escalation tree current?

And could the work have been done differently, or not alone?

The finding nobody wants

Frequently the system worked and the arrangement did not.

The alarm fired, the responder acted, help arrived — and the person should not have been there alone in the first place.

Recording that is the whole value of the review, and it is the finding most easily lost behind a timeline showing good response times.

Reporting obligations

General orientation, not legal advice.

Certain injuries and incidents must be reported to a regulator within stated periods, and the thresholds differ by jurisdiction.

Violence at work is reportable in many places and is under-reported almost everywhere.

Know which of your incidents cross the threshold before one does, because the clock starts at the incident and not at the review.

Telling everyone else

Anonymised, and promptly.

What happened, what changed as a result.

Silence after an incident teaches the workforce that reporting achieves nothing, and the near-miss reports stop with it — which removes the only early warning the system has.

Who conducts the review

Not the line manager of the person involved, for the same reason investigation and decision are separated everywhere else.

Someone who understands the work, because a reviewer who does not will conclude that the worker should have left earlier without understanding why they did not.

With the worker involved, when they are ready, which may be days later.

And with whoever answered the alarm, whose account of what information they had is frequently the most useful part.

The timeline

Reconstruct it minute by minute from the records: alarm raised, answered, calls made, decisions taken, dispatch, arrival.

Against what the assessment said should happen.

The gaps are the findings, and they are usually in the decision steps rather than the technical ones.

Publish the timeline internally, anonymised, because it is the most persuasive training material the organisation will ever have.

Questions the review must ask

Was this situation in the risk assessment?

Had the address or the client been flagged, and did the flag reach the worker?

Was the check-in interval appropriate for what happened?

Did the responder have the information they needed?

Could the work have been done in pairs, at a different time, or not at all?

And had anybody reported something similar before? A near miss at the same address six months earlier is the finding that matters most and is the one most often missed because nobody looked.

Supporting the worker afterwards

Assault and serious incidents produce effects that appear later, including in people who were composed at the time.

Do not require a return to the same client or site, and make that a stated right rather than a favour.

Offer support actively rather than pointing at a helpline, which is the difference between a policy and a response.

And check in again after a month, because the initial offer is frequently declined by somebody who later needs it.

What changes afterwards

Something should.

A flag, a pairing rule, an interval, a route, an arrangement with a client.

And it should be told to everybody, with the reason, because a workforce that sees an incident produce a change reports the next near miss.

An incident that produces a report and no change is the strongest possible argument for not reporting anything.

The records to preserve

Alarm log with every timing.

Location data for the period.

Audio, where any exists.

Call logs and the responder's notes.

The schedule, the risk assessment in force, and any address flag.

Preserved by a hold at the moment of report, because routine deletion runs on a schedule that does not know an incident occurred, and the evidence is frequently gone within days.