THE USEFUL RESULT
An onboarding checklist aligned with the actual agreement, not an imagined service package.
Before you start
- An approved, appropriately redacted scope
- Known dates and owners
- The minimum information required to start
Here’s the workflow
Start after agreement
Use an accepted scope, not a sales conversation. Remove confidential terms unnecessary for drafting the checklist.
Separate responsibilities
Ask for tasks owned by you, by the client, and jointly. Mark missing owners and dates instead of assigning them automatically.
Minimize intake
Ask only for information needed for the next stage. Do not collect passwords; use the product’s own invitation or access process.
Draft a useful welcome
Give the client one clear starting action and explain what happens next. Check that the welcome does not introduce extra services or commitments.
Verify the handoff
Review the checklist with the people doing the work. Keep an access-removal step for the end of the engagement.
MAKE THIS PROMPT YOURS
Using only this approved scope [scope], draft a welcome message and onboarding checklist. Separate our tasks, client tasks, and shared approvals. Flag missing owners, dates, or permissions. Ask only for information necessary to start. Never request passwords or add services not agreed. Do not send anything or create accounts.
Replace the bracketed context with approved information. Prompt wording is not a security boundary.Check before you rely on it
- The checklist stays inside the approved scope.
- No password collection is requested.
- The client has one clear starting action.
When it does not work
Use your existing onboarding checklist and ask AI only to identify missing information.
Only automate more when it helps
Automate predictable folder or task creation after validating access rules and preventing duplicate onboarding records.