# Do not transfer ownership until the receiver accepts it

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

---

## Do not transfer ownership until the receiver accepts it

ID: MHC-D-RESEARCH-0361 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/do-not-transfer-ownership-until-the-receiver-accepts-it

Forwarding the message is not the same as transferring responsibility.

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

### Use when

- A task, incident or customer issue changes hands across a shift, team or person.

### Avoid when

- Organizational policy may require additional formal transfer or approval beyond conversational acknowledgment.

### Explanation

Name what is being handed over, who is taking it and when the transfer becomes effective. The sender remains responsible until the receiver has acknowledged the handoff and has enough information to act. If nobody explicitly accepts, the ownership has not moved just because a message was sent.

### Example

An on-call engineer sends the incident state and waits for the incoming engineer to confirm ownership before leaving.

### Check

At any moment, one accountable owner can be named without guessing from message history.

### Limits

- Organizational policy may require additional formal transfer or approval beyond conversational acknowledgment.

### Evidence and sources

- supports: AHRQ TeamSTEPPS states that responsibility in a handoff remains with the sender until the receiver is aware of and accepts the transfer. — RS-C7BE182238850FC0. Formal authority structures may impose additional transfer requirements. (Transfer of responsibility and accountability; acknowledgment by receiver)
- RS-C7BE182238850FC0: Tool: Handoff — https://www.ahrq.gov/teamstepps-program/curriculum/communication/tools/handoff.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/hand-off-the-uncertainty-not-just-the-status
