}
{caption && !thumbnail && {caption}{src && Select the image to view it full size.}}
;
};
A handoff is ready when the next person can act without reconstructing the
conversation. This example hands over the Relio homepage message for review.
**Before you start:** the task and related project should exist, and the teammate
should be a member with access to the work. If needed,
[manage workspace members](/documentation/manage-members-and-permissions) first.
Find the task in **Tasks** or through the project's linked work. Reuse it
when the outcome is unchanged.
A task such as **Define the homepage message for CRE teams** is ready for
review when its draft headline, supporting paragraph, and three benefits
are available. If the next action is an independent deliverable, create a
separate task with its own completion criteria.
Update the description with the draft location, the decision needed, and
any unresolved questions. Keep completion criteria visible.
For example:
```text theme={null}
Next action: review the headline, supporting paragraph, and three benefits.
Check that the audience is clear and every benefit matches a documented
product capability. Leave proposed edits in the draft.
Ready for the next step when the reviewer has resolved the copy questions.
The project lead will then assemble the revised homepage brief.
```
Add the actual draft link and reviewer name before using this example.
Use **Assignees** to select the people doing the next part of the work.
If several people remain assigned, state who acts next in the description.
Choose the status that represents the current situation. Use your team's
review status when applicable, and keep the task open until its completion
conditions are met. Confirm any due date with the next owner.
Open **Comments** and explain what changed, what remains, and who should
act next. For example:
> The first message draft is ready at the link in the description. Please
> review the audience and benefit claims. The CTA wording still needs a
> decision before we assemble the final brief.
Adapt this to the actual work. Link the relevant project so the teammate
can find its activity and surrounding context.
Reopen the task and verify the assignees, description, status, comment,
and linked project. Make sure the teammate can access the draft as well as
the task. Use your normal team channel to confirm the handoff when needed.
## Check the result
The next person knows what to review, where the material lives, and what happens
after their review. If they still need the kickoff transcript to understand the
task, add a short explanation to its description.
See [Organize tasks](/documentation/organize-tasks) for task controls, or
[Plan a project from a brief](/recipes/project-from-brief) to structure the
work before it changes hands.
## Related topics
- [Plan a project from a brief](/recipes/project-from-brief.md)
- [Write a weekly project update](/recipes/weekly-project-update.md)
- [Work with records](/documentation/data/records.md)
- [Manage members and permissions](/documentation/manage-members-and-permissions.md)
- [Create your workspace](/documentation/create-your-workspace.md)
: