A useful client onboarding checklist ends when the delivery team can begin the agreed work. It should identify the scope, accountable owner, required assets, access permissions, client approver, and first milestone. A completed welcome email is only one step.
Use this checklist to prepare the handoff from sales to delivery. Assign an owner to each step and adapt the requirements to your service and agreement.
Download the free checklist (.txt)
Open the text file in any text editor, or copy the checklist into your project manager. No signup is required. You may adapt it for your own agency and client work; please do not resell the unmodified file as a standalone product.
Define “ready for delivery”
Before collecting documents, write one sentence describing the handoff. For example: “The delivery lead can start the first landing-page draft because the scope, source material, access, approver, and review date are confirmed.”
Use three statuses: Ready, Blocked, and Not required. An unchecked box should have a named owner and next action. “Not required” should include a reason so it is not mistaken for an overlooked task.
Create one onboarding record per engagement, with a unique project identifier. A returning client buying a new service may need a new engagement record even if its contact details are unchanged.
1. Confirm the commercial handoff
The account lead should transfer what was actually agreed to the delivery lead:
- The current agreement and statement of work.
- Deliverables, quantities, boundaries, and exclusions.
- First milestone and any dependencies affecting the date.
- Payment or purchase-order prerequisites defined in the agreement.
- The person responsible for handling a requested scope change.
Do not use this checklist to invent new payment requirements or approval terms. Record those that already apply. If a sales conversation conflicts with the written scope, resolve that conflict before scheduling delivery.
Completion rule: the delivery lead can describe both what the agency will deliver and what would require a change request.
2. Name the people who can move work forward
Record an agency owner, a client day-to-day contact, and the person authorized to approve work. One person can fill several roles, but the roles must be clear.
Agree on the primary communication channel and the location for decisions. If feedback arrives across email and chat, the agency owner should consolidate it before changing the brief. Record the agreed review turnaround; do not assume that silence means approval.
Completion rule: every next action has an owner, and the team knows who can approve the first deliverable.
3. Collect a usable brief and the minimum assets
A short complete brief is easier to act on than a long form with unanswered questions. Ask for:
- The audience and the action the work should encourage.
- The offer, relevant constraints, and claims the client can substantiate.
- Existing brand guidelines and approved source material.
- Required deliverable formats and destinations.
- The goal of the engagement and how the client will assess progress.
Separate launch-critical assets from optional references. If a logo is missing but the copy can proceed, mark the design step as blocked rather than treating the entire project as stopped. If the offer itself is unresolved, starting persuasive copy may create avoidable rework.
Completion rule: the first delivery task has the material needed to proceed, and missing items have owners and due dates.
4. Verify access without collecting passwords
List the systems required for the agreed service. Request access through the platform’s invitation or role-management feature where available. Keep passwords, recovery codes, and API secrets out of the brief and checklist.
Record which agency account received access, its intended permission level, and who checked it. Being invited is not the same as being able to do the required task. Have the responsible teammate verify access to the correct workspace or asset before marking the step ready.
Plan who will remove access when the engagement ends. Where a platform has unusual permissions or account ownership requirements, consult its current official documentation before changing settings.
Completion rule: the intended teammate can access the correct asset with permissions appropriate to the task, and the client retains ownership of its accounts.
5. Create the delivery workspace
Create the project from a service-specific template after checking whether it already exists. Add the engagement identifier, task owners, source links, and first review date. Keep the approved brief linked from the project so the team does not work from multiple conflicting copies.
Use the smallest workspace your team can maintain. An existing task board and shared folder may be enough. A new portal is only useful if it solves a specific access, approval, or visibility problem.
Completion rule: a teammate can find the approved scope, current assets, next task, and decision history without asking the account lead to reconstruct them.
6. Run a kickoff that resolves decisions
Use kickoff to confirm the goal, boundaries, dependencies, communication rules, and first milestone. Do not spend the whole meeting reading fields already collected in the brief.
End with a short written decision record: what is approved, what remains blocked, who owns each action, and when the next review takes place. The delivery lead then accepts the handoff or identifies the specific blocker.
Completion rule: the first task is assigned and the team can begin it using the agreed inputs.
What should you automate first?
Start with an internal draft action: create a draft project when the account lead marks the brief approved. Keep the final scope and client invitation under human review.
Before enabling the workflow, define four cases:
- Complete brief: create one draft project with the correct owner.
- Missing required field: notify the owner and pause that action.
- Repeated trigger: find the existing engagement instead of creating a duplicate.
- Connection failure: make the failure visible and provide a manual recovery step.
These are proposed acceptance criteria. The precise implementation depends on the chosen software and must be tested there. Our first-automation guide explains how to choose a manageable trial.
Is new onboarding software worth buying?
First check whether your current tools can support the checklist. Then compare the additional subscription and maintenance cost with time that can realistically be recovered.
For a worked example, assume eight onboardings per month at 45 minutes of repeated administration use six hours. A 50% reduction recovers three hours. Subtract one hour of monthly upkeep and the net is two hours. At an assumed internal value of $30 per hour, with $20 in additional software cost, the modeled capacity value is $40 per month. These are sample inputs; replace them with your own costs and timings.
Enter your own assumptions in the automation value calculator. Include software limits, seats, and setup labor when evaluating a specific product. When you know the missing capability, use the client onboarding software decision guide to build a shortlist. Buy for a verified workflow requirement, and keep the cost of running the system visible.
Common questions
How long should client onboarding take?
Set the target from your service dependencies and agreed start date. Record the time from signed agreement to accepted delivery handoff, and separately record time waiting for client inputs. That helps distinguish an agency process problem from an unresolved dependency.
Can a small agency use this without a client portal?
Yes. The checklist is independent of a particular platform. A shared document and existing task board can support it if ownership, permissions, and the current version remain clear.
What if the client has not supplied everything?
Mark each missing item as blocked, identify the affected deliverable, and agree on the next action. Proceed with unaffected work only when doing so fits the agreement and does not rely on guesses.
How do we know the checklist is helping?
Compare a few engagements using the same definitions: staff time, missing-input follow-ups, duplicate projects, and corrections after handoff. Record exceptions rather than declaring success from a completed form alone.
Return to the downloadable checklist, assign the first owner, and adapt one engagement before standardizing it across the team.
Review the evidence standard or report a factual correction.