Client Onboarding Checklist¶
Purpose¶
Make onboarding consistent so delivery starts smoothly and expectations are aligned.
📌 Target outcome: kickoff done + access received + tracker live + cadence agreed.
Checklist¶
Welcome & Kickoff¶
- Send welcome email
- Schedule kickoff meeting
- Share kickoff agenda (goals, scope, roles, timeline, risks)
Access & Credentials¶
- Collect necessary access and credentials
- Confirm security/compliance requirements (PII, access control, retention)
- Confirm who can grant access (IT / admin)
🔐 Do not store passwords in Notion. Store access links, account emails, and notes—use a password manager for secrets.
Communication¶
- Set up communication channels (email + Slack/Teams/WhatsApp as agreed)
- Define response expectations (SLA) for both sides
- Set up meeting cadence and calendar invites
Scope Alignment¶
- Review project scope and timeline
- Confirm success metrics + acceptance criteria
- Confirm assumptions and exclusions
Team & Execution Setup¶
- Assign project team (client + Jaspire)
- Define roles and responsibilities (RACI-style)
- Set up project tracking (Notion/Jira/Linear) and share access
- Create milestones and weekly plan for the first 2 weeks
Delivery Cadence¶
- Schedule regular check-ins (weekly)
- Schedule demos/reviews (bi-weekly or as needed)
- Confirm escalation path for blockers
Client Preferences¶
- Document client preferences and requirements
- Preferred comms channel:
- Preferred meeting times:
- Documentation expectations:
- Review/approval flow:
- Brand/security constraints:
Onboarding Record (Fill Per Client)¶
| Field | Value |
|---|---|
| Client name | {{Client}} |
| Primary contact | {{Name + email}} |
| Sponsor / decision maker | {{Name}} |
| Start date | {{YYYY-MM-DD}} |
| Kickoff date | {{YYYY-MM-DD}} |
| Project goal | {{1 sentence}} |
| Tools | {{Slack/Teams, repo, tracker}} |
| Data sources | {{DBs, files, systems}} |
| Environments | {{Dev/Staging/Prod}} |
| Risks | {{Key risks}} |