How to Onboard a New Client Without Dropping Details (Checklist)

The contract is signed. Everyone's excited. And then, three weeks in, someone on your team asks "wait, who's the actual point of contact for approvals?" — and nobody's sure. Not because anyone's careless, but because the details a new client mentioned in passing during the sales process never made it anywhere your team could find them.

Onboarding is where agencies lose the most information relative to how little time it takes to capture it. Here's a sequence that holds up across most engagement types.

Day one: the kickoff call

The kickoff call isn't a formality — it's the one time you'll have the client's full attention before the work starts eating theirs. Use it to lock down specifics you cannot get later without an awkward "sorry, can you re-explain that" email.

A working agenda:

1. Confirm the scope in plain language. Not the contract language — have the client repeat back what they think they're getting. Mismatches surface here, not in week six.
2. Identify every stakeholder, not just the signer. Who approves deliverables? Who has final say if two people disagree? Get names, roles, and how each one prefers to be reached.
3. Set the communication cadence. Weekly email, biweekly call, async updates in a portal — decide it out loud and write it down. Ambiguity here is the single biggest source of "why haven't I heard from you" emails later. See client communication best practices for how to keep that cadence from sliding once things get busy.
4. Walk through the first deliverable's timeline. Not the whole project — just the next milestone, with a real date attached.
5. Ask what "success" looks like to them, specifically. Agencies and clients frequently define a good outcome differently, and this is the cheapest moment to find out.

What to capture on day one, in writing

Whoever runs the kickoff call should walk away with a record that outlives their memory of the call. At minimum:

• Full stakeholder list with roles and contact preferences.
• Billing contact, if different from the day-to-day contact — this alone prevents a surprising number of late invoices.
• Brand assets, logins, and access details the client already has, so you're not chasing them down separately.
• Any hard deadlines or immovable dates (a launch, an event, a board meeting) the whole engagement needs to work around.
• Anything explicitly out of scope, stated plainly enough that it can be pointed back to later without it feeling like a gotcha.

If this lives in a shared doc that only the account lead can find, it's not actually captured — it needs to sit on the client's record where anyone on the team can pull it up mid-conversation.

Granting access without a scavenger hunt

Access requests are one of the more common places a new engagement stalls. Send one consolidated list in the first 48 hours rather than requesting things piecemeal as they come up — a shared drive, an ad account, a CMS login, whatever the engagement actually requires. A single ask reads as organized; five separate ones over two weeks reads as disorganized, even if the total effort is the same.

If you're giving the client visibility into their own project status, a branded portal beats another shared spreadsheet — it's one place they check instead of five threads they have to remember.

Setting expectations early

Most onboarding friction isn't about the work — it's about mismatched assumptions on turnaround time, revision rounds, and who's responsible for what. Spell out, before the first deliverable ships:

• How many revision rounds are included, and what happens past that.
• Realistic turnaround time for feedback on your side and theirs.
• Who owns internal follow-up if the client goes quiet for a few days.

Clients rarely push back on limits stated upfront. They do push back on limits that show up for the first time when they've already been "broken."

Assigning internal ownership

Before the client ever notices, decide internally:

• Who's the single point of contact from your side (even if multiple people do the work)?
• Who owns the relationship if that person is out sick or on vacation?
• Who's responsible for making sure onboarding information actually gets logged somewhere durable, not just discussed on a call?

A surprising amount of dropped-ball moments trace back to this last one — information existed, it just existed in one person's head or inbox instead of on the client's record.

Turning this into a repeatable process

None of this needs to be complicated the second or third time you run it — it just needs to be the same sequence every time, with the same fields captured in the same place. Teams that keep onboarding details in whatever tool holds the rest of the client relationship (not a one-off onboarding doc) tend to stop losing details somewhere around client number four or five. If you're evaluating whether your current setup can hold up to that, what an agency CRM actually does differently is a good starting point, and getting pricing right from the outset matters too — see how to price agency services for how scope and cadence decisions made at kickoff tie back into what you charge.