Client Onboarding Checklist for Agencies: What to Collect Before Kickoff

The kickoff call is booked, the team is ready, and then someone asks who has the CMS login. The logo turns out to be a screenshot from the client's homepage, and nobody is sure who signs off on the work. Week one slips into week two without anyone deciding it should.

Here's the short version. A client onboarding checklist for agencies covers five things to collect before kickoff: signed scope and payment, brand files and assets, logins and access, brand and communication preferences, and a named decision-maker. Gather them in one request, not across a week of emails.

Why do projects stall in week one?

Projects stall in week one because inputs are missing and expectations are fuzzy, not because the work is hard. The team is ready to start, but the logins, files, and approver they need haven't arrived.

TapClicks notes that onboarding is your chance to set clear expectations, highlight value, and address early concerns, and that rushing it risks confusion and miscommunication. Most agencies know this. The trouble is that the asks go out one at a time, in whatever order someone remembers them.

The usual culprits

I keep seeing the same four:

• Access to the CMS, ad accounts, or analytics is requested after kickoff instead of before.
• Brand files arrive as screenshots, or as "just grab it from our site."
• Nobody on the client side knows they're the approver.
• Preferences about updates and channels are discovered the first time someone gets annoyed.

None of these are exotic. They all come from asking piecemeal.

A week-one stall, step by step

Here's a composite scenario, not a specific client. A small web agency signs a site refresh on Monday.

1. Day 1: The welcome email asks for logins, a logo, and "anything else that's useful."
2. Day 2: The client sends a logo and says IT handles the CMS.
3. Day 4: A reminder goes out. IT replies asking what permissions the agency needs.
4. Day 6: The agency answers. Access arrives, but two-factor codes go to the client's phone.
5. Day 9: The team learns that a VP, not the marketing manager, approves the final design.

Nothing in that timeline is the client being difficult. Every delay is a question that could have been answered on day one, in one message.

What should a client onboarding checklist for agencies include?

A client onboarding checklist for agencies should cover five buckets: paperwork, files, access, preferences, and decisions. Together they hold everything the team needs to start the first deliverable without stopping to ask.

I call this the five-bucket pre-kickoff collection. It's a descriptive label for a way to group the asks, not a formal methodology.

The five buckets at a glance

This lines up with what other checklists cover. A checklist summarized on Facebook groups the work into payment, intake, access, assets, kickoff, and a 30-day review. ScaleTime's agency checklist starts with legal and payment requirements, then moves to roles, client goals, and a resource and project plan.

So, to answer what client onboarding entails: paperwork and payment, intake, files and access, role assignment, a kickoff meeting, and a review after the first month. The five buckets are the part you can collect before the kickoff.

LeadUp Marketing frames its checklist as the path from signed scope to first delivery across paid media, content, SEO, and creative. That's a useful way to think about the whole thing: your job is to shorten the distance between those two points.

Files and assets to ask for

Ask for the files the first deliverable actually uses:

• Logos in vector or high-resolution formats, including light and dark versions
• Brand guidelines, or a note saying none exist
• Existing creative, copy, and product or service documents
• Past reports or briefs, if you're taking over work

Name the format you want. "Logo as SVG or PNG with a transparent background" gets a better reply than "your logo."

Logins and access to request

List each system and the access level you need. Typical ones are the website CMS, ad accounts, analytics, and social channels.

Prefer invitations to your agency's email or role-based accounts over shared passwords, and say up front who at the client can grant them. That second part is where the nine days in the scenario above went.

Which brand details, preferences, and decisions matter most?

The details that matter most are the client's goals, how they want to be updated, and who approves the work. Get those three right and the rest of the onboarding gets easier.

Brand and communication preferences

TapClicks describes a structured onboarding as a way to capture key information like communication preferences, existing tools, and the client's goals. Agility PR adds a specific question worth borrowing: how often are updates needed, and through which channels?

Keep this short:

• What's the one outcome that would make this project a success?
• Which tools do you already use for this work?
• How often do you want updates, and where: email, chat, a call?
• Is there anything about tone or voice we should know before we write a word?

The last question matters more than it looks. Voice preferences are cheap to ask about in week one and expensive to discover in round three. If your project depends on a full brief, our guide on how to write a creative brief clients will actually fill in covers the questions to ask there.

Decisions to lock before kickoff

Four decisions belong on the checklist, and each needs a name next to it:

1. Final approver. One person who can say "yes, ship it."
2. Day-to-day contact. The person who answers questions within a day or two.
3. Out-of-scope items. A short list of things the project does not include.
4. Internal roles. Who on your side owns the account, the work, and the review.

ScaleTime lists assigning roles as a core onboarding step, and TapClicks calls out assigning points of contact. The same goes for your own team. The Medium guide on onboarding for digital agencies includes briefing the team as its own step, ahead of research. Do it before kickoff so the person running the call has read what the client said.

The approver decision deserves extra care. If the approver is a VP who isn't on the kickoff call, you'll hear about it at the first review. Our guide on how to set up an approval process that doesn't stall when clients go quiet goes deeper on what to do when they do.

How do you collect it all without chasing the client?

You collect it all by sending one short, bucketed request, with an owner and a due date on every item, and letting reminders do the chasing. The checklist should nag, not you.

Here's my contrarian take: don't send a 40-question onboarding questionnaire and a separate list of file requests. Send one short request with only what week one needs, and ask for the rest after kickoff. Long forms get half-filled and abandoned, which recreates the stall they were meant to prevent. The tradeoff is a second, smaller ask later. I'll take that trade every time.

A five-step collection routine

1. Send one bucketed request. Group items under Paperwork, Files, Access, Preferences, and Decisions. Cut anything the first deliverable doesn't need.
2. Set an owner and a due date per item. "Marketing manager, Thursday" beats "the client, soon."
3. Let clients reply by email. Most clients won't log into another tool for onboarding, so meet them in their inbox.
4. Remind automatically. Reminders on a schedule feel like process, not nagging.
5. Confirm completeness before kickoff. Check the list. If something is missing, say so on the call and name who owns it.

Doing this by hand works. It just eats time that should go to the project.

Or let Dora do the asking. She takes requests in any form, including email, asks the client for what's missing, and keeps files organized in the brand library. Set up a portal in a minute and try Dora free. Your first client is free, forever.

If you're weighing a portal for this, our rundown of common client portal mistakes small agencies make will save you a few bad setups.

Where spreadsheets and project tools fall short

Dock argues that spreadsheets lack visual clarity and that project management tools are too complex for onboarding checklists. Dock sells an onboarding product, so take that as one viewpoint. It still matches what I see: a spreadsheet works for two or three clients, then turns into a tab nobody checks.

Adapting the list by service type

Treat the five buckets as a base, then adjust. Clustdoc's collection of 40+ onboarding templates shows how much document collection varies by industry. Finance templates include things like KYC/AML checks and business credit applications.

For agencies, the same idea applies at a smaller scale:

• Web: hosting, DNS, CMS, and staging access.
• Paid media: ad account access and conversion tracking.
• Content and SEO: analytics access, existing content, and voice samples.
• Design: brand files and past creative.

Keep one template per service type, not one giant list.

What are the common onboarding mistakes, and how do you check it worked?

The most common onboarding mistakes are asking for too much at once and leaving the approver unnamed. Both bring back the stall you were trying to prevent, and both are easy to catch.

Mistakes that recreate the stall

• Asking for everything at once. A wall of questions gets half-answered. Prioritize week one.
• No named approver. Without one, feedback arrives from three people who disagree.
• Collecting logins in email threads. Credentials get buried and are awkward to revoke. Use invitations or one shared request.
• Skipping the internal briefing. The client repeats themselves on the call, and trust takes a small hit.
• Treating onboarding as done at kickoff. Expectations drift in the weeks that follow.

The 30-day review

A 30-day review is a short check-in after kickoff to confirm expectations, communication, and early results. It's part of the checklist structure in the Facebook summary mentioned earlier, and it's where you catch drift.

Don't take my word that the checklist works. I don't have a universal benchmark for how long this should take, so measure your own.

• Baseline: For your last 5 clients, count the days from signed scope to the day your team had everything needed for first delivery.
• Change: Use the five-bucket request, with reminders and a named owner on each item.
• Target: Get that gap under 5 working days across the next 3 onboardings.
• Tracking: Timestamp the request sent, each item received, and the kickoff held. Review the numbers at the 30-day check-in.

If the gap doesn't shrink, look at which bucket arrived last. It's usually access or the approver.

Want the checklist to run itself? Let Dora ask the client for what's missing and keep their files organized. Try Dora free. Your first client is free, forever. And what's the one item that always shows up last in your onboarding?

FAQ

What does client onboarding entail for an agency?

It covers paperwork and payment, an intake questionnaire, files and access, role assignment, a kickoff meeting, and a 30-day review. The first four can be collected before kickoff, which keeps the call focused on the work itself.

What should I collect from a new client before kickoff?

Collect the signed scope, logos and brand guidelines, logins for the systems you'll work in, the client's goals, their communication preferences, and a named approver. Ask only for what the first deliverable needs. Everything else can wait until after kickoff.

How long should an onboarding questionnaire be?

Short. Include only what week one needs and ask the rest after kickoff. Long forms tend to get half-filled and abandoned, which brings back the delay you were trying to avoid. A second, smaller ask later costs far less.

How do I collect logins and assets securely?

Use one request through a portal instead of scattered email threads, and keep files in one organized place. Prefer access invitations over shared passwords where the platform allows. Dora's brand library keeps client files organized in one place.

Should I use a spreadsheet or a client portal for onboarding?

A spreadsheet is fine for a few clients. Dock points out that spreadsheets lack visual clarity, and that gets worse as the client list grows. A portal that asks for missing items and reminds clients helps once you're juggling more onboardings at once.

What is a 30-day onboarding review?

It's a check-in about a month after kickoff to confirm expectations, communication, and early results. It's one of the standard categories in agency checklists, alongside payment, intake, access, assets, and kickoff. Use it to adjust update frequency and fix anything that drifted.