# Make the receiver synthesize the handoff

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Make the receiver synthesize the handoff

ID: MHC-D-RESEARCH-0364 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/make-the-receiver-synthesize-the-handoff

'Any questions?' is a weak test because confusion often has no question prepared.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- The sender has delivered several actions, risks or conditions and shared understanding matters.

### Avoid when

- Synthesis verifies shared understanding, not the underlying truth of the plan; wrong information can be repeated accurately.

### Explanation

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

1. What is the current state in your words?
2. What are your next two actions?
3. What condition would make you stop or escalate?
4. What remains unclear before you take ownership?

### Example

After a migration handoff, the receiver restates which batch is next, which records are excluded and the stop condition for errors.

### Check

The receiver's summary matches the operational state well enough to continue without hidden assumptions.

### Limits

- Synthesis verifies shared understanding, not the underlying truth of the plan; wrong information can be repeated accurately.

### Evidence and sources

- supports: AHRQ's I-PASS structure asks the receiver to synthesize what was heard, ask questions and restate key actions. — RS-21EE4D7FFFEED9C8. A fluent summary can still repeat a wrong premise; synthesis verifies shared understanding, not truth. (Synthesis by Receiver)
- RS-21EE4D7FFFEED9C8: Tool: I-PASS — https://www.ahrq.gov/teamstepps-program/curriculum/communication/tools/ipass.html

No review details supplied.
