Reporting a near miss shouldn't take twenty minutes

Near-miss reporting is the cheapest safety intervention available to any contractor and the one most reliably ignored. Not because crews do not care. Because the form takes twenty minutes, sits behind four menus, needs signal, and asks questions the person filling it in cannot answer standing in a hole.

So the near miss goes unreported, and the only events that reach the system are the ones serious enough that somebody had to report them. Which means the organisation is learning exclusively from its worst days.

Report from wherever you are, in seconds

In Utility Work X an incident can be raised from any screen in the app. No navigating back to a home page, no hunting through a menu structure designed by someone who has never worn gloves. What happened, where, who was involved, and it is in the operational record immediately.

Photographs and video attach directly from the device. This matters more than it sounds. A photograph taken at the moment of the event shows the actual conditions — the standing water, the collapsed edge, the missing barrier, the vehicle position. A photograph taken the next morning shows a tidied site. Evidence captured in the moment is evidence; evidence reconstructed later is testimony.

The weather at the time, recorded automatically

When an incident is raised, Utility Work X records the weather conditions at that location at that moment alongside it. Nobody has to remember, estimate, or argue about it later.

This is a small piece of automatic data capture that does a disproportionate amount of work. At the individual level it explains the event: the slip that makes no sense in the written report becomes obvious once you know it had been raining for six hours. At the aggregate level it is where the useful patterns are. If a contractor's slips, trips and vehicle incidents cluster in specific conditions, that is an actionable finding — a change to how sites are set up when those conditions are forecast. You cannot find that pattern if the weather was never recorded, and you certainly cannot reconstruct it for two hundred historic incidents.

It also closes a loop with the start-of-work risk profile. The conditions that contributed to an incident on one site feed the briefing the next crew reads before they start.

What counts as a near miss?

A near miss is an unplanned event that did not cause injury, damage or loss but had the clear potential to do so. The scaffold board that fell where nobody was standing. The reversing vehicle that stopped a metre short. The cable strike that turned out to be a disused duct.

Near misses matter because they are the same event as an accident with a different outcome. They happen far more often, they carry no consequence for the person reporting, and they describe the failure without anyone getting hurt. An organisation with a high near-miss reporting rate is not a dangerous one — it is usually the opposite. It is an organisation where people believe reporting is worth the effort.

From reactive to preventative

Once incidents are being captured in volume and with real detail, they stop being individual records and become data. Utility Work X analyses them by type, location, project, scheme, site, contractor, time of day and repeated cause. The output is not a monthly count on a slide. It is a set of specific questions worth asking — why this contractor, why this time of day, why this scheme, why this same cause four times.

Most field tools help you react to incidents. Utility Work X is built to help you understand the causes, and head the next one off.

Does faster reporting weaken the audit trail?

It strengthens it. Every report creates an auditable record of who reported what, when, and from where, timestamped and stored immutably. Speed is achieved by removing friction from the interface, not by removing fields from the record. The difference between a thirty-second report and a twenty-minute one is design — not how much evidence ends up in the system.

An incident reported badly in thirty seconds still beats one reported perfectly never.

Built by people who've done the work on site. Live and in use.