Firefighters running a live burn evolution at a training facility while an instructor reviews performance data on a tablet.

Reading Your Own Incident Data

Learn how to read response-time distributions, workload, unit utilisation, concurrency, incident types and other operational measures without being misled by a single average.

Full guide planned · 20 min read

The short version

Fire departments often have more data than they realise. CAD alone can contain years of incident locations, unit assignments, timestamps, workload, response patterns and resource use. The first step in becoming a data-informed organisation is not buying an analytics platform — it is learning how to ask useful questions of the information you already have. Do not begin with “what can we graph?” Begin with “what decision are we trying to make?” And be careful with averages: a mean response time can look acceptable while a significant number of incidents take far longer. The mean is the total divided by the number of incidents and is pulled about by unusual values; the median is the middle observation, with half above and half below; the 90th percentile is the point at or below which nine calls in ten fall. The distribution is how the observations are spread, and it is usually where the operation actually shows up. The same caution applies to timestamps: if you do not know where one comes from, who creates it, or whether the process changed, be careful what you conclude from it.

Start here

If you read one thing on this subject, read this.

Official resourceU.S. Fire Administration

Data Insights

USFA's National Fire Data Center turns national fire-service data into statistics, analysis and visualisations.

Why it matters

A worked example of turning operational data into something a chief can actually use.

Go deeper

Official resourceU.S. Fire Administration

The National Viewpoint

Regular analysis of what the national fire data is showing.

Why it matters

Useful for seeing how your own numbers compare with the national picture.

Official resourceU.S. Fire Administration

NERIS Public

Open incident-level NERIS data that departments and analysts can explore.

Why it matters

Somewhere to practise asking questions of real fire-service data before touching your own.

Official resourceNEMSIS

Public Dashboards

National EMS data presented as performance, clinical, surveillance and data-quality dashboards.

Why it matters

The EMS half of the same idea, and a fair model for what a public dashboard can look like.

Questions to ask your vendor

  1. Are units reaching incidents within the performance level we expect?
  2. Where are response times consistently longer?
  3. Which units are carrying the highest workload?
  4. How often are multiple ambulances committed at the same time?
  5. How often is a district covered by another station?
  6. Are turnout times different by shift, station, incident type, or time of day?
  7. Are certain units unavailable often enough to affect coverage?
  8. Has a deployment change actually improved performance?
  9. Where does each timestamp come from — call received, dispatch, turnout, arrival, patient contact, transport, hospital arrival, available?
  10. Is that timestamp created automatically or entered by a person?

This is a reading list, not a guide

Everything above was published by someone else, and is here because it is the clearest treatment of the subject we could find and verify. The Hub’s own guide to this topic is still being written. If you know a better source than the ones listed, that is worth telling us before it is.

Send a note