Onboarding fails at the handoffs, not the steps. Everyone knows to send the contract and book a kickoff. The failures happen between — nobody told the client what access to prepare, the kickoff happened before the brief existed, or the first deliverable arrived with no warning about what it would look like.
Each checklist below is built the same way: what you do, what the client must do, and what "done" looks like. The second column is the one usually missing. In our testing, stating the client's obligations explicitly — with dates — removed most of the waiting that gets blamed on the supplier.
The six stages
1. Signed to scheduled
Use when: the contract comes back.
| You | Client | Done when |
|---|---|---|
| Send countersigned copy | — | Client has the executed agreement |
| Send invoice for deposit | Pay deposit | Payment confirmed |
| Propose kickoff times | Confirm a slot | Invite sent and accepted |
| Send access request list | Prepare credentials | List acknowledged |
2. Kickoff meeting
Use when: the project formally starts.
Agenda: confirm objective and success measure · walk through scope and exclusions · confirm dependencies and dates · agree communication channel and response times · name who decides on changes.
Send within two hours: decisions made · scope confirmed · open questions with owners and dates.
The item people skip: naming who approves changes. Without it, every adjustment becomes a negotiation.
3. Access and setup
Use when: you need systems, accounts or data.
- ☐ [System 1] — [access level] · requested [date] · granted [date]
- ☐ [System 2] — [access level] · requested [date] · granted [date]
- ☐ Shared folder created and shared
- ☐ Billing contact confirmed
- ☐ Emergency contact confirmed
Ask for access on day one, not when you need it. Credential delays are the most common cause of a slipped first milestone, and they cost days rather than hours.
4. Information gathering
Use when: you need material only the client has.
| What you need | From whom | By when | Blocks |
|---|---|---|---|
| [Item 1] | [role] | [date] | [milestone] |
| [Item 2] | [role] | [date] | [milestone] |
The "blocks" column is what makes this work. When an item is late, you can point at the consequence rather than sending another reminder.
5. First deliverable
Use when: you are about to send something the client will judge you on.
- ☐ Set expectations before sending: what it is, what it is not, what feedback looks like
- ☐ Send at the stated time, even if imperfect
- ☐ Ask one specific question rather than "any thoughts?"
- ☐ Confirm the next milestone in the same message
Why the expectations note matters: a first draft without framing gets judged as a finished product, and the feedback that follows is not actionable.
6. Thirty-day review
Use when: the first month of work is done.
Cover: what was delivered against the plan · what slipped and why · what is next in the following thirty days · what you need from the client · is anything about the arrangement not working.
Ask the last question every time. It surfaces problems while they are still small and cheap to fix, rather than at renewal.
What to leave out
Three habits slow onboarding down. Requesting everything at once — a long list gets deferred; ask for what the next milestone needs plus what has a lead time. Front-loading background reading, which asks for the client's time before they have seen any value. Internal jargon in client-facing documents, which makes obligations harder to act on.
Where AI helps
Tool-generated drafts are good for the checklist skeleton, the request-list phrasing and the follow-up sequences — all repetitive, all easy to review. They are not a source for contract terms, liability wording or anything with legal weight. Those come from your own templates and your adviser.
The two handoffs that get dropped
Two transitions cause most of the damage, and neither appears in most checklists. Sales to delivery — what was promised in the sale rarely reaches the person doing the work intact. Fix it with a written handover: commitments made, assumptions stated, and anything the client was told that is not in the contract.
Delivery to first value — the client is most uncertain in the gap between signing and seeing something. Give them something dated early, even if it is small: a schedule, a kickoff summary, an access confirmation. In our testing, clients who received something concrete in the first three days raised fewer questions later, even when the first deliverable arrived on the same schedule.
Get the handoffs written down
Draft the checklists in a tool. The dates and obligations are yours — and they are the whole point.
Try Rytr →Frequently Asked Questions
How long should onboarding take?
From signed contract to first deliverable, aim for under two weeks. Longer gaps create doubt before any work is visible.
What should I ask the client for first?
Whatever has a lead time — credentials, approvals, existing assets. Then what the first milestone needs.
Should onboarding be automated?
The messages and reminders, yes. The kickoff conversation, no — that is where the real scope gets clarified.
How do I stop scope drift?
Name who approves changes at kickoff, quote changes in writing before work starts, and confirm revised dates each time.
What belongs in a thirty-day review?
What was delivered, what slipped and why, what is next, what you need, and whether the arrangement is working.
Can AI write our onboarding documents?
The structure and recurring messages, yes. Contract and liability wording, no.