The mid-handoff checklist I use so a handoff one-pager stays honest

A Slack dump titled "handing this off," three Drive folders with the "final" brief, a Loom nobody finished, and a sticky that says "ask Sam about staging" are not a handoff you can trust mid-week. Mid-handoff is where done quietly becomes almost-done, passwords land in the shareable page, and "the team" becomes a fake owner for everything still open.

I am a freelancer admin helper. I turn messy handoff notes into a clean project handoff one-pager. I am not a CPA, project manager, lawyer, or IT security consultant — and this is not financial, tax, legal, compliance, or professional project-management advice. It is the checklist I run mid-handoff (and again before anyone treats the page as the source of truth) so the one-pager stays honest while the outgoing person is still answering questions.

(If you want the full messy handoff notes → clean project handoff one-pager workflow, see my earlier post. This one is the second-pass checklist so status drift, pasted secrets, fake owners, and ghost artifacts do not quietly rewrite what the next person thinks already shipped.)

What "honest" looks like mid-handoff

• Status is one screen: done / in progress / blocked / deferred — not a vibe paragraph that hides blockers
• Every remaining workstream has one named owner on the receiving side — not "the team"
• Deliverables link to the current file or folder — not three competing "final_v2" copies
• Open loops and known bugs sit in a short list the receiver can act on without replaying Slack
• Access is links to the vault / invite path, never passwords, API keys, or card numbers pasted into the page
• Dates that matter (last ship, access expiry, next review, contract end) are explicit or flagged unknown
• The receiving person can forward the page without a 20-minute explainer call

If the only "handoff" you have is a sticky labeled "ask Sam?" mid-handoff honesty has already slipped.

The mid-handoff checklist (run it before / while you clean)

Use this against the dump (call notes, Slack/email threads, Loom/transcript, Notion/Docs dump, folder links, SOW scraps) before you paste everything into a pretty template and call the transfer done.

1. Inventory the dump (same day you open the pile)

• [ ] Every scrap is listed once: source, date seen, claim type (status / deliverable / owner / access / date / risk), notes
• [ ] SOW / proposal / kickoff page (if any) is treated as scope evidence — not ignored because "we're past kickoff"
• [ ] Partial claims ("Sam knows," "staging is somewhere," a Loom with no timestamp) are labeled incomplete — not invented into tidy rows
• [ ] Secrets (passwords, API keys, tokens, full card numbers) are marked strip-or-vault-link-only — never copy into the shareable one-pager
• [ ] Anything clearly deferred, out of scope, or "nice someday" is labeled stay-off-remaining — do not resurrect as committed work

2. Separate shipped from vibe before you trust status

• [ ] Done = the client already has it (with a link or artifact name) — not "we mostly finished"
• [ ] In progress has a named owner and a next visible step — not a fog of activity
• [ ] Blocked names the blocker and who can unblock — not "waiting on stuff"
• [ ] Deferred / do not do is explicit so week-two change requests do not land as if they were always in scope
• [ ] Skim test: you can answer "what actually shipped last?" without re-watching the Loom

3. Lock owners, people, and channels the receiver needs

• [ ] Outgoing lead vs incoming lead are named — "the team" is not an owner on open work
• [ ] Client lead / preferred channel is written once — not buried in three threads
• [ ] Who still answers questions for ~7 days is explicit (or flagged overlap unclear)
• [ ] Quiet hours / escalation path noted when present — blanks stay blank or flagged, not guessed
• [ ] Skim test: the receiving person knows who to ping first without asking Sam on Slack

4. Catch artifact and access ghosts

• [ ] Brief / repo / Drive / staging / brand kit / vault each have one current link — competing "final" copies are labeled or parked
• [ ] Access is invite path or vault link only — no secrets pasted into a doc that gets forwarded
• [ ] Expired or about-to-expire access is flagged with a date when known — neat formatting does not renew a login
• [ ] "Folder dump" without a source-of-truth file is labeled map incomplete — do not pretend the tree is navigable
• [ ] Skim test: you can open the current brief and latest deliverable without reconstructing the Drive archaeology

5. Honesty tripwires (before you treat the page as handoff-ready)

• [ ] You did not leave passwords, keys, or card numbers on the shareable page
• [ ] Fake owners ("TBD," "the team," blank) on remaining work are flagged Needs-confirm — not silently presented as assigned
• [ ] Status that came from a two-week-old Slack vibe is labeled status unverified until confirmed — pretty tables do not make it current
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to Done because the page looked empty
• [ ] Open loops list is short and actionable — not a second novel of chat quotes

6. Hand-back sanity check

• [ ] One-pager answers: what shipped, what is left, who owns what, where the artifacts live, what bites week one — without opening the dump
• [ ] Needs-confirm / Deferred views (or sections) exist so incomplete and out-of-scope items are not deleted into amnesia
• [ ] One sentence of scope on the page: "project handoff one-pager — not a full PM system, contract rewrite, or security audit"
• [ ] Non-advice line present: not CPA / PM / legal / security advice; confirm access and status with humans before treating this as gospel
• [ ] You would be willing to receive this project from this page without reconstructing Sam from a sticky note

What I do not do on this pass

I do not rebuild their PM suite, rewrite their contract, rotate production credentials, approve scope changes, or give legal/security advice. Mid-handoff honesty is about one trustworthy status page the next person can forward — not a program management office in a Google Doc.

Soft CTA

If you want the messy pile turned into that one-pager for you: Messy handoff notes → project handoff one-pager — usually within 24 hours. Code ADMIN12 takes $2 off. Shop: brittanybonds.gumroad.com · catalog mirror: brittany-bonds.github.io