Start with the customer’s question
When checkout stops working, customers need more than a red indicator. They want to know whether their order was affected, which parts of the service still work, and when they should look for another update. A useful status page answers those questions while your team investigates.
PageLantern’s updated public incident layout puts that explanation into a continuous thread. An incident brings together its impact summary, affected components, and updates, giving visitors one place to follow the situation as it changes.
Make each update move the story forward
The public stages are Investigating, Identified, Monitoring, and Resolved. They give customers a consistent way to understand progress without needing your internal incident vocabulary. Publishing an incident also asks for affected components and a next-update expectation, so the first message has useful context.
For example, explain that new payments are failing while existing orders remain accessible. When you identify the cause, add what changed. During recovery, describe what you are checking before calling the incident resolved. Keep the language tied to the customer’s experience.
Keep planned work easy to find
Scheduled maintenance has its own public tab, with a short preview on the main status view. Visitors can distinguish work you announced in advance from an unexpected interruption, while still finding both from the same page.
New status-page defaults emphasize components, incidents, and maintenance. Metric cards are optional, so you can begin with the service names customers recognize and add measurements when they help explain something. A simple, maintained page is more useful than a crowded page nobody keeps current.
Build a repeatable communication habit
Open your status-page editor and review the component names before the next incident. In Published incidents, use Post update to add progress to an existing thread. Give the update a clear status and include the next-update time when you can make a reliable commitment.
Your team still writes and publishes these messages; an update expectation is a promise you manage. Assign someone to keep it current, including when the only new information is that investigation continues. After recovery, close the thread with the customer impact and any next steps.