Alert Routing and Escalation Matrix

A report that is logged but not seen is only slightly better than one that was never made. The gap is usually not a missing tool. It is that nobody wrote down, for each kind of event, who gets told first, how they get told, how long they have to acknowledge, and who is next if they do not. Those rules live in a supervisor's head, which works until that supervisor is on vacation over a holiday weekend. This worksheet is the written version. Each row is one kind of event, from a fatality that triggers an OSHA report on a legal clock down to a routine observation that belongs in a weekly digest, and each column answers one of the routing questions. The example rows show a typical shape for a single site; the recipients, windows and channels are placeholders for your own names and numbers.

Fill it in with the people who will actually be on the receiving end, because they know which channel wakes them up and which one they mute. Then run one drill per quarter against the finished table and change whatever failed. Keep the acknowledgment windows honest: minutes for events that need someone on the floor now, and the next daily huddle for hazards that can wait, since a matrix that pages everyone for everything trains people to ignore it. The guide on this site covers the thinking in the section on alerts and escalation, our article on routing safety alerts to the right people goes deeper on channel choice and alert fatigue, and the article on incident logging versus official OSHA records explains why the legal reporting clocks in the first rows sit outside your internal log.