4 ways to automate near-miss reports

#1 - The basic check-in

Who it's for: Single-site businesses just starting to track near-misses, with no formal reporting form yet.

What it is: A near-miss report is a short record of something that almost went wrong but did not, logged so the pattern can be spotted before it turns into a real incident. This version is four steps on a phone: type what happened, tap the time, drop a location pin, and rate how close it came on a scale of 1 to 5. Each completion is one stamped record. Whoever saw the near-miss fires the canvas there and then, and the running list of completions becomes the log.

In practice: Take a single-site garden centre. A team member is moving stacked pallets in the yard when one slides off the forklift forks and lands where a customer had been standing seconds earlier. No one is hurt. Instead of mentioning it at the next team huddle and forgetting it, they open the canvas, type "pallet slipped off the forks in the yard, near the trolley bay", tap the time, drop a pin on the yard, and rate it a 4. Submitted. The duty manager sees it that afternoon, not three weeks later when it happens again with someone standing there.

Why it works: The whole value of a near-miss is that it is free information. Nothing went wrong this time, so the only cost is the 30 seconds it takes to log it. A stamped, located, rated record means the manager can count near-misses by place and by severity. Three slips on the same corner stop being three forgotten stories and start being a pattern that gets fixed.

Steps included:

• 1 text input (what happened)
• 1 date/time input (when it happened)
• 1 location step (GPS capture)
• 1 rating scale (how close it came, 1 to 5)

When to upgrade:

1. Add written guidance (#2) once more than one person reports, so everyone agrees on what counts as a near-miss and logs them the same way.
2. Add photo evidence (#3) once you want to see the area or the kit that was involved, not just read a description of it.
3. Add a signature (#4) once an auditor or an insurer could ask for a signed record of who reported what.

#2 - With written guidance

Who it's for: Sites with rotating or shift-based staff who all need to report the same way, even on their first week.

What it is: The basic report plus two guidance panels woven into the canvas. The first panel explains what counts as a near-miss, with plain examples: a slip that did not end in a fall, a burn that did not quite touch the skin, a near collision in the yard. The second panel explains what happens after a report is logged, including the point that no one gets in trouble for logging one. A new starter on their first shift reports the same way a five-year veteran does, without anyone briefing them in person.

In practice: Take a busy distribution warehouse running three shifts a day. Staff rotate, agency cover comes and goes, and most people have never been told what a near-miss actually is. One picker sees a colleague step backwards off a kerb in the loading bay and catch themselves on a racking upright. Is that worth logging? The "what counts" panel answers it on the spot: yes, a slip that did not end in a fall is exactly the thing. The "what happens after" panel reassures them their colleague will not be disciplined. The report gets logged instead of shrugged off, and the duty manager sees the loading-bay kerb come up three times in a fortnight.

What it adds to the previous template:

1. A "what counts as a near-miss" panel at the top, with concrete examples so people stop guessing.
2. A "what happens after you log it" panel that explains the duty manager reads each one and acts on patterns.
3. A clear no-blame message, which is what gets the quiet near-misses reported instead of buried.

Why it works: The two biggest reasons a near-miss never gets logged are "I did not think that counted" and "I did not want to drop my mate in it". Written guidance sits inline at the moment of reporting and answers both. The picker reads the examples right before they type, and reads the no-blame line right before they submit. It is not a poster in the break room they walked past once. It is on the screen at the moment of the task.

Steps included:

• 1 guidance panel (what counts as a near-miss)
• 1 text input (what happened)
• 1 date/time input (when it happened)
• 1 location step (GPS capture)
• 1 rating scale (how close it came, 1 to 5)
• 1 guidance panel (what happens after you log it)

When to upgrade: Move to Near-miss Report #3 once a written description is not enough on its own. Once you want to see the trip hazard, the damaged guard, or the badly stacked load with your own eyes, a typed line starts to look thin.

#3 - With photo evidence

Who it's for: Businesses across more than one site that want photo evidence of the area or the kit that was involved.

What it is: The guided report plus a photo step, taken at the same moment as the location pin. The reporter takes a quick shot of where it happened, or of any equipment that played a part: the frayed cable, the wet floor with no sign out, the pallet stacked too high. The photo lands in the same record as the time, the pin, and the closeness rating. A manager reviewing reports across several sites can see the actual condition, not just read about it.

In practice: Take a three-site manufacturing business with a shared health and safety lead. On the night shift at one plant, a machinist notices a machine guard hanging loose after a near-miss where a sleeve nearly caught. They log the report, rate it a 5, and take a photo of the loose guard. The next morning the safety lead opens the report from another site entirely, sees the photo, and recognises the same guard model is fitted on two other lines. One typed report would have been a line in a list. The photo turns it into an action across all three sites that same day.

What it adds to the previous template:

1. A photo step after the rating, capturing the area or the kit involved.
2. Visual proof of the actual condition, which a typed description alone cannot give.
3. Something a manager at another site can act on without travelling to see it in person.

Why it works: A description is one person's account. A photo is the thing itself. When a near-miss gets rated a 5 but the typed note is two vague lines, the photo is what tells the reviewer whether it really was that close. Captured at the moment, on the same device, in the same record, it cannot be staged or reconstructed later. It is the difference between "someone said a guard was loose" and "here is the loose guard".

Steps included:

• 1 guidance panel (what counts as a near-miss)
• 1 text input (what happened)
• 1 date/time input (when it happened)
• 1 location step (GPS capture)
• 1 rating scale (how close it came, 1 to 5)
• 1 guidance panel (what happens after you log it)
• 1 photo step (the area or the kit involved)

When to upgrade: Move to Near-miss Report #4 once an auditor or an insurer could ask who reported a near-miss and want a signed record, not just a name attached by the app.

#4 - With photo and signature

Who it's for: Audited sites that need a signed near-miss trail an inspector or insurer would accept.

What it is: The photo-evidenced report plus a reporter signature at the end. Five independent stamps on a single record: a typed account, a timestamp, a location pin, a closeness rating, a photo, and the reporter's own confirmation. The reporter signs on the touchscreen to confirm the report is accurate. An auditor or a loss adjuster would accept this as a contemporaneous record at the level expected from a paper incident book, captured in well under a minute on a phone.

In practice: Take a food-production site that gets audited twice a year. Every near-miss report logged on the floor ends with a finger-drawn signature confirming the account is accurate. When the audit lands, the safety manager pulls 40 near-misses at random and shows the auditor a signed, time-stamped, photographed record for every one, with a closeness rating and a pin. The auditor can see the site is not just collecting reports but standing behind each one. What used to be a scramble through a paper book turns into a 20-minute review on screen.

What it adds to the previous template:

1. A signature step at the end of every report.
2. A reporter confirmation on the same record as the account, the timestamp, the pin, the rating, and the photo.
3. A signed near-miss trail at the level an auditor or an insurer expects to see.

Why it works: A near-miss report has to be honest to be useful, and a signature is what puts the reporter's name to the account. The other stamps say what happened, when, where, how close, and what it looked like. The signature adds: and the person who saw it confirms this is accurate. Captured on the same device, at the same moment, in the same record, the set together is what auditors and insurers expect from a serious reporting culture.

Steps included:

• 1 guidance panel (what counts as a near-miss)
• 1 text input (what happened)
• 1 date/time input (when it happened)
• 1 location step (GPS capture)
• 1 rating scale (how close it came, 1 to 5)
• 1 guidance panel (what happens after you log it)
• 1 photo step (the area or the kit involved)
• 1 signature step (reporter sign-off)

When to upgrade: The next variations layer Poppi on top. A Poppi briefing that surfaces the open near-misses from the last week before a shift starts. A Poppi gate that flags any report rated 4 or 5 for a closer look. A Poppi action that posts a high-severity near-miss straight to the duty manager's channel. Coming in the next post update.

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. You only need to answer three questions about how your team runs.

Is it just you running this, or do other people report too?

If it is just you, the basic report (#1) is enough. You already know what counts as a near-miss and what to do with the log, so you do not need the canvas to coach you.

If anyone else reports (a colleague, a new starter, a rotating shift, agency cover), go to #2 onwards. The guidance panels are what stop people guessing about what counts, and the no-blame message is what gets the quiet near-misses reported instead of buried. You write the guidance once; everyone reads it inline.

Do you need a photo as proof, or is the typed record enough?

If the report stays inside the business and the manager will go and look at the spot themselves, the typed-and-rated record is enough. Go to #1 or #2.

If the manager reviews reports from more than one site, or wants to see the actual condition, a typed line is rarely enough. Go to #3. The photo at the moment of the report shows the trip hazard or the loose guard the way a description cannot.

Do you need someone to sign off at the end?

If the report is internal and no auditor will ever look at it, the record is enough. Stick at #3.

If your site is audited or insured and you need to stand behind each report, the signature is the lock. Go to #4. The signature puts the reporter's confirmation on the same record as the account, the timestamp, the pin, the rating, and the photo.

Related workflows

• 4 ways to automate hazard spot reports
• 4 ways to automate lone worker check-ins
• 4 ways to automate maintenance fault reports
• 4 ways to automate damage reports

Conclusion

A near-miss report is a short, stamped record of something that almost went wrong, logged so the pattern gets spotted before it becomes a real incident. The version an audited site runs turns a scramble through a paper book into a 20-minute review, with a signed, rated, photographed record behind every report.

Pick the version that matches how your team runs today, not the most sophisticated one you can imagine running someday. Open each template in the playground above and log a real near-miss with it this week.