| Field | Details |
|---|---|
| Product Name | |
| Product Description | |
| Product Owner / PM | |
| Tech Lead | |
| Last Updated |
| Level | Definition | This Product |
|---|---|---|
| High | Outage stops core business operations. Immediate financial, regulatory, or customer impact. | [ ] |
| Medium | Outage causes significant disruption but a manual workaround exists. | [ ] |
| Low | Limited impact. Most users can continue working without it. | [ ] |
**Overall business criticality of this product:**High / Medium / Low — add brief justification
**Recovery Time Objective (RTO) — maximum acceptable downtime:**e.g. 2 hours
**Recovery Point Objective (RPO) — maximum acceptable data loss:**e.g. last 1 hour of data
Describe or diagram the key components of your product: frontend, backend, database, integrations, infrastructure, and any third-party dependencies. Note the owner of each component where known.
| Component | Description | Owner |
|---|---|---|
| Frontend | ||
| Backend / API | ||
| Database | ||
| Integration 1 | ||
| Integration 2 | ||
| Infrastructure |
List every realistic failure scenario for your product. Think component by component: database, APIs, integrations, infrastructure, security, and human error. Focus recovery strategies on High priority scenarios.
| # | Scenario | Description | Priority | Recovery Strategy |
|---|---|---|---|---|
| 1 | See Section 5.1 | |||
| 2 | See Section 5.2 | |||
| 3 | See Section 5.3 | |||
| 4 | ||||
| 5 |
For each High priority scenario, document the step-by-step recovery process. Copy the block below to add more scenarios.