Skip to content

Operational Readiness Review

Template Library

Operational Readiness Review

Conduct the formal ES-111 operational readiness review across scope, support, monitoring, incidents, rollback, user transition, and risk.

ES-111 Review Readiness Review
Library AreaTemplate Library
Current PageOperational Readiness Review
FocusReview
UseReadiness Review
Repository Areadocs/template-library/operations/
← Previous Operational Risk Register
Current Operational Readiness Review
Next → Operational Readiness Summary

Template purpose

Use this template to conduct the formal ES-111 operational readiness review.

Project

<Project name>

Document control

Field Value
Artifact owner <owner>
Primary reviewers <reviewers>
Status <draft / in review / accepted / revised>
Last updated <YYYY-MM-DD>
Related Engineering Stage ES-111 — Operational Readiness
Project workspace target docs/project-workspace/operations/operational_readiness_review.md

Review information

Field Value
Review Date <date>
Reviewers <names/roles>
Release Scope <scope>
Review Decision <ready / conditional / not ready>

Review checklist

  • [ ] Operational scope matches release scope.
  • [ ] Approved users are clear.
  • [ ] Approved data is clear.
  • [ ] Disabled capabilities are clear.
  • [ ] Support owners are assigned.
  • [ ] Monitoring signals are defined.
  • [ ] Incident response path exists.
  • [ ] Rollback and stop criteria exist.
  • [ ] User transition message is clear.
  • [ ] Operational risks are assigned.
  • [ ] ES-112 readiness is clear.

Review domains

Domain Status Notes
Operational scope <ready / partial / blocked> <notes>
Support model <ready / partial / blocked> <notes>
Monitoring <ready / partial / blocked> <notes>
Incident response <ready / partial / blocked> <notes>
Rollback and stop <ready / partial / blocked> <notes>
User transition <ready / partial / blocked> <notes>
Operational risks <ready / partial / blocked> <notes>

Findings

ID Finding Severity Action Owner Status
ORF-001 <finding> <low / medium / high> <action> <owner> <open / closed>

Review decision rationale

<rationale>

Required follow-up

Follow-up Owner Due Carried Forward To
<follow-up> <owner> <date> <ES-112 / backlog>

Review checklist

  • [ ] Review decision is clear.
  • [ ] Findings have owners.
  • [ ] Required follow-up is assigned.
  • [ ] ES-112 deployment implications are visible.

Continue to Operational Readiness Summary

Proceed to the next ES-111 operational readiness artifact.

Open Operational Readiness Summary →