How to write a client handoff that does not drop context
A client handoff that does not drop context states what was agreed, what shipped, what is still open, who owns the next step, and which email or doc proves each point. If any of those five are missing, the next owner will re-ask the client. Use the checklist below, then draft the handoff in Slack from the Gmail thread and Drive file that already exist.
What should a client handoff include?
Use this as the minimum. If a line is unknown, write "not in the source" instead of guessing.
| Section | What to write | Where it usually lives |
|---|---|---|
| Who and when | Client, project name, handoff date, outgoing owner, incoming owner | Slack channel topic, SOW, CRM note |
| Agreed scope | What is in, what is out, and any change that was accepted later | Drive agreement, kickoff email |
| What shipped | Deliverables, links, and the date they were sent | Drive folder, Gmail "sent" |
| What is still open | Decisions, assets, access, and unpaid items, each with an owner | Latest Gmail thread, Sheets tracker |
| How to use it | Logins, environments, and the first thing the client should do | Handoff email, README in Drive |
| Support | Who answers what, and what is out of scope after today | Retainer note, Slack canvas |
| Sources | Links or message dates for every deadline and promise | Gmail, Drive, Linear, GitHub |
A reusable copy-paste version lives on the client handoff template. For an internal project (not a client), use the same sections and the project handoff guide.
Where does context usually get dropped?
Most failed handoffs are not missing a logo or a file. They are missing a decision that lived in one person's inbox.
- The "we decided on a call" line with no date. If it is not in email or the doc, the next owner cannot defend it.
- Open questions listed without owners. "Waiting on assets" is not a handoff. "Waiting on logo files from Priya, last asked 10 October in the kickoff thread" is.
- Scope that changed after the SOW. The incoming owner will follow the PDF. If week three added a landing page in Gmail, write that as a dated change.
- Access that only the outgoing person has. Analytics, ad accounts, and staging URLs disappear the day they go on PTO.
- A handoff written from memory. Memory invents deadlines. Sources do not.
If you run an agency, this is the same failure mode as a thin weekly report: the client has to re-explain the account. See Geniusly for agencies and the weekly client report template.
How do you write the handoff in Slack from Gmail and Drive?
- Name the two sources before you write. Example: the Gmail thread with Acme about the launch brief, and the Drive SOW titled "Acme website rebuild — signed." If you cannot name them, you are not ready to hand off.
- Pull facts into the seven sections above. Copy dates and names as they appear. If the email and the SOW disagree, quote both and mark the conflict. Do not pick a winner in the draft.
- Leave blanks visible. Write "owner not named in the thread" rather than assigning someone to look helpful.
- Post the draft in the project Slack channel, not only in a DM. The incoming owner, the outgoing owner, and one other person should see it.
- Ask the outgoing owner three questions: What did I invent? What access is still only yours? What will the client ask tomorrow?
- Send the cleaned version to the client only after those answers. Use the template so the client sees the same shape every time.
Doing this by hand from Gmail search and Drive is fine. It is also slow, which is why people skip it. An AI coworker can draft the first version if it can read those two sources and you still review it.
How can an AI coworker draft the handoff without inventing facts?
Geniusly can read authorized Gmail and Google Drive from Slack and prepare a project handoff for review. It does not send the client email. You stay the person who ships the handoff.
Connect Gmail in a private Geniusly DM (Gmail connection guide), connect Drive the same way when you need the agreement, then in the project channel ask something like:
Prepare a client handoff for Acme using the Gmail kickoff thread from this month and the Drive file "Acme website rebuild — signed." Use the sections: agreed scope, what shipped, what is still open, owners, access, and sources. Quote dates only if they appear in those sources. If a deadline or owner is missing, say it is not in the source. Do not invent a next meeting.
That prompt is the whole method: named sources, a fixed outline, and an instruction not to fill gaps. The project handoff use case shows the same pattern with an illustrative example. It is not a customer result.
If the handoff is really a weekly status, stop and use weekly status reports in Slack instead. A handoff is a change of owner. A status report is a change of week.
What does a finished handoff look like?
Here is the shape, not a real client:
Client: Acme · Project: Website rebuild · Handoff: 24 Oct 2026 · From: Jordan · To: Sam
Agreed scope (SOW, Drive): Five marketing pages, CMS training, not blog migration.
Later change (Gmail, 9 Oct): Acme asked to add a careers page. Jordan confirmed it is a change order. Status of the change order is not in the two sources.
Shipped: Staging URL in the 18 Oct email. CMS login in the Drive "Access" doc.
Open: Logo SVG — last asked of Priya on 16 Oct. Redirect list — owner not named. Final invoice — not in these sources.
Support after today: Sam owns Slack #client-acme. Bug reports go to the staging ticket, not Jordan's inbox.
Notice the change order is flagged as unresolved instead of quietly becoming scope. That is the difference between a handoff and a recap.
Frequently asked questions
What is the difference between a client handoff and a project handoff?
A client handoff is written for the client (or the next account owner facing the client). A project handoff is written for the next internal owner. The checklist is the same; the audience line changes. Geniusly's /templates/client-handoff is the client-facing version. /use-case/project-handoff is the internal Slack version.
Should I send the handoff as a Slack message or a document?
Draft it in Slack so the team can correct it, then paste the final version into email or a Drive doc the client can keep. Do not leave the only copy inside a busy channel.
Can Geniusly send the handoff email?
No. Geniusly can read authorized Gmail and prepare the text in Slack. You review it and send it yourself. It does not create a saved Gmail draft.
What if Gmail and the SOW disagree?
Write both statements and label the conflict. Do not resolve it in the draft. The incoming owner and the client should see the disagreement.
Is a handoff call still needed?
Yes, if the work is complex or the client needs a walkthrough. Send the written handoff first so the call is about decisions, not archaeology.