Most agencies don't have a formal onboarding process. They have a loose mental checklist that lives in the head of whoever ran the last project.
That works fine until someone is sick, a client escalates in week one, or you win two projects in the same week and everything collides.
A documented onboarding checklist takes 30 minutes to run — and it prevents 80% of the delays, confusion, and miscommunication that make the first two weeks painful.
Here's exactly what to put in it, and why each step matters.
Why most agency onboarding breaks in the first week
Client onboarding breaks in predictable places:
No central intake. Different team members asked different questions. Nobody has the full picture.
Access collection drags. You asked for tool access on day three. You're still chasing on day nine.
Scope drift starts at kickoff. The brief looked clear in the proposal. The kickoff call reveals three things nobody agreed on.
No shared timeline. The client thinks work starts Monday. Your team thinks it starts after the brand review.
A checklist doesn't solve all of these. But it makes all of them visible before they become expensive.
The 5-phase onboarding checklist
Phase 1: Pre-kickoff (before the call)
Do this the moment the contract is signed, not the night before kickoff.
Intake form sent and returned. This is your single most important step. If you start a kickoff call without a completed intake form, you're converting what should be a decision call into a discovery call. Those are different meetings.
Cover at minimum:
- Business goals for this project (not just deliverables)
- Existing tools, platforms, and accounts you'll need access to
- Key contacts: who approves work, who handles escalations, who has the login
- Current situation: what exists now, what's broken, what they've already tried
- Success metrics: what does "done well" mean to them
Internal brief drafted. Once the intake form is back, write a one-page internal brief. Who is this client, what do they want, what are the known risks, who owns what on your team.
Project structure set up. Create the folder structure, project management board, and shared docs before the kickoff call. Nothing looks less professional than spending the first week deciding how to organize the work.
Phase 2: Access collection (Day 1, not Day 3)
Send a complete access request on day one. Not after kickoff. Not "once we get started."
An effective access request lists:
- Every tool you need access to (specific platform names, not "website access")
- The permission level you need (admin, editor, read-only)
- The format you prefer (direct invite vs. shared credentials)
- A clear deadline: "We need these by [date] to start on schedule"
Send it as a numbered list. Keep it under 200 words. Include one contact to follow up with.
The common mistake: asking for access vaguely ("can you share the logins?") and then chasing individually for each tool over the following two weeks.
Phase 3: Kickoff call
A kickoff call has one job: align on scope, timeline, and decision-making.
Not discovery. Not selling. Not fixing what should have been in the intake form.
Go in with:
- Three specific questions to resolve (pulled from the intake form review)
- A draft timeline to walk through together
- Clear agreement on: who approves deliverables, what triggers a scope change, how you communicate status
End the call with: "Here's what we agreed to. I'll send this in writing within 24 hours."
Phase 4: Post-kickoff confirmation (within 24 hours)
Send a written summary the same day or next morning.
This is not a formality. It is your evidence trail if scope creep starts happening in week three.
Include:
- What you're delivering, and what you're not
- The timeline with milestones
- How the client can reach you and when to expect updates
- What you need from them, and by when
Phase 5: Week-one check-in
Five days in, send a short update.
Not because something is wrong. Because establishing a communication cadence in week one tells the client you have a process.
"Here's where we are. Here's what's next. Here's what we need from you."
That's it. Under 150 words. Consistent format every week.
The checklist in one place
PRE-KICKOFF
☐ Intake form sent
☐ Intake form returned and reviewed
☐ Internal brief drafted
☐ Folder structure created
☐ Project board set up
DAY 1
☐ Access request email sent (numbered list, specific tools, clear deadline)
☐ Kickoff agenda shared with client
KICKOFF CALL
☐ Scope confirmed
☐ Timeline walked through
☐ Decision process agreed (who approves, how scope changes work)
☐ Communication cadence set
POST-KICKOFF (within 24h)
☐ Written summary sent
☐ Deliverables listed (in scope and out of scope)
☐ Timeline confirmed in writing
WEEK ONE
☐ Status update sent (what's done, what's next, what you need)
☐ Any open access items followed up
How to make this repeatable
The difference between a checklist you use once and a system you run every time is documentation and ownership.
Document it. Put the checklist in your project management tool as a template. Every new project gets the same template, pre-populated, on day one.
Own each phase. Assign each phase to a role, not a person. "Account lead sends access request" works even when the account lead changes.
Run a five-minute review after week two. What slipped? What took longer than expected? Update the checklist before you start the next project.
That's how a checklist becomes a standard operating procedure.
Free resources
The checklist above is a simplified version of the full system. If you want the complete 57-step onboarding SOP with intake form templates, access request email templates, and AI prompt workflows, the full Agency Onboarding OS is available at agencyonboardingos.com.
Free to start:
No email required for any of them.
Top comments (0)