Get Worker Impact

A headline figure for the current month, with its change.

Either field is None when nothing was measured, so clients show unavailable rather than zero. The change compares the month so far against the prior month cut to the same elapsed days; against the whole of it, the 1st would report a collapse that never happened.

A headline figure for the current month, with its change.

Either field is None when nothing was measured, so clients show unavailable rather than zero. The change compares the month so far against the prior month cut to the same elapsed days; against the whole of it, the 1st would report a collapse that never happened.

The constants these figures were priced with, returned so the client's copy reads the same numbers rather than restating them.

Why each value is what it is:

• incident_duration_hours (4h, from the ROI framework) is assumed, not measured. The only signal for when an incident ended is the agent's own last post, so a measured duration would grow whenever the agent is slower to notice resolution, and every figure derived from it would improve as the product got worse.
• incident_active_fraction (30%) is the share of an incident a responder is hands-on rather than watching.
• incident_efficiency (10%) is what Traversal removes from that hands-on time, and also drives downtime averted.
• incident_avoidance (10%) covers responders never pulled in at all, so it is added to efficiency rather than compounded with it.
• minutes_per_alert_response (10 min) sits below the alert-stories figure the ROI framework quotes, because an alerts Worker answers every fire where alert stories counted only the ~7% opening a fresh investigation.
• responder_window_hours (4h) is a measurement bound, not a price: how long after a Worker joins a poster still counts as responding. Separate from incident_duration_hours because one number doing both jobs made the figures scale non-linearly in it — raising it admitted more responders and raised the per-responder rate.

Uniform across organizations, since comparing two customers' hours only means something if both were priced the same way.