Protocol

Close a critical instruction with a check-back

Sent is not the same state as understood.

When it fits

A number, instruction, identifier or action is important enough that one misheard detail can create rework or harm.

When to avoid it

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.

Keep this limit in mind

Do not turn ordinary conversation into constant repetition; reserve check-backs for information where misunderstanding has meaningful cost.

Connected ideas

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)

Tool: Check-Back (or Repeat-Back)