Build and review a NERIS fire incident report

Create, review, and correct fire incident reports with NERIS guidance and a clear QA queue. NERIS submission requires agency enablement, credentials, and apparatus mappings.

Guided reporting, validation, and QA review are ready today. NERIS submission requires agency enablement, credentials, and apparatus mappings. Submission and status tracking become available after that setup is complete.

All workspaces

LifelineIQ Fire workspace with fictional training data

What your team does in Fire

Incident documentation

Report Editor

Crews document the incident, apparatus, actions, people, and narrative, with NERIS requirements shown in the editor.

Core details. Fields change with incident type.
Apparatus and actions. Who responded and what they did.
NERIS requirements. Checked before submission.

Reporting status

Command Center

Drafts, reports in review, submissions, and rejections are visible without opening every incident.

Work in progress. Resume the right report.
Review queue. Ownership and status clear.
Submission state. Accepted or needs action.

Fix and resubmit

Rejected

A rejected report keeps the response from NERIS and identifies who needs to correct it.

Rejection detail. The actual response from NERIS.
Assigned correction. One person has the report.
Submission trail. Prior attempts and changes.

Everything in Fire

Every page your team can open in this workspace.

Incidents / NERIS

Command CenterNew ReportAll ReportsDraftsReview QueueNERIS SubmissionsRejectedNERIS DictionaryIncident Types

Personnel / Training

Personnel & Credentials

← Previous

Insight

Security

Walk through Fire with us.

Tell us how your team handles this work today, and we will show you how it runs in Fire.