Protocol

Close a critical instruction with a check-back

Sent is not the same state as understood.

Work through the ideaIllustrative example

Catch the wrong key before the next move.

In this fictional handover, the important instruction is to prepare room B after the agreed access window.

MiraSamBrass and steel door keys on a ring with a worn navy leather fobInstruction given

Mira gives the critical detail.

The intended room is B. The agreed access window also matters.

Prepare room B after its agreed access window begins.
What did the check-back establish?

Agreement on the critical instruction, after correction; it did not establish task completion.

Use check-backs where misunderstanding has a meaningful cost. Do not turn every ordinary exchange into repetition.

VedokrokKeep the idea. Try the next move.

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

  1. 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.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingClose a critical instruction with a check-back

Evidence and sources
Supports

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.

Read this idea as JSON · Release details