Command overview.
Apparatus readiness and incident activity, all in one place.
Response-time tiles average each apparatus response year to date (district time). Missing times and zero intervals are excluded; — means no valid measurements.
Upcoming
Incident volume
Unit readiness
Incident activity
Fleet watchlist
Communications.
District messages, announcements and priority acknowledgements. Private conversations are visible to participants only.
Messages are shared securely with their intended recipients. Priority messages require each recipient to acknowledge them.
My conversations
Apparatus Inspection.
Custom checklists, signed inspections and persistent deficiencies.
SCBA.
Pack and cylinder records, assignments, inspections and service dates.
Calendar.
Important dates, training, meetings and equipment deadlines.
Apparatus.
Track unit availability, service information, and notes.
Maintenance watchlist
Inventory.
Manage SCBA air packs, cylinders, tools, and anything else the district needs to track.
Equipment can be assigned to a station or individual apparatus. Inspection dates and history are recorded on each item's details.
Incident log.
Review response timestamps, dispatched apparatus, and activity by station.
District call numbers reset January 1 (Eastern Time). A call is counted only when a district apparatus has an en-route or on-scene time; dispatch-only records are retained without a call number. CAD incident IDs never change.
Personnel.
Member qualifications, station assignments, training totals, and certification history.
Training.
Record drill details and automatically credit each attending member.
CAD drill identifiers are retained. Officer-added attendance, time, topics, and equipment are protected from re-import overwrites. Drills never increase the annual emergency-call total.
Meetings.
Schedule and record district meetings, attendance and session hours in shared D1.
Meeting hours are recorded separately and do not count toward annual training requirements or emergency incident totals. Attendance and changes are stored in district database.
Special details.
Track event staffing and participant-hours separately from training and emergency incidents.
Analytics.
Compare year-to-date results, all-time history, and personnel training progress.
Training analytics
Calls by station
Incident categories
Uses the reporting period, dates, station and incident category selected above.
Dispatch to scene
Unit responses
Reports.
Choose your content, set filters, then preview and download.
Generate detailed incident records, individual CAD unit response times, response summaries, personnel, training, meetings, maintenance and equipment records. Select a template to begin.
Apparatus, SCBA and inventory reports
Select a report area to build signed inspections, service histories or upcoming inspection and expiration records.
Select time period
Date filters apply to dated records. Rosters and requirement definitions are lists, not event histories.
Choose a report template and records
Nothing is selected automatically. Choose individual datasets or use a template.
My saved detailed reports
My saved report configurations
Save the checked report groups, dates, station and sorting once, then reuse those selections. Configurations are stored in D1; report previews and exports use current shared records.
Fine tuning: fields, filters and sorting
Each selected category has its own fields and up to three filters. These choices apply to previews and every export format and can be saved in a template.
Call class filters Emergency incidents and both response datasets. Apparatus number filters unit-related records; Inventory number filters equipment-related records. Personnel, meeting and other unrelated lists remain unaffected. Summaries use each unit's own timestamps, equally weighted positive samples up to 24 hours. Zero, missing and invalid intervals are excluded and counted separately. The 90th percentile uses the nearest-rank method. Date filters follow the incident date; station filters restrict timing rows to that station's units.
Search updates 450 ms after you stop typing and filters the loaded records on this device.
The reporting period and date range are not saved in templates. Choose dates in Step 1 for each report; loading a template keeps your current date selection.
Save selected records, apparatus/inventory filters, fine tuning, search, sorting to your account.
Generate results
Step 5 · View results in metric tiles and records
Step 6 · Save reports
Monthly and year-to-date totals
Shared D1 totals respect your read permissions. Session-hours measure event duration; personnel-hours credit each participating firefighter separately, including individual training overrides. Station personnel-hours follow each firefighter's station assignment.
Step 1 · Select time period
Step 2 · Select report template
Step 3 · Fine tune report metrics
Choose report metrics (these selections can be saved)
Saved monthly templates
The reporting period and date range are not saved in templates. Choose dates in Step 1 for each report; loading a template keeps your current date selection.
Save your selected totals to your account.
Step 5 · View results in tiles
Sign in to generate this report.
Step 6 · Save reports
Data & settings.
Back up your dashboard, import records, or start with a clean roster.
Appearance & layout
Customize how the dashboard looks for you. Your appearance settings are saved to your officer account and follow you across devices.
Reports
Build customized reports and export selected records as CSV, HTML, or PDF. Full database backup and restore are managed under Administrator.
Import records
Restore a dashboard JSON backup, or import an incident CSV exported from this dashboard. Files are reviewed before authorized records are imported into the shared database.
Import CAD reports and archives
Import a single Columbia County closed-incident email/PDF or a collection of messages from a .mbox file. Review duplicates, responses, drills and details before saving structured records to the shared database.
Workspace mode
About data storage
Operational records are shared between authorized officers. Full database backup and recovery remain under Administrator settings.
Import and archive migration tools
Review your backup for cloud transfer
Choose the full JSON backup you just downloaded. We'll check its record counts, duplicate IDs and common compatibility issues right here on your device. This check does not upload the file, restore data or write to Cloudflare.
Your backup remains on your device during the initial check. Nothing is sent until you separately confirm a staging import below. Production databases remain untouched.
Controlled import to testing database
After reviewing your file, we'll compare every existing staging record before enabling import. Emergency calls, drills, special details, responses, apparatus information, maintenance schedules, service history and compatible personnel records are covered. Attendance credits and annual training requirements need separate cloud features; you can hold those records in your full backup and choose a clearly identified partial staging import. Inventory or certification records still block import.
Any accepted write goes only to stockportfiredistrict through your Google-authorized Worker. This is a one-time migration, not ongoing cloud synchronization. Browser-only colors, layout, draft permissions and local change logs are not migrated; the original JSON backup keeps them. The original backup and browser-local records remain unchanged.
Next phase · training record compatibility
After the main import is complete, check the deferred training session, member attendance and annual-hour requirements against the staging roster. This is a read-only review of your saved JSON and district records; it cannot change either database.
One-time OSHA duplicate cleanup · staging only
The original browser backup contains Osha hours, Osha, and Osha, all set to eight hours for all classes. You confirmed that the intended rule is OSHA Annual Training · 8 hours · Interior, Exterior, Fire Police. This process retains one original source ID, archives the extra imported staging rule with an audit entry, and removes duplicate rules only from a new corrected backup. Your existing local data and original JSON file are not changed automatically.
Controlled import of deferred training records
Once the separate staging Worker has been upgraded, compare the final training items with existing cloud records. The linked session and attendance are saved together; annual rules are separately audited. No production writes are allowed.
Report previews and exports use authorized shared district records. Full cloud database backups and restores are restricted to Administrator.
Version & update history
The version shown here identifies the dashboard frontend package. Backend Worker deployments and D1 migration numbers are tracked separately.
View update history
- V38.0
Combined operations update: maintenance, inspections, standby responses, personnel and attendance, messaging, inventory, SCBA and asset tags.
- V37.16 Current
Historical drill and special-detail imports without a usable duration remain in incident history without a fabricated session length or attendance credit.
- V37.15
Corrected historical CAD unit identity handling: 50-C1/2/3 are distinct from 49-C1/2/3, and station-dispatch identifiers 49-000/50-000 remain separately visible in archive records.
- V37.14
Added distinct overall and personal assigned-inspection YTD completion rates, independent of the inspection list filters.
- V37.1
Added inspection starter checklists and configuration, automatic SCBA linking, private photos, tag tracking, printer presets, direct inspection links and mobile layout fixes.
- V37.0
Introduced apparatus inspections, signed checklists, SCBA service records and asset QR tags.
- V36.9.29
Added All calls, FD, EMS and Split call-distribution charts.
- V36.9.28
Call-class selections now filter Emergency incidents together with both response-timing datasets.
- V36.9.27
Improved night-mode readability of monthly and year-to-date report metric selections.
- V36.9.26
Personnel name changes appear on the first opening of account-access controls and at the linked account’s next login check.
- V36.9.25
Primary administrators can browse dated full-database backups and download SQL.gz files with verification manifests through authenticated access.
- V36.9.24
Added a separate weekly backup service with verified compressed SQL snapshots, safe rotation, per-database archives and primary-administrator backup status.
- V36.9.23
Added visible named report saving, per-category field selection, filters and sorting, plus individual unit response timings and per-unit performance summaries.
- V36.9.22
Added separate Chief and Apparatus YTD turnout and travel tiles. Chiefs are 49-C1, 49-C2 and 49-C3; existing tile selections are preserved.
- V36.9.21
Zero-second CAD intervals now count as unavailable timing data and are excluded from Overview and Analytics response-time averages. Original records remain unchanged.
- V36.9.20
Overview response times now use YTD incidents, show minutes and seconds, and identify timed responses and recorded zero intervals. Includes the full Night-mode contrast review.
- V36.9.19
Simplified Reports, added day/night display modes, paged officer activity, corrected time labels and priority sender acknowledgment.
- V36.9.18
Added a shared district calendar, unified database-backed tabs and reports, moved advanced controls into their regular tabs, and simplified operational wording.
- V36.8
Added the D1 officer activity explorer, audit filters and exports, hourly authenticated-session observations, and server-side permission consistency checks.
- V36.7.1
Added an expandable release history to Data & Settings and clarified the shared D1 versus browser-local storage notice.
Asset Labels
Generate permanent QR labels by asset number. Station 49 red; Station 50 lime green. Export station sets and a master list.
Administrator.
Verify Firebase officer access, then prepare shared storage and reliable backups.
Field Management
Manage dropdown choices and identifiers used throughout the district dashboard. Changes are shared between authorized users. Existing records and service history are preserved.
Choose a field category to manage its shared values.
Officer access & permissions
Manage linked Google sign-in accounts and per-user rights. These controls update officer permissions through the authenticated D1 API.
Loading administrator access controls…
Officer activity
Authenticated database actions, account changes, and periodically observed sign-ins. Sign-in observations are limited to one per officer per hour; they are not a complete Firebase sign-in or failed-login history. Filters and exports include only authorized audit entries.
Full D1 backup & restore
Full-database snapshots include operational records, officer accounts, permissions, personal settings and audit history.
Automatic SQL snapshots are kept in private cloud storage. Success means the compressed file was read back, decompressed and checksum-verified; it does not replace an isolated restore rehearsal. Restore remains a separate, explicitly authorized procedure.
Open Administrator to check the automatic backup service.
These are full SQL database snapshots. Verification occurred when each backup was created. Keep its manifest to check SHA-256 hashes before recovery. External sign-in settings, secrets and Apps Script are maintained separately.
Officer accounts
Each officer can have custom access to individual functions. Starting presets are optional; explicit Allow or Deny settings override them. The Worker enforces actual permissions, but these editor controls still save local planning drafts only and do not change any officer account in staging.
Permission editor
Select a planned officer to choose exactly which actions they may take. You can also register new permission definitions in the backend as future dashboard modules are added.
Change history
This is a basic activity list from this browser only. It cannot identify or verify individual users. In production, incident, apparatus, maintenance, and permission changes will include the authenticated actor, timestamp, and before/after values in a server-side audit table.
ADVANCED ADMINISTRATION · PRIMARY ADMIN ONLYCloud services & database linkingExpand connection status
Effective deployment configuration, shown read-only. Verify the authenticated Worker and its D1 binding below. Database connections cannot be changed from browser settings, and production remains untouched.