Where Reports lives, what its five tabs answer, and how to compare periods, set a department target, and export or print the numbers.
Loading…
What this does not do
the numbers are only as good as what was entered — this reports your data, it does not validate it, and it makes no comparison to other departments. A target is drawn only when the department set one; CTT never invents one. No forecasting. Sample mode (`?sample=1`) is bundled illustrative data, badged on every card — never call it real. The under-three suppression is NOT complete: three surfaces cannot state a sample size (`n unknown`) and Response Times still shows a single incident's Avg/P90 under the "Needs 3" banner — say the page *flags* thin averages, never that it *withholds* them.
One incident tells you what happened on one call. Reports tells you what's been happening across all of them — whether dispatch-to-scene times are creeping up, which hoseline size actually gets pulled, and whether your drills are moving anything.
Where it lives
Click Reports on the Dashboard to open it. There's no admin gate on it — everyone signed in to the department reads it, whatever their role. Setting a target is a department admin task, covered below; reading one is not.
The five tabs
Reports is organized into five tabs — Overview, Equipment, Response Times, Command, and AAR Insights. Overview covers incident counts by type and by month, AAR completion rate, open action items, and mutual aid calls. Equipment covers hoseline size distribution, ladder size frequency, and special equipment usage. Response Times covers dispatch-to-scene averages and percentiles, plus fireground milestone timings — On scene, Water on fire, Primary all clear, and the rest. Command covers how often your command functions get established and how that rate is trending. AAR Insights rolls up completion rate and aggregates strengths, improvements, tags, and action items from across your after-action reviews.
What counts
Only finalized incidents feed these numbers — a draft sitting half-written on someone's desk doesn't count. Training drills are excluded by default; check Include training incidents to fold a drill's timings in. Finalizing an incident populates the underlying record, whether or not anyone ever opened the Quick Metrics form for it.
Date range and comparison
Pick a window with the preset buttons — 30d, 90d, 6 mo, 1 yr, or All Time, the default — or set custom dates. Turn on Compare with previous period to line the window up against the equal-length one before it; it's unavailable on an open-ended range, since all time has no previous period to compare against.
Baseline and targets
Every chart tracking a timed or counted metric can carry two reference lines. The first is your department's own baseline — the trailing median over your last 10 finalized incidents, or fewer if you don't have 10 — and it draws on its own as soon as there are finalized incidents behind that metric; the line names the count it used, so it reads "your last 4" when that's all there is. The second is a target, and it appears only if a department admin has set one under Benchmarks in Admin, where a target is optional: leave it blank and the chart carries the baseline alone. A value is only ever marked as missing against a target your department typed — with none set, nothing reads as a failing grade, because Coffee Table Tactics doesn't decide what "good" looks like for your department.
Click into a chart or a stat card and a drawer opens listing the incidents behind the number, so you can check it against the actual calls rather than take it on faith. The drawer says what it is listing: every incident in that period under the filters you have on, not only the ones in the segment you clicked.
Thin averages
An average, percentile, or rate built from fewer than three finalized incidents carries a flag rather than reading as settled — the card names the shortfall, for example "Needs 3 finalized incidents · has 1." A few figures — one each on Equipment, Response Times, and Command — can't even say how many incidents they're built from; those read "n unknown" rather than being hidden.
Sample data
Turn on Show sample data to see every tab filled with a bundled, fictional department's numbers instead of yours — a way to see a mature Reports page before your own history fills in. It's badged on every card, and drilling into a number or exporting is off while it's on, since a sample bar has no real incidents behind it.
Export and print
Every tab has an Export CSV button that writes out exactly what's loaded on screen, under the filters currently applied, so the spreadsheet and the screen never disagree. For a paper copy — a budget meeting handout, say — use your browser's print command; the active tab is laid out for paper on its own.