On a busy site, it's tempting to deal with a near miss in the moment and move on. But the events that didn't quite cause harm are often the clearest warning of the ones that eventually will. A simple, consistent reporting habit gives small teams a much better picture of what's actually happening.

What is a near miss?

A near miss is an unplanned event that could have resulted in injury, ill health or damage — but didn't. A dropped tool that lands in an empty area, a slip that doesn't end in a fall, a load that swings further than expected. No one was hurt, but the conditions for harm were there.

Capturing those events alongside actual incidents gives you a much fuller view of risk on site than only logging what caused injury.

What an incident report usually captures

A useful incident or near-miss record typically includes:

  • Date, time and exact location on site
  • Who was involved and who witnessed it
  • A factual description of what happened
  • Any injuries, damage or environmental impact
  • Immediate actions taken
  • Photo attachments showing the area, equipment or damage
  • Contributing factors (conditions, equipment, sequence of work)
  • Follow-up actions and who owns them

Why factual, timely records matter

Memory fades quickly on site. Details that feel obvious on the day are harder to reconstruct a week later, and much harder a month later. Recording events on the day they happen — with names, times and a plain description of what occurred — keeps the record useful for follow-up, insurance queries and internal reviews.

Stick to facts rather than blame. A clear timeline is far more useful than an opinion on who was at fault.

Keep records in one place

For small teams especially, the hardest part isn't writing a report — it's finding it again six months later. Paper notebooks get lost. Photos sit on someone's phone. WhatsApp threads scroll out of view. A single, searchable record per site means you can pull up what happened, when, and what was done about it.

How Graftly helps

Graftly lets site teams log incidents and near misses from their phone while details are fresh, attach photos, and keep an ongoing incident log per site. Records are stored alongside the rest of your site documentation — RAMS, toolbox talks, visitor logs and sign-offs — so small teams have one place to check what happened, what was recorded and what still needs follow-up.

You can see what Graftly can do on the homepage, read common questions in the FAQ, or get in touch with us if you'd like to talk it through.