
Every maintenance system depends on one moment: when a machine stops and an operator has to tell someone. If that moment is quick and easy, every breakdown is recorded, technicians respond faster and the machine history fills itself. If it is slow — find a phone, call maintenance, wait, explain, fill in a register later — operators shout across the floor or walk to the maintenance room, and nothing is recorded. The breakdown register stays half-empty, and every report built on it is wrong.
This guide explains how to design breakdown reporting that takes about thirty seconds, so operators actually use it, and what that simple change makes possible for maintenance management and downtime analysis.
Why reporting fails today
- It takes too long. Calling maintenance, waiting for an answer, explaining the problem, then writing in a register — several minutes while the machine is stopped and the supervisor is asking questions.
- Nobody is accountable. A shout across the floor is heard by whoever is nearest; if they are busy, the request is lost.
- The record is written later. If at all, from memory, without times.
- Nothing visible happens. Operators don't know whether anyone is coming, so they shout again, or go looking.
The thirty-second report
A well-designed report has four steps, each a tap or a scan:
- Scan the machine's QR code with the shop-floor tablet or the operator's phone. The machine is identified; no typing, no choosing from a long list.
- Pick the problem from a short list of symptoms for that type of machine — not causes, which the operator can't know, but what they see: won't start, stopped with alarm, abnormal noise, leak, overheating, hydraulic pressure low, quality problem, other.
- Say whether the machine is stopped or running with a problem. This sets the priority.
- Optionally, add a photo — of the alarm screen, the leak, the broken part. A photo of the controller's alarm message saves a technician a trip.
Then Send. The time is recorded automatically. That is all the operator needs to do.
Designing the symptom list
The symptom list is where most designs go wrong. Long lists, technical terms and lists of causes ("bearing failure", "contactor fault") ask operators to diagnose, which they can't do and won't try. Good lists are:
- Short — eight to ten options, with "other" and a voice or text note for anything unusual.
- Specific to the machine type — a press, an injection moulding machine and a compressor have different symptoms.
- In the operator's language, with icons where helpful.
- About what is seen or heard, not about what is broken.
Review the list after a month. If "other" is chosen often, look at the notes and add the common ones as options.
QR codes on every machine
Print durable QR labels for every machine and utility, with the machine number in large text beside the code, and fix them where operators stand — on the control panel, not on the back of the machine. In oily or hot environments, use laminated or metal labels. The same QR code serves breakdown reporting, the technician's access to machine history, PM checklists and machine documents.
Notification and response
When a report is sent, the maintenance team's phones show it immediately: machine, location, symptom, stopped or running, photo. A technician taps Accept, and the operator's screen shows who is coming. When the technician arrives, they tap Arrived; when the machine runs again, Restored. Three taps give three timestamps:
- Waiting time — from report to arrival.
- Repair time — from arrival to restoration.
- Total downtime — from report to restoration.
If nobody accepts within a set time — say five minutes for a stopped critical machine — the request escalates to the maintenance head. Escalation rules should be few and sensible; too many alerts and everyone ignores them.
Closing the job: what the technician records
The operator reports the symptom; the technician records the diagnosis. On closing the job, the technician picks:
- Cause — from a list by machine type (mechanical, electrical, hydraulic, pneumatic, control, tooling, operator error, material) with a sub-cause.
- Action — repaired, replaced, adjusted, cleaned, reset.
- Spares used — scanned or picked, deducted from stock.
- A one-line note and photos if useful.
The technician's closing record is the one that builds machine history. Keep it quick too — a minute or two — or it will be skipped.
What the data shows after three months
With every breakdown recorded with times and causes, reports that were impossible before appear automatically:
- Breakdown Pareto — which machines lose the most hours, and from which causes.
- Repeat failures — the same machine and cause recurring, the clearest sign of a problem that repair alone won't fix.
- Waiting versus repair time — long waiting times point to staffing or notification problems; long repair times point to skills, spares or documentation.
- Shift patterns — breakdowns clustered on one shift may point to practice or to fewer technicians.
- MTTR and MTBF per machine — see how to calculate MTTR and MTBF.
Linking with production downtime
Where operators already record stops on a shop-floor tablet, a stop with the reason "breakdown" should create the maintenance request automatically, and the restoration time should close the downtime record. One entry, two uses. This avoids the common situation where production's downtime records and maintenance's breakdown records disagree, and each department blames the other's numbers.
Not only breakdowns
The same thirty-second design works for other requests: abnormalities spotted during operator checks (a small leak, a loose guard), safety hazards, utility problems (low air pressure, no cooling water), and requests for help with setups. Each goes to the right team with the same response tracking. Abnormalities reported early, before they become breakdowns, are the most valuable reports of all — and operators make them only when reporting is easy.
Making it stick
- Response must be visible. If operators report and nobody comes, they will go back to shouting. Watch waiting times closely in the first weeks.
- Supervisors must redirect phone calls. When someone calls maintenance directly, the technician asks them to report it on the tablet, or reports it themselves on the spot.
- Show the results. Share the breakdown Pareto in production meetings so operators see that their reports lead to fixes.
- Don't punish reporting. If reporting a breakdown leads to blame, reports will dry up.
Devices
Reporting needs a device within reach of every machine. Options include the shop-floor tablet already used for production booking, a shared tablet for a group of machines, or operators' own phones with a simple app or web page. For machines without nearby devices, a QR code scanned with the supervisor's phone is a workable fallback. Our guide to Android tablets on the shop floor covers device choice and placement.
Priority without bureaucracy
Not every report is equally urgent. A stopped bottleneck machine matters more than a slow leak on a machine with a backup. Rather than asking operators to set priority — which they will always set high — let the system calculate it from the machine's criticality (set once, in the machine register) and whether the machine is stopped. Technicians see their list sorted by this priority, and the maintenance head can override when needed. Simple rules applied consistently are better than elaborate priority matrices that nobody follows.
Photos and videos
A photo of an alarm screen tells the technician the alarm code before they reach the machine, so they can bring the right tools or spare. A ten-second video of an abnormal noise or vibration is often more useful than any description. Encourage operators to attach them, especially for intermittent problems that may not be happening when the technician arrives. On closing, technicians' photos of the repair — wiring, settings, the failed part — become part of the machine's history and help the next technician facing the same problem.
Repeat failures need different treatment
A machine that breaks down for the same cause again and again needs root cause analysis, not faster repair. Set a rule in the software: when the same machine has the same cause recorded a set number of times within a period, it is flagged for review. The maintenance head and production discuss it in the weekly meeting and assign an investigation — using 5 Why analysis or a simple fishbone — with an owner and a date. Fast reporting fills the history; the repeat-failure rule makes sure the history is used.
A worked example
A plastics processor with 30 injection moulding machines and a maintenance team of five recorded breakdowns in a register that showed, on average, about one entry per day. Production supervisors estimated there were many more. Operators called maintenance on a shared phone or walked to the maintenance room.
QR labels were fixed to every machine and the shop-floor tablets, already used for production booking, gained a breakdown button. Stops recorded with the reason "breakdown" created maintenance requests automatically. In the first month, recorded breakdowns rose several times over — not because machines failed more, but because failures were now recorded. Waiting time was the first surprise: on the night shift, technicians took much longer to arrive because one technician covered two buildings. A second technician was moved to nights, and the breakdown Pareto pointed the team to heater band and thermocouple failures on older machines, which became the first preventive maintenance targets.
Measuring adoption
Track a few simple numbers in the first months: breakdowns reported per week (it should rise sharply, then settle), the share of breakdowns reported through the system rather than by phone, average waiting time, and the share of jobs closed with a real cause rather than "other". When the numbers stabilise, reporting has become habit.
Respect the operator's time
Every design decision in breakdown reporting comes back to one question: how long does the operator spend away from production? Operators are usually measured on output. A reporting process that costs them several minutes per breakdown is quietly avoided, however good the reasons for it. One that costs thirty seconds and brings a technician faster is adopted without any instruction. Test the design with a stopwatch on the shop floor before rolling it out.
Getting started
- Fix QR labels to every machine and utility, at the operator's position.
- Write a short symptom list for each machine type, in the operators' language.
- Give technicians the app on their phones, with accept, arrived and restored buttons.
- Set escalation for stopped critical machines.
- Review waiting time and recorded causes weekly for the first two months.
Most factories can have this running on one section within days, and on the whole floor within a few weeks.
The result, within a few months, is a maintenance history that fills itself, technicians who arrive faster, and breakdown data that finally shows where to invest in prevention.
Working with Corposol
Corposol builds custom maintenance and downtime software with QR-based breakdown reporting and technician apps, as part of our manufacturing software work for Indian SMEs. All custom code is transferred to you on final payment.
Frequently asked questions
Why do operators not report breakdowns in the system?
Usually because it takes too long, the device is too far away, or nothing happens after they report. Reporting must take seconds, the device must be at hand, and the operator must see that maintenance has responded.
What should an operator enter when a machine breaks down?
Only what they know: which machine (by scanning its QR code), what the problem looks like (from a short list), whether the machine is stopped or running with a problem, and optionally a photo. The technician records cause and action later.
How are technicians notified?
On their phones, through the maintenance app, immediately when a breakdown is reported, with the machine and problem. If nobody accepts within a set time, the request escalates to the maintenance head.
Does breakdown reporting give downtime data?
Yes. The time reported, the time a technician arrived and the time the machine was restored give waiting time, repair time and total downtime for every breakdown, by machine and cause.
