How fast should private dispatch operate?
When someone collapses in a production building, the mission clock starts before any responder receives an alert. Someone has to call security or dispatch, often one in the same. The dispatcher has to answer, figure out what’s happening, and alert the right people. At many private facilities, nobody times that part, or they’re simply recording times. Due in large part to the lack of data sharing in industry, there has been no formal study or data release that has assessed or tracked this performance.
Municipal 911 centers measure performance against published times. Fire departments measure turnout and travel time. Inside the facility’s fence like, the dispatcher that alerts a site’s firefighters, EMS, hazmat, and confined space rescue teams is often staffed by contract security officers, and the seconds and minutes to perform each step might only get evaluated after something goes wrong.
The Gap
OSHA’s confined space standard, 29 CFR 1910.146, requires a rescue service that can respond in a timely manner. It never says how fast that is. NFPA 350 helps answer the rescue question. Neither one says how fast the call should be answered or the rescue team alerted. That interval comes first, before any rescuer intervrnes, and every second lost there is lost for everyone downstream.
A Starting Benchmark
NFPA 1225 (2027 edition) sets times for emergency communications centers. It calls for 90% of emergency calls to be answered within 15 seconds and 95% within 20 seconds. It sets an objective of 60 seconds from answering to notifying the first responding unit for the highest-priority events.
NFPA 1225 is written for public communications centers, and it doesn’t say private facilities have to meet it. My argument in the white paper is that those times are still the most defensible place for a private site, with a dispatcher receiving emergency calls and dispatching facility responders, to start. A cardiac arrest, a growing fire, or a runaway reaction moves at the same speed on private property as it does in public. Using the consensus standards a site can measure against it instead of guessing.
Start by Measuring
The first job is knowing where you stand. What does the operation look like today? The five steps in the white paper start there:
- Map the response chain from the call reaching the dispatcher, to an effective force at the scene.
- Capture time stamps with a named source for each point and synchronized clocks across the dispatch system.
- Measure a baseline before setting goals.
- Adopt starting targets and document any departure from them.
- Report at the 90th percentile and review every miss.
Mapping the chain is where most of the surprises are. Facility teams have critical intervals no standard has timed: making the process safe before leaving a work area to respond, finding relief, getting out of work PPE, and crossing a large campus. Those minutes are real, and until someone assesses them there’s not a true understanding of how time impacts your incident.
If your site sees few calls, a month of data will not give you a meaningful 90th percentile. Add timed drills to assessment data and consider analyzing at a quarter or more.
What You Can Do Monday
- Synchronize the clocks on your console, alarm panels, and radio system.
- Log every event and drill for one month.
- Review every call that missed the starting targets, and find out why.
What’s in the Download
The Zenodo entry includes the white paper, a two-page executive brief for site leaders and contract managers, and an Excel workbook that calculates intervals from your event log and builds monthly and quarterly summaries. All three are free to use and adapt under CC BY 4.0.
Help Test It
The framework hasn’t been piloted yet. If your site tries it, I would like to hear what you find. De-identified interval data from a few sites would show whether the starting targets are realistic and where they need to change. You can reach me through the contact page.
