A duration survives in the production record. The explanation often stays with the people who were there. A useful handover gives the next team enough context to act without having to reconstruct the whole event.
Start with the event
Anchor the note to a line, a transition and a run. Ask what happened while it is still possible to check the sequence with the people involved. Use concrete observations: which item was unavailable, where waiting occurred and what the team did next.
Keep the conversation neutral. ‘The format kit was at the neighboring line when preparation began’ gives the next reviewer something to verify. ‘Nobody prepared properly’ combines an accusation with an explanation the note has not established.
Keep observations and explanations separate
A debrief can contain an observation, a suspected cause and a proposed action, but they should remain distinguishable. The observation may be well supported while the cause is still uncertain.
In a fictional example, a team waits for a guide rail. Possible explanations include shared tooling, an incorrect location record or a schedule change. The waiting alone cannot tell you which is correct. Preserve the uncertainty so the next discussion does not mistake a guess for an approved conclusion.
Finish with a usable handover
A compact note can answer four questions:
- What happened, and on which transition?
- What evidence or record supports the observation?
- What should the next team check before the comparable run?
- Who owns the follow-up, and when will it be reviewed?
Include what helped as well as what went wrong. A successful preparation step can be useful to another shift, especially when the reason it worked is documented.
Retrieve the note when it matters
A handover is only useful if someone can find it at the next preparation point. Link it to the relevant line and format family, and retain the original record. Avoid burying it in a general chat stream that the next supervisor has to search from memory.
Review the proposed action after the next comparable run. Did the issue recur? Was the action completed? Did the team discover a different explanation? Close or revise the note through the normal process.
This connection between a short debrief and the next preparation plan is central to Cadensa’s changeover workflow.
Take it to the line.
Try ending one debrief with a single sentence: ‘Before the next comparable run, [owner] will verify [specific condition].’
A Cadensa discussion guide. Adapt the ideas to your site’s approved procedures.


