Client Onboarding Checklist | 46 Items With Owners

This client onboarding checklist runs six phases and 46 items, from signature to the formal onboarding close. Every item carries an owner and an exit criterion, so you can tell a ticked box from a moving project. It is built for agencies, studios, consultancies and implementation teams. The whole checklist sits below, ungated, with an interactive version you can run in your browser.

Client onboarding or customer onboarding? Pick your checklist in 30 seconds

Client onboarding starts a paid service relationship. You have a signature, a scope, a sponsor on the other side, and a delivery team that needs assets before it can start.

Customer onboarding gets end users live inside a product. You have a login, an activation event, and a user who never signed anything.

So if your job is getting users to first value inside software you built, this is the wrong page. Go to the new customer onboarding checklist or the customer onboarding best practices guide instead. Everyone else stays here.

This distinction matters because the word "client" is used across accounting, legal, agency and consulting work. The exact documents change by industry. The operating system does not: capture the promise, clear the asset gate, agree the approval route, deliver first value and close onboarding in writing.

How to use this client onboarding checklist

Copy it per engagement. Do not keep one master copy that everyone edits at once. Then assign owners at kickoff, on both sides, by name.

Every item carries four attributes:

• Item. The thing that happens.
• Owner. One named person. Not a team, not "we".
• Exit criterion. The observable state that proves the item finished.
• Timebox. How long the phase gets, not how long the engagement gets.

The exit criterion is the part most checklists skip, and it does most of the work. "Send welcome email" is an activity. Someone can tick it while the client sits in silence. "Welcome email sent, onboarding owner named, kickoff slot booked" is an exit criterion. It cannot be true while the project is stuck.

Timeboxes sit on phases rather than items, because items inside a phase run in parallel. That is why each phase below has one timebox and one failure signal, instead of eight small deadlines nobody tracks.

The escalation rule, agreed before you start: if a phase overruns its timebox by 48 hours, a named person picks up the phone. Not another email. Not a nudge in the shared channel. A call, from someone the client already knows, on the day the clock runs out. Write that name into the checklist at kickoff, so nobody has to decide who it is at the moment it matters.

Phase 1: Signature to day 1 (confirm and capture)

The client signed. Now nothing happens for a while, because internally the deal moved to "won" and everyone looked away. This is the window where buyer’s remorse compounds unnoticed.

Timebox: 24 hours. Sales owns the handoff document. Delivery owns everything else.

The same-day welcome rule

Send the welcome message while the agreement is still fresh. The point is not an arbitrary one-hour target. It is continuity. A client should never wonder whether the signed agreement reached the delivery team or what happens next.

Exit criterion for phase 1: the client has a named contact, a questionnaire link and two kickoff options.

Failure signal: silence for more than 24 hours after signature. If you measure signed-to-first-touch in days, fix that before you fix anything else on this list.

Phase 2: Intake and the asset gate (days 1-3)

The work is not what delays most projects. A missing logo file does, plus a CMS login and one person on the client side who is on holiday until Tuesday.

Timebox: 3 business days, with one reminder at 48 hours. The delivery lead owns the chasing. The client sponsor owns the delivering.

The asset gate rule

Work does not start until the gate clears. You tell the client that in phase 1, not in week 3. Say it in the welcome email, then say it again on the kickoff agenda.

A gate announced in advance reads as a professional standard. The same gate announced after a slip reads as an excuse. That difference in timing is worth more than any project management tool you can buy.

Exit criterion for phase 2: every asset row is either received, or it carries a named owner and a date. Not "chasing". A name and a date.

Failure signal: you are still chasing logins in week 3. The client experiences that as vendor slowness, even though the delay came from their side, because you are the only person keeping score.

Phase 3: Kickoff (days 3-7)

Kickoff has one job: produce an artifact both sides signed. But a pleasant call that ends with "great, we’re all aligned" produces nothing you can point at in week 8.

Timebox: kickoff happens inside week 1.

The mutual success plan, in six lines

Copy this structure directly. It fits on one page, and you will reread it in week 8 when someone says this is not what we agreed.

1. Outcome. What the client is hiring you for, in the client’s own words, not in your service language.
2. Metric with baseline. The number that proves it worked, plus what that number reads today. A success metric without a baseline is theater.
3. Milestones with dates. Three to five, each with a date, each visible to both sides.
4. Owners on both sides. Named people per milestone. Yours and theirs.
5. Out of scope. The explicit list of what this engagement does not include.
6. Escalation path. Who calls whom, and when. Same rule as the top of this page, written where the client can see it.

Exit criterion for phase 3: the client sponsor signs the success plan. Attending the call does not count.

Failure signal: a pleasant kickoff that produced no artifact. If nothing left the call that a third party could read, you held a meeting, not a kickoff.

Phase 4: Setup, access and internal readiness (week 2)

Phases 1 to 3 face the client, while this one faces your own team. The test is blunt. Can production start on Monday without anyone sending the client another question?

Timebox: 5 business days. The delivery team owns the work, with a named client-side admin behind every access dependency.

The Monday test

Read item 30 again, because it is the one teams skip. Discover the approval route during the first review instead of before it, and a two-day review becomes a nine-day review. The date you committed at kickoff then dies quietly.

Exit criterion for phase 4: the team can start production work without asking the client another question.

Failure signal: anyone on your team asks "who signs off on this?" after the work has already started.

Phase 5: First deliverable and first value (weeks 2-4)

Show something small in week 1 or week 2. Not the finished thing. A rough cut, a first module, a working screen, a five-minute walkthrough recording.

Big reveals in week 6 create revision spirals, because the client has spent six weeks imagining a different project. They then have to reconcile it with yours in a single meeting.

Timebox: first deliverable accepted by day 30 for most engagements.

Item 37 separates onboarding from delivery, because watching someone do it once is the only reliable proof that training landed. Everything else is attendance.

Stop explaining the same thing on every engagement

If your team explains the same setup or the same workflow on every single engagement, that explanation belongs in a short structured video. Not on another call.

Run the arithmetic with your own numbers, because someone else’s benchmark will not convince your CFO. Count how many times your team gave that explanation live last quarter. Multiply by the call length. Multiply by the loaded hourly cost of the people on those calls.

That figure is what one recorded, reusable explanation is worth to you. It is usually larger than people expect, and it decides whether structured customer education is a nice idea or an obvious one.

Exit criterion for phase 5: the client accepts the first deliverable, and can operate the part that is theirs.

Failure signal: the client asks you to do something in month two that you already trained them to do in week 3.

Phase 6: Close onboarding formally (day 30)

Onboarding ends here, on a date, in writing. Without that moment, the engagement drifts into delivery with no review, no baseline and no clean handoff.

Timebox: day 30.

Onboarding needs an end date

Teams often treat go-live as the finish line. The account then drifts into delivery with no review, no baseline and no handoff. Nobody says the word "finished", so nobody notices when the original goal quietly stops mattering.

Put day 30 in the calendar during phase 1, before anyone has a reason to avoid it.

Exit criterion for phase 6: the review happened, and the success plan is either met or formally revised. Nobody on either side is guessing what "done" means.

The client onboarding flow chart

The chart maps the six phases of this client onboarding checklist, plus the three decision points where real engagements come apart.

• Assets not delivered by day 3. Send the outstanding-rows list to the sponsor, not to the day-to-day contact. If the gate is still open at day 5, the delivery lead calls the sponsor and moves the first deliverable date in writing. Absorbing that delay silently turns their problem into your reputation problem.
• Kickoff no-show. Rebook within 24 hours with two new dated options. Send the agenda and the draft success plan anyway. A no-show usually means you invited the wrong person.
• Client goes quiet for 5 days. Message the day-to-day contact, call the sponsor on day 6, then send a written summary of what stops and what the pause costs. Quiet clients are rarely angry. Usually something inside their own organization has blocked them, and one senior call clears it faster than five emails.

Real onboarding is not a straight line, so the recovery branches matter as much as the happy path.

Download the flow chart: SVG. Embed it on your own site or in a deck if it helps. Please credit corsoproduction.com with a link.

Use the interactive checklist

The complete client onboarding checklist sits above. You can copy all 46 items from this page right now.

The interactive version turns it into a working tool:

• Filter all 46 items by phase.
• Track completion without editing the source.
• Keep progress in your browser while the engagement runs.
• Print or save a clean PDF snapshot for your kickoff pack.
• Reset the checklist for the next engagement.

No account required. Use it, adapt it and move it into the system your team already trusts.

Adapt it: SMB, enterprise and SaaS implementation variants

One client onboarding checklist applied to every segment is why teams abandon checklists by the third project. Enterprise rows suffocate a three-week SMB engagement, while the SMB version leaves a procurement team unmanaged. So adjust before you start, not halfway through.

SMB (engagements under roughly 6 weeks). Compress phases 2, 3 and 4 into week 1. Cut the security review rows. Run one kickoff instead of a kickoff plus a technical session. Name a single approver in writing, with a deputy for holidays. Keep the asset gate and the 30-day review. Those two do the work, and they are the first two things people delete.

Enterprise. Add procurement and vendor onboarding as their own rows, with their own owner, because that process runs on a calendar you do not control. Add the security questionnaire, SSO configuration and the data processing agreement. Build a second stakeholder map for people who can veto without attending. Extend the asset gate to 10 business days, and expect access provisioning to be the long pole. Send a fortnightly written status to the executive sponsor even when nothing changed.

SaaS implementation. Add technical discovery, data migration, environment mapping and a go-live checklist with a rollback plan. Add a defined UAT window, with named testers and a pass or fail criterion. Once your users are live inside the product, the job changes from client onboarding to customer onboarding. You then switch to the product-side list: the new customer onboarding checklist covers that half.

Calculate what onboarding delays cost your team

Generic retention statistics will not tell you whether your own onboarding process deserves attention. Your calendar will.

Pull your last ten engagements and record four numbers: days from signature to first accepted deliverable, hours spent chasing assets, hours spent repeating the same explanation, and hours lost to rework after a late approval. Use the median rather than the average so one exceptional project does not distort the baseline.

The interactive calculator on this page multiplies those hours by your loaded team cost and engagement volume. It is not an industry benchmark. It is a model built from your own operating data, which makes it far more useful in a budget conversation.

Run this checklist for the next ten engagements, then compare the same four numbers. If signed-to-first-deliverable time falls but rework rises, you did not improve onboarding. You moved the delay downstream.

Five ways client onboarding checklists fail

1. Activities without exit criteria. Someone ticks the box while the project stands still. "Send training materials" becomes true the moment an email leaves, and nothing about it says the client can do the thing.

2. Items nobody owns. Assign a task to "the team" and nobody owns it. Checklists written in passive voice are the common version. A row reading "accounts set up" never names who does it, so it happens the day someone notices it did not.

3. One checklist for every segment. A security questionnaire row is essential for a 200-person enterprise and absurd for a four-week SMB project. Teams do not maintain a checklist that makes them feel stupid, so they stop opening it.

4. No asset gate. Work starts on promises and stops on missing logins. The delay is real, nobody bills it, and the client remembers it as your slowness.

5. The client onboarding checklist ends at go-live. Nobody declares onboarding finished, so there is no review, no feedback, no handoff and no baseline. The first check on the original goal then lands at renewal, which is the worst possible moment to find out.

FAQ

What should a client onboarding checklist include?

A client onboarding checklist should include six phases from signature to day 30. Confirm and capture within 24 hours. Intake and asset gate by day 3. Kickoff inside week 1. Setup and internal readiness in week 2. First deliverable and first value by day 30. Then a formal 30-day close. Each item needs an owner, an exit criterion and a phase timebox. Without those three, a checklist is a list of good intentions.

How long should client onboarding take?

There is no useful universal duration. A focused SMB service can reach an accepted first deliverable in days, while enterprise work may spend weeks in procurement, security review and access queues. Measure each phase across your last ten engagements, then plan from your own median and make every client-owned dependency visible.

What is the difference between a client onboarding checklist and a customer onboarding checklist?

A client onboarding checklist starts a paid service relationship: contracts, assets, access, kickoff, first deliverable. A customer onboarding checklist gets end users to first value inside a product: activation, setup, first key action, habit. If you are onboarding users into software, use the new customer onboarding checklist.

Who owns the client onboarding checklist?

One named delivery lead owns the client onboarding checklist end to end. Sales owns exactly one item, the handoff document, and hands over inside 24 hours. Ops owns billing and filing. The client sponsor owns delivering assets and signing the success plan. Shared ownership works exactly like no ownership.

When is client onboarding finished?

Client onboarding ends when the client’s own team can operate their part of the work without you. You confirm that at a dated 30-day review, against a signed success plan. Not at go-live, not when the invoice clears, and not when the kickoff call ends well.

Your onboarding is consistent. Are your clients?

A client onboarding checklist makes onboarding consistent, but it cannot fix the step where clients keep getting stuck after you hand the work over. That step is usually a workflow your team has explained live, from scratch, on every engagement you have ever run.

A pilot finds that step and rebuilds it as structured content your clients can use without you in the room.

Plan a customer adoption pilot