Client Handoff2 minute read
Client handoff template.
When a project ships, the client needs to know what they received, how to use it, what happens next, and who to contact. This template makes the handoff clear.
Copy the template
## Client Handoff **Client:** [Client name] **Project:** [Project name] **Delivered:** [Date] **Prepared by:** [Your name] ### What's included - [Deliverable 1 with description and location] - [Deliverable 2 with description and location] - [Deliverable 3 with description and location] ### How to use it Step-by-step instructions for the client to get value from the deliverables. ### What's next - [Next step 1 with timeline] - [Next step 2 with timeline] - [Next step 3 with timeline] ### Support & maintenance How the client can get help, report issues, or request changes. ### Contacts - **Project lead:** [Name, email] - **Technical support:** [Name, email] - **Account manager:** [Name, email] ### Files & access - [Link to files] - [Access instructions] - [Login credentials if needed] ### Notes Any constraints, known issues, or things the client should be aware of.
Questions & answers
What should a handoff include?
Deliverables, how to use them, next steps, support info, contacts, file access, and any notes the client needs.
When should I send the handoff?
When the project is done. Use it to confirm the client has everything they need and knows what happens next.
Should I schedule a handoff call?
Yes, if the deliverable is complex or the client needs training. Send the handoff doc before the call so they can review it.
Can AI prepare my handoff?
An AI assistant can draft it from the project files and notes. Geniusly prepares it in Slack for your review.
Meet your next teammate
Your agent.
Where you already chat.
Get work done in Slack, WhatsApp, or text. Start with your workspace, then keep the conversation going wherever you are.