Blog / Downtime
Downtime · Guide

Operator Downtime Logging That Gets Accurate Data

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

Operator downtime logging works when it takes a few seconds, uses a short code list, happens at the line when the stop happens and is checked against a machine counter or hour meter. People stop logging when it is slow, when nothing changes after they log, or when the log is used to blame them.

Why logs miss minutes

Operators know the real reason for every stop. They are also the busiest people on the line.

When logging takes effort, the log gets thin. Short stops are skipped. Long ones are written at the end of the shift, from memory.

The result is a log that looks fine and a line that has lost more time than the log shows. A Pareto built on it points the wrong way. See the downtime Pareto chart.

This guide is about the human side of logging. For the methods themselves, see how to track downtime.

Check your own log first

You can test any log in a day. Compare what was logged with what the machine says.

Overall Equipment Effectiveness (R. C. Hansen, 2001) lists the check: compare reported uptime with hour meters or cycle counts, and reconcile every minute of the schedule.

Example: a shift has 480 scheduled minutes. The hour meter shows the machine ran 390 minutes, so it was stopped for 90. The operator's log lists 55 minutes of stops.

Run time (hour meter)390 min
Stops with a reason55 min
Stops with no reason35 min
One 480-minute shift reconciled with the hour meter. Run time 390 minutes, logged stops 55 minutes, unexplained time 35 minutes.

390 + 55 + 35 = 480 minutes. The log explains 55 of 90 stopped minutes, which is 55 / 90 = 61%.

The 35 minutes with no reason are the target. Until they have a code, that part of the Pareto is a guess.

Seven rules for logging that works

  1. 1Make it quick. One tap or one tick. Aim for a few seconds per stop, not a form.
  2. 2Keep the list short. About six groups, a few causes under each, and no "other". See downtime reason codes.
  3. 3Log at the line, at the stop. A pad, a tablet or a button at the machine. Not a sheet in the office at the end of the shift.
  4. 4Let the machine mark the time. Do not ask people to write start and end times. If they must, the times become round numbers.
  5. 5Ask for the reason only on stops that matter. A stop of a set minimum length gets a code request. Short ones are counted from the machine.
  6. 6Show the result back. Post the top three causes each shift. When operators see a fix, they log more.
  7. 7Never use it to blame. The log is for fixing the line. If a code costs someone a reprimand, they will pick another.
Seven rules for operator downtime logging

The last two rules matter most. A log that gives nothing back becomes a chore. A log that blames becomes a lie.

Paper, tablet or machine signal?

All three work. Choose by the cost of missing data.

MethodGood forWeak at
Paper sheet at the lineStarting this week. See the downtime log template.Short stops, exact times, entering data later
Tablet or screen at the lineFast code picking, easy totalsStill depends on the operator for times
Machine signal plus operator reasonComplete stop count and exact timesNeeds a connection to the machine

The best split is simple. The machine records that it stopped, and when, and the operator says why.

That puts the effort where only a person can help. The ways to collect data are compared in OEE data collection methods.

Worked example: what to ask for

Example: a line stops 24 times in a shift. Seven of the stops are shorter than one minute.

If you ask the operator to log all 24, you ask for 24 entries in a shift. Most will be skipped.

If you set the rule at stops of one minute or longer, the operator logs 17 entries. The seven short ones are still counted from the machine and shown as "short stops", with a count and a total.

That is 17 entries in 480 minutes, one about every 28 minutes. At a few seconds each, logging costs the operator about a minute or two a shift. That is a number you can defend.

The short stops can then be tackled with the methods in micro-stops, even though nobody wrote them down.

Signs that the log is being guessed

  • Almost every duration ends in 0 or 5 minutes.
  • The log is filled in at the end of the shift, in one handwriting and one pen.
  • One code is used for more than a third of all minutes.
  • Logged minutes are far below the stopped minutes from the hour meter.
  • Different crews log very different numbers of stops on the same machine.

None of these proves a problem alone. Together they show where to look. The last one links to why OEE differs between shifts.

How to win operator buy-in

  • Ask the operators to design the code list. They will use their own words.
  • Act on the first top cause fast. One visible fix is worth ten meetings.
  • Tell them what the data does. It buys spare parts, changes schedules and removes the same stop for everyone.
  • Thank people by name when a logged cause is fixed.

Overall Equipment Effectiveness (R. C. Hansen, 2001) makes the same point from the other side: what you measure drives behavior, and positive, immediate and sincere reinforcement keeps gains going.

Common mistakes

  • Launching with 60 codes.
  • Logging by crew leader at the end of the day, not by the operator at the stop.
  • Collecting data and not showing it back.
  • Trusting the log without a check against the machine.
  • Counting a missing log as no downtime.
See it live in Fabrico

Fabrico takes the stop and its time from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and the operator tags the cause at the line. Where cameras are fitted, the video of any stop can be streamed on request next to its machine data. See how Fabrico splits the work between machine and operator.

Book a Fabrico demo

What people ask next

How long should it take an operator to log a stop?

A few seconds. If it takes longer than that, shorten the code list or move the entry closer to the machine. A long form is the usual reason logs get thin.

Should operators log every micro-stop?

No. They are too short and too many, so read them from the machine and count them. Ask the operator for a reason only above a set length. The micro-stops guide covers the rest.

Is paper good enough?

To start, yes. A paper sheet at the line beats no data. Check it against an hour meter or counter, and move to a screen or machine signal when the missing minutes cost more than the tool.

What if operators log everything as "other"?

Remove "other" from the list. Then check the code list: if people cannot find their cause, add it. See downtime reason codes.

How do I check that the log is accurate?

Compare logged stop minutes with stopped minutes from an hour meter or cycle count. Any gap is time with no reason. Close it until every minute is accounted for.

Related guides: Shop Floor Data Collection: Methods Compared · OEE Without Software: Paper and Spreadsheets · Machine Downtime QR Scanner: Setup and Limits

← More OEE Lab guides · Open the OEE Calculator →

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