Response Intelligence
This week
Your latest complete month of NERIS data, with the six-month trend behind each figure. The newest days live under Recent incidents.
DATA: SEPTEMBER 2026
Applies to This week, Performance, and Stations
90th percentile response to the first-arriving unit, six months
Measured per incident to the first arriving unit. Settled months only.Open performance
Risk outpacing response
38,272 residents live in priority tracts. 10 tracts.
Start your free trial →See your own priority tracts. Guided setup takes about 15 minutes; no credit card.
Right now
Last updated: Oct 1, 2026p90 6:53 total response · 86% of incidents met your response goal · 10 priority tracts
Worth your attention
ThresholdsResponse 0:29 over goalYour response goal is 6:24.View details
10 priority tracts need attentionThe top of your priority index (response time, community risk, and call demand): focus here for CRR activities and deployment reviewView details
1,041 calls this monthMedical accounts for 60% of volumeView details
Email alerts follow the thresholds under Goals & settings.
Setup
3 of 4 doneResponse goals saved
Your fire and EMS goals and priority-tract filters. Defaults follow NFPA 1750 until you save your own.
Done
Team invited
Chiefs, analysts, and CRR staff who should see this dashboard and receive reports.
Done
Report recipients chosen
Reports go to everyone on the team until you name recipients.
Units registered under stations in NERIS
Station tables need each unit tied to its station in the NERIS portal. 97% of unit responses carry a station today.
Done
Scorecard
September 2026, 1,041 calls| Measure | This month | Your goal | Against goal | Change from prior month | Last 6 months |
|---|---|---|---|---|---|
| Total responsefirst-arriving unit, 90th percentile | 6:53 | 6:24 | 0:29 overOver goal | −0:07 | |
| Call processingdispatch center interval | 1:08 | 1:04 | 0:04 overOver goal | −0:08 | |
| Turnoutnotified to en route; fire and EMS combined, against the fire turnout goal | 1:33 | 1:20 | 0:13 overOver goal | +0:08 | |
| Travelen route to on scene | 5:14 | 4:00 | 1:14 overOver goal | −0:15 | |
| Calls meeting goalshare of incidents within the response goal | 86% | 90% | 5 pts belowBelow goal | −2 pts |
Times are 90th percentiles; lower is better. Dashed line in each trend is your goal. Goals are yours to set on the Goals page; the sections below explain each number and where to act.
The sections below explain the scorecard: the levers behind each number, compliance by demand zone, call volume, ERF attainment, concurrency, and unit utilization. Goals default to NFPA 1750 until you set your own. Problem locations are on Priority tracts.
Risk measured on three axes›
The three axes of community risk. Public data can only estimate your risk from who lives here, a proxy that leans toward Consequence. Your NERIS incidents measure the other two axes directly: the real Probability and Impact of the calls you run.
Auto-Insight
Top Levers
The phases running over goal, split by who can move them: turnout is the operational lever the department owns; call processing is the dispatch center's interval; travel is a structural finding about deployment.
Operational levers
- 1.The lever you own toward your 6:24 goal is turnout: currently 1:33 vs. a 1:20 goal at the 90th percentile. Station 4 contributes most. 15% of monthly calls run through stations missing this goal.
Turnout is the phase the department controls directly, so it is the lever to report movement on next period. Ranked by goal gap weighted by affected call share. Turnout here combines fire and EMS responses and is compared with the fire turnout goal.
Dispatch center interval: call processing
Call processing: 1:08 vs. a 1:04 goal at the 90th percentile. 77% of monthly calls run through stations over the call processing goal.
Call processing is measured from the time the call was answered (the NERIS call-answered timestamp, or call create when answered is missing or later) to unit notification. That interval belongs to the dispatch center (the PSAP or county dispatch agency) unless the department dispatches its own calls; it is shown here because total response time includes it, and it belongs in the conversation with the dispatch agency rather than in the department's operational levers.
Structural finding: travel time
Travel: 5:14 vs. a 4:00 goal at the 90th percentile. The largest share of it runs through Station 3. 12% of monthly calls run through stations over the travel goal.
Travel time is set by station locations, unit placement, and dispatch rules rather than crew effort, and no gap here is a reason to drive faster: safe arrival comes before any stopwatch, and emergency vehicle crashes remain a leading cause of line-of-duty deaths. A travel gap that holds month after month is a deployment question. This panel measures the gap; sizing the remedy takes a deployment analysis of the kind a Standards of Cover study provides.
Response Performance
NFPA 1750 Response-Time Compliance
September 2026: 6:53 (90th pctile), 0:29 over your goal of 6:24. Focus CRR on your priority tracts to close it.
Improving Response times trending down over 3 months
Field note
Observation · Sep 2026 EMS total response held under goal for the third month in a row. Fire p90 is carried by two rural tracts on the east side where travel is the whole story; turnout and call processing are inside goal. [email protected], Sep 25, 2026
Methodology for total response time
Your department sets its own goals; the NFPA-aligned defaults below are the starting point until you customize them in the Flag priority tracts panel on the Priorities tab.
Total response time on this dashboard is measured from the time the call was answered to the first unit's on-scene time, using the NERIS call-answered timestamp, or the call-create timestamp when the answered time is missing or later than call create. It includes the three components below. NFPA 1750:2026 (consolidating the former NFPA 1710) sets a 90% attainment objective for each component and for the combined total. Clause numbers below carry over from the legacy NFPA 1710 document; the alarm handling figure is from the communications standard, NFPA 1225 (formerly NFPA 1221).
The 90th percentile (p90) for a period is the time by which 90% of your calls were on scene; the slowest 10% took longer. It is the standard NFPA measure because it reflects consistent performance rather than a single best or worst call.
- Call processing / alarm handling: NFPA 1225 (formerly NFPA 1221 7.4.2) sets 64 seconds (1:04) at 90% for alarm processing. Measured from the NERIS call-answered time (call create when answered is missing or later) to unit-notified. Many CAD systems copy call create into call answered, and then the two starts are the same. This is the dispatch center's interval (the PSAP or county dispatch agency) unless the department dispatches its own calls; it is shown because total response time includes it, not as a department measure. Broken out in the Component Breakdown card.
- Turnout time: NFPA 1750 4.1.2.1.1 sets 80 seconds (1:20) at 90% for fire suppression; 60 seconds (1:00) at 90% for EMS. Measured from unit notification to en-route.
- Travel time: NFPA 1750 4.1.2.1.1 sets 240 seconds (4:00) at 90% for first-arriving engine; 480 seconds (8:00) for full first-alarm assignment. Measured from en-route to on-scene.
The 6:24 default total response goal reflects 1:04 call processing + 1:20 turnout + 4:00 travel. Some agencies report response time as turnout + travel only (5:20); we use the dispatch-to-arrival convention because it is the wait residents experience and it is what NERIS records.
Mutual aid / auto-aid handling: detailed inclusion rules for incoming and outgoing aid responses are documented separately. See full methodology.
Overall Response Time (90th Percentile)
Department 90th percentile
6:53
Your response goal
6:24
Tracts meeting your goal
20 of 35 with data (57%)
Component Breakdown
Call Processing (90th %, dispatch center)
1:08
Call processing goal
1:04
Turnout Time (90th %)
1:33
Turnout goal
1:20
Travel Time (90th %)
5:14
Travel goal
4:00
NFPA-aligned defaults: 1:04 call processing, 1:20 fire turnout (1:00 EMS), 4:00 travel. Edit your goals from the Flag priority tracts panel on the Priorities tab. Total response above is the first-arriving unit; the three phases are 90th percentiles over every unit response, and the department turnout row is scored against the fire turnout goal (the EMS goal applies per station on the Stations page). Phases over 120 minutes are treated as data errors and left out.
See this for your department.
Your 90th-percentile response, NFPA compliance trend, and fire and EMS priority tracts, built from your NERIS data. Setup is guided: we connect the feed, configure your goals, and walk through the first month's numbers with you. 60-day free trial, no credit card; your 60 days start when your incident data arrives.
Start free trial →
NERIS Incident Data Probability
Incident Volume (September 2026)
Call volume by incident type from your NERIS data feed for the latest reporting month. For 6-month trends see Call Mix below.
Calls by Type (this month)
1,041total calls
Medical
Illness, injury, cardiac, overdose, MVC
624
(60%)
Fire
Structure, vehicle, outside, wildland
121
(12%)
Hazardous Situation
HazMat, gas leak, CO, MVC, investigation
40
(4%)
Other
Public service, rescue, alarms, false calls
256
(25%)
90.1
Calls per 1K residents per year
Medical share
Incident Volume by Tract
Calls this month
Most (93)
About 56
About 28
No calls
Priority tract
Station
Department boundary
Leaflet © OpenStreetMap contributors
All incident types by tract. Darker = more calls. Priority tracts outlined in red.
6-Month Call Mix
Your Call Load Over Time
Shifts in call volume and type mix. Headline metrics and 6-month trend lines for response, compliance, priority tracts, and CRR are in the metric cards at the top.
Call Volume by Type (6 months)
Latest: 1,041 calls
Medical
Fire
Hazardous Situation
Other
Deeper Analytics Impact
ERF, Concurrency & Utilization
Effective Response Force (ERF) attainment, concurrent calls, the CFAI (Commission on Fire Accreditation International) performance data chart, and unit hour utilization for the latest reporting month unless labeled as a trend.
Station-Level Analysis
Station Performance
Per-station 90th-percentile times by response component. The columns show whether a station's bottleneck is dispatch (call processing, the dispatch center's interval), the crew (turnout), or distance (travel). Cells color green / amber / red against your goal for that component (NFPA defaults: 1:04 call processing, 1:20 fire turnout / 1:00 EMS turnout, 4:00 travel). Cells with fewer than 10 timed responses for that phase in the period show a dash.
Pinned note
Context · Station 3 · Aug 2026 Bay door 2 was out of service for three weeks this month, so the engine was backed in at the rear apron. Turnout ran about 25 seconds long until the door was repaired on the 22nd. [email protected], Aug 28, 2026
| Station | Call Processing (dispatch) | Fire Turnout | EMS Turnout | Travel | Calls/Mo | Medical | Fire |
|---|---|---|---|---|---|---|---|
| Station 3 | 1:14 | 1:40 | 1:10 | 4:50 | 134 | 74 | 21 |
| Station 4 | 1:07 | 1:36 | 1:19 | 3:35 | 169 | 100 | 14 |
| Station 2 | 1:20 | 1:29 | 1:15 | 3:32 | 157 | 92 | 19 |
| Station 6 | 1:19 | 1:22 | 1:17 | 3:30 | 165 | 102 | 19 |
| Station 5 | 1:04 | 1:22 | 0:55 | 2:48 | 220 | 141 | 22 |
| Station 1 | 0:58 | 1:24 | 0:57 | 2:51 | 250 | 159 | 20 |
Turnout by Shift and Time of Day
Field note
Question Is the night turnout gap on C shift a staffing pattern or the bunk room location at Station 1? Worth asking the analyst before we cite it anywhere. [email protected], Sep 22, 2026
90th-percentile turnout split by day vs. night and, once your shift schedule is saved, by platoon, from the latest reporting month. Schedule: 3-platoon 24/48, shift change 07:00, Day window 07:00 to 22:00, timezone America/Denver.
Day turnout
1:28
656 responses
Night turnout
1:59
385 responses
A platoon
1:29
347 responses
B platoon
1:43
347 responses
C platoon
1:35
347 responses
Turnout combines fire and EMS responses; colors compare it with your fire turnout goal (1:20).
Night turnout runs 0:32 slower than day at the 90th percentile. B platoon is the slowest at 1:43, 0:14 behind the fastest platoon.
| Station | Day Turnout (n) | Night Turnout (n) | Night vs. Day |
|---|---|---|---|
| Station 4 | 1:24 (106) | 2:09 (63) | +0:45 |
| Station 6 | 1:14 (104) | 1:48 (61) | +0:34 |
| Station 2 | 1:17 (99) | 1:47 (58) | +0:30 |
| Station 1 | 1:05 (158) | 1:32 (92) | +0:27 |
| Station 5 | 1:03 (139) | 1:26 (81) | +0:23 |
| Station 3 | 1:20 (84) | 1:41 (50) | +0:21 |
Planning zones
Read-only in demo modeUpload your first-due (run-order) boundaries as planning zones so accreditation reporting uses the areas you actually run, not modeled drive times. CFAI asks for a documented and adopted methodology for organizing the response area into geographical planning zones (CC 2A.3); this is where you record yours. Upload one polygon per station as a zipped shapefile (.zip with .shp, .shx, .dbf, and .prj) or GeoJSON. The file is read in your browser; only the polygons and their station matches are saved. Until you upload, each census tract is a planning zone. That is a defensible starting point and what every report here falls back to.
Planning zones feed the CRA/SOC document (Section 5, Section 11's risk and performance by zone, and the station sections) and the performance data chart's planning-zone view. Response metrics on this page keep using the station recorded on each unit response.
The last 30 days at daily resolution, for shift briefings and board prep. Other pages settle to monthly figures; this one trails by about a day. Raw incident CSVs are on Exports.
Last 30 Days Probability
Summary
Incident Map
Recent Incidents
Each dot is one incident; click for time, type, and first-unit response. Street addresses are intentionally omitted.
Window
Domain
Station
--
Trend
Rolling 7-Day P90 Response Time
Each point is the trailing 7-day 90th-percentile response time ending that day; reference line is your saved response goal.
Fire
EMS
Lower is better
Busiest Hours
Hour-of-Day x Weekday (last 30 days)
Cell shading is call count for that day-of-week and hour; darker is busier. Useful for shift staffing conversations.
Fire causes and costs from the NERIS Incident Analysis module: the post-incident review your officers file after a call closes (cause, flame spread, detection, dollar loss, casualties). Updated with the nightly NERIS pull.
Trailing 12 Months Impact
Property and People Protected
From analyses your officers filed in NERIS. "Value protected" is estimated pre-incident property and contents value minus estimated loss: the dollar figure your suppression work saved. Casualty and rescue counts come from the analysis casualty sub-modules.
Property value protected
$13.5M
$2.6M est. loss on $16M at risk
Civilian fire deaths
1
14 civilian injuries
People rescued uninjured
19
removed or rescued without injury
Firefighter casualties
3
injuries and deaths, from filed analyses
Analyses filed
59
86% completed (closed with an end date)
Based on 59 analyses across 12 months. Dollar and casualty figures cover only incidents with a filed analysis; treat them as a floor, not a census.
362 of 515 eligible fire and hazmat incidents in the last six reported months have an analysis on file (70%). Every additional analysis sharpens the cause and loss picture below; the Data Quality tab tracks this month by month.
Area of fire origin
Cause categories from filed analyses, trailing 12 months. This list is your prevention target set.
Fire spread
Flame spread at the end of the incident. Fires held to the object or room of origin are the clearest signature of working alarms, early detection, and fast response.
71% of analyzed fires were held to the object or room of origin.
First detection
Initial detection from filed analyses. A low smoke-alarm share is the single strongest argument for an alarm installation campaign.
Contributing human factors
Factors your officers flagged as contributing to incident outcomes.
Prevention playbook
Your top causes, translated into CRR programs with a track record against them. Log the work in the CRR tracker and it becomes grant evidence.
Cooking fire safety campaign (targets "Cooking", 16 fires in the window): Stand-by-your-pan messaging, senior meal-site demos, and stovetop suppression devices for repeat-address and high-risk occupancies. Cooking is the most preventable major cause in the national data.
Electrical hazard inspections (targets "Electrical", 6 fires in the window): Partner with your code office on inspection sweeps of pre-1980 housing (your risk profile flags where it concentrates) and push outlet and extension cord safety.
Heating safety push before the cold season (targets "Heating", 4 fires in the window): Space heater clearance education, chimney sweep vouchers, and free CO alarm checks; schedule it for early fall.
Monthly loss and casualty trend
Newest first. Dollar figures are estimates entered by your officers in the analysis record; months without filed analyses show no row.
| Month | Analyses filed | Completed | Property loss | Contents loss | Civilian deaths | Civilian injuries | Rescued uninjured |
|---|---|---|---|---|---|---|---|
| Oct 2026 | 11 | 91% | $306K | $185K | 0 | 1 | 0 |
| Sep 2026 | 10 | 90% | $369K | $152K | 0 | 1 | 2 |
| Aug 2026 | 9 | 78% | $195K | $75K | 0 | 2 | 2 |
| Jul 2026 | 7 | 71% | $150K | $87K | 0 | 2 | 0 |
| Jun 2026 | 8 | 88% | $194K | $83K | 1 | 0 | 1 |
| May 2026 | 5 | 80% | $221K | $45K | 0 | 2 | 2 |
| Apr 2026 | 5 | 80% | $221K | $89K | 0 | 1 | 3 |
| Mar 2026 | 4 | 100% | $92K | $43K | 0 | 1 | 2 |
| Feb 2026 | 4 | 100% | $152K | $37K | 0 | 0 | 2 |
| Jan 2026 | 3 | 100% | $110K | $42K | 0 | 2 | 0 |
| Dec 2025 | 2 | 100% | $57K | $15K | 0 | 1 | 1 |
| Nov 2025 | 1 | 100% | $62K | $18K | 0 | 1 | 2 |
Every tract ranked by a priority score: persistently long response times over the last 6 months, community risk, and call volume per resident. The filters flag your priority tracts in the table and on the maps. Act on them in CRR activities.
Tract Priorities Consequence×Probability
Risk Meets Long Response Times
Every tract in your district, ranked by a priority score: the average of three percentiles, each ranked within your district. Response: median monthly 90th percentile over the trailing 6 months. Risk: the fire or EMS risk composite at the comparison scope you set below, the same value that flags priority tracts. Demand: calls per 1,000 residents per year. Your longest-response, highest-risk, busiest tract scores near 100. Fire and EMS are tracked separately.
Pinned note
Context · Tract 125.01 The 96-unit senior living complex on the parkway opened in March. It is driving the EMS demand in this tract and should be in the EMS risk narrative as a new, permanent load rather than a trend. [email protected], Aug 14, 2026
25%
of fire calls happen in your fire priority tracts
181 of 726 calls occurred in 7 priority tracts (the top 7 tracts by priority index (response time, risk, and demand), among tracts where there were at least 3 fire calls per year).
19%
of EMS calls happen in your EMS priority tracts
952 of 4,967 calls occurred in 7 priority tracts (the top 7 tracts by priority index (response time, risk, and demand), among tracts where there were at least 3 EMS calls per year).
| Rank▼ | Tract | Priority score▼ | fire p90 (6-mo median) | Risk pctl (state) | fire calls /1k residents (yr) | fire calls (window) | Residents | Status |
|---|---|---|---|---|---|---|---|---|
| #1 | 08013012707 | 88 | 7:26 | 87 | 11.6 | 14 | 2,409 | Priority |
| #2 | 08013012201 | 73 | 7:28 | 53 | 11.2 | 19 | 3,402 | Priority |
| #3 | 08013012207 | 72 | 5:52 | 87 | 11.8 | 29 | 4,899 | Priority |
| #4 | 08013012204 | 71 | 7:12 | 66 | 11.4 | 19 | 3,346 | Priority |
| #5 | 08013012105 | 66 | 7:13 | 54 | 11.0 | 34 | 6,180 | Priority |
| #6 | 08013012300 | 63 | 7:19 | 38 | 11.1 | 39 | 7,025 | Priority |
| #7 | 08013012505 | 60 | 7:06 | 19 | 13.2 | 27 | 4,100 | Priority |
| #8 | 08013012605 | 56 | 6:42 | 32 | 11.4 | 11 | 1,933 | |
| #9 | 08013012107 | 56 | 5:19 | 78 | 11.4 | 25 | 4,377 | |
| #10 | 08013013704 | 55 | 7:22 | 26 | 10.4 | 26 | 4,992 | |
| #11 | 08013012510 | 54 | 7:06 | 44 | 10.5 | 20 | 3,806 | |
| #12 | 08013012106 | 51 | 7:37 | 19 | 9.9 | 13 | 2,628 | |
| #13 | 08013012208 | 50 | 7:54 | 34 | 9.4 | 11 | 2,350 | |
| #14 | 08013012710 | 48 | 5:35 | 33 | 14.3 | 23 | 3,214 | |
| #15 | 08013012608 | 47 | 7:57 | 39 | 7.9 | 9 | 2,279 |
Priority score: the average of three percentiles ranked within your district: response time (median monthly 90th percentile, up to the last 6 complete months), community risk at your chosen comparison scope (the same value in the Risk column and the risk filter above), and demand (calls per 1,000 residents per year, annualized over the same window). 100 = your longest-response, highest-risk, busiest tract. Click a row to see the tract on the map; click a column header to sort. The CSV includes every tract with fire and EMS ranks, scores, and flags, ready for planning staff, council packets, or a grant appendix.
Fire Priority Map
Field note
Observation The two flagged fire tracts share the river crossing. When the bridge is closed for the county's deck work (six weeks, starting late summer) travel from Station 1 will route around by the highway; expect the map to worsen for that window. [email protected], Sep 11, 2026
Tracts shaded by median monthly fire-call p90 over the last 6 months vs. your goal; flagged priority tracts are outlined. Bubble size: total fire-call volume in that window.
—
EMS Priority Map
Tracts shaded by median monthly EMS-call p90 over the last 6 months vs. your goal; flagged priority tracts are outlined. Bubble size: total EMS-call volume in that window.
—
Domain playbook with counts, population, and suggested CRR response›
Fire Priority Tracts
7 tracts
~31,361 residents in these tracts
- Median fire p907:13
Long fire response times in tracts ranking high on fire risk factors: older and vacant housing, mobile homes, poverty, disability, and residents over 75 or under 5. Priority tracts for smoke alarm canvasses, home fire safety visits, and code enforcement.
EMS Priority Tracts
7 tracts
~23,847 residents in these tracts
- Median EMS p906:44
Long EMS response times in tracts ranking high on EMS risk factors: age 75+, disability, no household vehicle, uninsured, and poverty. Priority tracts for community paramedicine, fall prevention, and chronic care coordination.
Document prevention and education work in high-risk tracts to build the evidence for grant applications and board reports.
Community Risk Context Consequence
Risk at a Glance
Key risk indicators from public data. For the full community risk profile with detailed hazard, vulnerability, and demographic analysis, visit your free risk profile page.
Overall Risk
51/100
Social Vulnerability
41/100
Community Resilience
86/100
Est. Annual Loss
$55.8M
Top Hazards by Life-Safety Impact
| Hazard | Score | Life-Safety | Total Loss |
|---|---|---|---|
| Tornado | 66 | $1.3M | $4.1M |
| Wildfire | 67 | $680K | $2.1M |
| Winter Weather | 84 | $520K | $1.4M |
| Earthquake | 44 | $420K | $2.8M |
| Strong Wind | 61 | $312K | $1.9M |
Sorted by life-safety impact (EALPE). Life-safety loss uses FEMA Value of Statistical Life ($13.7M).
Risk Peer Benchmarking
Risk Compared With Peers
Your department compared against up to 15 peers: departments of the same staffing type (when NERIS records one), community class, and Census division with a population within 50% of yours, ranked by similarity on population, density, community risk, age 65+, poverty, and housing age. Peer benchmarks put your community risk profile in context and support "demonstrated need" narratives in grant applications.
| Department | State | Type | Est. Pop. | Risk Score | Soc. Vuln. | 65+ % | Poverty % | Stations | Match |
|---|---|---|---|---|---|---|---|---|---|
| Demo Fire Agency (You) | CO | CAREER | 122,726 | 51.3 | 41.0 | 14.1% | 19.4% | 6 | -- |
| Billings Fire Department | MT | CAREER | 114,205 | 56.7 | 37.6 | 18.5% | 9.3% | 21 | 97% |
| Arvada Fire Protection District | CO | CAREER | 97,244 | 38.9 | 25.1 | 18.1% | 6.2% | 21 | 96% |
| Idaho Falls Fire Department | ID | CAREER | 46,187 | 67.8 | 35.9 | 13.5% | 12.3% | 8 | 95% |
| Greeley Fire Department | CO | CAREER | 118,510 | 39.4 | 38.0 | 14.7% | 12.9% | 14 | 95% |
| Longmont Fire Department | CO | CAREER | 88,643 | 39.4 | 34.0 | 18.5% | 8.3% | 13 | 94% |
| Caldwell Fire Department | ID | CAREER | 51,037 | 18.3 | 45.4 | 12.7% | 11.8% | 18 | 91% |
| Nampa Fire Protection District | ID | CAREER | 140,241 | 10.9 | 32.4 | 15.6% | 10.2% | 7 | 89% |
| Sun City Fire District | AZ | CAREER | 46,537 | 82.2 | 82.6 | 57.5% | 11.8% | 3 | 89% |
| Meridian Fire Department | ID | CAREER | 146,834 | 8.3 | 20.7 | 14.8% | 5.6% | 8 | 88% |
| Peer Average | 94,382 | 40.2 | 39.1 | 20.4% | 9.8% | 13 | -- |
9 peers of the same staffing type, community class, and Census division, ranked by similarity on population, density, community risk, age 65+, poverty, and housing age. Click any department to view its free risk profile.
Exploration
Full Coverage Map
Every layer on one map: response time (latest month), community risk (NRI), incident volume (latest month), persistent priority tracts (last 6 months), and CRR activity locations (all time). The focused fire and EMS priority maps are in Priority Tracts above.
90th percentile response times by census tract. Green = under your response goal. Red = above your goal.
Prevention work tied to census tracts. Log education, inspection, and prevention activity, and track coverage of your priority tracts. Grant narratives built from it are on Grant evidence.
Take Action
Loading priority tract coverage...
Tracking CRR activity coverage across your priority tracts.
Community Risk Reduction Tracker
Field note
Action Smoke alarm canvass scheduled for the two flagged fire tracts, three Saturdays in a row with the church volunteers. Logged as we go so the coverage figure moves. [email protected], Sep 19, 2026
Log prevention, education, and inspection activities by census tract to show grantors that CRR work reaches your priority tracts.
14
Total Activities
2
In Priority Tracts
14% of activities
571
People Reached
4
Activity Types Used
Activity Locations by Risk Domain
Priority tracts shown. Activity markers show where CRR work has been logged. Click a tract or marker for details.
Activity Log
Sep 28, 2026
Home VisitWildfire PreparednessPriority Tract (as of Sep 2026)
Wildfire Mitigation Assessment: WUI Zone
Assessed 12 properties in WUI zone for defensible space compliance. Provided mitigation recommendations to homeowners.
Tracts: 08013012208, 24 people reachedSep 26, 2026
Parcel InspectionGeneral Risk Reduction
Multi-Family Building Inspections: East District
Completed fire code inspections on 6 multi-family buildings. Issued 2 correction notices for blocked egress.
Tracts: 08013012511, 08013013214Sep 24, 2026
Community EventCampaign
School Fire Safety Program: Lincoln Middle School
Delivered fire safety and evacuation education to 6th-8th graders. Students practiced stop-drop-roll and reviewed home escape plans.
Tracts: 08013012204, 08013012509, 185 people reachedSep 21, 2026
Community EventGeneral Risk Reduction
CERT Volunteer Training: Winter Session
16-hour Community Emergency Response Team training. 22 new volunteers certified in basic fire suppression and triage.
Tracts: 08013013205, 08013012205, 22 people reachedSep 19, 2026
Home VisitAlarmsPriority Tract (as of Sep 2026)
Smoke Detector Installation: Senior Housing
Installed 45 smoke detectors in low-income senior housing complex. Replaced expired batteries in 23 existing units.
Tracts: 08013012208, 08013013205, 68 people reachedSep 13, 2026
Community EventWildfire Preparedness
Community Wildfire Preparedness Workshop
Evening workshop on creating defensible space, evacuation planning, and go-bag essentials. Strong WUI neighborhood turnout.
Tracts: 08013012105, 42 people reachedSep 9, 2026
Parcel InspectionGeneral Risk Reduction
Commercial Kitchen Hood Inspection Round
Inspected 8 restaurant hood suppression systems. 1 system required immediate servicing.
Tracts: 08013012105, 08013012204Sep 3, 2026
Home VisitGeneral Risk Reduction
Home Safety Inspection Blitz: District 3
Conducted 18 voluntary home safety inspections. Identified 7 properties with fire code concerns and provided corrective guidance.
Tracts: 08013012204, 36 people reachedAug 30, 2026
Community EventGeneral Risk Reduction
CPR/AED Community Class
Free CPR and AED training for community members at Demo Agency Station 3. Partnered with local hospital.
Tracts: 08013012204, 08013012205, 16 people reachedAug 27, 2026
Community EventSenior Risk Reduction
Senior Center Fall Prevention and Fire Safety
Presented to seniors on cooking fire prevention, mobility considerations for evacuation, and medical alert integration.
Tracts: 08013012509, 08013012401, 35 people reachedAug 22, 2026
Parcel InspectionGeneral Risk Reduction
Assisted Living Facility Fire Drill
Observed and evaluated fire drill at Sunrise Senior Living. Evacuation completed in 4:15, within standard.
Tracts: 08013012511, 08013012510Aug 17, 2026
Home VisitAlarms
Carbon Monoxide Detector Program
Distributed 30 CO detectors to households using gas heating. Partnered with local utility for outreach.
Tracts: 08013012105, 08013012106, 08013012708, 30 people reachedAug 7, 2026
Community EventWildfire Preparedness
HOA Firewise USA Presentation
Presented Firewise USA program to three hillside HOAs. All three neighborhoods expressed interest in certification.
Tracts: 08013012207, 28 people reachedAug 2, 2026
Hydrant InspectionOperation Enhancement
Quarterly Hydrant Flow Test: District 2
Tested 15 hydrants in District 2. 13 operable, 1 low-flow, 1 inoperable and referred to water department.
Tracts: 08013012709, 08013012705Grant Narratives
Ready-to-Use Grant Language
Drafted from your community risk and response data, ready to copy into SAFER, AFG, BRIC, or HMGP applications.
SAFER
AFG
BRIC
HMGP
Priority Tracts
10
38,272 residents affected
P90 Response
6:53
vs. 6:24 goal
Top Hazard
Tornado
$1.3M/yr life-safety loss
Overall Risk Score
51/100
Relatively Moderate
Disaster Declarations
7
last 10 years (19 total)
Vulnerability
19.4%
poverty
Narrative Summary
Use this as a starting point, not a final draft. The text below is generated from the public-data and NERIS evidence above. Reviewers see hundreds of applications, and the strongest narratives add local knowledge only you have: incidents your crews have run, the names of neighborhoods and partners, mutual-aid arrangements, what you've already tried and why it fell short, and exactly what this funding will let you do that you can't do today. Revise it in your own voice; the data points carry more weight cited inside your story than standing alone.
Demo Fire Agency serves an estimated 122,726 residents across 35 census tracts from 6 fire stations.
The department's service area carries a FEMA National Risk Index composite rating of "Relatively Moderate" (score: 51 out of 100).
The primary life-safety hazards are tornado, wildfire, winter weather. Tornado alone accounts for an estimated $1.3M per year in population-equivalent loss (using FEMA's Value of Statistical Life methodology).
The area has received 7 federal disaster declarations in the past decade (19 total since 1959).
Tract-level analysis identifies 10 priority tracts across fire and EMS service domains. An estimated 38,272 residents live in these tracts. Fire priority tracts are the top 7 tracts by priority index (response time, risk, and demand), among tracts where there were at least 3 fire calls per year. EMS priority tracts are the top 7 tracts by priority index (response time, risk, and demand), among tracts where there were at least 3 EMS calls per year. These are the department's highest-priority areas for community risk reduction: the top of your priority index (response time, community risk, and call demand).
Community vulnerability factors that compound risk include: 19.4% below the federal poverty line; 38.2% housing built before 1980 (pre-modern fire codes).
CRR programming in these priority tracts (home safety visits, smoke alarm installation, public education) would put prevention resources where response time, community risk, and call demand together rank highest.
[NOTE TO APPLICANT: DELETE BEFORE SUBMISSION] This narrative was assembled from public-data and NERIS evidence as a starting draft. To strengthen it before submission, add specific incidents your department has run in these areas, the names of affected neighborhoods and community partners, mutual-aid arrangements, what your department has already tried (and the limits of those efforts), and exactly what this grant will enable that you cannot do today. Reviewers consistently reward locally-specific narrative over generic risk language; revise this text in your own voice.
NERIS data quality assessment.Free forever
Completeness of timestamps, locations, incident typing, and unit data in your NERIS records. Most gaps trace to a CAD or RMS export mapping, so one configuration fix usually repairs a field department-wide.
Completeness of timestamps, locations, incident typing, and unit data in your NERIS records. Most gaps trace to a CAD or RMS export mapping, so one configuration fix usually repairs a field department-wide.
A
Overall data quality: 91 of 100
Based on 5,983 incidents and 9,566 unit responses, Apr 2026 to Sep 2026.
Assessment refreshed Oct 1, 2026
Quality dimensions
Each dimension is scored 0-100 over the trailing six complete months. Green is 90 or better, amber 70-89, red below 70. The overall grade weights response-time readiness most heavily because it determines how much of the paid analytics your data can power.
Response-Time Ready
87.9%
5,260 of 5,983 incidents power p90 analytics
Unit Timestamps
86.9%
each stamp as a share of 9,566 unit responses
Dispatch97.6%En route82.5%On scene92%Clear75.6%
Location Quality
92.7%
5,341 of 5,983 incidents with coordinates; 5,749 matched to a census tract
Incident Typing
97%
5,801 of 5,983 incidents classified
Timeline Validity
97%
7,201 of 7,423 complete timelines in order
Incident Analysis module adoption
NERIS's Incident Analysis module is the post-incident review (cause, spread, detection, loss, casualties) filed after the call closes. Adoption is tracked here against your fire and hazmat incidents but is not part of the grade above. Filed analyses power the Fire Cause & Loss tab.
Eligible Incidents
513
fire and hazmat incidents in the window
Analyses Started
63.7%
327 of 513 eligible incidents have an analysis on file
Analyses Completed
54.4%
279 closed with an analysis end date
Field-by-field coverage
Field note
Action Unit clear times were missing on about a fifth of records because crews were closing the call from the tablet before clearing. Reminder went out with the new CAD build; the completeness figure should recover over the next two months. [email protected], Sep 4, 2026
Share of records where each NERIS field is populated, over the trailing six complete months. The trend column plots each month of the last twelve, so a field that broke with a CAD change shows the month it happened.
| Field | Scope | Populated | Coverage | Trend, 12 months | |
|---|---|---|---|---|---|
| Call create time | Incidents | 5,954 of 5,983 | 99.5% | ||
| Incident type | Incidents | 5,801 of 5,983 | 97% | ||
| Coordinates | Incidents | 5,341 of 5,983 | 89.3% | ||
| Census tract | Incidents | 5,749 of 5,983 | 96.1% | ||
| Unit responses attached | Incidents | 5,788 of 5,983 | 96.7% | ||
| Unit ID | Unit responses | 9,368 of 9,566 | 97.9% | ||
| Station assignment | Unit responses | 7,990 of 9,566 | 83.5% | ||
| Dispatch time | Unit responses | 9,332 of 9,566 | 97.6% | ||
| En-route time | Unit responses | 7,895 of 9,566 | 82.5% | ||
| On-scene time | Unit responses | 8,801 of 9,566 | 92% | ||
| Unit-clear time | Unit responses | 7,228 of 9,566 | 75.6% | ||
| Staffing | Unit responses | 5,765 of 9,566 | 60.3% | ||
| Call answered time | Incidents | 5,954 of 5,983 | 99.5% | ||
| Dispatch code | Incidents | 3,488 of 5,983 | 58.3% | ||
| Unit type | Unit responses | 9,244 of 9,566 | 96.6% | ||
| Response mode | Unit responses | 7,337 of 9,566 | 76.7% | ||
| Incident analysis filed | Fire + hazmat incidents | 327 of 513 | 63.7% |
Recommended fixes
Staffing (60.3% coverage): Record crew counts per unit in CAD or RMS; staffing feeds effective response force analysis.
Unit-clear time (75.6% coverage): The unit-clear status is mapped but crews are not pressing it consistently; it drives commitment and utilization analysis.
En-route time (82.5% coverage): The en-route status is mapped but crews are not pressing it consistently on the MDT. This is a crew habit, not a vendor issue; the stamp separates turnout from travel.
Station assignment (83.5% coverage): Register each unit under its home station in the NERIS portal (department settings, Stations, Units) with the CAD designation your dispatch center uses. Until then, station-level analytics group responses by unit number, which is a guess (a second ambulance or a chief's car shows up as its own station).
Coordinates (89.3% coverage): Some incidents arrive without a point. Improve address quality where geocoding fails (street number and street name). Without coordinates a call is counted but not plotted on the Recent incidents map, and past 10% the map switches to tract counts.
Incident Analysis module (63.7% of eligible incidents): The NERIS post-incident analysis is where cause, flame spread, detection, dollar loss, and casualty data live. It can be filed a day or two after the call by whoever handles investigations; start with structure fires. Every filed analysis feeds the Fire Cause & Loss tab and strengthens prevention grant narratives. It is not counted in your grade.
Monthly trend
Composite score by month, newest first. Watch this after a CAD or RMS configuration change; the following month shows whether the fix reached NERIS.
| Month | Incidents | Unit responses | Response-time ready | Score |
|---|---|---|---|---|
| Oct 2026 | 990 | 1,566 | 87.9% | 93 (A) |
| Sep 2026 | 952 | 1,564 | 88.9% | 92 (A) |
| Aug 2026 | 916 | 1,507 | 89.1% | 92 (A) |
| Jul 2026 | 996 | 1,542 | 85.9% | 91 (A) |
| Jun 2026 | 1,067 | 1,694 | 88.4% | 91 (A) |
| May 2026 | 1,020 | 1,638 | 87.5% | 91 (A) |
| Apr 2026 | 1,032 | 1,621 | 87.9% | 90 (A) |
| Mar 2026 | 995 | 1,622 | 86.5% | 90 (B) |
| Feb 2026 | 917 | 1,424 | 88.8% | 90 (B) |
| Jan 2026 | 1,029 | 1,565 | 88.6% | 89 (B) |
| Dec 2025 | 924 | 1,421 | 90.4% | 90 (B) |
| Nov 2025 | 902 | 1,360 | 89.1% | 89 (B) |
Board packets
September 2026 board packet
September 2026 · built Oct 4, 2026 · 2 pages · PDF
Sent to 2
August 2026 board packet
August 2026 · built Sep 3, 2026 · 2 pages · PDF
Sent to 2
July 2026 board packet
July 2026 · built Aug 3, 2026 · 2 pages · PDF
Sent to 2
June 2026 board packet
June 2026 · built Jul 4, 2026 · 2 pages · PDF
Sent to 2
Quarterly performance
Q3 2026 quarterly performance report
Q3 2026 · built Oct 9, 2026 · 9 pages · PDF
Sent to 2CRA/SOC
Q3 2026 council slide deck
Q3 2026 · built Oct 9, 2026 · 11 pages · PPTX
Sent to 2CRA/SOC
Q2 2026 quarterly performance report
Q2 2026 · built Jul 9, 2026 · 9 pages · PDF
Sent to 2CRA/SOC
Q2 2026 council slide deck
Q2 2026 · built Jul 9, 2026 · 11 pages · PPTX
Sent to 2CRA/SOC
Weekly briefs
Weekly brief, week of Sep 21
week of Sep 21 · built Sep 28, 2026 · 4 pages · PDF
Sent to 3
Weekly brief, week of Sep 14
week of Sep 14 · built Sep 21, 2026 · 4 pages · PDF
Sent to 3
Weekly brief, week of Sep 07
week of Sep 07 · built Sep 14, 2026 · 4 pages · PDF
Sent to 3
Weekly brief, week of Aug 31
week of Aug 31 · built Sep 7, 2026 · 4 pages · PDF
Sent to 3
Weekly brief, week of Aug 24
week of Aug 24 · built Aug 31, 2026 · 4 pages · PDF
Sent to 3
Files are built the morning after the data settles and kept while your subscription is active, plus 90 days. Every figure matches this dashboard.
Anytime
built from live dataPrint this page
Any page prints cleanly for a staff meeting or accreditation binder. Maps are left out because browsers print them unreliably.
Grant evidence packet
The evidence table, your priority tracts, and your narrative for SAFER, AFG, BRIC, or HMGP.
Quarterly performance report and council deck
Phase p90s by station and shift, ERF attainment, concurrency, priority tract movement, CRR summary. PDF plus an editable slide deck, built on the 8th after each quarter closes and listed above. Part of CRA/SOC.
Quarterly
Annual performance report
Year in review with year-over-year comparisons, built each January once twelve complete months exist. Part of CRA/SOC.
Yearly
CRA/SOC document (Word)
The full CRA/SOC document as an editable Word file: district overview, station information, community risk, incident analysis, planning zones from your uploaded boundaries or your census tracts, risk assessments, critical tasks and ERF with drive-time coverage maps, performance measurement, baseline objectives, and a section per station. Built on request and delivered to this library and your inbox, usually within the hour. Part of CRA/SOC.
CRA/SOC
Uploads
select one for its reportLoading…
Months before your NERIS data are built from your uploads. Months NERIS covers keep the NERIS figures and gain the call-answered times. Uploaded files are deleted 30 days after they are added to your history, or 14 days after upload if they never are.
Automatic reports
Read-only in demo modeWeekly brief
Mondays, early morning. The trailing 30 days against your goals, with the station table.
Send toEveryone on the team
Monthly board packet
The 2nd of the month, once the prior month settles.
Send toEveryone on the team
Quarterly report and council deck
The 8th after each quarter closes. PDF plus an editable slide deck. Part of CRA/SOC; not built for this subscription.
CRA/SOC
Annual report
January, once twelve complete months exist. Part of CRA/SOC; not built for this subscription.
CRA/SOC
CRA/SOC document (Word)
On request from the Library page; usually within the hour. Part of CRA/SOC; not built for this subscription.
CRA/SOC
Leave the recipient list empty to send to everyone on the team. A report that is switched off is still built and kept in the library; only the email stops.
Team
Your team appears here once you sign in. Everyone on the team receives each report unless you name recipients.
Invite or remove people on the settings page.Manage team
Threshold alerts
Goal attainment, station turnout, priority tract changes, and data quality alerts are managed in Goals & settings, not here.
Tables
CSV files for Excel or SheetsStation table
Per-station p90 for every phase, plus calls, for the latest complete month.
Tract priorities
Every tract with fire and EMS rank, score, median p90, risk percentile, calls per 1,000 residents, and the priority flag.
CRR activities
Bring in activities from a spreadsheet, or start from the template.
Your Data
Export Raw Incident Data
Six months of your incident records as CSV, ready to open in Excel, Google Sheets, or any analysis tool.
Durations are whole seconds; timestamps are UTC in ISO 8601 format. Street addresses are included here (unlike the map above, which omits them by design) because reconciling against your CAD or RMS is the main reason to pull this file. Rebuilt with every nightly data pull. Under our retention policy, NERIS-derived data is deleted 90 days after a trial expires or a subscription is canceled, so export anything you want to keep before then.
| Month | Source | Fire | EMS | Hazmat | Other | Total | p90, first unit | Met goal | Fire priority tracts | EMS priority tracts |
|---|---|---|---|---|---|---|---|---|---|---|
| Sep 2026 | NERIS | 121 | 624 | 40 | 256 | 1,041 | 6:53 | 86% | 4 | 6 |
| Aug 2026 | NERIS | 142 | 638 | 39 | 222 | 1,041 | 7:00 | 88% | 4 | 6 |
| Jul 2026 | NERIS | 96 | 619 | 34 | 229 | 978 | 7:27 | 79% | 4 | 8 |
| Jun 2026 | NERIS | 105 | 554 | 42 | 197 | 898 | 6:24 | 90% | 4 | 7 |
| May 2026 | NERIS | 113 | 642 | 51 | 236 | 1,042 | 7:01 | 87% | 4 | 6 |
| Apr 2026 | NERIS | 92 | 558 | 35 | 202 | 887 | 6:53 | 86% | 4 | 8 |
| Mar 2026 | NERIS | 97 | 571 | 40 | 196 | 904 | 7:26 | 85% | 4 | 8 |
| Feb 2026 | NERIS | 109 | 736 | 53 | 166 | 1,064 | 7:06 | 86% | 4 | 8 |
| Jan 2026 | NERIS | 113 | 728 | 44 | 164 | 1,049 | 6:41 | 87% | 4 | 8 |
| Dec 2025 | NERIS | 81 | 651 | 48 | 232 | 1,012 | 6:28 | 92% | 4 | 7 |
| Nov 2025 | NERIS | 98 | 654 | 46 | 178 | 976 | 6:14 | 93% | 4 | 8 |
| Oct 2025 | NERIS | 91 | 561 | 43 | 209 | 904 | 6:14 | 93% | 4 | 8 |
| Sep 2025 | NERIS | 104 | 561 | 43 | 196 | 904 | 6:14 | 93% | 4 | 8 |
| Aug 2025 | NERIS | 104 | 561 | 43 | 196 | 904 | 6:14 | 91% | 4 | 8 |
| Jul 2025 | NERIS | 123 | 657 | 36 | 218 | 1,034 | 6:26 | 89% | 4 | 8 |
| Jun 2025 | NERIS | 104 | 561 | 43 | 196 | 904 | 6:14 | 91% | 4 | 8 |
| May 2025 | NERIS | 91 | 561 | 43 | 209 | 904 | 6:14 | 91% | 4 | 8 |
| Apr 2025 | NERIS | 91 | 561 | 43 | 209 | 904 | 6:14 | 91% | ||
| Mar 2025 | NERIS | 18 | 79 | 4 | 20 | 121 | 9:37 | 16% | ||
| Feb 2025 | NERIS | 1 | 5 | 2 | 0 | 8 | 9:47 | 4% |
Settled months only, up to 24; the in-progress month is excluded. Source names what each month was built from: NERIS, or history your department uploaded for the months before NERIS.20 rows
Questions go to a person who knows your data. Quick questions about the numbers on this dashboard are included with CRA/SOC. The Supported level includes up to 5 analyst hours per month, so its questions are not counted. Deeper work (custom analyses, board and council prep, grant or accreditation support) is analyst time by the hour, quoted up front.
Attached context
Good questions to ask
Why did our p90 move this month? Which unit is behind Station 4's turnout? Can you turn the priority list into a slide for council? Is our ERF attainment a reporting gap or a staffing one?
Read-only in demo mode. These notes were recorded on the figures of this demo department; subscribers on CRA/SOC add their own from any figure.
ContextStation 3Aug 2026PinnedStation performance
Bay door 2 was out of service for three weeks this month, so the engine was backed in at the rear apron. Turnout ran about 25 seconds long until the door was repaired on the 22nd.
[email protected], Aug 28, 2026 (edited)
ContextTract 125.01PinnedPriority tract table
The 96-unit senior living complex on the parkway opened in March. It is driving the EMS demand in this tract and should be in the EMS risk narrative as a new, permanent load rather than a trend.
[email protected], Aug 14, 2026 (edited)
ActionSep 2026Concurrent call analysis
Second overlapping medical calls between 10:00 and 14:00 now go to the cross-staffed squad before mutual aid is requested. Adopted at the operations meeting on the first Tuesday; watch the weekday daytime cell next month.
[email protected], Sep 26, 2026 (edited)
ObservationSep 2026Response-time performance
EMS total response held under goal for the third month in a row. Fire p90 is carried by two rural tracts on the east side where travel is the whole story; turnout and call processing are inside goal.
[email protected], Sep 25, 2026 (edited)
QuestionDashboard onlyTurnout by shift and time of day
Is the night turnout gap on C shift a staffing pattern or the bunk room location at Station 1? Worth asking the analyst before we cite it anywhere.
[email protected], Sep 22, 2026 (edited)
ActionCRR coverage of priority tracts
Smoke alarm canvass scheduled for the two flagged fire tracts, three Saturdays in a row with the church volunteers. Logged as we go so the coverage figure moves.
[email protected], Sep 19, 2026 (edited)
ContextUnit hour utilization
M2 carries the interfacility transfers under the hospital agreement, which is why its utilization runs above the other medics. That is contracted workload, not a coverage problem.
[email protected], Sep 16, 2026 (edited)
ObservationFire priority map
The two flagged fire tracts share the river crossing. When the bridge is closed for the county's deck work (six weeks, starting late summer) travel from Station 1 will route around by the highway; expect the map to worsen for that window.
[email protected], Sep 11, 2026 (edited)
ActionField-by-field coverage
Unit clear times were missing on about a fifth of records because crews were closing the call from the tablet before clearing. Reminder went out with the new CAD build; the completeness figure should recover over the next two months.
[email protected], Sep 4, 2026 (edited)
ContextSOC Section 2: Fire Station Information
Station 2 was rebuilt in 2019 on the original site; the apparatus floor was lengthened for the ladder. Station 3 is a 1974 building with a single drive-through bay and is the first candidate for the capital plan.
[email protected], Aug 2, 2026 (edited)
Notes print in the CRA/SOC document under the section each figure feeds. Questions and notes marked dashboard-only stay here for the team.Build the package
SOC package readiness
8 of 12 sections have notes1. District Overview
none yetWrite
2. Fire Station Information
1 noteWritten
3. Community Risk Summary
1 noteWrite
4. District and Station Incident Analysis
2 notesWrite
5. Planning Zones
none yetWrite
6. Fire Risk Assessment
3 notesWrite
7. EMS Risk Assessment
1 noteWrite
8. Technical Rescue, Hazmat, and Wildland Risk
none yetWrite
9. Special Risks and Natural Hazards
none yetWrite
10. Critical Tasks and Effective Response Force
2 notesWrite
11. Performance Measurement
2 notesWritten
12. Baseline Performance Objectives
1 noteWrite
Each open-text section of the package prints the notes attached to its figures. Add one from any figure, or here for a section with no figure of its own.
Good notes to write
Reasons a month looks the way it does: a bay door out of service, a CAD change, a new dispatch contract. Changes on the ground: a senior living complex opened, a bridge closed, a new engine company went in service. The actions you took in response. Write it the week it happens; the SOC is written the year after.
Sections
2 of 12 written1. District Overview
Not writtenno field notes yet
2. Fire Station Information
Writtenno field notes yet
3. Community Risk Summary
Not writtenno field notes yet
4. District and Station Incident Analysis
Not writtenno field notes yet
5. Planning Zones
Not writtenno field notes yet
6. Fire Risk Assessment
Not writtenno field notes yet
7. EMS Risk Assessment
Not writtenno field notes yet
8. Technical Rescue, Hazmat, and Wildland Risk
Not writtenno field notes yet
9. Special Risks and Natural Hazards
Not writtenno field notes yet
10. Critical Tasks and Effective Response Force
Not writtenno field notes yet
11. Performance Measurement
Writtenno field notes yet
12. Baseline Performance Objectives
Not writtenno field notes yet
Risk prioritization matrix
Not startedVision 20/20 likelihood and consequence ratings; prints in Section 3
Twelve open-text sections plus the risk prioritization matrix. A written section prints in the package in place of its prompt.
Section 1
District Overview
District Overview Narrative. Provide a description of your district's geography, governance structure, and community characteristics. Include information about the service area's history, major geographic features, transportation corridors, and governance model (e.g., fire district, city department, fire authority).
Read-only in demo mode. Subscribers on CRA/SOC write and save each section here; the package prints it on the next build.
0 / 20,000
Field notes feeding this section
No field notes feed this section yet.
Every member of the department can read the saved narrative.Build the package
Flag priority tracts
Response: filter off (any speed qualifies)
Risk: filter off (any risk level qualifies)
Volume: at least 3 calls/yr
Demand: filter off (any call volume qualifies)
Flag: top 7 by priority index (20% of your 35 tracts)
Email alerts
Read-only in demo modeChecked nightly after your data updates, between Monday briefs. Alerts are per user; each teammate manages their own. One email per trigger; a condition that stays true won't email you every night.
Alerts go to each signed-in user who turns them on.Settings page