# Build a client onboarding checklist around the first deliverable

A client onboarding checklist should gather what is needed to start the first deliverable. Confirm the scope, decision owner, required inputs, access, and communication process. Avoid collecting sensitive information or broad account access merely because it might be useful later.

## Work backward from the first milestone
For a fictional booking-page project, the first milestone is a reviewed brief. That may require the existing page, intended users, approved content, and the person who can confirm scope. It does not necessarily require production administrator credentials on day one.

## A kickoff checklist
| Item | Confirmation |
| --- | --- |
| Approved scope | Both sides have the same version |
| Decision owner | Named person with authority to approve |
| Inputs | Files and context required for the first milestone |
| Access | Minimum permissions needed now |
| Communication | Channel and feedback cadence |
| Schedule | Dates and dependencies confirmed |
| Open questions | Listed with owners |

Keep the checklist proportional to the project. A small engagement should not require a bureaucratic intake process larger than the work itself.

## Draft an intake message
```text
To begin the brief review, please send the current page, approved content,
and the name of the person who will confirm scope. We do not need production
access for this first milestone. I will return the draft brief and open questions
by the agreed date once those inputs are complete.
```

This is fictional wording. Use only delivery dates and access claims that match your actual process.

## Use AI to trim the checklist
```text
Review this onboarding checklist against the first deliverable.
Separate required-now inputs from optional-later inputs.
Flag unnecessary sensitive information and excessive permissions.
Identify missing owners, dependencies, and approval steps.
Do not add forms or tools just to make the process look comprehensive.
Checklist and scope: [paste]
```

Confirm receipt and completeness through your normal process. If an input is missing, identify the specific dependency instead of saying the whole project is blocked indefinitely. Update the checklist as the scope changes, and remove access when it is no longer needed. Good onboarding makes the next piece of work clear for both sides.

---
SkillStall · 2026-10-02