Blog / OEE
OEE · Guide

OEE Without Software: Paper and Spreadsheets

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

You can track OEE with a paper sheet at the line and a spreadsheet in the office. Record planned time, stops with reasons, total count and good count for each shift, and calculate availability x performance x quality. It works well on one or two machines, and it breaks on short stops, late typing and many lines.

What you actually need

OEE needs only four inputs per shift, plus one number you look up once. A pen can collect all of them.

  • Planned production time: the minutes you meant to run.
  • Stops: start, end and reason for each one above your threshold.
  • Total count: every unit made, good or bad.
  • Good count: units right first time.
  • Ideal cycle time: the best time per unit, set once per product. See how to set it.

Print the downtime log template for the line, or use the OEE tracking template, which has the formulas built in. Hang the sheet where the operator stands, not in the office.

Build the spreadsheet, one row per shift

Never type a percentage by hand. Here is one row, laid out as a column, with inputs in B to F and formulas in G to K:

CellHoldsFormulaExample
BPlanned minutestyped480
CStop minutestyped46
DTotal counttyped9,700
EGood counttyped9,500
FIdeal cycle, secondsfrom product list2
GRun minutes=B2-C2434
HAvailability=G2/B290.4%
IPerformance=D2*F2/60/G274.5%
JQuality=E2/D297.9%
KOEE=H2*I2*J266.0%
Hypothetical shift. Check: 9,500 good x 2 s = 19,000 s, and 19,000 / 28,800 planned seconds = 66.0%.

That last check is worth keeping as its own column. Good count x ideal cycle / planned time must match OEE, and a mismatch means a typing error.

The availability x performance x quality split is the standard one, from Overall Equipment Effectiveness (R. C. Hansen, 2001).

For several shifts or weeks, add up the minutes and counts first, then calculate. Do not average the percentages.

What the sheet shows you, and what it hides

Look at the example again. Availability looks healthy at 90.4%, but performance is only 74.5%.

On a manual log, low performance rarely means the line ran slowly all shift. Often, it is short stops that nobody wrote down.

Good parts at ideal speed316.7 min
Slow running, unlogged short stops110.7 min
Logged stops46 min
Rejects6.7 min
The same hypothetical shift, drawn to scale. Nobody logged the biggest loss. It only appears because the count exposes it.

This is why the count matters more than the stop log. If you only log stops, you will report high availability and miss the biggest loss on the sheet.

To split that 110.7 minutes, stand at the line for an hour with a stopwatch, and tally each short stop. What are micro-stops shows what to look for.

Where manual tracking breaks

None of these show up in week one. They come slowly, and the numbers keep looking fine.

  • Short stops vanish. An operator clearing a jam for 40 seconds is not going to write it down, and should not have to.
  • End-of-shift memory. When stops get written from memory, times get rounded and small ones get dropped. Downtime data accuracy shows how to test this.
  • Reasons drift. Without a fixed list, the same fault gets three names, and the Pareto splits it up.
  • Late typing. If sheets get typed on Friday, you are reading a history report. Nobody can act on Monday's stop by Friday.
  • Broken formulas. One copied-over cell or a fresh copy of the file, and two people report different figures.
  • Product mix. A wrong ideal cycle on a changeover day makes performance jump for no real reason. See OEE with mixed products.
  • Counts from memory. If the good count comes from a pallet tally hours later, quality and performance both get fuzzy.

What it costs in time

Paper looks free until you add up the hours. Use your own numbers in this sum.

3 lines x 3 shifts = 9 sheets a day
9 x 4 min to type and check = 36 min a day
36 min x 240 days = 144 hours a year
Hypothetical plant. Add the operators' logging time on top. This is the office side alone.

How to keep manual tracking honest

  • Tie every shift to a count. Run time alone is not evidence.
  • Type daily. Same day, or the next morning at the latest.
  • Lock the formula cells, and keep one master file with one owner.
  • Review it at the line. Show yesterday's top stop to the crew that logged it, and keep it short.
  • Do a stopwatch hour each week. Compare your tally with what the log says.
  • Act on something. If nothing changes after logging, the log gets thinner. Operator logging covers why.

When to move on

Paper is enough while the sheets are honest and someone reads them. Move on when one of these is true:

  • Performance is low and you cannot explain where the time goes.
  • You are running more than a handful of lines, and typing is always behind.
  • Different people report different numbers for the same shift.
  • You fixed a loss, and you cannot prove the fix worked.

A browser tool is one small step up, and our free OEE tracker needs no install. The bigger step is taking stops and counts from the machine itself, which is the ground a light MES covers, as light MES vs full MES shows.

See it live in Fabrico

The 110 minutes nobody logged are the reason plants move past paper. Fabrico, a light MES for OEE, takes stops, speed and counts live 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. See how Fabrico captures stops.

What people ask next

Can you calculate OEE in a spreadsheet?

Yes. You need planned time, stop minutes, total count, good count and ideal cycle time, then the formulas above. The OEE tracking template has them built in, along with a weekly view.

How accurate is manual OEE tracking?

The counts can be accurate and the stop details less so, because short stops get missed. Performance then absorbs them. Check your log against an hour meter or a count, as downtime data accuracy explains.

How do I record micro-stops on paper?

Do not ask for each one in the log. Run a stopwatch study for an hour on typical shifts, tally them, and scale carefully. How to reduce micro-stops shows what to do with the result.

How many machines can you track by hand?

We know of no fixed limit. It depends on stop frequency and who types the sheets, so watch the warning signs: late typing, mismatched figures and unexplained performance loss.

Who should fill in the OEE sheet?

The operator, at the machine, for stops and reasons, with a supervisor checking the counts. The sheet should take seconds per stop. OEE training for operators shows how to teach it.

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: Shop Floor Data Collection: Methods Compared · OEE for One Machine: A Simple Way to Start · How to Start an OEE Program: The First 30 Days · Shop Floor Reporting: What to Report and When · OEE Formula in Excel: Paste-Ready Formulas

← More OEE Lab guides · OEE tracking template →

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