What Your Insurer Wants to See After a Terminal Incident (and How to Have It Ready)

The incident is over. The injured person is being treated, and the yard is back to work. Then the questions start, from your insurer, from the regulator and sometimes from your own board.

What exactly happened? How quickly did help arrive? Had anything like this happened before? And what have you changed since?

Most terminals can answer these questions in the end. The trouble is how. Interviews, radio logs, clips from three different cameras, a spreadsheet of past near-misses and a great deal of memory. It takes days, the story has gaps, and every gap weakens your position. This article looks at what an insurer usually wants to see after an incident, why rebuilding it afterwards is the hard way, and what a terminal managing director can put in place so the evidence already exists.

What does an insurer want to know after an incident?

Four things: a clear timeline, a measured response, the history of warning signs, and evidence that the terminal manages risk every month rather than only after something goes wrong.

The details vary from one insurer and one regulator to the next. The shape of the questions does not.

A clear timeline. Not “around half past two, near block 3”, but a sequence. Where people and machines were, what happened, when the alarm was raised and when the first responder arrived. A timeline with gaps invites the worst assumption.

Response, measured. How long did it take from the SOS to the medic on scene? Was the alert picked up quickly? Was that typical for the terminal, or unusually slow? A single number means little on its own. The same number set beside last month’s means a lot.

A history of warning signs. Had there been near-misses at the same place? Were they recorded, and were they acted on? A record of ignored near-misses reads very differently from a record of fixes.

Evidence of control. What does the terminal do every month to manage risk, and can it show it?

Why does the investigation matter to the insurer at all?

Because the investigation is the evidence. What a terminal finds, records and changes after an incident is what its insurer will rely on if a claim follows.

The Health and Safety Executive (HSE) says so plainly in its investigation workbook, HSG245: “Your investigation findings will also provide essential information for your insurers in the event of a claim.” The same guide warns that “the regulatory authorities will take a firm line if you have ignored previous warnings.”

The HSE’s short guide to employers’ liability insurance adds the other side of the relationship. An insurer cannot refuse to pay a valid claim just because records are missing, but the cover is not a blank cheque either: “If your insurer believes that you have failed to meet your legal responsibilities for the health and safety of your employees and that this has led to the claim, the policy may enable the insurer to sue you to reclaim the cost of the compensation.”

So the conversation with the insurer is not only about the event. It is about whether the terminal can show that it knew its risks, recorded them and acted on them.

Why is rebuilding the story after the event so hard?

Because the evidence is scattered and it decays. Each source holds a piece, nobody holds the sequence, and memory fades fastest in exactly the hours when the investigation should be starting.

On a container yard the pieces are spread wide. The crane operator saw one part. The truck driver saw another. The radio log has times but no positions. Camera clips have positions but cover only part of the yard, and someone has to find the right minutes in each of them.

HSG245 describes what good information gathering looks like. It “is timely” and “is structured, setting out clearly what is known, what is not known and records the investigative process.” That is hard to achieve when the first job is to gather a dozen fragments from a dozen people.

The guidance from the Occupational Safety and Health Administration (OSHA), Recommended Practices for Safety and Health Programs, makes the same point from the planning side. It asks employers to prepare in advance “so that an investigation can begin immediately when an incident occurs.” Preparation helps. A record that already exists helps more.

What changes when the evidence is recorded as the yard runs?

The investigation starts from a shared record instead of competing memories. The timeline, the response time and the history of the place are already there on the afternoon of the incident.

In Mapsted Yard Watch, that record is simply how the yard is run, not something assembled for the insurer afterwards:

• Look back replays a shift or a chosen time window on the terminal map for the truck or machine you pick: where it went, where it stopped and how it moved. The Follow camera stays with that truck, so the minute before the event is visible, not reconstructed.
• The SOS to medic timeline records each step of a medical response, from the alarm to the medic on scene.

Those two answer “what happened?” and “how fast?”. The history and the handling of the data come from three more:

• One alerts inbox holds every alert in one place, so the near-miss from last Tuesday and today’s SOS sit in the same history.
• The near-miss heat map shows where near-misses have clustered over weeks, so the history of warning signs is a picture, not a search through forms.
• The audit trail records who did what, and when, for alert, rule, machine and wristband actions, such as notifying a supervisor, marking an alert reviewed or revoking a wristband.

There is a quieter benefit. When the replay and the timeline are on the table the same afternoon, crews, supervisors and the HSE team look at the same picture. The discussion moves quickly from “what happened?” to “what do we change?”, and it stays about the yard rather than about whose account sounds more convincing.

OSHA’s guidance also warns against stopping at the first easy answer: “a good incident investigation does not stop when it concludes that a worker made an error.” A replay of the minute before the event is often what shows the queue, the blind corner or the short cut that put the worker there.

How does an incident timeline look in practice?

It is a short sequence of recorded steps: the alarm, the acknowledgement, the arrival on scene and then the review. Each step carries its own time, so nobody has to rebuild it later.

Take a common case. A lasher is hurt near the end of a stack row during the afternoon shift. He presses the SOS button on his wristband.

The alert lands in the inbox. The timeline records when it was acknowledged and when the medic reached him. Later that afternoon, the HSE lead opens Look back for the minutes before the alarm and follows the truck that was turning out of the row.

The same afternoon, the heat map shows whether that row end had near-misses in the weeks before. By the end of the day the terminal has what an insurer will ask for first: a sequence, a response time and a picture of the place. Nobody had to collect it.

What does an insurer report add?

It turns single incidents into a trend. The strongest evidence of control is a little boring: a record kept month after month.

Yard Watch builds an insurer report covering the last 30 days, with CSV export, from the yard’s own records. The export can go to your insurer, your broker or your auditors, and a terminal that exports and keeps a copy each month builds its own track record. Because it comes from the same data as the live view, there is no second version of the truth.

OSHA’s recommended practices describe why a trend matters more than a snapshot. “Both lagging and leading indicators should be used.” Lagging indicators count harm that has already happened. Leading indicators, in OSHA’s words, “reflect steps taken to prevent injuries or illnesses before they occur”, and its examples include “Timely completion of corrective actions after a workplace hazard is identified or an incident occurs”.

The HSE makes a similar point about records in its guide to reporting accidents and incidents at work: “This information is a valuable management tool that can be used as an aid to risk assessment, helping to develop solutions to potential risks.”

How should personal data be handled in incident evidence?

Carefully, and in a way you can show. Evidence about people is only useful if it was collected and accessed properly, and a system that shows everything to everyone is a liability of its own.

In Yard Watch, time reports are per crew. On the alert and evacuation screens, roles other than the medical service see a badge ID, role and crew rather than a name. The “look up a person” query in Look back asks for a reason and writes each query to the access log, alongside the audit trail of who did what, and when.

This protects crews, and it protects the evidence. When an incident file reaches an insurer or a regulator, the first question about personal data is often who looked at it and why. A terminal that knows which screens show names, and can produce the access log of “look up a person” queries in Look back, is in a far stronger position than one that cannot.

It also matters for reporting. Crews who trust that the system protects them, rather than watches them, keep wearing their wristbands and keep reporting near-misses. Without that trust the record has holes, and holes are exactly what an insurer notices.

What happens to the record when the network goes down?

The parts that protect people on site carry on, and the rest catches up. A supplier should be able to name exactly which is which.

In Yard Watch, alarms, access rules and the SOS relay keep working on site when the cloud or cellular link is cut. The live map, history and reports pause and catch up when the link returns.

That distinction matters for evidence. Incidents often happen on bad days: a storm, a power cut, a network outage. Ask any vendor for a named list of what still works on site, and plan your procedures around that list rather than around a general promise.

What are the limits of recorded evidence?

Recorded evidence shows what happened and how fast the terminal responded. It does not decide liability, and it does not replace the judgement of the people investigating.

A replay shows positions and movement. It does not show intent, and it does not show what someone could see from a crane cab. Interviews still matter; they simply start from the record instead of from nothing.

Nor is a good record a promise about the price of cover. Insurers weigh many things. What a clear record does is support the conversation: the terminal can show what it knew, what it did and what changed, instead of asking the insurer to take its word for it.

None of this replaces your procedures or the emergency services. The HSE and OSHA guidance cited here applies in full; a record built as the yard runs makes it easier to follow.

How can you test your own terminal’s readiness?

Pick a minor incident from last quarter and ask your team to produce four things within one hour. If that takes a day, the evidence lives in people’s heads, which is exactly where an insurer does not want it.

1. The timeline. What happened, minute by minute, and who and what was nearby.
2. The response. The time from the alarm to the first responder on scene.
3. The warning signs. Every near-miss at the same place in the six months before.
4. The change. What was changed afterwards, and whether the following month shows it worked.

HSG245 asks employers to “keep your own records of adverse events, their causes and the remedial measures taken.” The one-hour test is a quick way to find out whether those records exist in a form anyone can use.

If the answers come back fast and complete, you are already in a good position. If they do not, the gap is rarely effort. It is that the yard was never recording the story in the first place.

Mapsted Yard Watch records the terminal as it runs: a replay with the Follow camera, SOS to medic timelines, one inbox for every alert, a near-miss heat map, an insurer report covering the last 30 days with CSV export, and an audit trail of who did what, and when. It is already used to track 1,000+ assets across multiple sites. Book a private demo to see an incident go from alert to evidence.

Mapsted Yard Watch supports, and does not replace, your safety procedures and emergency services. It does not provide legal or insurance advice.

Frequently asked questions

What does an insurer usually ask for after a workplace incident?

Most insurers want a clear timeline of what happened, how quickly help arrived, whether there were earlier warning signs at the same place, and what the site has changed since. They also look for evidence that risk is managed routinely, such as regular reports and investigations that lead to real changes. The details differ between insurers, but these questions come up in nearly every claim.

Why does an incident investigation matter for insurance?

Because the investigation is the evidence. The HSE’s investigation guide notes that findings provide essential information for insurers if a claim is made. A thorough, timely investigation that records what was known, what was not and what was changed shows that the terminal understood its risks. A late or patchy one leaves gaps that an insurer may read in the worst light.

What is an insurer report in container terminal safety software?

It is a report built from the yard’s own safety records, so the trend is visible before anyone asks for it. In Mapsted Yard Watch the insurer report covers the last 30 days and can be exported as CSV. Its value is consistency: one incident shows little, but the same report exported and kept month after month shows whether risk is being managed.

Will better incident records lower my insurance premium?

Nobody can promise that, and you should be wary of anyone who does. Insurers weigh many factors when they price cover. What a clear, consistent record does is support the conversation with your insurer, because the terminal can show what happened, how it responded and what it changed, instead of asking the insurer to rely on memory and good intentions.