Client Onboarding Process: Five Steps and a Free Checklist

Why client onboarding goes wrong

The delays usually come from waiting: for logins, for files, for the one person at the client who knows the password. Owners online describe the same pattern of wrong screenshots, access to the wrong account and the fourth identical reminder.

Underneath that sit two gaps. Nobody on your side owns the chasing, so it happens when someone remembers. And the client has never been told exactly what you need and by when, so they send it in pieces.

Onboarding is also where a client decides whether you're organised. They can't judge your work yet, only whether the first two weeks felt clear.

The five steps of client onboarding

In a team of five, the seller and the person running the work are often the same, and sometimes that's you. Write the name down anyway, because the next client might be handled by someone else.

1. Confirm the agreement

Work shouldn't start on a handshake and a friendly email. Get the agreement signed first, with the scope, price and payment terms in writing. Write down what's not included too, or the edges of the scope are left to argue about later.

Send any deposit or up-front invoice now. Some firms also have checks they're required to do before taking a client on. In the UK, for example, accountants and other firms covered by anti-money laundering rules must check a client's identity before the relationship starts. Rules differ by country and sector, so check what applies to you. This post isn't legal advice.

If new enquiries often turn out to be a poor fit, put a short client intake form in front of the first call. It catches mismatches on budget, timing and scope before anyone signs.

2. Send one welcome message

Within a working day of signing, send one message from the person who'll look after the client. Keep it short. It needs three things:

• what happens next, as a short list with rough dates
• who to contact on your side, and for what
• a kick-off date, or two to choose from

Save it as a template, so no detail gets dropped.

3. Collect everything on one list

This is the step that usually stalls. Send a single request list with everything you need: logins or access, files and brand material, the client's contacts, and any background you'll need to do the work. Put one deadline on the whole list, and next to each item name who at the client is likely to have it. Clients often don't know who holds the admin account, and the question prompts them to find out.

Test access the day it arrives, so "it should work" doesn't become a lost morning later. Then set a day for chasing, such as two working days after the deadline, so it doesn't depend on someone's memory.

4. Hold a kick-off

Hold the kick-off once the essentials are in, so it isn't spent asking for passwords. Use it to agree the things that cause trouble later:

• the scope, read back in plain words
• what a good result looks like, in the client's own words
• how and how often you'll update them
• what happens when they ask for something extra

That last one matters most. Agree now that extra requests get written down, priced and approved before the work starts. It's a much easier conversation in week one than in month three. The change request process has a simple form for it.

Send the notes and actions the same day. There's a fuller agenda, by kind of work, in the client kick-off meeting agenda.

5. Check in after the first delivery

Onboarding ends when the first piece of work is delivered and you've asked how it went. A short call or message is enough: is this what you expected, and should we change anything? Small problems are cheap to fix now and expensive once they're habits.

Then mark onboarding as done and add anything you learned to your master checklist. If the check-in turns up a real problem, handle it as a complaint, promptly and in writing.

Client onboarding checklist

Copy this for each new client, and tick through it here to see how far along you are.

A typical example

This one is made up, but typical. A five-person web design studio signs a new client on a Tuesday. The person who sold the job sends the welcome message the same afternoon, with a kick-off date the following week. The request list goes out on Wednesday: hosting login, domain account, brand files and the name of whoever approves designs. Each item has a likely contact next to it, and everything is due by Monday.

By Monday the hosting login is in and tested, but nobody at the client knows who owns the domain account. Because the list named a likely person, the client's office manager finds it in an old email from their previous web designer. The kick-off goes ahead with everything in place. It covers updates (a short written note every Friday) and extra requests (logged and priced before work starts).

Three weeks in, the client asks for "one more page". It goes on the change log with a price, they approve it, and nobody has an awkward conversation about it later.

Monthly clients and one-off projects

The five steps are the same for both. What changes is where the weight falls.

A one-off project leans on confirming and kicking off. The price rests on the scope, so it has to be exact, and the kick-off has to agree what finished looks like and who signs it off. Collecting is usually one burst of files and a login or two. The end is already in sight, so the offboarding list at the bottom of this page matters as much as the welcome.

A monthly arrangement leans on collecting and checking in. You'll need lasting access, often to several accounts, and you may be taking over from another provider. Ask for their notes, and agree the date they stop and you start. At the kick-off, agree the routine: what arrives each month, on which day, and how you'll report on it. Give the scope a monthly limit, such as hours or pieces of work, so extra requests have something to be measured against.

Monthly work also needs a second check-in, after the first full month, once the routine has run and its small problems have shown up. After that, a quarterly client review takes over.

Common client onboarding mistakes

Starting work before the agreement is signed. It feels helpful, and makes the scope impossible to hold.

Asking for things in pieces. Five separate emails asking for five things will get five separate delays. Send one list.

Nobody owns the chasing. If it's everyone's job, it happens when someone remembers. Put one name on it, and a day.

A kick-off with no rule for extra requests. Without one, every "quick change" becomes a negotiation, or free work. Our RACI chart template helps if you're unsure who should approve what.

Onboarding that never ends. Without a check-in, nobody asks whether it's going well. Close it properly, then move the client into your normal delivery rhythm, with a quarterly client review for the ones that matter most.

Keeping it in one person's head. If the person who looks after a client leaves or goes on holiday, a handover document stops the client noticing. Once the checklist works, turn it into a short procedure the whole team uses. How to write an SOP that actually gets used shows how.

If you came here looking for how to welcome a new member of staff, that's a different process. See the employee onboarding checklist.

When the work ends: a short offboarding list

Onboarding has a mirror image. When a contract finishes, a few steps stop loose ends turning into awkward emails months later:

• confirm the end date in writing
• deliver the final work and hand back any files that belong to the client
• send the last invoice, and check nothing is left unbilled
• remove your access to their accounts, and theirs to yours where it should end
• ask for feedback, and whether they'd be happy to recommend you

A clean ending makes it easier for a client to come back, or to send someone your way.