How to Dictate an Async Work Handoff That Saves a Round Trip
Turn what you know at the end of your shift into a handoff with a verified state, an owner and a clear first action.
You're finishing your day when a colleague in another time zone is about to start theirs. They need to pick up a task, but the project thread has forty messages and the latest decision is buried halfway down. Take a moment to dictate the handoff you would give them if you were both looking at the same screen. Then edit it so they can start without you.
A handoff has one job: transfer enough information for the next person to act. A status update can simply tell the team how things are going. A handoff should say what changed hands and where to begin.
Name the decision the next person needs to make
Before recording, choose one outcome the recipient can reach. You might need them to approve a draft, run a check or decide whether to wait. Put that outcome in the opening line and address the person or role responsible. If several people are mentioned, tell them whether any of them actually needs to take action.
For example: “Sam, please check the staging preview on mobile before the newsletter goes out.” The message has one owner and one thing to verify. If Sam cannot approve the send, the rest of the handoff should say who can. Don't imply that a check grants authority it does not grant.
Dictate from the last verified state
Say what is already done, what you actually saw and what you left untouched. Be specific about what is still unknown. In the newsletter example, you might say: “The new hero image is in the staging preview. Desktop looked fine at the width I tested. I haven't checked the mobile preview. The scheduled send is unchanged.”
Put links into the draft by copying them from the source. Label which one is the current preview and which one is the background thread. Send the handoff through the channel where the owner is expected to see it. If a link is restricted, verify they can open it or tell them where to request access. Avoid making a private preview public just to simplify the handoff.
Include the action and the stopping point
Say what the recipient should try first and what result is enough. “Open the preview on a phone. Make sure the headline and button fit in the screen. If the button is cut off, add a screenshot to the issue and tag the editor.” If the task also needs a sign-off, say which record or message should contain it.
Give an absolute deadline with a time zone if timing matters. When the next step depends on a condition, put the condition next to the action. For instance: “If the button still clips, leave the send schedule alone and notify the editor.” Otherwise, someone reading quickly might follow the first half and miss the exception. Copy exact times from the schedule and double-check names and numbers.
Read the draft as the person coming on shift
Read the first two lines without the rest of the thread. Could you name the owner and start the first action? Then check what to do if the test fails and where to leave the result. If you cannot answer those questions, revise the handoff before posting it.
When the action has been taken, ask the owner to mark it in the shared issue or reply in the same thread. That keeps the next shift from working from an old copy. If the handoff follows a meeting, use your notes to confirm the decision and owner; an action summary is different from a record of the meeting.
Try this with a low-risk handoff today. On a supported Mac, download Whisper One, sign in and use the quick start to dictate into an unsent draft. Add the source links, check the names and times, then post it yourself.
