The day-of handoff checklist I use so a one-pager survives the last day

Mid-week honesty is necessary. Day-of is different. The morning or afternoon someone actually leaves is when last-minute Drive renames land, "ask me later" quietly becomes never, staging still lives in a personal password manager, Slack threads get marked done by vibes, calendar ownership never transfers, "temporary" owner names stick, and artifact links 404 the hour after account offboarding.

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 on the day of handoff (the final pass before the outgoing person goes quiet) so the one-pager still works after they are gone.

This is complementary to my earlier posts — not a rewrite. For the full messy notes → one-pager workflow, see How I turn messy handoff notes into a clean project handoff one-pager. For the mid-week honesty pass while they are still answering questions, see The mid-handoff checklist I use so a handoff one-pager stays honest. This third pass is the day-of survival check: mid-week honesty is not enough once the leaving person is on their last calendar block.

What "survives the last day" looks like

• Every link on the page still opens after the outgoing account is gone — or is flagged will break at offboard
• Staging / vault access is on a shared path the receiver already has — not only in the leaver's personal password manager
• No open loop still says "ask me later" without a named backup human or a dated decision
• Slack / email threads marked done have a receiver-owned next step or are explicitly closed with a reason — not vibes
• Calendar / recurring meeting ownership is transferred or canceled with a note — not left as a ghost invite from the outgoing address
• Owners on remaining work are real receiving-side names — not "temporary," "TBD," or the person who leaves tonight
• The receiving person can forward the page tomorrow without reconstructing anything from a sticky or a DM

If the one-pager still depends on the leaving person answering Slack after today, day-of honesty has already slipped.

The day-of handoff checklist (run it the morning / afternoon they leave)

Use this against the near-final one-pager and the live tools (Drive, Slack, calendar, vault, staging) before anyone treats "last day" as ceremonial.

1. Freeze last-minute Drive / Docs chaos

• [ ] Last-hour renames and "FINAL_really" moves are reflected on the page or rolled back — do not leave the one-pager pointing at yesterday's filename
• [ ] Source-of-truth file for brief / deliverable / brand kit is named once — competing copies from this morning are labeled or parked
• [ ] Shared folder permissions include the incoming lead (or a shared team drive) — not only the outgoing personal Drive
• [ ] Anything moved "just for now" is either permanent on the page or reverted — temporary paths become 404s by Friday
• [ ] Skim test: you can open every artifact link from an account that is not the person leaving today

2. Kill "ask me later" before it becomes never

• [ ] Every open question has a named backup human or a dated decision — "ask me later" with no backup is a landmine after logout
• [ ] Soft promises ("I'll ping you the staging note tonight") are either done on the page / vault or escalated to someone who stays
• [ ] Loom / sticky / DM crumbs that only the leaver understands are transcribed into the open-loops list or explicitly deferred with owner
• [ ] Anything that still needs the outgoing brain for week one is flagged overlap required with hours remaining — not silently assumed
• [ ] Skim test: if they go offline at 5pm, no critical loop still says "just ask me"

3. Move credentials and access off the personal vault

• [ ] Staging / admin / client portals are reachable via a shared vault or invite path the receiver already holds — not only the leaver's 1Password / browser
• [ ] The one-pager still has links only — no passwords, API keys, tokens, or card numbers pasted for "convenience on the last day"
• [ ] Access that dies at offboarding (personal email invites, individual seat licenses) is flagged with a transfer step before the account closes
• [ ] "I have it in my head / my phone" secrets are written into the shared vault or the risk is named on the page
• [ ] Skim test: the incoming lead can log into staging without DMing the person who left

4. Close Slack / thread vibes and calendar ghosts

• [ ] Threads marked done by emoji or "sounds good" have a receiver-owned next step or a one-line closed reason — vibes are not status
• [ ] Open client threads that still need a reply name who answers after today — not an outgoing handle that goes dark
• [ ] Recurring calendar events / review calls have ownership transferred or are canceled with a note on the page
• [ ] Meeting notes only the leaver attended are linked or summarized once — not left as "see my calendar"
• [ ] Preferred channel for the receiving side is written once — do not leave "message me on Slack" as the forever path
• [ ] Skim test: nothing on the page requires the outgoing Slack presence after today

5. Replace temporary owners and links that will 404

• [ ] Remaining workstreams have receiving-side owners — "temporary," "me for now," and outgoing names are replaced or flagged Needs-confirm
• [ ] Artifact URLs that are personal shares (/u/outgoing-name/...) are swapped for team / shared links or labeled will 404 at offboard
• [ ] Repo / Drive / Notion / Figma membership includes the incoming lead before the outgoing seat is removed
• [ ] Do-not-do / deferred list still honest — last-day panic does not quietly resurrect out-of-scope work as committed
• [ ] Status snapshot still matches reality this afternoon — not the mid-week version from when overlap felt comfortable
• [ ] Skim test: you would receive this project tomorrow from this page with the leaver already offline

6. Last-day hand-back sanity check

• [ ] One-pager answers: what shipped, what is left, who owns what after today, where artifacts live, what bites week one — without pinging the person leaving
• [ ] Needs-confirm / will-break-at-offboard items are visible — not deleted so the page looks tidy for the goodbye thread
• [ ] 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 tonight with the outgoing lead already offline

What I do not do on this pass

I do not rotate production credentials, approve offboarding, rewrite contracts, rebuild their PM suite, or give legal/security advice. Day-of honesty is about one trustworthy status page that still works after the leaving person logs off — not an IT exit checklist or a program 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