Search Pilla

Search pages and workflows, or ask Poppi (AI).

5 ways to automate hazard spotting

Liam Jones

Liam Jones

Founder of Pilla

Date Modified

12 July 2026

AI Summary
  • ChatGPT logo
  • Claude logo
  • Perplexity logo
  • Google AI Mode logo

I'm Liam Jones, founder of Pilla and a qualified management consultant. I've helped hundreds of businesses set up workflows, and in this article I'm going to show you five real examples of how to set up hazard spotting.

I'll start with the simplest version, then show you one addition at a time, so you can pick the options your workplace needs. You can open up each template in our workflow builder playground as a starting point and experiment for yourself.

If you're looking to automate this part of your operation, speak to an expert and we'll show you what it would take to set up.

The workflows at a glance

Article Content

#1 - The basic check-in

Who it's for: Single-site businesses where workers spot hazards and want them on record before they slip their mind.

What it is: A basic hazard check-in is a location-tagged record filed at the moment a worker spots something wrong. Four steps on a phone: type what you saw, tap to drop a pin, pick a risk level (Low, Medium, High), and type what you did about it right now. Each completion is one timestamped record, captured at the spot. The hazard is on the account before the person walks away from it.

In practice: A garden centre team member wheels trolleys back from the car park and sees a paving slab lifting at the edge of the main path. They open the canvas, type "lifted slab on the path to the tills, sticks up about an inch", tap to pin it, pick "Medium", and type "put a cone over it for now". Submit. The duty manager has the hazard, the exact spot, and the temporary fix, all timestamped, before the trolleys are even put away.

Why it works: The moment of spotting is the moment with the most detail, and it is the moment you usually lose. A hazard remembered at the end of the shift loses the specifics: where exactly, how bad, what was already done. Filing it at the spot captures all three while they are fresh. The timestamp proves when it was known. Nothing falls off a mental list.

Steps included:

  • 1 text input (what you saw)
  • 1 location step (GPS pin)
  • 1 single-choice step (risk level: Low, Medium, High)
  • 1 text input (what you did right now)

#2 - With written guidance

Who it's for: Sites with rotating staff who all need to report hazards the same way.

What it is: The basic check-in plus guidance notes woven into the canvas. One panel at the top explains what counts as a hazard. One at the end explains who picks it up. A new starter on their first shift gets the same definition of "hazard" as someone who has worked there for years, without needing to be briefed separately.

In practice: A 24-hour distribution warehouse with three shifts and steady agency staff turnover. A new picker does not know whether a trailing cable is worth logging, so they leave it. The opening guidance panel settles it: if you would warn a colleague, log it. The closing panel says the duty manager picks it up, high-risk items get sorted today, rest go on the list. Night shift and day shift now report the same hazards the same way.

What it adds to the basic check-in:

  1. A "what counts as a hazard" panel at the top, with concrete examples (spills, cables, broken kit, things at head height)
  2. A "who picks it up next" panel at the end, so the reporter knows the hazard is owned and triaged
  3. One consistent reporting standard across everyone who runs it, instead of each person guessing

Why it works: Written guidance sits inline at the moment the worker is about to act, not in an induction they half-remember. It removes the two reasons people skip reporting: not being sure it counts, and not believing anything will happen.

Steps included:

  • 1 guidance note (what counts as a hazard)
  • 1 text input (what you saw)
  • 1 location step (GPS pin)
  • 1 single-choice step (risk level: Low, Medium, High)
  • 1 text input (what you did right now)
  • 1 guidance note (who picks it up next)

#3 - With a signature

Who it's for: Audited sites needing a signed, contemporaneous hazard record on every report.

What it is: The basic check-in plus a reporter signature at the end of every submission. Three independent stamps on a single report: timestamp, location pin, and signature. The reporter signs to confirm the report is honest and accurate.

In practice: A regional construction firm runs several active sites. Every hazard logged by every operative carries a finger-drawn signature. A labourer reports a leaning stack of materials, pins it, picks the risk level, records the action, and signs. The signature is captured on the touchscreen, timestamped, and attached to the same record as the pin. When the safety audit comes round, the auditor pulls a sample of reports, sees a named reporter and signature on each one, and the audit closes quickly.

What it adds to the basic check-in:

  1. A signature step at the end of every report
  2. A third independent stamp (the signature) on the same record as the timestamp and location pin
  3. A defensible record at the level an auditor or insurer expects, with the reporter's confirmation attached

Why it works: The signature closes the loop. Timestamp, location, and description say a hazard was there. The signature adds: and this person stands behind the report. Captured on the same device, at the same moment, the three together are what an auditor expects to see.

Steps included:

  • 1 text input (what you saw)
  • 1 location step (GPS pin)
  • 1 single-choice step (risk level: Low, Medium, High)
  • 1 text input (what you did right now)
  • 1 signature (sign-off)

#4 - With photo evidence

Who it's for: Multi-site businesses wanting photo proof of each hazard so the person fixing it can see exactly what was reported.

What it is: The basic check-in plus a close-up photo of the specific hazard taken at the spot. The worker captures the exact problem with enough context that someone who was not there can see what they saw. The photo lands in the same record as the written note, the risk level, and the location pin.

In practice: A facilities company maintains a dozen office buildings. A caretaker on a morning walk finds a handrail coming away from the wall on a stairwell. A typed note says "loose handrail, third floor". The photo shows the two bolts pulled out and how far the rail flexes. The maintenance lead at head office sees the photo, knows it is a same-day fix, brings the right parts, and sends the right person first time. The before state is on record, so once it is repaired there is proof of what was caught.

What it adds to the basic check-in:

  1. A close-up photo of the specific hazard, captured at the spot
  2. Visual proof of the state the hazard was in when it was found
  3. Enough context for the person fixing it to plan the job before they arrive

Why it works: A written note tells you a hazard exists. A photo tells you what it actually is. The two together let the person fixing it judge urgency and bring the right kit. Captured on the same device, at the same spot, the photo cannot be staged after the fact.

Steps included:

  • 1 text input (what you saw)
  • 1 location step (GPS pin)
  • 1 single-choice step (risk level: Low, Medium, High)
  • 1 text input (what you did right now)
  • 1 photo of the specific hazard

#5 - With Poppi checking the photo

Who it's for: Multi-site groups where photos get taken but nobody reviews them, or head office cannot look at every report.

What it is: A photo-checked report is the basic check-in plus a photo of the specific hazard that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: is the specific workplace hazard clearly visible in the photo and concerning enough to report? If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets addressed before everyone moves on.

In practice: A three-site facilities group closes maintenance requests at 6pm. The caretaker photographs a cracked floor tile as always. Poppi reads the photo: clear defect, concerning, needs fixing. Verdict yes, nothing changes. On a rushed Friday the photo shows a crack but it is too small to report and the image is blurry. Poppi answers no and posts to the team chat ("The photo shows a defect but it is not clear enough to judge the severity"). The caretaker retakes it while still on site.

What it adds to the basic check-in:

  1. A photo of the specific hazard that gets checked the moment it's saved, not just stored
  2. A team chat message with Poppi's reason the moment a photo fails the check
  3. The manager stops being the only person who ever looks at the photos

Why it works: The check happens in the seconds between the photo being taken and the worker leaving. That is the only moment the problem is still cheap to fix. A manager reviewing photos the next day can only note that a photo is poor; Poppi catching it on the spot gets it retaken before the worker leaves.

Steps included:

  • 1 text input (what you saw)
  • 1 location step (GPS pin)
  • 1 single-choice step (risk level: Low, Medium, High)
  • 1 text input (what you did right now)
  • 1 photo of the specific hazard
  • 1 Poppi decision (judges the photo against your question)
  • 1 Poppi action (posts to the team chat if the photo fails the check)

How to pick the right version

You do not need to know our product to choose. Every version here is the basic check-in plus one addition, so pick the additions your workplace actually needs.

Do other people run this, or is it just you?

If you spot all the hazards yourself, the basic report is enough: #1. If others file reports too (new starters, a rotating crew), go to #2. The guidance notes stop people guessing whether something counts as a hazard and whether anything happens if they report it.

Does the report need a name against it?

If knowing a hazard was spotted is enough, skip this. If you want who reported it on the record, #3 adds a signature.

Do you need photo proof?

A ticked record says the work was done; a photo shows it. If you want visual proof of the hazard, #4 adds a close-up photo of the specific hazard.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it is saved, and tell the team chat when something needs attention.

Is the hazard likely to get worse if not seen quickly?

If head office reviews photos on a weekly report, the written record is enough. If a hazard needs same-day attention and photos often slip through, #5 makes sure Poppi catches them before the worker leaves the site.

Conclusion

A hazard report is a location-tagged record filed at the spot, capturing what you saw, how risky it is, and what you did about it. Every version above is the same basic check-in plus one addition: written guidance, a signature, a photo, or an AI check on the photo. Pick the ones your workplace needs and combine them in the playground.

Build your own hazard spotting workflow on Pilla.

===SQLDATA=== PHOTO_INSTRUCTION: a close-up of the specific hazard (e.g., a cracked step, a loose bolt, or exposed wiring) JUDGE_QUESTION: Is the specific workplace hazard clearly visible in the photo and concerning enough to report? ALERT_MESSAGE: NONE ===END===