A Slack dump titled "handing this off," a Drive folder with three versions of the same brief, a Loom you have not watched, and a sticky that says "ask Sam about the staging password" are not a handoff. They are how the next person spends week one reconstructing what already shipped.
Here is the workflow I use when someone dumps messy client or project handoff notes on me and wants one page that says what was done, what is left, who owns what, and how to keep moving without a scavenger hunt.
What "good enough" looks like
- Status is one screen: done / in progress / blocked / deferred — not a novel
- Deliverables and file locations are named so the next person can find them
- Open loops and known bugs sit in a short list, not buried in chat
- Access, owners, and preferred channels are listed once
- Dates that matter (last ship, next review, contract end) are explicit
- The receiving person can forward the page without a 20-minute explainer
Intake checklist
- The handoff dump (call notes, Slack/email threads, Loom/transcript, Notion/Docs dump, folder links)
- Any SOW / proposal / kickoff page already shared (so I do not invent scope)
- Who is leaving vs who is receiving, and who still answers questions for a week
- Hard constraints (access expiry, client quiet hours, tools, brand, compliance)
- What "done with handoff" means for them (aligned one-pager, shared folder map, first check-in booked)
The pass order that saves time
- Inventory — pull every claim about status, deliverable, owner, access, date, and risk.
- Separate shipped from vibe — finished work and real blockers stay; "we should someday…" goes to deferred / open questions.
- Normalize owners — one name per workstream; no "the team" as a fake owner on the receiving side.
- Map the artifacts — live links to the current brief, latest build, staging, brand kit, credentials vault (link only — never paste secrets into the page).
- Flag gaps — missing acceptance criteria, expired access, unclear who talks to the client next.
- Build the one-pager — status, people, artifacts, open loops, risks, next 7–14 days.
- Hand back — the handoff page only; no rewriting their contract or building a full PM system unless they asked separately.
One-pager sections that work
| Section | What goes here |
|---|---|
| Project name | Working title + one-line purpose |
| Handoff date / from → to | Who is leaving, who is receiving |
| Status snapshot | Done / in progress / blocked / deferred in plain English |
| What shipped | Deliverables the client already has (with links) |
| What is left | Remaining work with owners — not wish-list fluff |
| Artifacts & access | Brief, repo/Drive, staging, brand kit, password vault links only |
| People | Client lead, outgoing lead, incoming lead, preferred channel |
| Open loops | Bugs, decisions pending, questions still unanswered |
| Risks / watch-outs | What will bite the next person in week one |
| Next 7–14 days | Concrete actions with owners and dates |
| Do not do | Explicit out-of-scope / deferred so scope does not quietly expand |
Common traps
- Pasting passwords, API keys, or full card numbers into a "handoff" doc that gets forwarded
- Writing a second project plan instead of a readable status page
- Leaving "TBD" on every owner so nothing is actionable for the receiving person
- Mixing brainstorm ideas into remaining committed work
- Listing folders without saying which file is the current source of truth
- Skipping "do not do" so week-two change requests land as if they were always in scope
Soft handoff
When the page is done, send:
- The project handoff one-pager
- A short list of open loops and missing access that still need a human confirm
- One suggested next step (book a 30-minute receiving check-in, or rotate the outgoing person off client chat)
That is the whole job. No full PM suite rebuild required for a handoff cleanup pass. I am a freelancer admin / spreadsheet person, not a project manager or CPA — this is status and artifact hygiene, not legal advice or professional project governance.
I do this as a 24-hour DFY service for freelancers and small businesses ($12 for messy handoff notes → clean project handoff one-pager). Shop: https://brittanybonds.gumroad.com/l/handoffpage — code ADMIN12 for $2 off. Full catalog: https://brittanybonds.gumroad.com/ and https://brittany-bonds.github.io/
Top comments (0)