Outcome. A fixed sequence of onboarding tasks, spread over the first weeks of the account, is created and assigned automatically as soon as a deal closes, replacing a manual checklist someone copies by hand.
Workflow mapEnrollment, branches and actions at a glance
flowchart TD
A[Deal stage = Closed Won, checklist not created] --> B[Create: Send welcome packet]
B --> C[Delay 1 business day]
C --> D[Create: Confirm kickoff scheduled]
D --> E[Delay 2 business days]
E --> F[Create: Collect data migration requirements]
F --> G[Delay 3 business days]
G --> H[Create: Confirm provisioning complete]
H --> I[Delay 5 business days]
I --> J[Create: 30-day check-in call]
J --> K[Set Onboarding Checklist Created = true]
When to use it / when not to
- Use it when onboarding always follows the same short list of steps regardless of deal size (data collection, provisioning check, kickoff confirmation, 30-day check-in).
- Use it as the simplest structured option when a full ticket-based project (customer-onboarding-005) is more process than the team needs.
- Do not use it if onboarding steps genuinely branch by product or plan, build customer-onboarding-017 first and route into a checklist variant per branch.
- Do not use it for onboarding that needs status tracking with stages, not just to-do items, use customer-onboarding-011 instead.
