Blog / Downtime
Downtime · Guide

Waiting for Operator Downtime: Log and Fix It

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

Waiting for operator downtime is time a machine could run during planned production but stands idle because no qualified person is there. Log it with the role that was missing, count it as an availability loss, and chart it by hour first, because it often clusters around breaks, handovers and moments when one person has two machines calling.

The logging problem nobody mentions

A missing operator cannot tag their own absence. That single fact explains why this reason is often under-reported, with the minutes landing in "other" or nowhere at all.

Give the job to someone who is there. The team lead tags the stop, or the first person back at the machine picks the reason, with a rule that it happens before restart.

The machine signal helps here. A stop recorded from the machine gives you the start and end, so people only need to add the cause.

Agree when the clock runs, too. A clear rule: it starts when the machine stops or finishes its cycle with no qualified person within reach, and it ends when that person restarts it.

Split it into five reasons

"No operator" on its own suggests a hiring problem. Often the real cause is smaller and cheaper to fix, so use these sub-codes inside your reason code list.

Sub-codeWhat it looks likeFirst fix to try
Break not coveredMachine stops while the crew is on a break the line should run throughStagger breaks, or add relief cover
Absent, not replacedEmpty station all shiftAgreed cover list before the shift
Moved to another linePerson pulled to fight a fire elsewhereTeam lead decides, and it gets logged
Machine interferenceOne person, two machines calling at onceChange the machine count or the attention needed
Waiting for qualified personSetter, inspector or forklift driver not freeCross-train one more person
Each sub-code has a different owner and a different first fix.

Where a missing operator lands in OEE

If the machine was scheduled to run, the wait is an availability loss. Whether a scheduled break counts depends on your rule for that line, and how to count breaks in OEE sets it out.

The common trap is the overrun. A 30-minute break taken out of planned time, with a line restart at 38 minutes, leaves 8 minutes that belong in the log.

If you want to see how well your people's time is used, as distinct from the machine's, overall labor effectiveness looks at the same event from the labor side.

Read it by the hour, not by the day

Example: a line logs 91 minutes of waiting for operator in one early shift. Spread across the shift, the minutes show a shape that a daily total would hide.

42263531218 0607080910111213
Hypothetical shift: 75 of the 91 minutes fall in three hours (first break, second break, last hour).

Three peaks carry 82% of the loss: 75 of 91 minutes. In this example, the 08:00 and 11:00 peaks match the breaks, and the 13:00 peak is the crew leaving the line before handover.

At 600 units an hour, those 91 minutes are 910 units for the shift. The plant does not need to add a whole person to get most of it back, because three small timing fixes cover three peaks.

Timing problem or headcount problem?

The same chart answers the question managers ask first. Take out the peak hours and look at what is left.

  • Tall peaks, low floor. In the example, the other five hours hold 16 minutes, about 3 an hour, so this is a timing problem.
  • High floor in every hour. If each hour loses 10 minutes or more on most days, cover is thin all shift, and a staffing case becomes fair.
  • One role on most entries. If most minutes wait for a setter, the gap is one skill and not the whole crew.

Use several weeks of data for this, because one bad shift with two absences can look like a pattern. Those 10 minutes are only a starting line for your own review, so adjust them to your line.

Machine interference: the hidden version

When one person runs several machines, each machine waits whenever the person is busy with another. Nobody is absent, so this rarely gets logged as an operator problem.

A rough load check takes a minute with a stopwatch and a calculator.

Operator load = (attention min / cycle min) x machines
(3 / 15) x 4 = 80%
Spare capacity for one person: 20%
Hypothetical cell. At 80% load, machines will often call at the same moment, so waits appear long before the load reaches 100%.

Two machines calling together at 80% load is normal, since real cycles drift out of step. If waiting is high, cut the attention time with longer magazines or easier loading, or reduce the number of machines per person.

Check whether the wait sits on a bottleneck machine before you act. A minute lost on a machine with spare capacity may cost no output at all, and bottleneck analysis shows you which is which.

Fixes that usually work first

  • Stagger breaks so one person covers the critical station while others rest. Agree this with the crew and follow local rules on rest time.
  • Handover at the machine. The outgoing and incoming operators meet at the line, using a short shift handover checklist.
  • A cover list made before the shift. The team lead knows who steps in, so absence does not start a search.
  • One more qualified person per key skill. Start with the setter or inspector role that shows up most in your log.
  • A visible call. An andon signal shows that a machine needs a person, which cuts the time before anyone notices.
  • Balance the work. If one station is always overloaded, try the line balancing calculator.

Wrong ways to read this data

  • Reading it as a discipline issue. People left the station for a reason, so ask what pulled them away before you draw a conclusion.
  • Removing the code to look better. The minutes then move to "other", where nobody can act on them.
  • Asking for headcount from a daily total. Show the hourly chart first, because it may point to timing and not to numbers.
  • Mixing it with waiting for material. A crew moved because the line ran out of stock is a material wait, so tag the first cause.

Start with five days of data

Add the five sub-codes, name who tags the stop when the operator is gone, and collect five days of data. Then chart the minutes by hour and by role, and take the tallest bar to the daily production meeting.

See it live in Fabrico

A stop with no one at the machine still needs a start time and a reason. Fabrico records the stop live from the machine, and an operator tags the cause at the line, so the minutes show in OEE per line and shift. See how Fabrico tracks stops.

What people ask next

Is no operator downtime an availability loss?

Yes, if the line was scheduled to run in that time. It stays in planned production time and lowers availability. Use the availability calculator to see the effect on your own numbers.

Should breaks count as downtime?

It depends on the rule you set for the line. Many plants take scheduled breaks out of planned time, then count any overrun as a loss. How to count breaks in OEE explains the options.

How do you log downtime when the operator is not there?

Let the machine record the start and end, then have the team lead or the returning operator pick the reason before restart. On paper, use one line in the downtime log template.

What is machine interference?

It is the waiting that happens when one operator runs several machines and two need attention at the same time. The operator is present and busy, so the wait often goes unlogged. Measure attention time and cycle time to estimate the load.

What if we simply do not have enough people?

Rank your lines and stations by the output each one protects, then cover the most valuable first. OEE in a labor shortage walks through how to choose.

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

Related guides: Units Per Labor Hour: Formula and Use With OEE · First Response to a Line Stop: Operator Guide

← More OEE Lab guides · OEE in a labor shortage →

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