What is an alert roster?
By Jim Hankins
An alert roster is the ordered list of people a call-out reaches, and the sequence in which it reaches them. It is one of the oldest tools in emergency communications, it predates the technology that now carries it by decades, and almost every modern notification system is a version of it.
The definition, stripped back
An alert roster answers two questions and no others: who needs to know, and in what order. Everything else, the phones, the apps, the sirens, is delivery.
The order is the part people underestimate. A list of names is a contact sheet. A list of names with a sequence, an interval and a rule for what happens when someone does not answer is an alert roster, and the difference is the difference between information and a response.
Military origins: the recall roster
The practice is military in origin, where it is often called a recall roster. A unit that may need to assemble at short notice cannot rely on everyone happening to be reachable, so it maintains a standing list of its people and a defined order for working through it.
The classic implementation is a telephone tree: the first person called calls two more, each of whom calls two more, and the unit is notified in a fraction of the time a single caller would need. It is a manual fan-out, and for most of the twentieth century it was the fastest mechanism available.
Related practice runs through civil defense, volunteer fire services and search and rescue, all of which face the same problem, people who are not on site, not on shift, and not expecting the call.
The failure mode that defined everything after it
A telephone tree has one catastrophic weakness: it is a chain. If a link does not answer, every branch below them is silently never contacted, and nobody finds out until the muster.
Every improvement since has been an attack on that single flaw. Acknowledgement turns silence into a signal rather than an assumption. Parallel notification removes the dependency between links. Escalation defines what happens instead of nothing when a step fails. Those three ideas are the whole of modern call-out design, and all three exist because the chain broke.
Why acknowledgement is the load-bearing idea
The question an alert roster has to answer is not “did we send it?” but “did somebody take it?” Those are very different things, and only the second one ends a call-out.
This is why an acknowledgement stops escalation and silence advances it. Nothing about a delivered message proves a human read it, so a system that treats delivery as completion is measuring its own effort rather than the outcome.
From a roster of people to a roster of moments
The original alert roster was pulled when something happened: an incident, a recall, an activation. Someone made a decision and the roster ran.
The check-in inverts that trigger. Instead of an event starting the notification, the absence of an expected event starts it, a heartbeat that stopped. The roster is unchanged; what changed is that it no longer needs anybody to decide to pull it, which matters most in exactly the cases where the person who would have decided is the person in trouble.
Building one that works
Order by who can act, not by seniority or closeness. The neighbor who can knock in five minutes outranks the relative three states away, however much the relative would want to be first.
Keep it short. A roster of everyone diffuses responsibility until nobody owns the response.
Define the interval and the escalation before you need them. Improvising the order during a live call-out is how people end up phoning each other to ask who was supposed to be phoning.
And make acknowledgement explicit, so that silence means something rather than nothing.
Where AlertRoster fits
AlertRoster is a modern implementation of this idea, rosters, acknowledgement, escalation, and check-ins whose absence triggers the roster. The name is deliberate: the product is one instance of a practice that is much older than any software.
It is used by search and rescue and on-call teams, and by people working alone who want the same mechanism at household scale.
Alert rosters in practice
The same mechanism, sized to seven different situations:
“Call me when you get there” — and what happens when the call doesn’t come
“I’ll just be a minute” — the most dangerous sentence in the house
A safety net for teens that isn’t a tracker
Dating safety: set it before the date begins
Living independently, with a safety net underneath
Showing alone: a safety plan for agents
Not every job happens behind a desk
Try it
AlertRoster is at alertroster.com. Setting up a check-in takes about a minute.
AlertRoster is a call-out notification and escalation tool. It is not an emergency service and does not contact one on your behalf. It is not a fire alarm, a security alarm, or an alarm monitoring service, and it holds no life-safety certification. It should not be the only way a call-out can reach your people.
About the author
Jim Hankins is the founder and CEO of Cloud Bedrock, LLC and the developer of AlertRoster, which he first launched in 2009. A US Army combat veteran and a 42-year veteran of IT and software development, he has spent much of his career building emergency communications platforms including as CTO of GEOS, the international emergency response coordination service acquired by Garmin in January 2021, and two successful exits. He has also volunteered in search and rescue, supporting the search for missing children.