Downtime and Scrap Shift Log

This template records downtime events, scrap by reason, rework, and shift output in one place. It is meant for production lines that need a clean shift-level record for Pareto analysis, supervisor review, and follow-up actions. Use it when you want to connect losses to a specific line, shift, and operator handoff.

Usually the shift supervisor, line lead, or designated operator completes it at the end of the shift, with maintenance or quality adding details when needed. The key is to assign one owner so the log is consistent across shifts. If multiple people contribute, use clear field ownership and review before sign-off.

Complete it once per shift, with downtime events and scrap entries captured as they happen or immediately after the event. Waiting until the end of the day usually leads to missing timestamps, vague reason codes, and undercounted losses. If your line changes over frequently, capture each changeover as its own event.

Each downtime event should include a start time, end time, duration, and a reason code, plus notes if the cause is unclear or shared across departments. Keep the reason list controlled so operators do not invent free-text categories that break analysis. If a stop is still open at shift end, note it as open and close it in the next shift handoff.

The scrap section separates scrap units, rework units, and any active quality hold so the team can see whether the issue is isolated or still affecting output. That makes it easier to decide whether to quarantine product, notify quality, or escalate to maintenance. Use conditional logic so quality hold details appear only when the hold is active.

Common mistakes include rounding downtime too early, mixing scrap with rework, leaving reason codes blank, and counting units started instead of good units produced. Another frequent issue is skipping the sign-off fields, which makes later review harder. The form works best when required fields are limited to the data you will actually use.

Yes, and it should be. Most teams customize the production line list, downtime reason codes, scrap reason codes, and escalation fields to match their process and equipment. Keep the core structure intact so shift-to-shift comparisons stay consistent across lines.

Ad hoc notes are hard to compare across shifts because they often miss timestamps, counts, and standardized reasons. A structured log gives you cleaner data for Pareto analysis, handoff review, and maintenance follow-up. It also creates a clearer audit trail for what happened during the shift.

This log can feed maintenance work orders, quality hold workflows, and production reporting dashboards. If your system supports it, map work order numbers and reason codes into downstream tools so the shift record becomes an action item rather than a dead-end note. It also works well with line-level reporting and daily tier meetings.