Client onboarding checklist: 12 steps to start every project well

Client onboarding matters because it sets the expectations every later conversation is measured against. When a client does not know how revisions work, when updates arrive, or who approves what, they fill the gap with their own assumptions, and those assumptions almost never match yours.

It is also the moment you have the most goodwill. The contract is fresh, both sides are optimistic, and asking for access, decisions, and a single point of contact feels natural. Six weeks in, the same requests can feel like friction.

A complete client onboarding checklist has twelve steps across four stages. Copy the ones that fit your work and drop the rest.

Stage 1: Confirm the agreement

1. Restate the scope in plain language. List the deliverables and, just as usefully, what is not included.
2. Confirm the change process. How does a new request get quoted, approved, and scheduled?
3. Confirm payment terms and the first invoice date. Awkward later, easy now.

Stage 2: Collect what you need

4. Access: logins, admin invites, shared drives, and any tools you will work inside.
5. Assets: brand files, previous work, research, and examples they like or dislike.
6. People: one decision maker, one day-to-day contact, and anyone else who must approve.

Stage 3: Set the working rhythm

7. Pick one channel for requests, so work does not arrive in five places.
8. Agree on an update day and what an update will contain.
9. Set response expectations in both directions, including how long feedback rounds take.

Stage 4: Kick off and confirm

10. Run a kickoff call that walks the timeline and the first milestone.
11. Send a one-page summary of everything agreed, within 24 hours.
12. Share where progress lives, ideally a link the client can open any time.

A client onboarding email should summarize the agreement, list what you still need, and state the rhythm, all in a format the client can skim in under a minute.

The most common client onboarding mistakes are starting work before access arrives and leaving approvals undefined. Watch for these:

• Starting before the kickoff summary is sent. The summary is the document you will point back to when memories differ.
• Two decision makers, no tie-breaker. Ask who has the final say before the first round of feedback, not during it.
• Accepting requests from every channel. Email, texts, DMs, and calls all at once guarantees something gets lost.
• No first milestone inside two weeks. Early visible progress builds the trust that carries you through the slower middle.

Make onboarding repeatable by turning the checklist into a template project you copy for each new client, with the tasks, the email, and the kickoff agenda already in it. The second time you onboard a client, you should only be filling in names and dates.

Track the “still needed from client” items as dated follow-ups rather than a mental note. The client follow-up guide explains how to keep those visible until they arrive.

Create the engagement and its agreed deliverables in Noddis. Route supported email, text, or Slack requests through Capture Inbox; record a kickoff in Voice Notes when appropriate, then check the transcript and resulting work. Add commitments for the access, assets, and decisions you are waiting on.

For a Pro portal, enable sharing, select client-facing tasks and sections, and preview it before sending the kickoff email. Keep credentials out of tasks and share links: use a suitable password manager or access invitation for those.