# Publish incidents, run maintenance and write postmortems

- Date: 2026-08-27
- Categories: New, Improved
- Tags: On-Call, Status pages, Uptime
- Author: The EvoHub team
- URL: https://changelog-dev.evohub.io/publish-incidents-run-maintenance-and-write-postmortems

> Publish an On-Call incident to your status page and keep it in sync, schedule maintenance that updates status pages and silences monitors in one step, and write structured postmortems.

### Incidents on your status page
- **Publish to status page** from an incident: choose the page, the affected components, the public impact and a message.
- Status changes, title and severity edits, and timeline notes then follow automatically. Unpublish at any time.
- Incident severity now uses the same scale as status pages: none, minor, major and critical.
- Add a summary when creating an incident, use per-status update templates, and edit or delete timeline entries. Changes are carried over to the status page.

### Maintenance
- A new **Maintenance** page in On-Call. Schedule a window and, in the same step, mark status page components as under maintenance and silence chosen uptime monitors.
- On-call alerts are silenced during the window unless you turn **Silence on-call alerts** off.
- Each window has a detail page with a timeline of updates. Windows can be edited, and **End now** completes a window and keeps it in the history.
- While a maintenance window is active, uptime alerts for your organization are silenced, monitors under maintenance show in blue, and alerts held back by a window say which one on their timeline.

### Postmortems
- A structured postmortem on resolved incidents (summary, root cause, contributing factors, timeline, action items and lessons learned), with starter templates.
- Keep it internal, or publish it to the incident on your status page.

### Schedules
- A schedule has its own time zone, chosen when it is created and changeable later.
- A layer can run all day and hand over at a set time, or cover only part of the day.