Before you use it
- Use when
- The sender has delivered several actions, risks or conditions and shared understanding matters.
Keep this limit in mind
- Synthesis verifies shared understanding, not the underlying truth of the plan; wrong information can be repeated accurately.
Why it matters
Ask the receiver to summarize the current state, key actions and important contingency in their own words. Let them ask questions, then correct missing or distorted parts. The synthesis exposes different mental models before work resumes under the wrong one.
Steps
- What is the current state in your words?
- What are your next two actions?
- What condition would make you stop or escalate?
- What remains unclear before you take ownership?
An example
After a migration handoff, the receiver restates which batch is next, which records are excluded and the stop condition for errors.
Check your result
The receiver's summary matches the operational state well enough to continue without hidden assumptions.
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 readingMake the receiver synthesize the handoff
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaClose a critical instruction with a check-backUse before this idea
Hand off the contingency with the task
Evidence and sources
AHRQ's I-PASS structure asks the receiver to synthesize what was heard, ask questions and restate key actions.
A fluent summary can still repeat a wrong premise; synthesis verifies shared understanding, not truth.
Tool: I-PASS · Synthesis by Receiver
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.
