The client onboarding checklist that prevents every later argument

The short answer

• Onboarding is one checklist, run the same way every time - not charm, not improvization.
• Collect the practical list first: who approves invoices, who to ask questions, where files live, how they prefer updates.
• Put the scope and the not-included list in writing before any work starts. The not-included list is the part that saves the relationship.
• Say the money words out loud: rate, invoice timing, payment terms, late policy. Silence here is where late payments are born.
• Set the communication rhythm in week one: when you'll update, how, and what an urgent thing looks like.

The first week, in order

1. Day one: the welcome note - what happens next, when, and the single question list (access, contacts, files, brand materials).
2. Day one or two: the scope note - the work, the deliverables, the dates, and the not-included list, sent for a yes in writing.
3. Before work starts: the money note - rate, invoice schedule, payment terms, and the late-payment steps in plain words. Agreeing this before work is what makes chasing later neutral instead of awkward.
4. First working session: the rhythm - standing update day, response-time expectations both ways, and the escalation path for urgent items.
5. End of week one: the recap - what got done, what's next, anything you need. The recap in week one sets the expectation for every week after.

What this prevents

• Scope creep - because 'we assumed' has nowhere to live when the not-included list exists.
• Late payments - because terms agreed in advance make the reminder administrative instead of confrontational.
• Ghosting - because a client who chose a communication rhythm in week one has agreed to answer.
• The mystery client - because you asked who approves invoices on day one, not on day forty.

The free tool for this

A project price from the work you actually listed - A project price from the work you actually listed. It runs in the page, asks for your own numbers, and sends nothing anywhere.

If you would rather not build it yourself

Client OS runs this as a system: /onboard generates the welcome pack from one client record, the scope note and the not-included list are templates, and the invoice policy attaches to the client so every invoice and reminder follows it automatically. ClientOS is $19. See it on the shop, and there is a plain page about it here: what it holds.

Questions people actually ask

Isn't this a lot of process for a small client?

The checklist scales down - a two-line scope note and one message about payment terms still covers the three things that cause 90% of later problems. Process that fits in one message is not overhead; it's insurance.

What if the client resists written scope?

Resistance to writing down what was agreed is itself information. Gently insist on at least a confirming email - 'just so I build it right' - and price the ambiguity you're being asked to carry.

Read next

How to keep track of unpaid invoices without a system you hate, What to look for in a client tracker before you pay for one, How to write a late payment reminder that actually gets paid, The one-page weekly review for a one-person business, What every invoice line item should say (and what never to write).