§ 01 · Why response time matters
The physics don't negotiate
A modern room fire reaches flashover in 4–8 minutes. Cardiac-arrest survival falls roughly 7–10% for every minute without CPR and defibrillation. Every standard in this document exists to protect a segment of the same short chain of minutes.
The cascade — who controls which minutes
Cumulative time from 911 call answered, at the NFPA 1750 station-based objectives (90th percentile)
| Segment | Objective | Controlled by | What is happening |
|---|
| Detection & call | variable | Community | Fire grows / patient deteriorates until someone calls 911 — why smoke alarms and AEDs are response-time programs |
| Alarm handling | 1:04 | Dispatch center | Call answered, located, dispatched (NFPA 1225) |
| Turnout | 1:20 fire · 1:00 EMS | Fire companies | Crew to apparatus, en route — the segment the firehouse owns |
| Travel — first unit | 4:00 | Deployment (stations) | First engine / first EMS unit driving |
| Travel — full force | 8:00 / 10:10 | Deployment + staffing | Assembling the effective response force |
| Setup & intervention | ~2:00 | Training | Line stretched, water on fire / compressions started |
▸ The takeawayAgainst a 4–8 minute flashover window, the department-controlled segments total
6:24 at objective. There is no slack in this chain — which is why each segment is measured separately, at the 90th percentile, in
Report 3.
§ 02 · Community risk summary — imported from Report 1
What this standard must cover
Composite risk
R 7.5
Moderate · 1 High zone (Z-06)
Demand zones
4·4·2
urban · suburban · rural
Population
34,800
19.2% over 65
Annual demand
2,410
60% EMS · +2.8%/yr
Concurrency
23%
calls beginning while committed
§ 03 · Response-time objectives — the adopted standard
What we promise, zone by zone
Two framings, both adopted: station-based element objectives (each segment of the cascade, everywhere) and demand-zone totals (the end-to-end promise, scaled to density per NFPA 1750 Table 7.4.2). A response is compliant when it meets the objectives of its own zone and risk class.
3.1 — Station-based element objectives (governing)
All zones · 90th percentile
| Element | Objective | Personnel |
|---|
| Alarm handling (create → dispatch) | 1:04 | — |
| Turnout — fire | 1:20 | — |
| Turnout — EMS | 1:00 | — |
| Travel — first engine | 4:00 | 4 |
| Travel — EMS first response (AED) | 4:00 | 2 |
| Travel — ALS arrival | 8:00 | 2 |
| Travel — ERF, Low/Moderate | 8:00 | 20 / 28 |
| Travel — ERF, High | 10:10 | 42 |
3.2 — Demand-zone totals (NFPA 1750 Table 7.4.2)
Call received → first unit on location · reliability standard per zone
| Demand zone | Density | Total response | Standard | Min staff | Fairview zones |
|---|
| Urban | >1,000/mi² | 9:00 | 90% | 15 | Z-03 · Z-04 · Z-06 · Z-09 |
| Suburban | 500–1,000/mi² | 10:00 | 80% | 10 | Z-02 · Z-05 · Z-07 · Z-08 |
| Rural | <500/mi² | 14:00 | 80% | 6 | Z-01 · Z-10 |
Derived planning totals (call received → on scene): first engine 6:24 · ERF Low/Moderate 10:24 · ERF High 12:34. Observed 90th percentiles are computed from incident-level totals, never by summing component percentiles.
3.3 — EMS response objectives (integrated service line)
EMS is a co-equal service line, not an add-on — 60% of Fairview demand
| Objective | Time | Standard | Notes |
|---|
| First responder with AED on scene | 6:04 total | 90% | alarm 1:04 + turnout 1:00 + travel 4:00 |
| ALS provider on scene | 10:04 total | 90% | MEDIC units — Stations 1, 3, 5 |
| Cardiac-arrest response force | 10:24 | 90% | 6 personnel — see §05 critical tasks |
| Demand-zone totals | 9:00 / 10:00 / 14:00 | 90 / 80 / 80% | same zone promise as fire |
§ 04 · Effective response force by hazard class
How many people the risk demands
First-due gets there first; the ERF puts the fire out. Requirements derive from the critical-task analysis in §05 and attach to the risk classes established in Report 1.
| Hazard class | Typical occupancy | ERF personnel | Assembly objective | Applies in |
|---|
| Low | Detached single-family, outbuilding | 20 | 10:24 | All zones |
| Moderate | Rowhomes, garden apartments, small commercial | 28 | 10:24 | Z-03 · Z-04 · Z-09 typical |
| High | Industrial park, senior living, mall, schools | 42 | 12:34 | Z-06 target hazards |
| Cardiac | Out-of-hospital cardiac arrest | 6 | 10:24 | All zones |
✕ The honest gapFairview's on-duty career strength is 7 (Stations 1–2). Every ERF above Low requires volunteer turnout and/or automatic aid by design. Daytime assemble-able force averages ~21 — below the Moderate ERF of 28. This is a standards document, not a press release: the gap is stated here and measured quarterly in Report 3 §04.
§ 05 · Critical task analysis
Where the numbers come from
ERF counts are not opinions — they are the sum of tasks that must happen simultaneously to stop the event.
Structure fire — Moderate hazard (28 personnel)
| Task | Personnel |
|---|
| Command & safety | 2 |
| Pump operator / water supply engineer | 1 |
| Initial attack line (2½ capability) | 4 |
| Backup line | 4 |
| Primary search & rescue | 4 |
| Ventilation / ladder company | 4 |
| Rapid intervention team (RIT) | 4 |
| Sustained water supply | 2 |
| Utilities · rehab · support | 3 |
| Total | 28 |
High hazard adds a second attack/search complement, aerial operations and expanded command → 42. Low hazard consolidates to 20.
Cardiac arrest — EMS (6 personnel)
| Task | Personnel |
|---|
| High-quality compressions (rotating pair) | 2 |
| Airway management | 1 |
| ALS — monitor, meds, defibrillation | 1 |
| Documentation / timekeeper / code lead support | 1 |
| Family care & logistics / lift | 1 |
| Total | 6 |
▸ Why this is in a fire SOCThe same dual-role personnel deliver both service lines. A cardiac arrest commits 6 people for 45–80 minutes — which is why EMS critical tasking, and the concurrency it creates, belongs in the Standards of Cover rather than a separate document.
§ 06 · Current deployment profile
What the system fields today
| Station | Model | Apparatus | First-due zones | ERF role |
|---|
| Station 1 — HQ | Career · 4/shift | ENG 1 · ENG 1-2 · LAD 1 · RES 1 · AMB 1 · MEDIC 1 | Z-03, Z-09 | First-due core + ladder |
| Station 2 | Career · 3/shift | ENG 2 · TWR 2 · AMB 2 | Z-04, Z-05 | Second engine + tower |
| Station 3 | Combination · 2 career day | ENG 3 · ENG 3-2 · RES 3 · AMB 3 · MEDIC 3 | Z-06, Z-07, Z-08 | High-zone first-due · ALS |
| Station 4 | Volunteer | ENG 4 · BRUSH 4 · TANKER 4 · AMB 4 | Z-02, Z-10 | Rural water · WUI |
| Station 5 | Volunteer | ENG 5 · TANKER 5 · AMB 5 · MEDIC 5 | Z-01 | Rural first-due · ALS |
Personnel
| Career firefighter/medics | 38 |
| Active operational volunteers | 82 |
| On-duty career strength (24/7) | 7 |
| Avg turnout-capable — day | ~21 |
| Avg turnout-capable — night | ~38 |
§ 07 · Achievability — the standard vs. the system we have
Can this deployment deliver this standard?
Modeled honestly, before measurement: coverage geometry, assemble-able force, and the concurrency constraint. Measured attainment is Report 3's job.
7.1 — Modeled first-engine coverage
| Threshold | Population covered | Verdict |
|---|
| 4:00 travel (station-based objective) | 47% | Urban core only |
| 8:00 travel | 88% | All but rural fringes |
| Urban zones within 9:00 total | ~95% | Achievable |
| Rural zones within 14:00 total | ~90% | Achievable with reliable turnout |
7.2 — ERF capability vs. requirement
| Requirement | Need | Day | Night |
|---|
| Low ERF | 20 | ~21 ⚠ | ~38 ✓ |
| Moderate ERF | 28 | below ✕ | ~38 ✓ |
| High ERF (Z-06) | 42 | aid req'd ✕ | aid req'd ✕ |
| Cardiac force | 6 | ✓ | ✓ |
✕ 7.3 — The concurrency constraint
All objectives above assume an idle system. In reality 23% of calls begin while units are committed (Report 3 §05), and the measured concurrency penalty is +1:33 to +1:48 on the total-response 90th. The standard therefore adopts: (a) automatic aid for all High-class ERFs and daytime Moderate ERFs; (b) a monitored overlap-rate threshold of 25%, beyond which peak-demand staffing must be brought to the governing body as a budget question, not an operational one.
§ 08 · Alarm handling — NFPA 1225
The dispatch center's segment
| Interval | Objective | Standard |
|---|
| Call answer | 0:15 | 95% |
| Answer → dispatch (emergent) | 1:04 | 90% |
| EMD compliance (pre-arrival instructions) | — | program std |
Fairview is dispatched by the county communications center; these objectives are adopted jointly and reported in Report 3's alarm-handling measure card — currently the system's strongest metric (97–98% meeting).
§ 09 · Water supply standard
Flow, everywhere, by design
| Setting | Standard |
|---|
| Hydranted zones (82% of protected properties) | Establish supply from municipal hydrant within creditable distance; sustained fire flow per pre-plan |
| Unhydranted zones (Z-01, Z-10) | Tanker shuttle: 750 gpm sustained within 15 minutes via TANKER 4/5 + automatic-aid tankers; dry-hydrant draft points maintained annually |
| Target hazards | Site-specific flow pre-plans for Riverbend Industrial Park, Lakeside Senior Living, Fairview Commons Mall |
§ 10 · Measurement & accountability
How this standard gets audited
Every objective in this document is measured quarterly in the Report 3 Service Delivery Scorecard using the measure-card convention:
| Rule | Convention |
|---|
| Statistic | True 90th percentile from individual responses (CPSE); never averages, never summed component percentiles |
| Compliance | Each response judged against its own zone / risk-class / service-line objective, then aggregated |
| Small samples | n < 50 → median reported, flagged LTD |
| Exclusions | Canceled, clock-error, aid-given, no-arrival — counted and published, never silent |
| Clocks | NFPA 1225/1750: create → dispatch → enroute → arrival → clear, per unit |
| Concurrency | Overlap rate, cross-service overlap, and the clean-vs-overlapped penalty reported every quarter |
✓ The accountability loopReport 1 says what the risk is. This document says what response that risk is owed. Report 3 says — every quarter, in public — whether it was delivered. No number in the chain is hand-entered; each report renders from the previous report's versioned data artifact.
§ 11 · Adoption
Resolution of the governing body
(Demo text) — RESOLVED, that the governing body of the Fairview Fire District hereby adopts this Standards of Cover, including the response-time objectives of §03, the effective-response-force requirements of §04, and the measurement conventions of §10; directs the Fire Chief to publish the Service Delivery Scorecard quarterly; and establishes that a sustained failure of any adopted standard for two consecutive quarters, or an overlap rate exceeding 25%, shall be brought before this body with a corrective-action plan and costed options.
| Adopted | 2026-07-17 (demo) |
| Review cycle | Annual · full revision with each CRA update |
| Version | SOC v1.0 · soc-standards artifact (demo) |
§ 12 · Reference
Standards library & glossary
Standards referenced
NFPA 1750 (2026) — community risk assessment, SOC, and deployment (§5.3 adoption & review; §7.4 / Table 7.4.2 demand zones; §10.3.6 risk categorization) · NFPA 1710/1720 legacy deployment benchmarks · NFPA 1225 (2026) communications & alarm handling · NFPA 1300 CRA/CRR · CPSE/CFAI 10th Edition (baseline vs. benchmark, 90th-percentile convention, Categories II & V) · AHA chain-of-survival guidance.
Glossary
ERF — Effective Response Force: the personnel and apparatus a risk class requires on scene. Distribution — first-due coverage; Concentration — full-force assembly. Demand zone — density-based classification setting the total-response objective. Overlap rate — share of calls beginning while same-agency units are committed. LTD — limited data (n<50, median shown). Measure card — objective · measured 90th · gap · % meeting · standard · n.
Frequently asked
Why 90th percentile, not average? Averages hide the bad nights; the tail is where risk lives. Why do rural zones get 14:00? Density economics: NFPA 1750 scales the promise to what a community's footprint can sustain — and Report 3 shows Fairview's rural zones meeting their standard while urban travel misses its own. Honest zone-scaled standards beat one impossible number. Why is EMS in a fire SOC? Same people, same stations, 60% of demand — and the concurrency between the two service lines is the system's binding constraint.