Before you use it
- Use when
- A number, instruction, identifier or action is important enough that one misheard detail can create rework or harm.
Keep this limit in mind
- Do not turn ordinary conversation into constant repetition; reserve check-backs for information where misunderstanding has meaningful cost.
Why it matters
After giving the critical information, ask the receiver to repeat the key part in their own words or exact value. Compare the repeat-back with the intended message and correct discrepancies immediately. Keep the loop short: instruction, repeat-back, confirmation or correction.
Steps
- Both people can point to the same critical value or action before execution begins.
An example
For a production change, the receiver repeats the system, client, transport and execution window before starting.
Check your result
Both people can point to the same critical value or action before execution begins.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingClose a critical instruction with a check-back
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaCall out the critical fact and name its receiver
Evidence and sources
AHRQ TeamSTEPPS defines check-back as closed-loop communication used to verify that exchanged information was received and understood.
Repeat-back is most useful for consequential information; using it mechanically for every exchange can add noise.
Tool: Check-Back (or Repeat-Back) · Check-Back overview
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.
