“Can you update the services page?” sounds like a complete request until someone opens the page.
Which version of the copy is approved? Are they meant to change the prices or just the wording around them? Should they publish the result or send it for review? If those answers live in different conversations, the task begins with a search for context. It may stop there until someone has time to ask.
A useful handoff does not need a long brief. It needs enough information for the next person to move without guessing at decisions you meant to keep.
Start with the finished result
“Update the services page” names an activity. “Replace the retired service description, keep the current prices, and send me a preview before it goes live” describes a result.
The second version gives the work an edge. The person doing it can tell when they have finished, and you can review what they actually agreed to deliver.
Be specific about the part that matters. If the page needs to answer a customer’s common question, say what that question is. If the task is to shorten a report, explain who will read it and what they need to take from it. You do not have to dictate every sentence or click. You do have to describe the difference the work should make.
Say which decisions travel with the task
Passing on work is not always the same as passing on authority.
Someone may be free to rearrange a page but not to change its prices. They may choose a meeting time but need approval before promising a delivery date. Write that boundary down. Otherwise, a capable person either makes a decision you needed to make yourself or pauses at every small choice.
Point them to the current source material, too. “Use the copy in the approved brief, not the draft in the shared folder” can save an entire round of corrections. If there is no agreed source yet, that is the first decision—not a detail to discover halfway through the task.
Give the work a checkpoint
“ASAP” rarely tells someone when you need their input. A final deadline may not help either if the work could go in two different directions.
Ask for a checkpoint when a decision would still be easy to change: a page outline before the full rewrite, a sample slide before the whole deck, or a proposed approach before a supplier is contacted. Say what you will review and when you can respond.
Keep the checkpoint proportionate. A small, familiar task may need only a completion message. A new task with unclear requirements deserves an earlier conversation. The aim is to catch uncertainty before it becomes rework, not to turn every handoff into a meeting.
Make “done” visible
When the work is finished, ask for its location and a short note about what changed. A link to the updated page and one unresolved question are more useful than “All done” in a chat thread.
If you are waiting for several people, record those handoffs as waiting items rather than carrying them as tasks you can do yourself. Our 15-minute weekly review offers a simple way to separate waiting from doing and choose when to follow up.
Try this on one task you are about to pass on. Write five short lines: the result you need; the material to start from; what the other person may decide; when you want to see progress; and what they should send back when it is done. If one line is hard to write, you have probably found the conversation to have before the handoff.
Clearer instructions will not remove every question. They give the next person a place to begin—and make the questions that remain worth asking.