What this is
What is a downtime log?
What is a downtime log?
A downtime log is a running record of every stop on a line during a shift, capturing when it started and ended, how long it lasted, and a reason code for why it happened. It exists so downtime can be totalled and ranked by cause rather than just reported as a single lost-time figure.
What counts as a stop that needs logging?
Any interruption to the planned run, regardless of duration. The template is explicit that stops under five minutes are the ones most often skipped, and on most lines they add up to more lost time across a shift than the breakdowns that get all the attention.
What is SAE JA1011 and why does a downtime log sit against it?
SAE JA1011 sets out the criteria a maintenance process has to meet before it can be called reliability centred maintenance rather than a periodic review. It doesn't specify a log format, but RCM analysis runs on real failure data, and this log is where that data, reason codes attached to actual stops, gets captured in the first place.
Scope
When is a downtime log required?
This log is one step in the Production Control programme. Using it to capture the changeover itself, the line-clearance check, or the shift's output totals produces a register you can't report on later.
Use this template when
- Any stop happens on the line, of any duration, during the shift being logged
- You need reason-code-level detail feeding Rate Review, the Breakdown Record and Reliability
- The operator is logging in real time, not reconstructing stops at the end of shift
- A stop needs linking back to a Work Order already raised for it
- You are building the shift's availability figure and reason-code breakdown for the daily report
Do not use it for
- Changeover Record, which times and records a changeover from last good piece to first good piece, with what was done in between, rather than logging it as a single downtime stop.
- Line Clearance Record, which confirms a line is clear before the next product starts, not why the line stopped.
- Production Order Record, which records the execution of a production order, quantities, materials, yield, not the interruptions to it.
- Breakdown Record, which takes over once a stop is confirmed as an equipment failure needing a maintenance response rather than a quick reset.
- Anything outside KnowOps, which belongs in the workspace that owns that process
Compliance mapping
Which SAE JA1011 requirements does this satisfy?
SAE JA1011 doesn't specify a downtime log format. It specifies what an RCM process must be able to show, and a downtime log is the evidence an RCM review draws on when it asks whether failure modes and their consequences have actually been identified from real data rather than assumed.
| Clause | Requirement | Where it lands |
|---|---|---|
| SAE JA1011 cl.5 | Functions and performance standards must be identified before a failure can be classified against them | Header |
| SAE JA1011 cl.5 | Functional failures must be defined against those performance standards | Header |
| SAE JA1011 cl.5 | Failure modes must be identified, not just the fact that a failure occurred | Stops |
| SAE JA1011 cl.5 | Failure effects must be evaluated for each identified mode | Stops |
| SAE JA1011 cl.5 | Recurring failures must be distinguished from one-off failures | Stops |
| SAE JA1011 cl.5 | Default and proactive actions must be tracked back to the failure that triggered them | Stops |
| SAE JA1011 cl.5 | The process must be auditable against real failure data, not reconstructed after the fact | Shift position |
What it does not cover
- Stops under five minutes left unlogged, which means the reason-code data this log exists to produce excludes what is usually the largest category of loss.
- Reason Code defaulted to Equipment failure without Equipment or Description checked, which cannot support a failure-mode analysis that SAE JA1011 requires to be based on real data.
- Repeat Of An Earlier Stop marked No for a stop that has recurred for weeks, which hides the recurring failure mode an RCM review is specifically meant to surface.
- Temporary Fix Applied marked Yes with Follow Up Raised left blank, which leaves a failure mode patched rather than resolved, with no record it will be revisited.
- Largest Reason By Minutes and Most Frequent Reason answered without checking the individual Stops entries, which turns the shift-level rollup into a guess rather than a calculation.
Global
Downtime Log requirements by country
SAE JA1011 is a US-originated engineering-society standard, not a law anywhere, but what counts as proper RCM against it varies by what else a site has to answer to.
SAE JA1011 (Society of Automotive Engineers), plus customer-specific RCM mandates
OEM contracts increasingly cite SAE JA1011 by name as the bar for calling a maintenance programme RCM rather than a periodic review
a downtime log full of catch-all reason codes and unlogged short stops won't support a claim of running RCM against this standard, whatever the maintenance team calls it internally.
ISO 55001 asset management, alongside SAE JA1011 as the RCM method
ISO 55001-certified sites are asked to show the data behind maintenance decisions, and SAE JA1011 is the most commonly cited criteria set for what that RCM data has to include
this log is that data; gaps in it are gaps in the asset management system's evidence trail, not just a shift-report inconvenience.
SAE JA1011 as a voluntary reliability benchmark
sites with no contractual obligation to SAE JA1011 still use it informally to judge whether a downtime log is granular enough to plan maintenance from, rather than just report on
even without an audit behind it, a log full of Equipment failure with no equipment named fails this test on its own terms.
How to complete it
How to complete a downtime log, step by step
The fields are simple to fill in during a shift. Whether the log is defensible comes down to four judgement calls that don't show up as a missing tick.
The template's own info field says these are usually the biggest loss on the line. A defensible log has multiple sub-five-minute entries per shift on any line with jam-prone equipment; a log with none is a log nobody is actually keeping.
Equipment failure covers everything from a snapped belt to a jammed sensor. Without Equipment named and a real Description, the reason code is a category with no diagnostic value behind it.
Marking a stop as not a repeat because nobody remembers the last one isn't the same as checking. A defensible answer means someone actually looked at recent entries for the same Equipment and Reason Code before answering.
A temporary fix without a follow-up is a scheduled repeat of the same stop. The two fields only mean anything read together, and a log full of Yes-then-blank pairs is a maintenance backlog nobody is tracking.
What auditors find
Most common downtime log findings
The same handful of gaps account for most of the downtime logs that don't hold up when someone actually checks them against what happened on the line.
| Finding | Clause | What fixes it |
|---|---|---|
| Stops under five minutes routinely absent from the log on lines known to jam frequently | SAE JA1011 cl.5 | Set a visible shift expectation for entries, informed by Planned Run Time Minutes and typical stop frequency, so a suspiciously low Stops Recorded count gets queried before the shift closes. |
| Reason Code defaults to Equipment failure without Equipment or Description completed | SAE JA1011 cl.5 | Make Equipment required whenever Reason Code is Equipment failure, and require at least a short Description for every stop over the sub-five-minute range. |
| Repeat Of An Earlier Stop answered No without checking prior entries | SAE JA1011 cl.5 | Surface the last three stops for the same Equipment on the entry screen so the operator is answering against the record, not against memory. |
| Temporary Fix Applied is Yes with Follow Up Raised left blank | SAE JA1011 cl.5 | Make Follow Up Raised required whenever Temporary Fix Applied is Yes, and feed open follow-ups into the Breakdown Record backlog. |
| Largest Reason By Minutes and Most Frequent Reason don't match what the individual Stops entries add up to | SAE JA1011 cl.5 | Calculate both fields from the Stops entries recorded that shift rather than leaving them as a free judgement call at sign-off. |
| Planned stops logged as Unplanned because nobody checked the production schedule | SAE JA1011 cl.5 | Pull the Planned Or Unplanned default from the schedule for known planned stops, changeovers, cleaning windows, so it only needs correcting rather than deciding from scratch. |
Case in point
Case in point: the jam nobody logged
A filling line was averaging 78% availability and nobody could say why. The logged stops, all Equipment failure over ten minutes, only accounted for about half the gap. Operators weren't logging the recurring thirty-second label-feed jam because clearing it felt faster than opening the form.
Two weeks of deliberately logging every stop, including the jam, showed it happening eleven to fourteen times a shift for a combined loss bigger than every other reason code on the line. A guide-rail adjustment, a two-hour maintenance job, closed most of the gap the monthly averages had never been able to explain.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
3 sections
- Reference
- OPS-010
- Archetype
- Log
- Record ID
- DT-2026-000
- Scoring
- Downtime by reason
- Direction
- High is bad
- Singleton
- Yes
- Basis
- SAE JA1011
- Links
- Feeds Rate Review, Breakdown Record, Reliability
- Tags
- Production, Downtime, OEE
- Sections
- 3
- Fields
- 39
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
13 fieldsLog ID*
Auto sequence. Format DT-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date*
Shift*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Line*
Planned Run Time Minutes*
Total Downtime Minutes*
The Stops Under Five Minutes
Nobody records a two minute jam, and on most lines the two minute jams add up to more lost time than every breakdown combined. Record them or keep guessing.
Stops
Repeats12 fieldsStart Time*
End Time*
Duration Minutes*
Reason Code*
Equipment failure, changeover, material shortage, quality, labour, cleaning, or planned.
- Equipment failurenot scored
- Changeovernot scored
- Material shortagenot scored
- Qualitynot scored
- Labournot scored
- Cleaningnot scored
- Plannednot scored
Equipment
Description
Planned Or Unplanned*
- Plannednot scored
- Unplannednot scored
Repeat Of An Earlier Stop*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Escalated
Work Order ID
Links to MNT-002 Work Order ID
Temporary Fix Applied
A temporary fix that is never followed up is a breakdown that comes back.
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Follow Up Raised
Shift position
14 fieldsStops Recorded*
Stops Under Five Minutes*
Availability Percent*
Largest Reason By Minutes*
- Equipment failurenot scored
- Changeovernot scored
- Material shortagenot scored
- Qualitynot scored
- Labournot scored
- Cleaningnot scored
- Plannednot scored
Most Frequent Reason*
- Equipment failurenot scored
- Changeovernot scored
- Material shortagenot scored
- Qualitynot scored
- Labournot scored
- Cleaningnot scored
- Plannednot scored
Feeds Rate Review*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Line Lead*
Signature*
Production Manager*
Second Signature*
OPS-010 · record IDs look like DT-2026-000 · Feeds Rate Review, Breakdown Record, Reliability
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Runs the Production Control programme this log belongs to, keeps the reason-code list consistent across Reason Code, Largest Reason By Minutes and Most Frequent Reason, and feeds the daily report.
Picks up Work Order ID, Temporary Fix Applied and Follow Up Raised, so a stop logged here turns into a tracked maintenance job instead of a repeat entry next shift.
Takes stops reason-coded Quality and connects them to whatever quality hold or nonconformance caused the line to stop, so the two records agree on cause.
Watches for reason codes with no Equipment or Description, flags recurring stops marked as not a repeat, and holds any correction to this log for your approval first.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Downtime Log definitions and key terms
- RCM (Reliability Centred Maintenance)
- A structured method for deciding what maintenance a piece of equipment actually needs, built from its functions, the ways it can fail, and the consequences of each failure, as opposed to a fixed maintenance calendar.
- Reason code
- A fixed category assigned to a stop, equipment failure, changeover, material shortage, quality, labour, cleaning, or planned, that lets downtime be totalled and ranked by cause rather than just by duration.
- Availability
- The proportion of planned run time the line was actually able to run, calculated as planned time minus downtime over planned time. One of the three factors in OEE.
- Functional failure
- A failure defined against what the equipment is actually required to do, rather than a generic breakdown, the starting point SAE JA1011 requires before failure modes can be identified.
- Downtime breakdown
- Ranking reason codes by total minutes lost to find the small number of causes responsible for most of the downtime, only possible if every stop, including short ones, is actually logged.
FAQ
Frequently asked questions about downtime log
Does a two-minute jam really need its own log entry?+
Yes, that's the specific gap this template's info field calls out. On most lines the sub-five-minute stops add up to more lost time across a shift than the breakdowns that get all the attention, but only if they are actually recorded.
What's the difference between this log and the Breakdown Record?+
This log captures every stop as it happens, with a reason code. The Breakdown Record takes over once a stop is confirmed as an equipment failure serious enough to need a maintenance work order, and Work Order ID is where the two connect.
Who decides Largest Reason By Minutes and Most Frequent Reason at the end of a shift?+
Whoever is closing the shift position, but it should be read off the Stops entries rather than estimated. The two aren't always the same reason code, since one weights by total minutes and the other by count of stops.
Should a planned stoppage, like a scheduled clean, appear in this log at all?+
Yes, Planned Or Unplanned exists precisely so scheduled downtime is captured alongside unplanned stops, keeping Total Downtime Minutes and Availability Percent honest against the full planned run time.
What happens to a stop marked Escalated?+
It should be visible outside the shift-level rollup, typically picked up by whoever owns Reliability or the Breakdown Record, since an escalated stop usually means the normal response wasn't enough.
Does this log replace the changeover timing on the Changeover Record?+
No. A changeover still gets logged here as a stop by reason code for the shift totals, but the detailed last-good-piece-to-first-good-piece timing and SMED breakdown belongs on the Changeover Record, not here.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Production Control
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Line Clearance Record
Confirms a line is clear of the previous product, its packaging and its paperwork before the next one starts
Production Order Record
Records the execution of a production order, covering quantities, materials consumed, yield and where it went
Changeover Record
Times and records a changeover from last good piece to first good piece, with what was done in between
Scrap and Waste Record
Records material scrapped or wasted, at which step, why, and what it was worth
Daily Production Report
Summarises the day across lines: output, attainment, losses, quality and the issues carried forward
More in Production Control
Line Clearance Record
Confirms a line is clear of the previous product, its packaging and its paperwork before the next one starts
Production Order Record
Records the execution of a production order, covering quantities, materials consumed, yield and where it went
Changeover Record
Times and records a changeover from last good piece to first good piece, with what was done in between
Scrap and Waste Record
Records material scrapped or wasted, at which step, why, and what it was worth
Daily Production Report
Summarises the day across lines: output, attainment, losses, quality and the issues carried forward
Rate and OEE Review
Reviews availability, performance and quality for a line over a period and identifies the dominant loss
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- SAE JA1011 — Evaluation Criteria for Reliability-Centred Maintenance (RCM) Processes
- SAE — Society of Automotive Engineers
- ISO 55001:2014 — Asset management, Management systems, Requirements
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.