Client onboarding process checklist
The client who ends up chasing you a week later
Here is the pattern. A new customer signs up on a slow Tuesday and you ask them everything you need, calmly, in order. Then a new customer signs up on a manic Thursday between two jobs and you get their name, their address, and a "we'll sort the rest later" that never quite gets sorted. A week in, you are the one sending the awkward follow-up message asking for the gate code, or the invoice email, or whether the dog bites. Every client gets a slightly different welcome depending on how busy you were the day they joined, and the gaps only show up once you are already halfway through the job.
A client onboarding checklist fixes this. It is just a fixed list of the information and admin you need from a new customer before you start the work, written down once so you are not reinventing it from memory every time someone new signs up. It is not a contract and it is not a script for what to say. It is the list of facts and permissions you need in hand before day one, so day one goes smoothly regardless of how frantic the week has been.
Building one properly
The trick is that you already have the checklist. It is scattered across every awkward follow-up text you have ever sent a client. The method is just collecting that scattered knowledge into one document, once, so you stop rebuilding it from memory under pressure.
Step 1: pull up your last ten new clients and write down what you had to chase
Not what you asked for up front. What you had to go back and ask for afterwards, because it was missing and something stalled without it. Text threads and email are the best source here, because the chasing message is usually still sitting there.
Step 2: sort those chased items into a small number of categories
Most small businesses land on four or five: contact details, access and logistics, payment, safety or legal information, and preferences. Anything that does not fit one of your categories either gets its own category or gets cut, because if you cannot say why you are collecting it, you probably do not need it.
Step 3: for each item, write down what actually breaks if you do not have it by day one
This is the step almost everyone skips, and it is the one that makes the checklist worth having, because it tells you which items are genuinely non-negotiable and which are just nice to know.
Worked example: a mobile dog groomer
Say you run a made-up mobile dog groomer called Bark & Suds (not a real business, just an example to make this concrete). You groom dogs at the client's home, so your chased-information list, once you actually go and look at your old messages, might read like this.
| Information needed | Why it matters | What goes wrong if you skip it |
|---|---|---|
| Parking or access instructions | You are driving a van full of gear to a house you have never been to | You circle the block for ten minutes and the next client's booking starts late |
| Whether the dog is reactive or has bitten before | You are alone with an animal you do not know | You get bitten, or the dog bolts, on the first visit |
| Preferred payment method and timing | You need to get paid without an awkward conversation on the doorstep | You end up invoicing after the fact and chasing payment for weeks |
| Coat and skin conditions | Some products and tools are wrong for certain skin issues | You use the wrong shampoo and the dog has a reaction |
| Emergency contact if owner is not home | Some clients want the groom done while they are out | Something goes wrong and there is no one to call |
Notice none of these are things Bark & Suds asks because they are curious. Every row exists because it went wrong once and got written down afterwards, in a chasing message. That is the whole method: your checklist is just your history of chasing, organised.
Step 4: turn the list into one document with a trigger point
Each item needs a moment it gets collected: before the booking is confirmed, before payment, or before the technician turns up. Bark & Suds might decide access instructions and reactive-dog info are collected before confirming the booking, and payment details are collected once the booking is confirmed. Without a trigger point, the checklist just sits there and everyone reverts to asking whatever comes to mind on the day.
Step 5: run it on the next real client and fix what is missing
The first version is always wrong somewhere. Run it once, notice what you still had to chase, and add that row. This is a living document, not a one-off exercise.
What good looks like, versus what most people produce
Most small operators have a version of this checklist already, it just lives in their head and comes out slightly different every time depending on mood, tiredness and how many other things are going on that day. That is the informal version, and it is the reason onboarding feels inconsistent even though you are the same competent person every time.
A good checklist is written down, has a category for every item, has a trigger point for when it gets collected, and has a reason attached to each line so a future version of you (or someone you eventually hire) knows why it is there and will not quietly drop it. A bad one is a mental list, exists only in the busy person's head, and gets applied inconsistently because it was never actually inconsistent by design, just inconsistent by circumstance.
The three mistakes that make it useless
The first is making it too long. If you ask for everything you could conceivably ever want to know, new clients feel like they are filling out a loan application instead of signing up for a service, and the ones with less patience just stop halfway through. Every line should earn its place with a real story behind it, like the ones in the worked example above.
The second is not attaching a trigger point. A checklist with no moment it gets used just becomes a document you wrote once and never open again, because nothing prompts you to check it mid-conversation.
The third is treating it as finished. The business changes, the services change, and a checklist that was right eighteen months ago quietly stops matching what you actually need. If you have not added a row to it in the last few months, it is probably out of date, not perfect.
What to actually do with it once it is written
This is the part most articles on this topic skip entirely: a checklist sitting in a notes app does nothing on its own. It needs to become something you actually use at the moment a new client signs up, which usually means one of two things. Either turn it into a short intake form (a free tool like Google Forms works fine) that a new client fills in themselves before you start, or turn it into a welcome message template you send manually that walks through each item in the same order every time. Either way, the goal is the same: the checklist should do the remembering, not you, on the day you are least likely to remember.
Doing this properly takes an afternoon, sitting down with your old messages and actually building the categories, the trigger points and the reasons out. If you would rather have it done for you, a SOP: Client Onboarding built from your own answers is $99.