Principle

Do not transfer ownership until the receiver accepts it

Forwarding the message is not the same as transferring responsibility.

Work through the ideaIllustrative example

A request can travel while responsibility stays.

Mira is leaving a planning shift. Sam is the proposed incoming owner, under a rule requiring explicit acknowledgment.

MiraSamBrass and steel door keys on a ring with a worn navy leather fobMira is responsible

Mira holds the task.

The next room check, state and checkpoint are ready to hand over.

Next: check the recorded preparation state and report at the agreed checkpoint.
What should be nameable throughout the handover?

The current accountable owner, using the actual assignment and transfer rules.

Organizational policy can require additional formal transfer or approval beyond a conversational acknowledgment.

VedokrokKeep the idea. Try the next move.

Before you use it

Use when
  • A task, incident or customer issue changes hands across a shift, team or person.

Keep this limit in mind

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

Why it matters

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.

An example

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

Check your result

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

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 readingDo not transfer ownership until the receiver accepts it

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.

Formal authority structures may impose additional transfer requirements.

Tool: Handoff · Transfer of responsibility and accountability; acknowledgment by receiver

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