What this is
What is a breakdown debrief?
What is a breakdown debrief?
A breakdown debrief is a short structured conversation held immediately after an unplanned equipment stop, with the people who were there, recording the sequence of events, what helped, what slowed the response and what could be fixed this week. It is deliberately informal and time-boxed, to capture the practical detail that decays within hours, before anyone decides whether a formal investigation is needed.
How is a debrief different from the work order that fixed the breakdown?
The work order records the fault and the repair: what failed, what was replaced, what was set, how long it took. The debrief records the friction around that repair: whether the drawing was findable, the isolation points labelled, the part on the shelf, the right skills on shift. Those are two datasets with two owners, and the second is the only route to shortening the next stop of a fault you cannot prevent.
When should a debrief be held, and by whom?
Within twenty-four hours, and in practice before the shift that dealt with it goes home. It is led by the maintenance supervisor with everyone involved present, including the operator who saw the first symptom. Held on day five it becomes a reconstruction from the work order, which is why Held Within 24 Hours is the first substantive field: its answer predicts the value of everything below it.
Scope
When is a breakdown debrief required?
This record captures learning from one unplanned stop, quickly and informally. It is not the failure record, the repair record, the investigation or the production loss account. Using it as any of those produces narrative where the library expects coded, comparable data.
Use this template when
- A significant unplanned stop has just ended and the crew who dealt with it are still on site
- The repair took materially longer than the fault warranted and nobody yet knows why
- A stop was handled well and you want the reason recorded before the next process change removes it
- A decision is needed on whether the event justifies a full root cause analysis, and on what basis
- A recurring asset is being built up towards a repeat failure or bad actor review and needs its narrative evidence
Do not use it for
- The record that an asset failed and stopped production, which is Equipment Failure Report and carries the event data the reliability figures are built from
- How the asset failed in coded terms, which is Failure Mode Record, because free text in a debrief cannot be counted across a fleet
- What was actually done to the machine, which is Repair Record, or Temporary Repair Record where the fix is provisional and needs a removal date
- A structured causal investigation, which is Root Cause Analysis: evidence tested rather than recalled, with a method and a hypothesis trail
- The cost and output consequences of the stop, which is Production Impact Record, and which a fifteen-minute conversation should not attempt to quantify
Compliance mapping
Which ISO 55001 cl.10.1 requirements does this satisfy?
No standard requires a debrief. Several require what a debrief is the cheapest route to: causes evaluated so failures do not recur, asset performance analysed, and the information maintenance needs made accessible. The debrief is a method, and the clauses bite on whether it produced anything.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.10.1 | React to a nonconformity, evaluate the need for action to eliminate its causes so that it does not recur, and review the effectiveness of what was done | Outcome |
| ISO 55001 cl.10.3 | Continual improvement of the suitability, adequacy and effectiveness of asset management and of the asset management system | Outcome |
| ISO 55001 cl.9.1 | Determine what needs monitoring and measuring for asset performance, evaluate the results and retain the evidence | What happened |
| ISO 55001 cl.7.5 | Determine the information required to support assets and asset management, including its quality and how and when it can be accessed | Practical obstacles |
| ISO 55001 cl.7.2 | Determine the competence necessary for those whose work affects asset performance, and ensure it is available | Practical obstacles |
| OSHA 1910.147(c)(6) | Periodic inspection of the energy control procedure to ensure the procedure and its requirements are being followed | Practical obstacles |
| ISO 14224 | Failure and maintenance data collected against identified equipment with sufficient detail and traceability to support reliability analysis | Header |
| BRCGS Food Safety cl.4.7 | Maintenance carried out so that it does not present a risk of product contamination, with temporary repairs controlled and time-limited | What happened |
What it does not cover
- Root cause analysis, which applies a structured method to evidence rather than recall, tests hypotheses against the failed component and the process data, and reaches a cause that can be designed out.
- The coded failure record, which under ISO 14224 needs equipment class, failure mode, detection method and maintenance activity in comparable form, none of which free-text narrative provides.
- The repair record, which captures parts, torques, settings and, for a temporary repair, the removal date that stops a cable tie becoming permanent.
- Incident investigation, which is required by ISO 45001 cl.10.2 and by injury recordkeeping rules if anyone was hurt or nearly hurt during the response, and which cannot be discharged by a maintenance conversation.
- Product disposition, which for a stop in a process area such as pasteurising or filling is a food safety decision under ISO 22000 cl.8.9 or the site's HACCP plan, not an engineering one.
Global
Breakdown Debrief requirements by country
The debrief itself is voluntary everywhere. The duties it touches are not: keeping equipment in efficient working order, controlling hazardous energy, and designing maintenance access into machinery in the first place.
OSHA 29 CFR 1910.147; 1910.212; FDA 21 CFR 117 for food facilities
No duty to review a breakdown, but hazardous energy control and guarding duties apply to every response, and equipment maintenance is a preventive control in a food plant.
A debrief that records isolation as difficult has created evidence about the energy control procedure, and leaving it unrouted is worse than not asking the question.
Provision and Use of Work Equipment Regulations 1998, reg.5 and reg.22
Work equipment must be maintained in efficient working order and in good repair, with a maintenance log kept up to date where one exists, and maintenance operations carried out without exposing anyone to risk.
Reg.22 makes the awkward-access answer a legal matter, not a convenience one: if maintenance cannot be done safely with the machine stopped and isolated, the arrangement needs changing.
Machinery Directive 2006/42/EC Annex I 1.6.1, succeeded by Regulation (EU) 2023/1230
Machinery must be designed so that adjustment, maintenance and repair points are accessible and can be reached and used safely.
A pattern of poor-access answers on a machine placed on the market recently is a conformity question for the supplier, not only a workshop grumble.
Provincial OHS regulations on control of hazardous energy; CSA Z460
Lockout procedures required per machine, with periodic review of their adequacy in most provinces.
Debrief answers about isolation feed the procedure review provinces expect, giving it real operational evidence instead of a desk check.
Model WHS Act and Regulations, Chapter 5 (plant and structures)
Duties to maintain plant, to manage risks from plant so far as reasonably practicable, and to inspect and maintain guarding and control measures.
Reasonably practicable is judged on what the business knew, and a stack of debriefs naming the same obstacle is knowledge on the record.
ISO 55001 cl.10; ISO 14224
Causes of nonconformity evaluated so recurrence is prevented, and failure and maintenance data collected to a comparable structure.
Auditors look for the link from a stop to an action and back to a verified effect; debriefs with quick wins and no owners break that chain at the first link.
How to complete it
How to complete a breakdown debrief, step by step
The template is fifteen minutes long and most of it answers itself. What determines whether the record is worth reading in six months is how the conversation is run.
Run the fault first and quickly, then draw a line and go back over the clock. From the call to the restart, where did the time go? The answer is usually a list of waits: for a drawing, for a key, for a fitter with the right ticket, for the cabinet to cool. Those waits are the content of this record. The fault belongs in the failure report, and repeating it here costs the only field nobody else collects.
The operator saw the first symptom, often hours before the stop, and is the only person who can say whether the machine had been running differently. Maintenance-only debriefs start the sequence at the call-out and lose that entirely. Put the operator's account first, before the engineering explanation is on the table, because once a mechanism is named everyone's recollection rearranges itself to fit it.
Full Investigation Warranted gets answered by the person who has just finished the repair and understands it, which reliably produces No. Take the decision out of that moment by defining the trigger in advance: third stop on the same asset in a quarter, any stop over a threshold duration, any temporary repair still in place, any stop with a safety or product consequence. The supervisor then applies a rule, not a judgement made while tired.
Quick Wins Identified is where the value of the exercise accumulates, and it is optional free text on a record that closes. A laminated drawing, a labelled isolation point, a spare on the shelf: each needs an owner and a date before the meeting ends, which means Action Required is Yes far more often than sites expect. A debrief identifying four quick wins and raising no action has recorded the reason it will happen again.
What auditors find
Most common breakdown debrief findings
Debrief findings are rarely that the debriefs are missing. They exist, they were held on time, and they are signed. The findings are about what was in them and whether anything downstream ever read them together.
| Finding | Clause | What fixes it |
|---|---|---|
| Debrief held four or five days after the stop; the narrative is a paraphrase of the work order. | ISO 55001 cl.10.1 | Hold it on shift, before the crew disperses; a late debrief is recorded as Later, not backdated. |
| Attendees list contains maintenance only; the operator who saw the first symptom is absent. | ISO 55001 cl.7.5 | Name the operator, shift supervisor and fitters individually, and take the operator's account first. |
| Quick wins identified but Action Required answered No, so nothing left the record with an owner. | ISO 55001 cl.10.1 | Raise every quick win as an action with an owner and a date, however small the item. |
| What Slowed Us Down describes the failure mechanism rather than the obstruction to the repair. | ISO 55001 cl.10.3 | Walk the clock from call to restart and record the waits; the mechanism belongs in the failure report. |
| Case ID missing or different from the triggering failure report, so the chain cannot be assembled. | ISO 14224 | Copy the Case ID from the parent record; never mint a new thread key on a follow-on record. |
| Full Investigation Warranted answered No on every debrief for an asset that has stopped four times in a quarter. | ISO 55001 cl.10.1 | Define the escalation trigger on repeat frequency and duration, not on the supervisor's read of this stop. |
| Obstacle answers never aggregated; Access To Equipment Adequate recorded Poor repeatedly on one asset with no design action. | ISO 55001 cl.9.1 | Report the nine obstacle answers by asset monthly and treat a persistent Poor as a modification request. |
| Isolation Straightforward recorded as Difficult with no consequent review of the energy control procedure. | OSHA 1910.147(c)(6) | Route a difficult or awkward isolation to a procedure and labelling review, not to a comment field. |
| A temporary repair described in the debrief and recorded nowhere else, with no removal date. | BRCGS Food Safety cl.4.7 | Raise the temporary repair record from the debrief, with a removal date and a permanent fix owner. |
| What Went Well left blank on every debrief, so nothing protects the practices that shortened the stop. | ISO 55001 cl.10.3 | Require one line; a spares change or a rota change will otherwise remove the thing that worked. |
Case in point
Case in point: three good debriefs and a nineteen-hour stop
A yoghurt plant's filling line lost its capper three times in four months. Each stop was between forty minutes and two hours, each was diagnosed quickly as a servo drive fault, and each got a debrief inside the day. All three recorded Parts Available as No. All three noted a quick win: hold a spare drive on site. Full Investigation Warranted was answered No each time, reasonably, because each stop was short and the fault was understood.
The fourth failure ran nineteen hours. The drive had to come from the manufacturer in Germany, the line stayed down through two production days and around forty thousand litres of cultured product was written off. That triggered the root cause analysis. It found the drive was running hot because a cabinet side panel had been refitted the wrong way round after a deep clean two years earlier, blinding a cooling louvre. The panel was the cause of all four failures.
The evidence had been in the debriefs. The second carried the line, in What Slowed Us Down, that the cabinet was too hot to work in and the crew had waited for it to cool. Nobody read the three together, because each was raised, signed and filed against its own stop, and no report put one asset's debriefs side by side. The corrective action was not a better form. It was a standing monthly review of debriefs grouped by asset, which is what turns three anecdotes into the observation that the cabinet is always hot.
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.
4 sections
- Reference
- MNT-019
- Archetype
- Record
- Record ID
- BD-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 55001 cl.10.1
- Links
- Links Case; feeds RCA
- Tags
- Maintenance, Learning
- Sections
- 4
- Fields
- 39
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 4
Header
18 fieldsDebrief ID*
Auto sequence. Format BD-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 and Time*
Raised 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.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Case ID*
Copy from the record that triggered this work.
Thread key. Every record in this chain carries this value
Parent Type*
What kind of record this follows.
Parent ID*
The reference of that record.
Immediate predecessor record
Raised Date*
Fifteen Minutes, Within A Day
Short and informal, while it is fresh. Formal investigations happen later and often miss the small practical things this catches.
Held Within 24 Hours*
- Yes3 pts
- Later1 pt
- No0 pts
Attendees*
Duration Minutes
What happened
3 fieldsSequence Of Events*
What Went Well
Fast diagnosis, parts available, good handover. Protect these when you change things.
What Slowed Us Down*
Practical obstacles
9 fieldsInformation Available When Needed*
- Yes3 pts
- Partly1 pt
- No0 pts
Drawings And Manuals Accessible*
- Yes3 pts
- Partly1 pt
- No0 pts
Correct Tools To Hand*
- Yes3 pts
- Partly1 pt
- No0 pts
Parts Available*
- Yes3 pts
- Partly1 pt
- No0 pts
Access To Equipment Adequate*
Poor maintenance access designed in years ago costs hours on every job.
- Yes3 pts
- Awkward1 pt
- Poor0 pts
Isolation Straightforward*
- Yes3 pts
- Awkward1 pt
- Difficult0 pts
Right Skills On Shift*
- Yes3 pts
- Partly1 pt
- No0 pts
Help Available When Needed*
- Yes3 pts
- Delayed1 pt
- No0 pts
Communication With Production Good*
- Yes3 pts
- Adequate2 pts
- Poor0 pts
Outcome
9 fieldsQuick Wins Identified
Things that can be fixed this week. A labelled isolation point, a spare on the shelf, a laminated drawing.
Full Investigation Warranted*
RCA ID
Links to FDN-013 RCA ID
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
Maintenance Supervisor*
Signature*
MNT-019 · record IDs look like BD-2026-000 · Links Case; feeds RCA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The debrief itself is easy and usually happens. What fails is everything after it: the quick win with no owner, the obstacle answer nobody counted, the three records on one asset nobody read side by side.
Raises the debrief from the failure record on the same case thread, groups debriefs by asset, and counts the obstacle answers so a repeated Poor becomes a modification request.
Watches the debrief population for the escalation trigger, third stop in a quarter or a temporary repair still open, and raises the analysis rather than leaving it to the supervisor's judgement at the end of a long shift.
Takes difficult isolation and poor access answers into the energy control procedure and plant risk records, where they become a review rather than a comment.
Turns a Right Skills On Shift answer of Partly or No into a competence gap against the rota, so the cover problem is sized rather than noted.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Breakdown Debrief definitions and key terms
- Breakdown
- An unplanned stop or loss of function of an asset requiring intervention before production can resume, as distinct from a planned outage or a degraded run.
- Hot debrief
- A short review held immediately after an event, while the people involved are still present and their recall is intact, trading rigour for detail that would otherwise be lost.
- Mean time to repair
- The average active repair time for a class of failures, which excludes waiting for parts, access and skills, and is therefore usually far shorter than the downtime experienced.
- Maintainability
- The designed-in ease of restoring an asset to service: access, isolation, diagnostics, standard fasteners and component reach. It is set at purchase and paid for on every job.
- Failure mode
- The manner in which an item loses its ability to perform its function, expressed in a standard taxonomy such as ISO 14224 so that occurrences can be counted across a fleet.
- Bad actor
- An asset whose failure frequency or consequence puts it in the small population responsible for most unplanned loss, identified from event data rather than from reputation.
- Temporary repair
- A fix that restores function without restoring design condition, which must carry a removal date and a permanent fix owner or it becomes the design condition.
- Case ID
- The thread key carried by every record in one chain of work, so a failure report, debrief, repair record and analysis can be reassembled as a single event afterwards.
FAQ
Frequently asked questions about breakdown debrief
Is a debrief the same as a root cause analysis?+
No, and conflating them costs both. A debrief is recall-based, fifteen minutes long, and its subject is the response. An analysis is evidence-based, takes days, and its subject is the cause. The debrief is better than the analysis at one thing: the small practical detail that has vanished by the time an analysis starts, such as which drawing was missing. It should feed the analysis, never replace it.
Should we debrief every breakdown?+
No. Define the threshold and hold to it, or the practice dies of volume within two months. A workable rule is any stop over a duration threshold set per line, any stop that recurs on the same asset inside a quarter, any stop involving a temporary repair, and any stop with a safety or product consequence regardless of length. Everything else gets a work order and nothing more.
Who has to be in the room?+
The operator, the fitters who did the work, and the supervisor who led it. The operator is the non-negotiable one and the one most often missing. Reliability engineers and managers are optional and, in the first few debriefs, unhelpful: their presence turns a conversation about awkward access into a conversation about who authorised it, and the practical detail stops arriving.
How long should a debrief take?+
Fifteen minutes, standing up, at the machine if it is safe to be there. The time box is a design feature, not a compromise. A debrief scheduled for an hour becomes a meeting, gets a date in the diary, and by the time the diary comes round the recall it existed to capture is gone. The template is deliberately short for the same reason.
Should the debrief be scored?+
Not with a headline number, which is why this template does not carry one. A percentage on a debrief invites the answer that produces a good percentage, and the obstacle questions are only useful when answered honestly. Score the individual obstacle answers and aggregate them by asset and by area instead: that is where a pattern shows, and it does not put the supervisor's competence on the record.
Does a debrief expose the crew to blame?+
It can, and if it does you will get one useful debrief and then none. The protection is structural rather than cultural language: the questions are about information, tools, parts, access, isolation, skills and help, all of which the organisation provides rather than the crew chooses. Keep the record on obstacles, keep individual performance in another conversation, and never let a debrief become the source document for a disciplinary.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Reliability and Predictive Maintenance
Root Cause Analysis
Finds out why something happened rather than who was involved
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
More in Breakdowns
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
Production Impact Record
Records what the failure cost in lost output, scrap and late orders
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:
- ISO 55001:2014 clauses 10.1, 10.3, 9.1, 7.5 and 7.2, asset management systems
- ISO 14224:2016, collection and exchange of reliability and maintenance data for equipment
- OSHA 29 CFR 1910.147(c)(6), periodic inspection of energy control procedures (US)
- Provision and Use of Work Equipment Regulations 1998, regulations 5 and 22 (GB)
- Machinery Directive 2006/42/EC Annex I 1.6.1 and Regulation (EU) 2023/1230, maintenance access
- BRCGS Global Standard for Food Safety, clause 4.7 maintenance
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.