---
title: "Client Onboarding Checklist"
description: "A reusable client onboarding process for agencies, from signed agreement to the first review."
canonical_url: "https://usecleo.io/guides/client-onboarding-checklist"
---

> Index of every page on this site: [llms.txt](https://usecleo.io/llms.txt)

Client onboarding turns a signed agreement into a working relationship. The goal is not to send more forms. It is to remove uncertainty about access, ownership, scope, communication, and the first measurable outcome.

This checklist is written for marketing agencies, but the structure works for consultants and other recurring service businesses.

## On this page

- [Before the kickoff](#before-the-kickoff)
- [Information and access to collect](#information-and-access-to-collect)
- [Run the kickoff meeting](#run-the-kickoff-meeting)
- [Build the first 30-day plan](#build-the-first-30-day-plan)
- [Set up the CRM record](#set-up-the-crm-record)
- [Client onboarding checklist](#client-onboarding-checklist)
- [Frequently asked questions](#frequently-asked-questions)

## Before the kickoff

The first onboarding work starts before the meeting. Review what sales promised, identify gaps, and decide who owns each part of delivery.

Prepare:

- Signed scope and commercial terms
- Services included and explicitly excluded
- Named agency owner and delivery leads
- Client decision-maker and day-to-day contact
- Target launch date or first milestone
- Known dependencies and risks
- Open questions carried over from sales

Do not make the client repeat information already collected during sales. Transfer it into the onboarding record and ask only for confirmation or missing details.

## Information and access to collect

Separate business context from technical access. The people who know the goals may not be the people who administer the tools.

### Business context

Ask for:

- Primary business objective
- Target customer and priority offers
- Current performance baseline
- Previous work and lessons learned
- Approval process
- Legal or brand restrictions
- Reporting audience and cadence

A useful objective contains a number, audience, and time period. “Improve leads” is too vague. “Increase qualified demo requests from UK companies over the next quarter” can guide channel, creative, and reporting choices.

### Access inventory

Create an inventory rather than requesting passwords in email.

<table>
<thead>
  <tr>
    <th>
      System
    </th>
    
    <th>
      Access needed
    </th>
    
    <th>
      Client owner
    </th>
    
    <th>
      Agency owner
    </th>
    
    <th>
      Status
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Analytics
    </td>
    
    <td>
      Read or analyst
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Pending
    </td>
  </tr>
  
  <tr>
    <td>
      Advertising account
    </td>
    
    <td>
      Campaign management
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Granted
    </td>
  </tr>
  
  <tr>
    <td>
      Website or CMS
    </td>
    
    <td>
      Scoped publishing
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Pending
    </td>
  </tr>
  
  <tr>
    <td>
      Email platform
    </td>
    
    <td>
      Campaign management
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Not needed
    </td>
  </tr>
  
  <tr>
    <td>
      CRM
    </td>
    
    <td>
      Required records and reporting
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Name
    </td>
    
    <td>
      Granted
    </td>
  </tr>
</tbody>
</table>

Use each platform's user and role controls. Shared credentials make revocation and audit harder.

## Run the kickoff meeting

A kickoff should resolve decisions, not merely introduce everyone.

Cover these topics:

1. Restate the outcome and scope.
2. Confirm the target audience and priority offer.
3. Agree on success measures and current baselines.
4. Review responsibilities and approval owners.
5. Confirm the communication channel and meeting cadence.
6. Surface dependencies, risks, and unavailable access.
7. Agree on the first milestone and next actions.

End with named owners and dates. “The client will send assets” is incomplete. “Jordan will send the approved brand assets by Thursday” is actionable.

## Build the first 30-day plan

The first month should produce evidence that the engagement is moving, even when the final business result takes longer.

### Week 1: establish the baseline

Confirm access, validate tracking, review existing assets, and record baseline performance. If data is incomplete, document the gap rather than treating missing data as zero.

### Week 2: agree on direction

Present the strategy, priorities, or initial findings. Resolve approval requirements before production begins.

### Week 3: launch the first work

Ship the smallest meaningful unit: a campaign, landing-page revision, measurement fix, or content brief. Avoid waiting for every future detail before producing anything observable.

### Week 4: review and adjust

Compare the work against the baseline, record what changed, and confirm priorities for the next cycle.

## Set up the CRM record

The CRM should preserve the commercial and relationship context around delivery.

Create or update:

- The client account and key contacts
- Contact roles such as decision-maker, billing contact, and technical contact
- Contract value, start date, renewal date, and services
- Agency owner and delivery stakeholders
- Communication preferences
- Important risks and commitments from sales
- A note summarizing kickoff decisions

Use [tags](https://usecleo.io/guides/tags) for visible states such as `onboarding` or `access-blocked`. Use structured fields for dates, values, and named options. When a recurring review needs the same audience, create a [smart list](https://usecleo.io/guides/smart-lists).

## Client onboarding checklist

### Commercial handoff

- [ ] Signed scope is attached or linked
- [ ] Services and exclusions are understood
- [ ] Billing contact and terms are confirmed
- [ ] Sales commitments are recorded

### People and communication

- [ ] Agency owner is named
- [ ] Client decision-maker is named
- [ ] Day-to-day contacts are identified
- [ ] Approval process is documented
- [ ] Meeting and reporting cadence is agreed

### Strategy and measurement

- [ ] Primary objective is specific
- [ ] Target audience and offer are confirmed
- [ ] Baseline metrics are recorded
- [ ] Success measures have owners and sources

### Access and delivery

- [ ] Required systems are listed
- [ ] Access uses individual accounts where possible
- [ ] Missing access has an owner and due date
- [ ] First milestone and next actions are dated

## Frequently asked questions

### How long should client onboarding take?

The duration depends on service complexity and access requirements. Define a target for reaching the first useful milestone, then track blockers separately. A ten-day onboarding delayed by missing analytics access is different from ten days of internal inactivity.

### Who should own onboarding?

Name one accountable owner on the agency side. Specialists can own individual tasks, but the client should know who coordinates the whole process.

### What should be stored in the CRM?

Store relationship context, stakeholders, commercial dates, ownership, commitments, and important decisions. Delivery files can remain in their specialist tools with links from the relevant record.

### How do I reduce onboarding delays?

Request access early, assign every request to a person, set due dates, and review outstanding dependencies at each check-in. Use the [CRM data organization guide](https://usecleo.io/guides/crm-for-marketing-agencies) to keep account records consistent.

## Sitemap

See the full [sitemap](https://usecleo.io/sitemap.md) for all pages.