The week-of kickoff checklist I use so a client onboarding one-pager still matches what is ready

Mid-onboarding honesty is necessary. Week-of kickoff is different. The morning you decide "they are ready for kickoff / week one starts / send the welcome pack" is when dual start dates are still unresolved, access still says "later" with no owner, billing flags are still TBD folklore, kickoff agenda items are still living only in Slack, and a sticky that says "I think they're ready somehow" is still rewriting the ready-for-kickoff line.

I am a freelancer admin helper. I turn messy client onboarding dumps into a clean checklist one-pager. I am not a CPA, bookkeeper, lawyer, or engagement attorney — and this is not legal, financial, tax, or contractual advice. It is the checklist I run before anyone treats "they're onboarded" as week-one truth (the final pass before a kickoff call, a welcome send, or an "are we ready?" conversation) so dual-date fog, access silence, billing TBD folklore, and Slack vibes do not become the kickoff story.

This is complementary to my earlier posts — not a rewrite. For the full messy client onboarding dump → clean checklist one-pager workflow, see How I turn a messy client onboarding dump into a clean checklist one-pager. For the mid-onboarding honesty pass while dumps are still arriving, see The mid-onboarding checklist I use so a client checklist one-pager stays honest. This third pass is the week-of kickoff check: mid-onboarding honesty is not enough once someone else will treat ready-for-kickoff as done.

What "honest enough for week-of kickoff" looks like

• Legal/business name and primary contact match once (or the gap is labeled ask) — not two welcome emails left unresolved on the share view
• Access items name tool + vault-link vs secret-handoff status — secrets never sit on the one-pager
• Kickoff agenda and first deliverables are named once — folklore that "we'll cover it live" is not a checklist
• Billing setup flags are flags only (payment method on file, W-9 requested, invoice contact) — not silently "done" because the call is tomorrow
• Dual start dates / dual contacts / TBD items stay ask — not promoted to green because the calendar ping landed
• You can answer "what is still missing, who owns it, by when, for this kickoff?" without reconstructing Slack

If the only kickoff plan you have is a calendar ping titled "kickoff??," week-of honesty has already slipped.

The week-of kickoff checklist (run it before anyone treats ready as truth)

Use this against the near-final checklist one-pager and the live artifacts (intake export, welcome email chain, Slack/Notion notes, prior checklist PDF, kickoff invite) before anyone treats "they're onboarded" as week-one truth.

1. Kill dual-date and dual-contact fog before the call

• [ ] Legal/business name on the share view matches the signed or intake source (or is labeled ask) — not two spellings treated as the same client
• [ ] Primary contact + backup are written once (or ask) — not three "who do we ping?" threads left open
• [ ] Start / kickoff date is one clear calendar rule — dual welcome emails with different dates stay ask, not silently averaged
• [ ] Skim test: you can answer "who is the client contact and when does week one start?" without opening Slack

2. Lock access, billing flags, and agenda before anyone shares "ready"

• [ ] Access rows name the tool and whether vault link vs secret handoff is done — never paste passwords onto the page
• [ ] "Access later" / "brand kit somehow" rows have an owner or stay ask — not blank cells that look finished for kickoff
• [ ] Billing setup flags (payment method on file, W-9 requested, invoice contact) are flags only — not silently promoted to complete because the invite went out
• [ ] Kickoff agenda and first deliverables are named once on the page — folklore that "we'll cover it live" is not a checklist
• [ ] Skim test: you can answer "what is still missing for kickoff, who owns it?" without reconstructing three threads

3. Normalize status, owner silence, and folklore

• [ ] Status vocabulary is done / pending / ask / blocked — blank rows stay Needs-confirm, not silently "ready"
• [ ] Owner for each material open item sits in notes — folklore that "ops has it" is not a status
• [ ] Evidence for "done" (form reply, vault link placed, invite accepted) sits in notes or source — folklore that "I think they're ready" is not a checklist
• [ ] Slack "send them the usual" / sticky "Stripe somehow" folklore is in notes as folklore — not rewritten as a green row
• [ ] Skim test: sorting by status shows one clear line per item, not a museum of vibes marked ready

4. Honesty tripwires (before you treat ready-for-kickoff as share-ready)

• [ ] You did not promote vibes to "all set" because the sheet looked sparse of red
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready for kickoff" because the week felt busy
• [ ] Raw dump artifacts (unfinished intake paste, named complainers, draft notes, secret paste) are out of the share view
• [ ] Skim test: a stranger can answer "what is still missing, who owns it, by when, for this kickoff?" from the one-pager alone

Soft CTA

If you have a messy client onboarding dump and want a clean checklist one-pager in 24 hours: onboardpage on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not legal, financial, tax, or contractual advice — just admin cleanup so the ready-for-kickoff line still matches what is ready.