Onboarding checklist

Copy this template into your project tracker and fill in owners, due dates, and evidence.

How to use

• Duplicate the sections you need.
• Replace bracketed prompts with your details.
• Track completion status and evidence location.

Foundation

• Assign program owner — Identify the primary admin and escalation backup. · Owner: ___ · Artifact: org chart snippet.
• Confirm contracts & SLAs — Store signed order form and SLA addendum in your contract repository. · Owner: ___ · Artifact: PDF upload.
• Provision environments — Production, Sandbox, and API keys created. · Owner: ___ · Artifact: Screenshot of environment list.

Access & controls

• Enable SSO — Complete IdP connection and test failover login. · Owner: ___ · Artifact: SSO test log.
• Map roles — Apply least-privilege roles defined in Roles and SSO. · Owner: ___ · Artifact: Role assignment export.
• Set retention policies — Document legal basis and configuration in Policies. · Owner: ___ · Artifact: Policy review note.

Data readiness

• Import starter data — Load seed projects or templates. · Owner: ___ · Artifact: Import job report.
• Integrate webhooks — Verify signatures and retries. · Owner: ___ · Artifact: Webhook delivery log.
• Schedule exports — Point scheduled exports to the compliance drive. · Owner: ___ · Artifact: Cron confirmation.

Change management

• Run pilot — Complete the Quickstart with real stakeholders. · Owner: ___ · Artifact: Pilot summary doc.
• Train users — Deliver two enablement sessions (Admins + Analysts). · Owner: ___ · Artifact: Recording link.
• Publish support paths — Share Contact support and escalation matrix internally. · Owner: ___ · Artifact: Announcement post.

Launch validation

• Incident drill — Dry-run the Status and incidents playbook. · Owner: ___ · Artifact: Incident drill notes.
• Audit evidence — Store proof-of-completion in the compliance folder. · Owner: ___ · Artifact: Audit log.
• Executive sign-off — Capture sign-off from the program sponsor. · Owner: ___ · Artifact: Sign-off document.

Reference map to Version 25

Use these direct links back to Version 25.docx (mirrored in the NZ guide) when you need to double-check instructions:

• R dot quick-create workflows: Section 4.1.1 (pp. 3–9) covers New Jam/Call/Task/Note, including tables you can embed in training decks.
• Metrics, Collab, Tasks, Jams, Notes: Sections 4.1.2–4.1.6 (pp. 9–15) detail each sidebar destination so you can verify configuration screenshots.
• Notifications + Status: Sections 4.1.7–4.1.8 (pp. 15–18) show where to confirm alerts, custom statuses, support, and change log steps.
• Middle + Right panels: Sections 4.2–4.3 (pp. 18–21) outline Channels dropdowns, Shared Jams, Direct Chats, and the context rail.
• Jam deep dive: Section 5 (pp. 22–23) is the authoritative view of Video, Files, Discussion, Summary, Sentiment, and Related Tasks blocks.

Copy these references into your internal tracker so reviewers can jump directly to the canonical wording.

Celebrate