Delegate a task without leaving the important parts in your head

Describe what done looks like

A task label is not a finished result. “Organise the workshop” could mean booking a venue, designing the session or coordinating every participant. Write an observable finish: “A confirmed room, a two-hour agenda and invitations sent to the twelve participants by Thursday.”

Then separate fixed constraints from preferences. A maximum budget and an accessibility requirement are not equivalent to your favourite room layout. If a method is genuinely required, explain why. If the other person can choose, say so explicitly rather than later criticising them for not guessing your preferred approach.

A handoff you can read together

Illustrative brief: “Please coordinate Tuesday’s workshop for twelve people. We need a confirmed accessible room, a two-hour draft agenda and invitations sent by Thursday. The budget is £300. Choose the room and running order; check with me before changing the date or budget. I will provide the participant list today. Let us review the draft on Wednesday morning.”

The numbers are examples, not recommended workshop standards. What matters is that the brief names the result, constraints, freedom, supplied resource and checkpoint. Ask whether the person can accept the task with their current workload; assigning words to a document does not create capacity.

Check understanding without testing obedience

Ask: “What do you see as the deliverable, and what do you need from me?” This is a chance to uncover missing information, not an exam. If their summary differs from yours, improve the brief before work begins.

A useful checkpoint happens while there is still time to change direction. Checking the draft agenda before invitations go out makes sense; demanding updates after every small action may add effort without resolving uncertainty. Choose the checkpoint according to the consequence of a late misunderstanding.

When the task changes

If the attendee count doubles or the budget falls, revisit the handoff. New constraints can change the time or expertise required. Do not keep the original deadline by silently expecting the other person to absorb every addition.

If the result misses the brief, distinguish an unclear instruction from a missed agreed requirement. Both may need correction, but they call for different conversations. Start with the concrete gap: “The invitations are ready, but the room is not confirmed.” Then agree on the next action and who owns it.

Five things to write before handing over

Use a short note in your existing work channel. Regulated or safety-critical work also requires the appropriate competence and mandatory checks; a clear handoff alone does not replace those requirements.

1. The finished result and deadline.
2. The constraints that really must hold.
3. The decisions the other person may make.
4. The resources or information you will provide.
5. The checkpoint and the point at which they should flag a problem.