Before you use it
- Use when
- Action items are scattered across prose and ownership is implied.
Keep this limit in mind
- Shared work can have multiple contributors; the named owner is for coordination, not blame.
Current editorial reading
Make the request answerable
State one accountable owner, an observable output and a deadline or trigger. Include the needed context and access. For consequential work transferred between people, ask the incoming owner to confirm the responsibility and next checkpoint. If they have not accepted it, report the handoff as pending rather than silently treating the task as covered.
Transfer responsibility explicitly
For example: “Mira, can you check batch 42 and report its terminal result by 16:00 UTC?” Record the reply and any changed deadline, then tell affected colleagues who is handling it. Google’s incident-command handoff uses an explicit acknowledgment; applying that distinction to an ordinary work request is an editorial adaptation. Follow the team’s actual assignment rules, and keep critical incidents on their formal channel. Where an established policy already assigns the role, record that basis rather than inventing a new acceptance requirement.
Take it with you
Use the team’s assignment rules to distinguish a request, a transferred responsibility and completed work. A clear owner/output/deadline line does not itself prove execution.
Sources and evidence (1)
What we checked
Google’s incident-command handoff calls for briefing the incoming commander, explicit acknowledgment and communication of the transfer to others.
Selected official practitioner guidance inspected on 2026-10-05. No workplace experiment or handoff was performed.
Managing Incidents · Clear, Live Handoff
The cited handoff procedure concerns transfer of incident command after the incoming commander has been informed.
This bounds the recommendation: routine tasks follow their own assignment rules. The one-line request example is editorial practice, not proof of a universal communication effect.
Managing Incidents · Clear, Live Handoff; Recursive Separation of Responsibilities
Editorial sources (1)
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 readingName the owner, then confirm the handoff
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaLabel the message mode: decision, action, blocker or FYIUseful with this idea
Split a message when it asks for unrelated decisions
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
CDC clear-communication guidance recommends one obvious main message, placing it early and including a clear action for the audience.
Complex work can require several actions, but the communication still benefits from a dominant purpose.
Description and Examples of Index Items · Core items 1, 2 and 5
CDC guidance recommends active voice and familiar audience language, with technical terms explained where needed.
Technical precision should not be removed when it is necessary for the task.
Description and Examples of Index Items · Core items 6 and 7
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details
