NERIS Implementation Guide

Confirm the reporting path first

Start with the official USFA NERIS resources and your state reporting contact. NERIS is the national reporting direction, but state onboarding, timing, and support steps can still affect how a local department should prepare.

Before configuring software, document who is responsible for report entry, officer review, correction, submission, and retention. This prevents the new system from inheriting unclear approval steps.

• State onboarding requirements
• Department administrator roles
• Officer review and approval steps
• Correction process for incomplete reports
• Local retention and export needs
• First-month quality review process

Prepare the data behind each report

Incident reports depend on clean supporting records. Review station names, apparatus, personnel, roles, response areas, mutual-aid patterns, and common incident workflows before the department starts relying on the new process.

If the reporting system connects to RMS, dispatch, personnel, and equipment data, crews spend less time re-entering details and officers have better records for review.

Train from real call scenarios

Training should use common department incidents, not only abstract screenshots. Walk through a medical assist, fire alarm, structure fire, motor vehicle crash, false alarm, and mutual-aid response so crews understand the practical workflow.

Station Boss supports NERIS-ready reporting as part of the broader fire department software platform, so implementation can include RMS, dispatch, training, scheduling, and operations instead of only the report form.