Use this client onboarding checklist to convert an accepted sale into a controlled, confident start to delivery.
The checklist begins after the client accepts the commercial and legal terms. It protects the client experience and the owner’s capacity by confirming prerequisites before work starts. The client onboarding guide explains the broader system.
When Client Onboarding Starts and Ends
Onboarding starts when the acceptance conditions are met—normally a signed agreement, required payment, or confirmed checkout. It ends when the client, scope, contacts, access, schedule, responsibilities, and first action are confirmed and the delivery workflow contains the necessary records.
Do Not Use Kickoff to Discover Missing Basics
Collect standard information asynchronously where possible. Reserve a kickoff call for decisions, alignment, and unresolved dependencies. If payment, access, scope, or decision authority is missing, delay the start transparently rather than creating an informal exception.
Handle Access Securely
Request the minimum access required, prefer named user accounts and least privilege, and use a secure credential-sharing method. Never ask a client to place passwords or recovery codes inside an ordinary onboarding document.
Copy the Client Onboarding Checklist
Duplicate this checklist for every client. Add the client, owner, dates, and evidence links, then complete each item in the system where delivery is managed.
Engagement identity
Client: [Legal or trading name]
Engagement: [Offer or project name]
Provider owner: [Person accountable for onboarding]
Client decision-maker: [Authorized approver]
Planned start: [Date, subject to prerequisites]
Onboarding record: [Authoritative project or client location]
1. Agreement and payment
2. Contacts and communication
3. Scope and success
4. Intake and access
5. Timeline and milestones
6. Risk and readiness
7. Welcome and kickoff
8. Onboarding completion
Prerequisites complete: [Yes, no, or exception with authorization]
Open dependency: [Item, owner, due date, and effect]
First delivery action: [Action, owner, and due date]
Onboarding completed by: [Name and date]
Client confirmation: [Method and date]
Retrospective note: [What to change before the next onboarding]
Completed Client Onboarding Checklist Example
This condensed example shows how Northstar Email Studio would onboard OrbitFlow after an accepted proposal.
Show the completed example
Engagement identity
Client: OrbitFlow Ltd.
Engagement: OrbitFlow Trial Activation Email Sprint, project NS-OF-2026-11.
Provider owner: Alex Morgan, Northstar Email Studio.
Client decision-maker: Proceed with the bounded next step, owned by Alex Morgan, and review the evidence on 30 September 2026.
Planned start: Start after signature, deposit, and access; complete within three weeks, subject to two-business-day client approvals.
Onboarding record: Store the dated source record in the restricted client folder, retain only the agreed evidence, and delete temporary exports after acceptance.
1. Agreement and payment
2. Contacts and communication
3. Scope and success
4. Intake and access
5. Timeline and milestones
6. Risk and readiness
7. Welcome and kickoff
8. Onboarding completion
Prerequisites complete: Yes — agreement signed, deposit cleared, contacts named, access tested, and interview recruitment confirmed on 21 November 2026.
Open dependency: Client will recruit five interview participants by 6 November; delivery dates move if recruitment is late
First delivery action: Export the agreed activation baseline and confirm the five interview participants before research begins.
Onboarding completed by: Alex Morgan on 21 November 2026.
Client confirmation: Lena Ortiz confirmed scope, access, contacts, milestones, and kickoff readiness in the project portal.
Retrospective note: The analytics-access request should be sent with a permission screenshot to prevent one avoidable day of setup delay.
Quality Check
- Agreement and payment conditions are verified before delivery.
- One provider owner and one client decision-maker are named.
- Scope, exclusions, revisions, and acceptance match the agreement.
- Client responsibilities and delay effects are documented.
- Access uses least privilege and an appropriate secure method.
- Milestones include customer inputs and approvals, not only provider tasks.
- Material risks have owners and controls.
- The welcome message contains one clear next action.
- Decisions are stored in an authoritative location.
- Onboarding ends with readiness evidence and a dated next action.
Common Client Onboarding Mistakes
Starting before prerequisites are met
Informal exceptions weaken payment, schedule, and scope control before delivery begins.
Requesting every possible detail
Long intake forms create work without improving the current project. Ask only what changes delivery.
Using shared passwords
Prefer named accounts, least privilege, and secure credential sharing.
Leaving approvals off the timeline
Client review is part of delivery capacity and must have an owner and date.
Treating welcome as onboarding
A friendly message cannot replace confirmed access, scope, payment, responsibilities, and readiness.
Related Guides and Templates
- Start from an accepted Sales Proposal template.
- Control communication through the client communication guide.
- Define boundaries with the project scope guide.
- Prepare the closing process with the Client Offboarding Checklist.