AdvancedDeliverablesFree prompt

Go-Live Plan with Rollback Procedures and No-Go Criteria

Detailed production deployment plan with decision gates and rollback procedures.

Create a go-live plan that minimizes deployment risks, establishes clear go/no-go criteria, defines deployment windows, and ensures rollback capability in case of critical issues.

At a glance

Access

Free prompt

Open to copy without upgrading.

Prompt objective

Create a go-live plan that minimizes deployment risks, establishes clear go/no-go criteria, defines deployment windows, and ensures rollback capability in case of critical issues.

Real use case

FarmaVida pharmacy chain is migrating the POS system across 120 stores in 3 waves over weekends. The previous go-live (8 months ago) caused 6 hours of downtime and R$280,000 in lost sales. The CTO requires a plan with a no-go gate and tested rollback.

Customize these fields first

PROJECT NAMEWHAT WILL BE DEPLOYEDDATEE.G., SATURDAY 10PM - SUNDAY 6AME.G., 120 STORES IN 3 WAVESQUANTITYLIST SYSTEMS THAT DEPEND ON OR ARE IMPACTED BY THIS DEPLOYMENTDESCRIBE WHAT HAPPENED

Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.

Prompt

Develop a complete Go-Live Plan for:\\\\\\\\n\\\\\\\\nProject: [PROJECT NAME]\\\\\\\\nSystem/Product: [WHAT WILL BE DEPLOYED]\\\\\\\\nPlanned Date: [DATE]\\\\\\\\nDeployment Window: [E.G., SATURDAY 10PM - SUNDAY 6AM]\\\\\\\\nEnvironments: [E.G., 120 STORES IN 3 WAVES]\\\\\\\\nImpacted Users: [QUANTITY]\\\\\\\\nIntegrated Systems: [LIST SYSTEMS THAT DEPEND ON OR ARE IMPACTED BY THIS DEPLOYMENT]\\\\\\\\nLast Go-Live Incident: [DESCRIBE WHAT HAPPENED]\\\\\\\\n\\\\\\\\nThe plan must include:\\\\\\\\n\\\\\\\\n**Phase 1 — Preparation (T-14 days to T-1):**\\\\\\\\n1) Readiness checklist (30+ items):\\\\\\\\n   - Production environment validated\\\\\\\\n   - Data migrated and reconciled\\\\\\\\n   - User acceptance testing (UAT) completed with sign-off\\\\\\\\n   - User training completed\\\\\\\\n   - Operational documentation updated\\\\\\\\n   - Communication sent to all impacted parties\\\\\\\\n   - On-call team confirmed\\\\\\\\n2) Dry run (full rehearsal):\\\\\\\\n   - Dry run date and environment\\\\\\\\n   - Scenarios to test\\\\\\\\n   - Dry run success criteria\\\\\\\\n\\\\\\\\n**Phase 2 — Go/No-Go Gate (T-1 day):**\\\\\\\\n3) Decision meeting:\\\\\\\\n   - Mandatory participants\\\\\\\\n   - GO criteria (ALL must be TRUE):\\\\\\\\n     [10 SPECIFIC CRITERIA FOR THIS PROJECT]\\\\\\\\n   - NO-GO criteria (ANY one blocks deployment):\\\\\\\\n     [5 BLOCKING CRITERIA]\\\\\\\\n   - Final decision authority: [ROLE/TITLE]\\\\\\\\n   - Decision communication: who notifies whom\\\\\\\\n\\\\\\\\n**Phase 3 — Execution (Go-Live Day):**\\\\\\\\n4) Step-by-step runbook:\\\\\\\\n   - Action sequence with owner and time\\\\\\\\n   - Checkpoints between stages\\\\\\\\n   - Scripts/commands to execute (reference)\\\\\\\\n   - Success criteria for each stage\\\\\\\\n5) War room:\\\\\\\\n   - Participants and communication channels\\\\\\\\n   - Status update frequency\\\\\\\\n   - Escalation matrix during go-live\\\\\\\\n\\\\\\\\n**Phase 4 — Rollback:**\\\\\\\\n6) Rollback activation criteria:\\\\\\\\n   - Point of no return (after this point, rollback is not viable)\\\\\\\\n   - Scenarios that trigger rollback\\\\\\\\n   - Rollback decision authority\\\\\\\\n7) Step-by-step rollback procedure\\\\\\\\n8) Estimated rollback time\\\\\\\\n9) Rollback communication (internal and external)\\\\\\\\n\\\\\\\\n**Phase 5 — Stabilization (T+1 to T+14):**\\\\\\\\n10) Intensive monitoring (metrics and alerts)\\\\\\\\n11) Criteria for closing post-go-live support\\\\\\\\n12) Handover to operations (BAU)\\\\\\\\n\\\\\\\\nFormat: operational plan with runbook, checklists, decision criteria, and communication templates.

Open directly in an AI — the text is pre-filled:

How to use this prompt

  1. 1Replace the key placeholders first: PROJECT NAME, WHAT WILL BE DEPLOYED, DATE, E.G., SATURDAY 10PM - SUNDAY 6AM.
  2. 2Replace any bracketed placeholders like [this] with your own context.
  3. 3Add extra background information when you want more tailored results.
  4. 4Combine multiple prompts in one conversation when you need a richer output.
  5. 5Save your best-performing prompts so they are easy to reuse later.

Next best step

Open the guide first, then branch only if you still need more.

A guide for choosing prompts, tools, courses, and workflows without creating expensive tool sprawl.

If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.

Related prompts

View all

Explore other prompt categories

Move sideways into adjacent libraries when the current category is not the full answer.

Free browsing stays open. Premium prompts unlock the reusable workflow layer.

Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.

Free access

  • Browse guides, role paths, and category pages.
  • Preview prompts before you decide to upgrade.
  • Find the right starting point without friction.

Membership access

  • Unlock premium prompts and the full copy text.
  • See more workflow paths and course connections.
  • Keep the reusable templates in one place.
Chat on WhatsApp