beginner / 35 minutes
AI Client Onboarding Workflow
Map the first client handoff without hiding missing access, unclear ownership or decisions that still belong to a person.
Result: A client onboarding plan with required inputs, owners, dates, handoffs and open items.
Jump to prompt ↓5 steps to a reviewable draft
- 01
Define the onboarding finish line
State what must be true before delivery can start, including access, files, approvals and introductions.
Result: A concrete onboarding completion condition.
- 02
Map inputs and owners
List each item the client and team must provide, who checks it and what happens when it is missing.
Result: An input register with named responsibility.
- 03
Build the onboarding plan
Ask for a checklist that preserves dependencies and open decisions.
Result: A checklist that exposes missing inputs before they delay delivery.
Your prompt
Create a client onboarding plan from this signed scope: {{scope}}. Completion condition: {{finish_line}}. Required client inputs: {{client_inputs}}. Internal owners and handoffs: {{owners}}. Known dates and constraints: {{dates}}. Return a sequenced checklist with item, owner, dependency, due date, evidence of completion and an open-items section. Mark unknowns [OPEN]. Do not invent access requirements, dates, responsibilities or contractual commitments.Example inputWebsite copy project. Client supplies approved offer facts and analytics access. Writer owns discovery; owner approves claims.
Example outputItem: approved offer facts. Owner: client. Dependency: discovery call complete. Evidence: signed fact sheet. Due date: [OPEN].
- 04
Walk through the handoffs
Review the checklist with the delivery owner and test what happens if a client input arrives late.
Result: A workable sequence with escalation points.
- 05
Send the agreed version
Share the client-facing actions, keep internal notes separate and record the next checkpoint.
Result: Both sides know the next action and owner.
What a finished draft should contain
A website-copy onboarding plan that holds drafting until offer facts are approved and records analytics access as an open dependency.
What this process cannot decide
- AI cannot interpret a contract
- Access credentials require secure handling
- Dates and responsibilities need owner confirmation.
