What this client onboarding checklist covers
Use this section to confirm the checklist fits the work before you start. If it does, move through the steps in order and log anything that needs an owner.
- Client intake
- Access collection
- Scope confirmation
- Timeline planning
- Communication rules
- Kickoff preparation
Who should use it
This checklist is written for people who need to ship practical work, review client deliverables, or maintain a site without adding process for its own sake.
- Freelancers starting client projects
- Small agencies standardizing delivery
- Consultants collecting assets and decisions
- Builders selling productized services
Information, access, and planning requirements
Use it immediately after the agreement is signed and before production work begins.
- Have a signed agreement or written approval.
- Know the primary client contact.
- Prepare a central place for assets and project notes.
- Decide how you will handle missing information.
Client onboarding checklist: step by step
Work from top to bottom. Skip a step only when someone has already checked it and there is a clear owner for the result.
- Step 1
Confirm project basics
Record the client, project name, decision makers, goals, deliverables, timeline, and budget constraints.
- Step 2
Collect access
Request CMS, domain, hosting, analytics, email, design, payment, and third-party tool access through secure methods.
- Step 3
Gather brand assets
Collect logos, colors, fonts, imagery, copy references, legal copy, and approved positioning.
- Step 4
Clarify scope
Restate deliverables, exclusions, revision limits, dependencies, and approval responsibilities.
- Step 5
Set communication rules
Define the primary channel, meeting cadence, response expectations, and escalation path.
- Step 6
Plan milestones
Create a simple timeline with kickoff, content due dates, review windows, build milestones, QA, and launch.
- Step 7
Identify risks
List missing assets, unclear decisions, technical dependencies, and client bottlenecks before they slow the project.
- Step 8
Run kickoff
Review scope, process, timeline, roles, next actions, and what happens if deadlines slip.
- Step 9
Send the onboarding recap
Summarize decisions, links, responsibilities, and immediate next steps in one written message.
Common onboarding mistakes
These are the issues that usually create rework, client friction, or avoidable launch cleanup.
- Starting work before access is collected.
- Assuming the buyer is the decision maker.
- Letting scope live only in conversation.
- Not defining how feedback should be delivered.
- Failing to document what is still missing after kickoff.
Download this client onboarding checklist
Use this page as the working version. Print it, save it as a PDF, or copy the steps into your project workspace. If you need the next related check, open Small Business Website Checklist.
Client onboarding FAQ
When should client onboarding start?
Start after agreement and before production. If onboarding begins too late, the project usually starts with avoidable delays.
What access should I request first?
Request access that can block work: domain, hosting, CMS, analytics, design files, brand assets, and key third-party tools.
How do I keep onboarding from feeling heavy?
Use one organized intake process, ask only for what is needed now, and explain why each item matters.