QR codes for safety reporting
The person most likely to notice a hazard is standing next to it. A blind corner where a forklift comes through too fast. A packing station set at the wrong height. A pallet that keeps splitting when it’s stacked three high.
Some of those observations never reach anyone who can act on them. A long or inaccessible reporting path can be part of the problem.
The problem
Someone spots a problem at 10:40 in the morning. To report it, they need to find the shift lead, who is somewhere else. Or wait for the end-of-shift huddle, four hours away. Or walk to the terminal in the break room, remember a login they use twice a year, and fill in a form built for a desk.
By the time any of that is possible, the urgency is gone. The forklift didn’t hit anyone. People move on.
This is a problem with the reporting path, not with motivation. The company usually has a system for exactly this kind of report. The people who see the problem can’t reach it.
What Amazon does
Amazon built an internal tool called Dragonfly for this. Employees submit safety suggestions in real time, either from their own device or from workstations on site. Submissions go to the employee’s manager and escalate to site leadership when needed.
The interesting part is how people get in. Amazon puts green panels on the floor that read “Have a safety idea?” with a QR code and one line of instruction underneath. Scan, submit, back to work. No hunting for a terminal, no URL to remember.
According to Amazon’s 2025 safety update, more than 200,000 employees used Dragonfly that year. Amazon also reports that its global recordable incident rate improved 43% from 2019 through 2025. These are Amazon’s reported company-wide figures, not evidence that the QR entry point alone caused the change.
Two things are worth taking from that.
The volume shows that the tool reached a large number of employees. It does not isolate which part of Amazon’s safety program drove participation or outcomes.
The loop is the other. Amazon added a feature that lets employees rate how their manager responded to a submission. That detail matters more than the form does. A channel that takes input and produces nothing visible stops being used quickly.
The part most companies get wrong
Companies without Amazon’s budget usually conclude they need to build a Dragonfly. They don’t. They need the last thirty seconds of it.
Almost every company already has somewhere for a safety report to land. A form in ServiceNow. A Jira project. A Freshservice queue. An SAP EHS module nobody logs into. A Microsoft Form somebody in HSE built two years ago and still maintains.
The form exists. What’s missing is a route to it that works while someone is standing in a warehouse aisle wearing gloves.
How a QR code closes the gap
A QR code turns a physical location into an entry point. Someone scans it with the phone camera and opens the reporting form. Whether an app or login is required depends on the destination.
Amazon’s panels route into A to Z, the app their employees already have. If your workforce doesn’t have an app, the code can point straight at a web form instead. The mechanism is the same either way, and it isn’t sophisticated. That’s why it works.
A few things decide whether it actually gets used.
The form has to be short enough for the situation. Ask only for information the safety team needs, such as what the person saw and where. Anonymous reporting may help in some organizations, but it must fit the employer’s investigation, privacy, and follow-up requirements.
The target has to be reachable with the credentials workers actually have. If anonymous access is required, use a public form and a redirect that does not require workspace membership.
The URL behind the code has to be stable. This is where most of these projects quietly die. The form moves, the Jira project gets renamed, HSE switches tools, and two hundred printed stickers now point at a 404. Nobody reprints them. The channel is dead and nobody notices for six months.
The fix is a stable redirect between the code and the form. You update the destination when the form moves while the encoded address stays the same. A Lora shortcut such as /safety has a QR code on the lor.cx host, but it still requires Lora sign-in and workspace membership. Use it for an enrolled workforce; use a public redirect for anonymous reporting.
Where to put the codes
Placement gets treated as an afterthought and then decides how much of this works.
Sensible spots: at eye level in break rooms and changing areas, next to time clocks, on safety noticeboards, at the entrance to a production hall, on the inside of locker doors, on specific machines, positioned so the code is read when the machine is off rather than while it’s running.
Less sensible: anywhere that asks someone to stop and look down at a phone in a lane where forklifts, pallet trucks, or moving equipment operate. A reporting channel that creates a new hazard is a bad trade. If something needs reporting from inside an active area, the person should step out of it first.
The same logic applies to lighting and height. A code at ankle level behind a rack in a badly lit corner will not be scanned, whatever’s printed under it. Print size and contrast matter more than people expect once codes go on painted metal or shrink-wrap.
Label every code with what it does. Amazon’s panels don’t show a bare code, they ask a question: “Have a safety idea?” An unlabeled QR code gets ignored, or gets mistaken for a material tag.
What happens after the scan
The reporting channel is the easy half. The harder half is what you do with what comes in.
Decide before you print anything: who reads the queue, how fast the person who submitted gets a response, and what happens to reports that get rejected. “No” is an acceptable answer. Silence isn’t.
If you can’t staff the triage, don’t open the channel. A safety inbox nobody empties teaches people their input goes nowhere, and they’ll apply that lesson to the next thing you launch.
Measuring adoption
Submission count is the obvious metric and the least useful one. It rises at launch and drifts down afterwards regardless of quality.
Scans by placement can help diagnose visibility, but only when each placement uses a distinct tracked shortcut (Business and Enterprise). A low count does not show that a location is safe; it may reflect placement, awareness, connectivity, or another reporting path.
Also track time to response and define an internal service level. Use your own data to see whether slow follow-up affects participation.
Limits
QR codes don’t replace a safety culture. If people don’t believe they can stop work when something feels wrong, a sticker won’t change that. Amazon pairs Dragonfly with a stated philosophy called Safe to Go, which lets employees speak up, slow down, or stop work if something doesn’t feel right. The tool works because that policy exists.
They also do not replace formal incident reporting. In the US, covered employers must record qualifying work-related injuries and illnesses using OSHA Forms 300, 300A, and 301 or equivalent forms; the exact duties depend on coverage and the case criteria (OSHA recordkeeping guidance). A QR channel can complement that process for hazards, near misses, and suggestions, but the employer must route every report into the required safety workflow.
Effort
Pilot the workflow in one area before printing at scale. Test access, safe placement, ownership, triage, response times, privacy, and the formal reporting handoff with the people responsible for workplace safety.