onpage logo

What's Post-Mortem Reporting

Blameless post-mortems allow us to examine mistakes in a way that focuses on the situational aspects of a failure’s mechanism and the decision-making process of individuals proximate to the failure. – The DevOps Handbook 

The engineers at Google describe post-mortem reporting as a “Written record of an incident, its impact, the actions taken to mitigate or resolve it, the root cause(s), and the follow-up actions to prevent the incident from recurring.”

Post mortem reporting

audit trail

Significance of Post-Mortem Reporting

Post mortems are necessary as they give us insight into why an incident happened. They allow us to deconstruct a particular incident and see what transpired after the critical event and how that can be improved  in the future. Was the problem due to a scheduled or unscheduled incident? When the Sev-1 incident  occurred, was the right team notified? If the team was notified, did they actually hear the alert or did the alert just go off as a ping on their smartphone?


OnPage's Real-Time and Post-Mortem Reporting

Real-Time Insights

The reporting dashboard provides quick, real-time views into all activities, including the number of messages received each day, the top responders and the method used to respond. With these insights, managers can better estimate workloads and resources, view progress and response time. They can also determine which team members are spending the most time responding to issues and reassign upcoming incident management to others to provide relief.

Post mortem reporting

Real-Time Audit Trails

Team members gain instant visibility into incident notifications, escalations and acknowledgments with time-stamped audit trails to ensure that each incident is being managed appropriately and effectively. This report shows the subject of the alert message, when it was created, who responded and when they responded.

Downloadable Reports

Post incident reviews (PIR) and post-mortem meetings are now easier to prepare with downloadable reports of incident alert management metrics. Teams can review the data, discuss and discover any issues and correct them to help teams improve incident alert performance.

Data includes each alert sent, the number of incidents, a record of time-stamped responses received and missed alerts, groups and team members involved, and more. Post-mortem reporting makes it easy to review current or historical incident response to identify workflow pitfalls, areas where the process is not being followed correctly or HR issues. Reports and charts can also reveal if there are team members who are taking too much of the burden of responding to incidents, providing opportunities to balance responsibilities among others to keep everyone motivated.

Post mortem reporting

OnPage Post-Mortem Reporting

Gain instant visibility into your team’s incident load by month and response performance through OnPage’s Reporting Dashboard. Watch the video to learn more. 

New Feature Enhancements

New OnPage dashboard

Sophisticated Dashboard Data

We are pleased to announce a refreshed UI to the OnPage dashboard. The new, modern interface incorporates enhancements that make the interactions intuitive, without compromising the efficacy of intelligence reporting. The advanced dashboard provides a detailed snapshot of responder activities and message statistics.

Message Notes on Report Console

The OnPage reporting console now allows users to compose incident notes. Transcribe what occurred during the incident and detail when critical events were resolved. OnPage message notes are fully downloadable and perfect for post-incident analysis.


Live call routing reporting

Powerful Live Call Routing Reports

Gain intelligent insights into your team’s live call routing usage with time stamps and response statuses with OnPage’s reporting dashboard for Live Call Routing. The customizable reports can be exported for further analysis by managers.


See OnPage in Action.

Learn more about Real-Time Reporting, Escalation Policies and On-Call Scheduling. Request a demo.

  • This field is for validation purposes and should be left unchanged.