A project handoff without a checklist depends entirely on the outgoing person remembering to mention everything that matters, under time pressure, often while also wrapping up their own work. The details that get dropped are rarely the big ones, they're the small, easy-to-forget context that makes the difference between a smooth transition and a confused client.
A good handoff checklist isn't about covering every possible detail. It's about capturing the specific things that live only in one person's head.
A handoff that relies on one person's memory isn't a process
An informal handoff, a quick call or a short message, works fine when nothing important gets left out, and there's no way to actually verify that in the moment. A checklist exists precisely to catch what an unaided memory would miss under pressure.
Capture the context behind decisions, not just current status
"Here's where things stand" tells the incoming person what's true right now, not why it got that way. Include the reasoning behind key decisions, why a certain approach was chosen, what was already tried and rejected, so the new owner doesn't unknowingly revisit settled ground.
In Stelaah, a project's full history, decisions, files, and client conversations stays attached to the record, so a handoff can point to the real context instead of trying to summarize it from memory. See how projects works.
Name what hasn't been communicated to the client yet
The gap between what the team knows and what the client's actually been told is one of the easiest things to lose in a handoff, and one of the most damaging when it happens. Explicitly list what the client doesn't know yet, not just what they've already been told.
Include the small client preferences that never make it into a brief
How a specific client likes to be communicated with, what tends to frustrate them, what they've mentioned liking, rarely makes it into a formal brief but genuinely affects how the relationship goes. Capture these small, informal preferences explicitly rather than letting the incoming person relearn them the hard way.
Confirm the receiving person actually understood it, not just received it
Sending a completed checklist isn't the same as the new owner actually absorbing it. Have a short conversation after the handoff document is shared, specifically to surface questions, rather than assuming silence means full understanding.
A simple checklist
If you do nothing else, do these five things:
- Capture the reasoning behind key decisions, not just current status.
- Name explicitly what the client hasn't been told yet.
- Include the small, informal client preferences that never make it into a brief.
- Confirm understanding with a real conversation, not just a document handoff.
- Never rely on one person's memory as the actual handoff process.
Do that, and a project handoff stops depending on what one person happens to remember to mention.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
