FirePortal is where the department keeps itself organized between calls. Incidents, members, apparatus, and the reports the county and state ask for, all in one place, and most of it filled in for you as calls come through.
| CAD # | Type | Pri | Address | Units |
|---|---|---|---|---|
| F26-0912 | Building Fire | P1 | 820 Riverside Ave | ENG27 LAD27 |
| F26-0911 | MVA w/ Injury | P2 | Route 9 & Depot Rd | RES27 |
| F26-0910 | Auto Alarm | P3 | 140 Ridge Pike | ENG27 |
| F26-0909 | Odor Investigation | P3 | 210 Canal St | ENG27 |
| F26-0908 | Brush Fire | P2 | Millbrook Preserve | BRU27 TAC27 |
Every department drowns in the same paperwork: who ran, what happened, how long it took, and which report needs it by when. FirePortal is built so that answering those questions is looking something up, not reconstructing it from memory.
Because FirePortal is part of BeaconESS, the calls it tracks arrive on their own from FireHUD and Turnout. The record starts writing itself the moment the tones drop.
Every call, searchable, with the units, times, and responders already attached.
Contacts, roles, and status for the whole department in one current list.
Your rigs and what runs on them, so reports and staffing line up.
The period-end numbers and exports your county and state ask for, without the all-nighter.
Officers see and do more; everyone sees what they should. You decide.
Calls flow in from dispatch automatically, so the record is mostly done before anyone sits down.
Add members, set roles, note certifications. It is the one place the department stays organized.
At the end of the month, the quarter, or the year, the numbers are already there. Run the export and move on.
See what FirePortal looks like with your department's own incidents, members, and apparatus in it.