Enterprise Implementation Readiness Checklist Builder
Build a go-live readiness checklist for enterprise customer implementations covering stakeholders, data, training, support, risks, and success criteria.
Prompt Template
You are an enterprise implementation lead. Create a go-live readiness checklist for [customer/company] implementing [product/service]. Implementation context: - Customer type and size: [industry, employee count, locations] - Product or project scope: [what is being rolled out] - Go-live date: [date] - Stakeholders: [executive sponsor, admin, IT, legal, security, end users, support] - Current implementation stage: [kickoff / configuration / testing / training / pilot / final rollout] - Integrations and data dependencies: [systems, data imports, SSO, APIs] - Success metrics: [activation, usage, revenue, compliance, time saved] - Known risks or blockers: [list] - Support model after launch: [CSM, help desk, internal champion, office hours] Create: 1. Executive readiness summary using red/yellow/green status 2. Workstream checklist for technical setup, data, process, training, support, communications, and governance 3. Owner, due date, dependency, and status columns for each checklist item 4. Go/no-go criteria for launch day 5. Risk register with mitigation plans 6. Stakeholder communication plan before, during, and after go-live 7. First-30-days adoption plan with success metrics 8. Escalation path for launch-week issues 9. Post-launch retrospective agenda Make it practical enough to paste into a project plan or customer success workspace.
Example Output
# Enterprise Implementation Readiness — Northstar Logistics
Executive Summary
**Overall status:** Yellow. Core configuration is complete, but SSO testing and manager training must finish before go-live on June 12.
Readiness Checklist
| Workstream | Item | Owner | Due | Status | Dependency |
|---|---|---|---|---|---|
| Technical | Confirm SSO login for pilot users | IT Admin | Jun 3 | Yellow | IdP metadata |
| Data | Validate account import sample | CS Ops | Jun 4 | Green | CSV export |
| Training | Run manager enablement session | Customer Champion | Jun 7 | Red | Final workflow demo |
| Support | Publish internal escalation path | Support Lead | Jun 9 | Yellow | Launch room staffing |
Go/No-Go Criteria
- 95% of pilot users can log in successfully
- Critical integrations pass end-to-end test cases
- Executive sponsor approves launch communication
- Support owns documented severity levels and response times
Launch-Week Escalation
Create a shared Slack/Teams launch room with customer admin, implementation lead, support manager, and engineering on-call. Review blockers twice daily for the first 3 business days.
Tips for Best Results
- 💡Include real stakeholders and owners so the checklist becomes actionable instead of generic.
- 💡Separate technical readiness from adoption readiness; both can block launch.
- 💡Define go/no-go criteria before launch week to avoid emotional last-minute decisions.
- 💡Ask for a red/yellow/green executive version when leadership needs a concise status readout.
Related Prompts
Stakeholder Communication and Alignment Plan
Build a structured stakeholder communication plan that maps influence, interest, and preferred channels to keep all parties aligned throughout a project or initiative.
Merger Integration Planning Playbook
Build a post-acquisition integration plan covering people, systems, customers, and risk so leadership can move fast without creating chaos.
Office Relocation Change Management Plan Builder
Plan an office move with stakeholder communication, operational continuity, employee readiness, vendor coordination, and risk controls.