A downtime log your team can start today.

A shift log with stop reasons, start and end times and the department that can fix each stop. It adds a Pareto that ranks reasons by hours, and an OEE tab. Built around the stop lists South African plants actually use.

5 tabs

log, reasons, Pareto, OEE, what a sensor adds

free, no call needed

What's inside

Five tabs, one record

Tab	What it does
Shift log	One row per stop: line, start, end, duration, reason, planned or unplanned, operator
Stop reasons	Your own list, each reason with the department that can win it back
Pareto	Reasons ranked by hours, not by count, for the weekly meeting
OEE	Availability, performance and quality from one shift's numbers, plus the share of paid time that produced good units
What a sensor adds	What a manual log can't capture: interruptions (short stops), exact times, and the difference between an interruption and slow running

Inside the template: Shift log and Pareto tabs

Illustrative

Shift log

Line	Start	End	Min	Reason	Type	Department	Operator
Line 1	06:00	06:25	25	Changeover	Planned	Production	B
Line 1	07:42	08:10	28	Filler jam	Unplanned	Maintenance	B
Line 1	09:30	09:45	15	Waiting for labels	Unplanned	Stores	B
Line 1	11:05	11:47	42	Conveyor motor	Unplanned	Maintenance	C

Pareto, one week, ranked by hours

Breakdowns

11.6 h

Changeovers

7.9 h

Waiting for material

4.2 h

Quality holds

2.1 h

Other

1.3 h

Example rows typed into the template, not a customer's record.

Using it well

Five habits that make a log worth reading

Log as it happens
A stop written up at shift end is a memory, not a record.
Use your own reason list
Ten to thirty reasons your operators recognise beat a hundred they don't.
Split planned from unplanned
Changeovers and cleaning are planned; breakdowns and waiting are not.
Record start and end, not just duration
Times show when losses cluster: start of shift, after breaks, at changeovers.
Rank by hours every week
The most frequent stop is rarely the most expensive one.

Where a manual log stops

The gap in your output is unexplained time

Compare what the line should have made in its run time with what it did make. A manual log can't tell you whether that gap was interruptions nobody wrote down or the line running slower than rated. A count sensor can.

Measure the gap on one of your lines ›