In most workshops, the person who sees the breakdown is not the person who fixes it. An operator notices a leak under a press, a forklift driver hears a bearing starting to sing, a cleaner walks past a red warning light at 6 a.m. None of the three has a CMMS account, and none of them ever will: they are not users of the maintenance software, they are witnesses.
Every maintenance manager knows how this ends. The fault is passed on by word of mouth, gets distorted along the way, lands in a WhatsApp message, or simply waits until tomorrow. It never enters the system. And what does not enter the system will never be scheduled, never be measured, and never be counted in your figures.
The hidden cost of informal reporting
A fault reported verbally loses three things on the way.
It loses the exact asset. “The pump in building B” covers four different pumps. The technician walks over, searches, comes back.
It loses the time. Nobody knows whether the noise started this morning or last week. From then on, any honest response-time figure is out of reach.
It loses the trace. If the same machine fails three times in two months, nothing shows it: the first two times exist nowhere. You discover the recurring problem on the day it becomes a production stoppage.
The QR code as a public front door
The idea is simple: give every asset its own public reporting link, and turn that link into a printed QR code stuck on the machine.
The code asks for no account, no app, no password. It opens a web page in the phone’s browser, like any other link. The person describes what they saw, leaves their name if they want to, and sends. That is all.
Two details make the difference in daily use.
First, the code identifies the asset. The reporter has nothing to look for and nothing to pick from a list they do not know: the request comes out already attached to the right machine. That is exactly what a verbal report cannot carry.
Second, the form fits on one screen. Reporting has to take under a minute. A long form is an empty form: by the third mandatory field, the operator goes back to the line and will mention the leak at lunch, or never.
What happens on the manager’s side
A channel open to everyone is only worth having if it does not create a second queue to watch.
Public reports therefore land in the Requests module, exactly like an internal request: attached to the asset, timestamped, with the details and the name left by the reporter. The manager sees them in the same list as everything else, accepts and converts them into a work order, or turns them down. There is no second inbox.
That is also what makes the numbers usable: how many reports come in, how many become jobs, how long between the scan and the response. None of those figures exist when reporting happens out loud.
Opening up without exposing yourself
A page reachable without an account raises a fair security question. Three principles are enough to answer it.
The page shows only what is needed. The name of the asset concerned, the name of your organisation, the form. No list of your equipment, no work history, no access whatsoever to the rest of your data. A label that travels never becomes a window into your workshop.
The link can be revoked. Every asset has its own. If a label leaves with a machine you sold, or if a link turns up where it should not, you revoke it and the old label stops working. You generate a new one and reprint.
The page is protected against bots and bursts. A public form with no guardrails eventually collects automated spam. The rate is capped, and automated submissions are filtered out without getting in the way of real reporters.
Where to stick the first labels
There is no need to label the whole site on day one. Start with the assets that meet two conditions: they break down, and they are seen by people outside maintenance. Production machines in open access, doors and loading bays, chillers, and in facilities work, restrooms and utilities.
Put the QR code where the eye lands when the problem is noticed: on the housing, at eye level, not on the back of the cabinet. Add a readable line of text next to the code, something like “Problem with this machine? Scan here”. A bare code with no instruction gets ignored.
In short
QR fault reporting replaces neither your internal requests nor your preventive maintenance plan. It fills one precise gap: the one between the moment a fault is seen and the moment it enters your system. Today that gap is measured in hours, sometimes days, and it appears on no dashboard, because nothing is recorded there at all.
A sticker on the machine, a scan, a one-screen form. That is the shortest path between the first witness and the right work order.
For the next step, read our guide to maintenance request management, or see the full QR fault reporting page.