Use sample incident data to see how FIREFLY connects the department, captures the incident record, checks the filing fields, and produces a report that is ready to review or submit.
Residential structure fire
418 Harbor Road • River Bend Fire Department • Incident 25-0417
Connected department
Station 3 / Capt. Elena Lewis
Timeline captured
Arrival through knockdown
Report outcome
Ready for review and submission
Click through the same order crews and leadership already think in.
Each step keeps sample data visible so you can see how the report grows from connected department details into a filing-ready record.
Step 1
Connect the department
Start with the department profile, station defaults, and the user who is filing the report.
Step 2
Load the incident record
Pull in the sample incident, address, response type, and the units that were dispatched.
Step 3
Capture the incident timeline
Record the sequence as it unfolds so the report already has a usable storyline when the incident ends.
Step 4
Validate NERIS fields
Review required report fields, confirm the data that is already present, and flag anything still missing.
Step 5
Produce a filing-ready report
Finish with a report preview that is ready to submit, edit, or hand off to the next reviewer.
Connect the department
Start with the department profile, station defaults, and the user who is filing the report.
Sample record
Agency
River Bend Fire Department
Station
Station 3
Reporter
Capt. Elena Lewis
Template
NERIS Simplified
What FIREFLY has already organized
Department profile loaded
Reporter signed in
Default station selected
FIREFLY starts with the department already connected, so the report opens in the right context from the beginning.
Connected in one pass
The department profile and reporter context are already in place when the workflow starts, which reduces setup friction.
Sequence stays organized
The incident story is collected in the same order a crew already thinks about it: connect, capture, review, file.
Report output feels obvious
The finished preview makes it clear what gets submitted, what gets edited, and what still needs review.
Want the demo to match your department workflow?
This walkthrough is intentionally sample-based so you can see the reporting sequence without needing live incident data. When you’re ready, we can map it to your department’s reporting structure and rollout path.
