| Approval gate | A single named approver authorises before the technologist is contacted. | Two different roles may activate depending on the unit. | conflicting | Ambiguous authority is the most common driver of avoidable callbacks in this dataset. |
| Qualifying clinical criteria | The organization states its qualifying indications explicitly. | Left to the requesting service with no written criteria. | absent | Requires physician and medical leadership authorship; NeuroOps supplies no clinical criteria. |
| Target response interval | Acknowledgement plus on-site interval, with escalation starting when the target is at risk. | Single 60-minute response figure, no acknowledgement step. | narrower | No early-warning point; escalation currently starts after the window has already failed. |
| Escalation ladder | Named ordered ladder with logging past step two. | Informal ladder described verbally; not in the document. | absent | No escalation data exists, so the operational review has nothing to work from. |
| Callback burden ceiling | Stated ceiling plus relief mechanism. | Not addressed. | absent | Callback load currently sits near the top of the illustrative demo range with no trigger. |
| Personnel qualification | Required role level and modality competency stated. | Not addressed; anyone in the rotation takes the call. | absent | Two of three rotation members have a critical-care competency lapsing this month. |
| Minimum safe coverage definition | Stated per shift and modality with deferral rather than attempt. | No written definition. | absent | Deferral decisions currently rest on one person's judgement with no institutional backing. |