Status Page Templates for Incident Communication

What this guide covers

This guide focuses on choosing component names, short status descriptions, and update cadence before the incident starts. The goal is to make the operating decision clear before a stressful incident forces the team to improvise.

• Pre-write the four common incident states.
• Templates cut typing when stress is highest.
• Always edit the template with the real, current facts.

How Sandglass supports the practice

Prepare templates for investigating, identified, monitoring, and resolved states, then map each template to the status page components your customers recognize. Sandglass supports the continuous side of this work with checks, incidents, alert routing, and public status visibility.

• Back the practices here with HTTP, ping, TCP, content, SSL certificate, and heartbeat checks.
• Route incidents to email, Slack webhook channels, and generic webhooks so the right people respond fast.
• Use a public status page to keep customers informed while the team works the incident.

Common mistakes to avoid

Templates should reduce typing under pressure, not hide uncertainty. Keep them short and edit them with real facts during the incident.