Automated Escalation Response Time Report
Every Monday, WebRun pulls each alarm's fire time from Norav Medical alongside its escalation and acknowledgment timestamps from PagerDuty, calculates the response time for every escalation from the past week, logs the full breakdown to Google Sheets, and posts a summary to Slack for the safety team.
How do I report on telemetry alarm escalation response times?
Every Monday, WebRun matches each alarm's fire time in Norav Medical to its escalation and acknowledgment timestamps in PagerDuty, and calculates the response time for every escalation from the past week. It logs the full, ranked breakdown to Google Sheets and posts a summary to Slack for the safety team, so response times are measured, not guessed at.
- Response times are measured every week, not estimated
- Slowest cases are ranked automatically for review
- Norav Medical and PagerDuty timestamps are matched incident by incident
Built for quality and safety teams · nursing supervisors · unit directors · telemetry monitor technicians
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.noravmedical.comin a real browser with your saved login - no setup, no API keys. -
1
Norav Medical - pull each alarm's fire time
noravmedical.com
WebRun opens Norav Medical to pull each alarm's fire time. - Open the central station's alarm history for the past 7 days
- Capture the fire time, bed, and alarm type for each escalated alarm
Done when Every escalated alarm from the past week is listed with its fire time.
-
2
PagerDuty - pull escalation and ack timestamps
pagerduty.com
WebRun opens PagerDuty to pull escalation and ack timestamps. - Pull the escalation and acknowledgment timestamps for each alarm from PagerDuty's log
- Note how many escalation steps it took to reach someone
- Match each PagerDuty incident back to its Norav Medical alarm
Done when Every alarm has its escalation and acknowledgment timestamps matched.
-
3
Google Sheets - log response times for the week
google.com
WebRun opens Google Sheets to log response times for the week. - Calculate the response time, from fire to acknowledgment, for each alarm
- Log every alarm's response time and escalation steps to the week's tracker
- Rank the slowest response times for review
Done when This week's response times are logged and ranked.
-
4
Slack - post the summary to the safety team
slack.com
WebRun opens Slack to post the summary to the safety team. - Post the week's average response time and the slowest cases to the safety team's channel
- Link to the full Google Sheets breakdown for detail
Done when The safety team has this week's response time summary in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change how alarms are escalated based on the report?
No. It only measures and reports response times from what already happened. Any change to the escalation policy is a decision made by unit leadership.
How is response time calculated?
As the time between an alarm firing on the Norav Medical central station and the acknowledgment timestamp recorded in PagerDuty, matched incident by incident.
Can we see which cases were slowest?
Yes. Every week's report ranks the slowest response times first in both the Google Sheets log and the Slack summary, so patterns are easy to spot.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.