Standards of Cover

Standards of Cover: An Overview

A Standards of Cover (SOC) states how quickly, and with how many people, your department will reach each kind of emergency in each part of your community.


This guide covers what goes in an SOC, the data it takes, how to set response-time objectives, and how departments keep theirs current between studies.

Darkhorse Response HQ showing 90th percentile performance for each interval against its target

Definition

What is a Standards of Cover?

What is a Standards of Cover?

What is a Standards of Cover?

The Commission on Fire Accreditation International (CFAI) defines it as “those written policies and procedures that establish the distribution and concentration of fixed and mobile resources of an organization.”


Put simply, it is the service level your department commits to, measured against the service it delivers.

What goes in an SOC

A

Description of the community

Legal basis, history, finances, geography, population and growth. The context every later section leans on.

B

Services provided

Every program you run, and how your stations, apparatus and staff are deployed today.

C

Community expectations and goals

What residents and elected officials expect from the department, gathered and written down.

D

Community risk assessment

Fire, EMS, technical rescue, hazmat and other risks, scored by probability and consequence, area by area.

E

Historical system performance

Distribution, concentration, reliability and comparability, measured from your own incident data.

F

Performance objectives

Benchmarks (your goals) and baselines (your actual 90th-percentile times), by program and risk level.

G

Compliance methodology

Who measures performance, how often, and how gaps get reported and acted on.

H

Evaluation and recommendations

Where the department falls short, why, and what to change first.

CRA, SOC and accreditation

Two parts: The CRA and the SOC

The two are usually written together and submitted as one document, the CRA-SOC. CPSE requires a completed CRA-SOC and a community-driven strategic plan before an agency can become an Applicant for accreditation.


Each one answers a different question.

01 · Community Risk Assessment

What can happen, and where

Scores the fire, medical, rescue and hazmat risks in your community by probability, consequence and impact, area by area.

“What are we protecting against?”

02 · Standards of Cover

What you send, and how fast

Turns that risk into deployment: which units, staffed how, arriving within what time, for each risk level and population density.

“What will we send, and how quickly?”

03 · CPSE accreditation

Whether you do what you said

Peer assessors check both documents against your measured performance. Accredited agencies then report on it every year.

“Are we meeting our own objectives?”

Data you need

Most of an SOC comes out of your CAD and RMS.

Most of an SOC comes out of your CAD and RMS.

Most of an SOC comes out of your CAD and RMS.

These are the inputs a defensible SOC draws on. Plan on three to five years of history, because a single year can hide a trend.

CAD

Incident records

Every call with its type, priority, location and final disposition, for three to five years.

CAD

Unit timestamps

Call received, dispatched, en route, on scene and cleared, for every responding unit. Alarm handling, turnout and travel times all come from here.

CAD · RMS

Apparatus and staffing

Which units exist, where they are housed, how they are staffed, and when they are out of service.

RMS

Incident outcomes

NFIRS or NERIS reports: fire spread, property loss, patient care and actions taken on scene.

GIS

Stations and road network

Station locations and a routable street network, so travel time comes from the roads your crews drive.

Planning

Population and growth

Census population, density by area, and approved development, so the SOC can look ahead as well as back.

Assessor · RMS

Buildings and occupancies

Occupancy type, size, age and target hazards. These feed the risk scores in the CRA.

Agreements

Mutual and automatic aid

Who responds into your area, who you cover, and how quickly each of them arrives.

Response-time objectives

Objectives are set at the 90th percentile, by program and risk.

Objectives are set at the 90th percentile, by program and risk.

Objectives are set at the 90th percentile, by program and risk.

Each objective names a program (fire, EMS, rescue, hazmat), a risk level, a population density, a response element and a time. Measuring at the 90th percentile describes the response nine residents in ten receive.


Averages hide the slowest calls; those are the calls residents and councils remember.

The response-time continuum

Call clock
  1. Alarm handling1:00

    Call answered to unit dispatched

  2. Turnout1:20

    Unit dispatched to wheels rolling

  3. Travel4:00

    Wheels rolling to arrival on scene, the largest share of total response time

Total response time 6:20Illustrative fire call: 60 seconds of alarm handling, 80 seconds of turnout and 4:00 of travel add up to 6:20, the benchmark in the examples below.

Distribution

How quickly the first unit arrives. Station locations and the road network decide it.

Measured by first-due travel time

Concentration

How quickly the effective response force (ERF) assembles: enough people on scene for the critical tasks at that risk level.

Measured by ERF total response time

Reliability

How often the first-due unit is free to take calls in its own area. Unit hour utilization (UHU) drives it.

Measured by first-due availability

Benchmark and baseline

Every objective carries two numbers.

01

The benchmark is your goal. The service level the department and council agree on, for example a first-due engine within 6:20 total response time, 90% of the time.

02

The baseline is what you deliver. Your actual 90th-percentile time over the last three to five years, calculated from CAD timestamps.

03

The gap is the plan. Where the baseline misses the benchmark, the SOC explains why and what will close the gap.

NFPA 1710 reference values

60s

Turnout time for EMS calls

80s

Turnout time for fire and special operations

4:00

Travel time for the first-arriving engine

8:00

Travel time for the full first-alarm assignment at a low- or medium-hazard fire

90%

Of incidents should meet each value

NFPA 1710 covers career departments, and NFPA has since carried it into NFPA 1750. Most SOCs still cite 1710. Your own objectives follow your risk levels and population densities.

Examples

What objectives may look like

What objectives may look like

What objectives may look like

Accredited agencies publish their SOCs, and reading two or three is the fastest way to learn the format. Here is a typical set of objective statements, followed by public SOCs worth reading.

Distribution · benchmark

For 90% of moderate-risk structure fires in urban areas, the first-due engine, staffed with four firefighters, shall arrive within 6:20 total response time.

Concentration · benchmark

For 90% of moderate-risk structure fires in urban areas, an effective response force of 16 firefighters shall arrive within 10:20 total response time.

Distribution · baseline

From 2022 to 2025, the first-due engine arrived within 7:04 at 90% of moderate-risk structure fires in urban areas. The gap to the benchmark is 0:44.

Illustrative statements in the format accredited agencies use.

Why SOCs go stale

Why Your SOC Can Become Outdated

Chiefs describe the same situation: the study is a few years old, the city has changed, and nobody can say how far the numbers have moved. These are the usual reasons.

Chiefs describe the same situation: the study is a few years old, the city has changed, and nobody can say how far the numbers have moved. These are the usual reasons.

01

Growth lands where the stations are not

New subdivisions and annexations add calls at the edge of first-due areas, where travel times are longest. The 90th percentile moves before the average does.

02

Busier units cover less of their own area

As call volume climbs, unit hour utilization rises and the first-due engine is out more often, so a unit from farther away takes the call. Reliability slips first, then response time.

03

A faster department can still miss its targets

Most calls arrive on ordinary days, with most units available. Small everyday delays in turnout and travel move the 90th percentile more than the rare overloaded night does. Read the analysis →

04

The deployment changes underneath it

A unit gets cross-staffed, a company moves, a shift pattern changes. Each one shifts your effective response force times, while the SOC still describes the old system.

05

The numbers live in a one-time report

When the analysis is a study, updating it means another study. So the SOC waits for reaccreditation five years later, and the annual compliance report gets rebuilt by hand in between.

So

Keep the SOC connected to the data that changes it.

A living SOC recalculates your baselines as new CAD data comes in, shows which objectives are slipping and where, and lets you test a fix before you take it to council: moving a unit, adding a peak-hour company, siting a new station. Darkhorse Response does that measuring and modeling, and Darkhorse Risk keeps the risk assessment underneath it current.

In practice

Keeping a plan true while the county grew.

Keeping a plan true while the county grew.

Keeping a plan true while the county grew.

Strathcona County grew by more than 20% in eight years, and its two urban stations in Sherwood Park fell behind their response targets. The county modeled call growth and drive times 15 years out, sited a third urban station, and opened it in 2013. A year later, the measured effect on response performance was within 1% of the forecast made five years earlier.

Strathcona County grew by more than 20% in eight years, and its two urban stations in Sherwood Park fell behind their response targets. The county modeled call growth and drive times 15 years out, sited a third urban station, and opened it in 2013. A year later, the measured effect on response performance was within 1% of the forecast made five years earlier.

Strathcona County Emergency Services

Alberta · 6 stations, 3 more planned · Darkhorse Response

Use case

Within 1% of forecast, five years later

Population 98,000+ · 20%+ growth, 2001 to 2009

The county keeps refreshing its forecasts with new census data, so it can see when and where a response target is about to slip, and time the next station to match.

Watch · CPSE-sponsored webinar

Evidence-based deployment and station planning

How departments set deployment objectives from their own incident data, and test station and unit changes against them before committing budget.

Keep reading

Darkhorse Articles on SOC performance.

Darkhorse Articles on SOC performance.

Next step

Your own baselines, on your own data.

Every dollar counts.
Every second counts.
Every decision counts.
Every life counts.