The Client Onboarding Checklist (Task, Owner, Timing)
A client onboarding checklist is the task-by-task list that gets a new client from signed contract to first deliverable without anything falling through the cracks. The difference between a checklist that works and one that doesn't is two columns most people skip: who owns each task and when it is due.
This guide gives you a complete onboarding checklist as a table you can copy, organized by stage, with an owner and a target day for every item.
Quick summary
- A useful checklist assigns each task an owner and a due day, not just a checkbox.
- Group tasks into pre-kickoff, kickoff, and post-kickoff so dependencies are visible.
- Two tasks block everything else if they slip: the deposit and the client's intake information.
- Run the same checklist every time so onboarding is repeatable and delegable; a client portal keeps the shared items in one place.
How to use this checklist
A checklist is only as good as its discipline. Three rules make it work:
- Assign an owner. "Someone will do it" means no one does. Every task needs a name.
- Give it a day. "ASAP" is not a deadline. Tie each task to a day relative to signing (Day 0).
- Make client tasks visible to the client. They cannot complete what they cannot see.
This checklist is the task-level companion to the broader client onboarding process. Use the process for the shape of the engagement and this checklist for the individual to-dos.
The client onboarding checklist
Pre-kickoff (Day 0 to 4)
| Task | Owner | Timing |
|---|---|---|
| Countersign the contract | You | Day 0 |
| Send and collect the deposit invoice | You / client | Day 0 to 2 |
| Send the welcome email with next steps | You | Day 0 to 1 |
| Create the client record in your CRM | You | Day 1 |
| Send the intake questionnaire | You | Day 1 |
| Request brand assets and access | You | Day 1 |
| Complete the questionnaire | Client | Day 2 to 4 |
| Upload assets and grant access | Client | Day 2 to 4 |
| Schedule the kickoff meeting | You | Day 1 to 2 |
Kickoff (Day 3 to 5)
| Task | Owner | Timing |
|---|---|---|
| Run the kickoff meeting | You | Day 3 to 5 |
| Confirm goals and success criteria | Both | At kickoff |
| Confirm scope boundaries | Both | At kickoff |
| Agree on timeline and client deadlines | Both | At kickoff |
| Set communication cadence and channel | Both | At kickoff |
| Send the written kickoff recap | You | Within 24h |
Post-kickoff setup (Day 4 to 7)
| Task | Owner | Timing |
|---|---|---|
| Provision the client portal login | You | Day 4 to 5 |
| Build the project plan and milestones | You | Day 4 to 6 |
| Set up time tracking for the project | You | Day 5 |
| Add the recurring or milestone billing schedule | You | Day 5 to 6 |
| Introduce the delivery team | You | Day 5 to 6 |
| Deliver the first small win | You | Day 7 to 14 |
The two tasks that block everything
Most onboarding delays trace back to just two items.
- The deposit. Starting work before money clears is a risk you take knowingly or not at all. Make the deposit invoice part of the contract flow so it is never an afterthought.
- The client's intake information. You cannot plan or staff a project you do not understand. If the questionnaire and assets are late, every downstream task slides.
Protect these two with reminders. A short automated nudge two days after you send the intake link recovers more stalled onboardings than any amount of polite waiting.
Make it repeatable and automatic
Run the exact same checklist for every client and two things happen: onboarding gets faster, and you can hand it to someone else. Once it is stable, workflow automation can fire the standard tasks, sending the welcome email, the questionnaire, and the deposit invoice, the moment a contract is signed, so the checklist runs itself for the predictable parts.
When this checklist is the wrong fit
This checklist assumes a real project with a kickoff and a delivery phase. It is too much for some work.
- Tiny one-off tasks. A single edit does not need a 20-item checklist; a one-line brief covers it.
- Existing clients adding work. Skip the introduction and setup steps you already completed; reuse the relationship you have.
The honest caveat: a checklist gives a feeling of control that can mask a slow start. Checking twenty boxes is not the same as delivering value. If you find yourself a week in with every box ticked but no work shipped, the checklist has become the goal instead of the tool. The first win matters more than a perfect setup.
Frequently asked questions
What should a client onboarding checklist include?
It should include every task from signed contract to first deliverable, grouped into pre-kickoff, kickoff, and post-kickoff setup. Core items are countersigning the contract, collecting the deposit, sending the welcome email and intake questionnaire, requesting assets, running the kickoff, provisioning portal access, building the project plan, and delivering an early win, each with an owner and due day.
Who owns the tasks in client onboarding?
Most setup tasks belong to your account or project lead, while the intake questionnaire, deposit payment, and asset uploads belong to the client. The key is that every task has one named owner rather than a vague shared responsibility, because unassigned tasks are the ones that slip.
What is the first thing to do when onboarding a new client?
Countersign the contract and confirm the engagement, then immediately send a welcome email outlining what happens next and trigger the deposit invoice. Acting fast right after signing reassures the client and prevents the silence that causes early doubt.
How do you make client onboarding repeatable?
Use the same checklist with fixed owners and timing for every client, store shared items in a client portal, and automate the predictable steps with workflow automation tied to your CRM. Running an identical process each time makes onboarding faster, more consistent, and easy to delegate.
Related guides:
Ready to streamline your business?
Try Agiled free and see how our all-in-one platform can help you manage your business more efficiently.