4 status page templates for incident updates
Copy and adapt incident communication templates for planned maintenance, minor and major incidents, and complete outages. Includes first, progress, and resolution updates.
The payment button is failing, and the status page has just turned red. A customer still needs to know whether they can finish a purchase and when they should check back. The on-call team can answer both questions before it knows the cause.
The four status page templates below cover planned maintenance, a minor incident, a major incident, and a complete outage. Replace the bracketed fields with verified information. Remove lines you cannot substantiate or that do not apply.
Before you post
- Acknowledge the incident promptly. The first update can describe the symptom and what you are checking. Say when the scope is still unknown.
- Give a time and time zone for the next update. A commitment to post again is separate from an estimate of when service will return. Post at the promised time even if the investigation is ongoing.
- For maintenance, allow people time to plan around the affected features. Base the notice period on expected impact and existing commitments, and include the start and end of the planned window.
- Share information customers can act on. Keep credentials, raw internal logs, identifiable customer data, and unconfirmed causes out of the public update. Use a progress update while you are still verifying recovery. Atlassian incident communication tips · PagerDuty external communication guidelines
1. Planned maintenance
Use this for work such as a database migration or an upgrade. Update the notice if the planned window changes.
Scheduled
We plan to perform maintenance on [service] from [start] to [end] ([time zone]). During that window, [feature] may [expected impact]. If you need to plan around the work, see [verified guidance or workaround].
In progress
Maintenance on [service] has started. [Confirmed status of the affected feature.] We will update this page by [time and time zone].
Completed
Maintenance on [service] ended at [time and time zone]. We have verified that [affected feature] is available again. Thank you for your patience.
If the work is done and user-facing checks are still running, post that as progress. Some platforms can move a maintenance record forward on a schedule. Check whether your publishing workflow still calls for manual verification. Atlassian scheduled maintenance documentation
2. Minor incident
Use this when the impact is known to be limited, such as one secondary feature being unavailable. If you are still working out the scope, describe the symptom you have verified and update the severity later.
Investigating
We are investigating an issue with [feature]. So far we have observed [confirmed symptom]. Our next update will be by [time and time zone].
Progress
We have confirmed that [affected users or scope] see [symptom] when using [feature]. We are [current action or check]. We will post again by [time and time zone].
Resolved
We verified that [feature] was available again at [time and time zone]. If you are still seeing [symptom], please let us know through [support channel].
A small incident still deserves a clear update. Leave out a workaround or recovery estimate you have not verified.
3. Major incident
Use this when a core workflow is affected or when the evidence shows a wider impact.
Investigating
We are investigating a disruption to [core feature]. We have confirmed [scope and symptom users see]. We will update this page by [time and time zone].
Mitigating and monitoring
We have [mitigation we can share]. We have observed [verified improvement and remaining impact] and are checking [key user action]. We will post again by [time and time zone].
Resolved
[Core feature] recovered at [time and time zone]. We have verified [key user action]. For [remaining delays, backlogs, or steps users may need to take], see [follow-up guidance or support channel]. We’re sorry for the disruption.
Keep reporting any material impact. If your team publishes a postmortem, include the verified timeline, customer impact, and follow-up actions.
4. Complete outage
Use this when you have confirmed that the named service is unavailable within the stated scope. Identify regions or functions that are still working separately.
Investigating
[Service] is unavailable in [confirmed scope]. Users may be unable to [key action]. We are responding and will post another update by [time and time zone].
Recovering
[Verified feature or region] is recovering. [Feature or region still affected] remains unavailable. We are verifying [key action]. We will update this page by [time and time zone].
Resolved
We verified that [service] was available again in [verified scope] at [time and time zone]. For requests still awaiting action, follow [verified instructions]. We’re sorry for the interruption.
For a wide outage, follow the cadence in your runbook and keep a publishing route that works when the primary service is down. Decide what follow-up to publish according to your incident process, customer commitments, and review.
Put the templates in the on-call workflow
- Keep a copy in the runbook. Name who confirms impact, who publishes, and who owns the next update. Record a primary and backup publishing route.
- Use them in a drill. Walk through a simulated alert and draft the first update. Test access, placeholder replacement, time zones, and recovery checks against your team’s response targets.
In Guance, monitor and Incident Center records can help the responder compare the alert with the response timeline. Use a separate, reviewed public note for the customer message. With a workspace Custom Status Page, set the note’s business date and record type, link any confirmed affected services, and enable display before publishing. Leave affected services blank if the scope is still unknown. The record then appears in history only when All Services is selected. After publication, saving a title or body edit to the source note updates what readers see. Association changes such as affected services require republishing. Guance’s official platform status page reports on Guance’s own service. Guance Incident Center · Custom Status Page configuration · Guance official Status Page documentation
Frequently asked questions
Should the update name a technical cause?
Share a cause when it is verified and suitable for publication. During the investigation, explain the impact, the work in progress, and the next update time. Put detailed analysis in a reviewed follow-up.
How often should we post?
Use the severity, material changes, and your notification commitments to set the cadence. Post when the impact changes materially, and keep any time you already promised, even if the investigation has no new conclusion.
Can we use a lighter tone?
Use your usual voice where it helps people understand the message. Keep the facts easy to find. Readers want to know what changed, whether to take action, and when to check again.
Does planned maintenance need a completion update?
Mark an announced maintenance as complete once the work is finished and the affected features have been verified. If the work runs long or users still see a problem, post the current state and the next update time.
References
Contact us
Join the community
to join the community
Try Guance
Start online and pay only for what you use.
Get startedChoose a Guance plan
