RedAlert

RedAlert Platform

The report should take three minutes, not thirty

RedAlert is NERIS V1 Certified. Dispatch data fills in what the county already knows, templates handle the calls you run constantly, narratives generate in one click, and validation catches problems before submission rather than weeks later. Reports can be started from the apparatus tablet, from a phone in the field, or at a desk, and they all land in the same record.

Narratives that write themselves

The narrative is the part nobody wants to write, and the part that gets thinnest at eleven at night after a long call.

RedAlert generates it in one click, built from the call type, actions taken, response times, and the rest of what the record already knows. Departments also build a bank of saved narratives for the calls they run constantly, so an officer picks from a list and the narrative prefills. Edit it, add what's specific to this call, and move on.

Templates for the calls you run every week

Every department has them. The nursing home you go to for lift assists twice a month. The alarm panel at the same commercial building. The stretch of highway where the MVAs happen.

Build a template once and the next lookalike report takes thirty seconds to complete. RedAlert marries the template to the dispatch information that came in with the call, and the report is essentially done. No retyping the same occupancy details, the same apparatus, and the same actions taken from one report to the next.

Plus-one codes and special studies

Most departments track things NERIS doesn't ask about. Something the county wants. A city council metric. A grant condition. An internal question the chief has been trying to answer for two years.

Add those as custom fields on the incident report and they get filled out as part of the normal reporting process, then flow into your reporting alongside everything else. Your crews don't do anything extra beyond the field itself, and you stop maintaining a side spreadsheet to answer a question the incident report should have answered.

The report starts before anyone sits down

Departments running a CAD interface get times, units, address, call type, and dispatcher comments populated the moment dispatch tones out. Crews start the report from the apparatus tablet in RedAlert MDT while they're still on scene waiting on a tow. Officers finish it from a phone in RedAlert Mobile with photos attached, or in RedAlert Desktop.

Wherever it's started, it's the same record. No export, no re-keying, and no version of the report living somewhere else.

Validation before submission, not after

RedAlert's validator checks records against the NERIS schema before they go out, so errors surface while the officer is still in the report.

What's included

  • NERIS V1 Certified incident reporting for state and federal submission
  • One-click narrative generation from call type, actions taken, and response times
  • Saved narrative bank for common call types
  • Incident templates for recurring calls, merged with live dispatch data
  • Custom plus-one codes and special studies as fields on the incident report
  • Custom validator that catches errors before submission
  • CAD-populated times, units, address, call type, and dispatcher comments
  • Reports started from the MDT on scene, from RedAlert Mobile in the field, or in Desktop
  • Photos and documentation attached to the incident record
  • Personnel attached from the same member records you maintain
  • Hundreds of built-in incident and response reports, plus custom reports built by our team

Common questions

Is RedAlert NERIS certified?

Yes. RedAlert is NERIS V1 Certified. NERIS templates, updated incident schemas, built-in validation, and migration from NFIRS are part of the platform rather than a separately priced module.

Can RedAlert write the narrative for us?

It can generate one in a single click, built from the call type, actions taken, response times, and the rest of the record. Departments also build a bank of saved narratives for calls they run constantly, so common reports start from a prefilled narrative rather than a blank box. Officers edit from there rather than writing from scratch.

What are incident templates?

Saved report setups for calls you run repeatedly. If you respond to the same nursing home for lift assists, build the template once, and the next one merges with the dispatch data and completes instantly. It eliminates retyping the same occupancy, apparatus, and actions from one report to the next.

Can we track data that NERIS doesn't collect?

Yes, through custom plus-one codes and special studies. Departments add their own fields to the incident report for anything the county, the state, the city, or the department itself wants tracked. Those fields get completed during normal reporting and flow into your reports alongside standard NERIS data.

Where can reports be started?

Three places. From the apparatus tablet in RedAlert MDT while the crew is still on scene, from a phone or tablet in RedAlert Mobile with photos attached, or in RedAlert Desktop. All three write to the same incident record.

What happens to our NFIRS history?

It comes with you and stays queryable. Alpine's onshore team migrates historical incident data as part of every implementation, so you can report across the NFIRS and NERIS periods because both live in the same database.

How does personnel get attached to the incident?

From your member records, either by an officer selecting them on the report in Desktop or RedAlert Mobile, or automatically from Kiosk check-in for departments running one. Personnel are never assumed from who tapped responding on their phone.

What if the NERIS schema changes?

That's what a vendor is for. Alpine's engineers are in Rochester and have tracked federal and state reporting requirements since 1994. Schema updates arrive as software updates.

See incident reporting & NERIS in RedAlert

A real walkthrough with a real person, shaped around how your department runs.

Remote Support