# How to hand off work clearly to a colleague

Hand off work with a clear current state, next owner, trigger and stop condition. Rehearse what the receiving colleague needs to recover and confirm.

[Canonical page](https://ptichi.com/goals/handoff-work-clearly)

A clear work handoff tells a colleague what is ready, what remains open, what they should do next and which condition could stop that action. Keep the necessary files and decisions findable. Then check two separate things: **what the colleague understood, and whether they can take responsibility for the next step.**

The listener needs enough to continue. A detailed account of everything you did may still leave them unable to answer, “What do I do first?”

## Start at the point where someone else takes over

A status update answers, “Where are we?” A handoff must also answer, “What becomes my job now?”

That changes which detail belongs in the opening. You may have spent two days comparing drafts, but the colleague taking over may need to know that one figure remains unverified and the draft must not go to the client yet.

Use these questions to prepare the handoff:

- What is complete, and what is still a draft or blocked?
- Which person owns the next action?
- What event makes that action appropriate?
- Where are the working file and the evidence needed to proceed?
- When should the colleague stop, ask or escalate?

These are editorial preparation questions, not a validated communication score. Some handoffs need all five; a small, familiar task may need less explanation.

## One fictional handoff, with the missing facts restored

Imagine you are handing a client draft to a colleague before leaving for the day. These are the invented facts:

- Draft 3 is ready except for two revenue figures.
- Maya is checking those figures in review task 42.
- The receiving colleague should update the figures after Maya marks both verified, then send Nora the review link.
- Nora owns final approval. Sending her a review link does not mean the client can receive the draft.
- If verification is still incomplete at three, the draft stays a draft and Nora needs a blocked-status update.

A weak version hides most of that:

> The draft is basically ready. Maya has been looking at the numbers, and there’s a task with the latest notes. Could you pick it up and get it over to Nora? It should be fine.

“Pick it up” has no clear starting action. “Basically ready” hides the condition. “It should be fine” supplies reassurance where the colleague needs a decision boundary.

Here is a more usable version:

> Draft 3 is ready except for two revenue figures. Maya is checking them in review task 42. Can you take the next step? Once Maya marks both verified, update the figures and send Nora the review link. Nora still owns final approval. If the checks are not finished by three, keep it as a draft and tell Nora the review is blocked. The file and task are linked in my handoff note.

The second version adds the fictional facts the first left out. It is an authored example, not a transcript or a measured Ptichi result.

It is also longer. That is acceptable if the extra words prevent the recipient from taking the wrong action. Once the conditions are clear, remove history that does not change them.

## Put the condition next to the action

Compare:

> Send Nora the draft. Maya still has two figures to check.

with:

> Send Nora the review link **after Maya verifies both figures**.

The second sentence attaches the trigger to the action it controls. The same principle works for a technical handoff: “Run reconciliation after the interface completes; if either record still fails, leave the batch open and send the IDs to the support queue.”

Do not turn a hoped-for event into a completed fact. If the verification time is unknown, say what remains unknown and when the next update will happen. The [uncertainty guide](/goals/explain-uncertainty-clearly-at-work) helps you prepare that part.

## Understanding the work is different from accepting it

“Does that make sense?” is an easy question to answer without revealing much. Try a concrete check:

> From this handoff, what would you do first? What would make you hold the draft?

Let the colleague answer before supplying the key. A different answer may expose missing context, an unclear condition or a different interpretation. Clarify that part rather than asking them to repeat your exact sentence.

Then ask about ownership:

> Can you take responsibility for that next step, or is there something we need to resolve first?

A colleague can understand the task and still lack time, access or authority to carry it out. If the handoff depends on their agreement, record it as requested until they confirm. Use your organization’s assignment process where responsibilities are set formally.

This distinction has a concrete operational precedent. Google’s SRE chapter on [managing incidents](https://sre.google/sre-book/managing-incidents/#clear-live-handoff) calls for an explicit incident-command handoff, acknowledgment from the incoming commander and communication of the change to the other responders. That is incident-management guidance, not a study validating ordinary office speech or this Ptichi exercise.

**Our read:** for everyday handoffs, make the next responsibility and any pending acceptance visible. A well-spoken message cannot supply an agreement nobody made.

## Rehearse one handoff you could actually give

Use the fictional draft above, or a harmless task you know well. Keep real work details in your approved work tools; invented names and facts are enough for this exercise. Write a short key before speaking: current state, next action, trigger and stop condition.

### Take A: explain the handoff normally

Say it out loud as though the colleague has just joined the conversation. If useful, record it with your own ordinary recorder. The Ptichi website does not capture audio.

Do not polish every word before this attempt. You need something specific to inspect.

### Listen: look for the next action and its boundary

On self-playback, locate the sentence that names the next action. Is its trigger attached? Does “ready” mean ready for review or approved for use? Is the stop condition audible?

Self-listening can help you find an omission or a tangled sentence. You already know the intended facts, so it cannot establish what an unfamiliar colleague understood.

With a willing listener who has not seen the key or heard the handoff, ask them to state the first action and the condition that could stop it. Keep their original answer, including uncertainty, before showing the key.

### Change one thing

Pick the omission or ambiguity that most changes the action. For example, move “after both figures are verified” into the sentence that asks for the draft update.

Keep the remaining facts stable. Changing the trigger, owner and deadline at once would make it hard to identify what you repaired.

### Take B: give the repaired handoff

Explain it again in your own words. Keep the condition intact even if a shorter sentence sounds smoother without it.

If the same listener heard Take A or saw the key, record that exposure. They can help you rehearse the repair, but their second answer is not an independent first-hearing comparison.

### Compare: inspect the task, not the voice

Ask whether the action and its condition are easier to locate, and whether any necessary fact disappeared. Avoid replacing these questions with a general confidence or clarity rating.

A fluent take with the wrong permission is still the wrong handoff. A hesitation before a precise condition is not automatically a problem.

### Change the situation

Try a new handoff: a colleague needs to cover a meeting while you are away. What is already agreed, what decision can they make, and which question must come back to you?

Write that task’s key before speaking. This is changed-scenario practice, not evidence that the first repair transfers automatically. If you test it with a listener, note whether they already know the situation or its answer.

## Leave a note the colleague can use later

Speech gives orientation. The working note gives the recipient somewhere to return when they act.

For the fictional draft, that note could contain:

- **State:** Draft 3; two figures remain unverified.
- **Next owner and action:** the receiving colleague updates verified figures and sends Nora the review link, after accepting the handoff.
- **Evidence:** links to Draft 3 and review task 42; Maya owns verification.
- **Boundary:** no client send before Nora’s final approval; if verification is incomplete at three, keep the draft open and update Nora.

Confirm that the recipient can find and open the necessary artifacts. A spoken file name cannot repair missing access. For an asynchronous handoff, put the action and condition in the note itself, and keep any required acknowledgment visible.

## Where a clearer explanation stops helping

This rehearsal cannot resolve an unmade decision, missing permissions, insufficient capacity or unclear organizational responsibility. Those need an actual decision or a different owner.

High-risk and regulated work may require a formal handoff procedure. Follow that procedure; this general speaking exercise does not replace it.

Ptichi has not validated this protocol as a way to reduce workplace errors or improve learning. The useful observation is narrower: what one recipient recovered in a stated situation, plus any ownership they explicitly accepted.

## Prepare the next handoff with Ptichi

Use [Before Meeting](/practice/practice-before-a-meeting) to rehearse this handoff now: choose the next action, make one ordinary attempt, attach its missing condition and retest. This is available web guidance; bring your own recorder if you want playback.

If you only need to report progress, use the [project status guide](/goals/concise-project-status-update). If you want to interpret a listener’s response carefully, read [The listener is part of the measurement](/research/the-listener-is-part-of-the-measurement).

Interactive controls remain on the canonical page. This is a saved text representation, not a completed practice or a product result.

## Sources and limits

- [Managing Incidents — Clear, Live Handoff](https://sre.google/sre-book/managing-incidents/)
  Google SRE guidance calls for an explicit incident-command handoff, incoming acknowledgment and communication of the change to responders.
  Operational incident-management guidance, not a controlled speaking, workplace-learning or Ptichi efficacy study.

## Evidence and limits

- authored-example: This page includes a Ptichi-authored example built for explanation or rehearsal.
  It is an editorial example, not an observed-user result, experiment or proof that Ptichi improves speech.
- bounded-self-listening-exercise: This page includes a bounded listen-and-compare exercise that you can run with your own recorder.
  The exercise does not prove that Ptichi improves speech or that a second take will generalize to other listeners or situations.

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "@id": "https://ptichi.com/goals/handoff-work-clearly#article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://ptichi.com/goals/handoff-work-clearly#webpage",
    "url": "https://ptichi.com/goals/handoff-work-clearly",
    "isPartOf": {
      "@id": "https://ptichi.com/#website"
    },
    "breadcrumb": {
      "@type": "BreadcrumbList",
      "@id": "https://ptichi.com/goals/handoff-work-clearly#breadcrumbs",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Ptichi",
          "item": "https://ptichi.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Goals",
          "item": "https://ptichi.com/goals"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "How to hand off work clearly to a colleague",
          "item": "https://ptichi.com/goals/handoff-work-clearly"
        }
      ]
    }
  },
  "articleSection": "Goals",
  "headline": "How to hand off work clearly to a colleague",
  "description": "Hand off work with a clear current state, next owner, trigger and stop condition. Rehearse what the receiving colleague needs to recover and confirm.",
  "url": "https://ptichi.com/goals/handoff-work-clearly",
  "inLanguage": "en",
  "dateModified": "2026-10-04",
  "creditText": "Ptichi editorial",
  "publishingPrinciples": "https://ptichi.com/product/editorial-policy",
  "isPartOf": {
    "@id": "https://ptichi.com/#website"
  },
  "citation": [
    {
      "@type": "CreativeWork",
      "name": "Managing Incidents — Clear, Live Handoff",
      "url": "https://sre.google/sre-book/managing-incidents/"
    }
  ]
}
```