Every board you run in WebEOC has a live screen here.
Find the board, log or form you use today on the map below, see the QRM screen it becomes, and see what a quiet Tuesday and an activation day look like after you move.
What each WebEOC habit becomes in QRM
- In WebEOC: Incidents and the EOC. In QRM: Command Room. One room per declared incident. The map, live video, objectives, the roster and the running log share one floor, and responders join from a browser or a phone.
- In WebEOC: Position logs. In QRM: ICS-214 Records. An append-only activity log for the incident. Every entry is timed and attributed, you can filter and replay it, and Export ICS-214 prints the form.
- In WebEOC: Significant events board. In QRM: Significant events. Star any log entry as significant. Starred entries appear on the Situation Report, its PDF and the COP for every incident you may enter.
- In WebEOC: Mission and task tracking. In QRM: Room tasks. Tasks inside the incident, with owners, due times, ICS section and ESF tags, on a board everyone on the floor can see.
- In WebEOC: Resource requests (ICS 213RR). In QRM: Resources. Request resources in place from the room. Each request is tied to the incident and your asset records, carries an ESF tag, and rolls up by ESF on the COP.
- In WebEOC: Situation report board. In QRM: Situation Report. The ICS-209 for the incident: summary, locations, lifelines and significant events. QaiS drafts it from the room's records, you edit it, and an approved copy is kept as a numbered snapshot with a PDF.
- In WebEOC: ICS forms. In QRM: ICS Library. FEMA and NIMS ICS forms 201 to 225, an Incident Support Model EOC set, and the FEMA Public Assistance and Individual Assistance recovery forms, as live forms you fill, route and report on.
- In WebEOC: IAP builder. In QRM: Action Plans. An Incident Action Plan or EOC Action Plan assembled from one operational period's forms, reviewed, and published as a versioned PDF in the FEMA 202 to 208 box layouts.
- In WebEOC: Operational periods. In QRM: Operational periods. Numbered periods with objectives, a briefing and a Planning P tracker. Opening the next period closes the current one, and a closed period cannot be changed.
- In WebEOC: EOC staffing roster. In QRM: Incident org chart. An org chart for this incident, built from the room roster, with 28 ICS and EOC positions in six sections and open seats you can see. The Team tab groups people by section.
- In WebEOC: ESF and lifeline status. In QRM: Community Lifelines. The eight FEMA Community Lifelines on every incident, reported as stable, stabilizing or unstable, with ESF 1 to 15 tags on tasks and requests.
- In WebEOC: After-action reports. In QRM: After-Action Report. The AAR is built from what happened in the room: the chronology, decisions, gaps and the improvement plan. Public input comes in through a form behind a QR code.
- In WebEOC: Fusion and mutual aid. In QRM: Networks. A network joins partner organizations: shared channels, each other's contact rosters, shared resources with their status, and network alerts to each duty officer.
- In WebEOC: Partner accounts. In QRM: Guest seats. Invite a partner by name. They get a passwordless link, check in from a phone, and the Incident Commander admits them. They need no QRM account.
- In WebEOC: Public information board. In QRM: Joint Information Center. Releases move from draft to review to approved to released, and rumors are tracked until they are closed. Nothing sends from this tab: an approved release hands a draft to the tool that sends it.
- In WebEOC: Mass notification partner. In QRM: SiSA Alert. SiSA Alert, the HQE mass notification product, opens as a tab in the room. It is licensed separately and carries IPAWS, text, voice and email delivery.
- In WebEOC: Status boards. In QRM: Field readiness boards. Boards with your own states, colors and columns. Units, stations or sectors report from a phone link that needs no account, and an alerting status notifies the EOC.
- In WebEOC: Shelter status board. In QRM: Fortress shelter rosters. Who is inside each shelter right now: check-ins by door QR code, pass, desk or text, capacity, and people who need help, on a board and a map.
- In WebEOC: Map add-on. In QRM: RallyPoint COP. The common operating picture comes with RallyPoint: incidents, evacuation orders, open requests, resources and shelter capacity on one map, with a situation brief for whatever you click.
- In WebEOC: GIS layers. In QRM: Shared map layers. One layer library for every map. Upload shapefiles, KML, KMZ, GeoJSON or CSV, or link an ArcGIS, WMS or WFS service, then share each layer to the apps that need it.
- In WebEOC: Evacuation boards. In QRM: Evacuation Command. Zones, routes, road closures, hazards and shelters, with a public status page and an ArcGIS-compatible feature service your GIS team reads by URL.
- In WebEOC: Volunteer rosters. In QRM: Volunteer Command. CERT, MRC, ham radio and search and rescue rosters with credentials, deployments, shifts, and recall by text with a YES or NO reply.
- In WebEOC: Mobile access. In QRM: QRM app. One app on iOS and Android with the whole workspace in it, including the Command Room and every agent.
- In WebEOC: Damage assessment board. In QRM: Damage Assessment. One record per home or business, with FEMA damage categories, photos and location. It works on a phone without a signal, and only a person confirms a category.
- In WebEOC: Public damage reports. In QRM: Report damage. Residents report damage from the RallyPoint public page while the event is open. Reports land in a review queue, where staff accept or dismiss each one.
- In WebEOC: FEMA PA cost tracking. In QRM: PA cost capture. Force account labor with the overtime split, equipment at FEMA schedule rates, bills, purchase orders and donated volunteer hours, booked by FEMA category A to G. Labor and equipment summaries export as CSV.
- In WebEOC: Preliminary damage assessment. In QRM: Joint PDA links. Send state and FEMA reviewers a link to a sample of confirmed records. They need no login, see no private fields, and their answers land on each record.
- ThreatSense (also in QRM): Weather and hazard feeds, wildfire, earthquakes, power outages and IPAWS alerts, matched against the sites you register, with the expected impact routed to the right person.
- AFN Dispatch (also in QRM): A registry of residents who need a ride, activations scoped to zones, a dispatch board, and rides you follow on a map. Start is the one human approval.
- QaiS and agents (also in QRM): QaiS reads every module. It drafts the sitrep and the morning brief, and people approve what is sent or spent.
- RallyPoint portal (also in QRM): A public page for residents with zone status, an address check, active orders and surveys.
- Signal Command (also in QRM): Plan radio and siren coverage on a map: place antennas and sirens, render the coverage, and export the layer as GeoJSON or KMZ.
- Projects and finance (also in QRM): Projects, tickets, messages, finance and partner contacts in the same workspace as the EOC.
Moving over in 30 days
Week 1: export your boards, forms and contact lists; Import Anything reads any format and puts each record in the right module. Week 2: your board designs become forms, status boards and automations. Week 3: run your own drill side by side with WebEOC and score it together. Day 30: cut over to one login and one phone app.
Questions
Can QRM replace WebEOC in our emergency operations center?
Yes. In QRM each declared incident gets a Command Room with the map, live video, objectives, the ICS-214 activity log, tasks, resource requests, the Situation Report (ICS-209), Action Plans and the After-Action Report. The ICS Library carries FEMA and NIMS ICS forms 201 to 225 and an Incident Support Model EOC set. The move takes 30 days and includes a side-by-side drill on your own scenario before cutover.
How do partner agencies join an incident in QRM?
Two ways. Organizations that coordinate regularly join a QRM Network, which gives them shared channels, each other's contact rosters, shared resources with status, and network alerts to each duty officer. For a single incident, the Incident Commander invites a partner by name: they get a passwordless link, check in from a phone and are admitted from the lobby, with no QRM account needed.
Does QRM send IPAWS alerts and mass notifications?
Emergency mass notification is SiSA Alert, a separate HQE product that opens as a tab in the QRM Command Room and carries IPAWS, text, voice and email delivery. The QRM Joint Information Center tracks releases and rumors, and an approved release hands SiSA Alert a prefilled draft that a person reviews and sends.
Does QRM work with ArcGIS and our existing GIS layers?
Yes. Shared map layers accept shapefiles, KML, KMZ, GeoJSON and CSV, and link ArcGIS, WMS and WFS services, so every QRM map reads one layer library. Evacuation Command publishes zones, closures, shelters, hazards and routes as an ArcGIS-compatible feature service that ArcGIS Online, ArcGIS Pro, Field Maps and QGIS read by URL.
How does QRM handle damage assessment and FEMA Public Assistance costs?
Damage Assessment records homes and businesses with FEMA damage categories, takes resident reports into a review queue, tracks Public Assistance sites by category A to G, and captures force account labor, equipment at FEMA schedule rates, bills, purchase orders and donated volunteer hours. A per-capita meter shows how close the event is to a declaration, and labor and equipment summaries export as CSV.
Is there a mobile app?
Yes. The QRM app runs on iOS and Android with the whole workspace in it, including the Command Room. Partners invited to an incident can check in from any phone browser.
Book a bake-off
QRM by HQE Systems · qais.app · Screens are from QRM demo workspaces with fictional data. SiSA Alert is a separate HQE product. WebEOC is a trademark of Juvare, LLC. QRM is not affiliated with Juvare.