# Status page: incidents

## At a glance
| Field | Set in Incido |
|-------|---------------|
| Affected components | [list] |
| Severity | Critical / High / Medium / Low |
| Notify subscribers | On for Critical/High stage changes |

---

## Message templates

**Investigating**
> We are investigating [symptom] affecting [component(s)]. Next update by [time] or sooner.

**Identified**
> We have identified an issue affecting [component(s)] and are working on a fix. [One sentence on customer impact.]

**Monitoring**
> A fix has been deployed. We are monitoring [component(s)] and will confirm when fully resolved.

**Resolved**
> The incident affecting [component(s)] is resolved. All systems are operational.

**Resolved + follow-up**
> The incident affecting [component(s)] is resolved. We are reviewing what happened and will share customer-relevant findings if needed.

### Writing rules
1. Lead with **customer impact**, not internal cause
2. Set a **next update time** while investigating
3. Update **component status** to match reality
4. Notify subscribers on **material** changes only

# Status page: maintenance

## At a glance
| Field | Value |
|-------|-------|
| Affected components | [list] |
| Window | [start] – [end] ([timezone]) |

---

## Message templates

**Scheduled**
> Maintenance on [component(s)] is scheduled from [start] to [end] ([timezone]). [Expected impact in plain language.]

**In progress**
> Maintenance on [component(s)] is in progress. [Expected impact]. We will update when complete.

**Extended**
> Maintenance on [component(s)] will take longer than planned. We now expect completion by [revised time].

**Complete**
> Maintenance on [component(s)] is complete. All systems are operational.

## Subscriber checklist
- [ ] Advance notice before window
- [ ] Start notification (if impact begins)
- [ ] Completion notification