An onboarding handover should tell the person responsible what the client bought, what happens next and which tasks remain open. Its purpose is to prevent a sale from becoming a collection of assumptions across different tools.
Record the service commitment
Include the agreed service, start date, payment status where needed and relevant promises made during the sale. Use the actual agreement as the reference rather than an informal recollection of the conversation.
Keep personal information limited to what the receiving role needs. A general task board does not need every detail from a private coaching discussion.
Assign the next actions
A practical checklist can include confirming access, sending the start instructions, arranging any first appointment and explaining how support works. Give each action an owner and a completion state.
Separate "message sent" from "access confirmed" when that difference matters. A welcome email does not prove the client can use the service.
Make exceptions visible
Flag anything that differs from the standard process, such as an agreed delayed start. State who can resolve the exception. An assistant should not have to invent a policy to close the task.
Test the handover
Ask the receiving person to explain the next step using only the record. Missing information becomes easier to identify when the person who made the sale is not supplying context verbally.
Review a few completed handovers for preventable delays. Improve the checklist around real failures rather than adding fields that nobody uses.
Related guide: How to organise delivery as your online client base grows.