Blog / Downtime
Downtime · Guide

Machine Downtime QR Scanner: Setup and Limits

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

A machine downtime QR scanner is a code stuck on each machine that opens a stop form on a phone or tablet, with the machine name already filled in. The operator picks a reason and the form saves the time. It is a cheap way to log longer stops, but the code detects nothing, so it misses stops that nobody scans.

What the QR code actually does

A QR code only stores text, usually a web link. It has no sensor and knows nothing about the machine.

All it does is remove typing. The link carries the machine ID, so the operator lands on the right form in a couple of seconds and only has to pick the reason.

So a QR system is a faster version of a paper log. That is useful, and it is also the limit.

Set it up in an afternoon

1
Pick a form tool
Any form that saves a timestamp and sends rows to a sheet will do.
2
List machines and reasons
Use your existing reason list. Keep it short enough to read on a phone.
3
Make one link per machine
Add the machine ID to each link, so that field fills itself.
4
Print and place the codes
One code per machine, at eye height where the operator stands during a stop.
5
Test it at the line
Try it with gloves, in poor light and on the factory Wi-Fi.
6
Review the first week
Compare scanned stops with the output count, and fix what people skip.
A first version for one line. Do not roll out to the plant until the first week has been reviewed.

Google Forms has a pre-fill option that gives you a link, so one form can serve many machines. Microsoft Forms suits plants that already run Microsoft 365, but test prefilling first, and if a field will not fill, make one form per machine.

Point each code at a link on your own domain if you can, and redirect it from there. Then you can change the form later without reprinting a single label.

What goes on the form

  • Machine: filled in by the link, though a person can still change it.
  • Event: "stop started" or "line running again".
  • Reason: a short list, taken from your downtime reason codes.
  • Note: optional, one line.
  • Name or crew: optional. Skip it if it makes people nervous.

Two scans per stop give start and end times, so you can compute the minutes. One scan with "how many minutes?" is faster but brings back guessing, so prefer two if your crews will do it.

Printing and placing the codes

  • Use a laminated or industrial label that survives oil, heat and washdown.
  • Print it large enough to scan from where the operator stands, and choose a high error correction setting.
  • Keep it off guards and doors that move, and away from shiny metal that throws glare.
  • Print the machine name in plain text beside the code, so a damaged label can still be reported.
  • Ask the plant first about phones on the floor. A shared tablet at the station is a common answer where personal phones are not allowed.

Restrict the form to company logins where your tool allows it. A public link on a machine can be used by anyone who walks past or takes a photo of it.

What it catches and what it misses

Example: one 450-minute shift on a packing machine. A part counter shows 38 stops totalling 141 minutes, and QR scans show 11 stops totalling 96 minutes.

Stops, from a machine signal38
Stops, from QR scans11
Minutes, from a machine signal141 min
Minutes, from QR scans96 min
Hypothetical shift. The QR log holds the long stops and misses most of the short ones.

The missing 45 minutes have two sources. There are 27 short stops of about 1 minute that nobody scanned, and another 18 minutes of late scans on the stops that were logged.

Availability from the QR log is (450 - 96) / 450 = 78.7%, and from the signal, counting every stop, it is (450 - 141) / 450 = 68.7%. That is a gap of 10 points.

OEE itself does not move if you calculate it from good count, because the output is what it is. The unlogged minutes just appear as speed loss, with no cause attached.

See downtime data accuracy for how to run this test on your own line.

QR, paper or machine signal?

Paper logQR formMachine signal
Who spots the stop?OperatorOperatorThe signal
Stop timeOften written laterTime of the scanTime of the stop
ReasonWritten by handPicked from a listAdded by a person, or suggested
Short stopsMostly missedMostly missedCaptured
Data entryTyped up laterRows arrive in a sheetRows arrive by themselves
Needs at the machineA clipboardA label and a deviceA signal or sensor
A QR form beats paper on data entry and reasons, but not on finding stops.

The honest use of QR is as a reason layer. On older machines, a current sensor or a stack light signal can provide the stop, and a scan can add the why.

See retrofit sensors for OEE for the options.

When QR logging makes sense

  • You have no stop data today and want a start this month.
  • Your stops are long and few, as on many batch or machining cells.
  • Crews walk between several machines, so a fixed panel at each would sit unused.
  • You want reasons on top of a signal you already have.

It is a weak fit on a fast line with many short stops, since no one should scan a code for a 30-second jam. See micro-stops.

How to keep people scanning

  • Show the data back. Put the top reasons on the board each morning, so scans lead to visible fixes.
  • Set a minimum. Say "scan any stop longer than 5 minutes" so the rule is clear.
  • Allow scans after the fix. Getting the line running comes first, so let people scan just after with a real time field.
  • Check it weekly. Compare scanned minutes with lost output.

The wider method is on how to track downtime. For other no-cost routes, see free downtime tracking software and the downtime log template.

See it live in Fabrico

A scan records what someone reports. Fabrico takes stops, speed and counts live from PLCs or external IoT sensors on older machines, and operators tag the cause at the line. See how Fabrico connects to machines.

What people ask next

Can a QR code track machine downtime by itself?

No. A QR code only opens a form, so a person has to notice the stop and scan. To detect stops without a person, you need a signal from the machine. See what is machine monitoring.

Do I need a special QR scanner for downtime logging?

Usually not. The camera on most phones and tablets opens the link. A rugged handheld with a built-in scanner suits gloved work, as long as it has a browser to open the same form.

How many QR codes do I need per line?

One per machine that can stop on its own, so reasons land on the right machine. A line with several machines needs a clear rule on which one to scan. See line OEE vs machine OEE.

Should operators scan every stop?

Set a minimum length, such as 5 minutes, and be open about it. Shorter stops need a machine signal or a counter. The stop threshold guide explains how to pick the line.

How do I turn QR scan data into a downtime report?

Sum the minutes per machine and reason from the form's sheet, then rank them. The machine downtime report template gives you a layout.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · Operator downtime logging →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES