Everything an EOC runs on, in one browser tab
GovResponse is a single real-time web application. Command and field share the same data — from the tactical map to ICS forms, California SEMS, after-action reporting, and FEMA cost recovery.
One live map for the whole incident
A Mapbox operations map is the center of GovResponse. Every resource, need, shelter, evacuation zone, weather alert, and damage point is plotted and updates in real time across everyone connected.
- ▸Toggle layers independently — resources, needs, shelters, evac zones and routes, address numbers, danger zones, drawn overlays, weather, and damage
- ▸Click any marker to jump straight to the record and edit it
- ▸Draw hazards, closures, and zones with polygon, line, and point tools that persist across operational periods
- ▸Import reference GeoJSON or KML layers, scoped to the org or the incident
Resources, needs, shelters, and supplies
Run the operational core of the incident from connected panels. Deploy resources, track needs to resolution, manage mass care, and watch supply levels — all reflected on the map and in the activity log.
- ▸Resources by category and status, with personnel counts, capacity, mission, and agency
- ▸Needs with urgency, affected population, assignment, and progress tracking
- ▸Shelters with capacity, intake and discharge, per-shelter supplies, and ADA, pet, and medical flags
- ▸Supplies with stock levels and low or critical alerts
Zones and door-to-door, together
Manage evacuation at two levels: org-scoped zones with an auditable status, and individual addresses the field clears one by one.
- ▸Zone status from normal to advisory, warning, order, and repopulation — with a set-by and set-at audit trail
- ▸Door-to-door address checks: pending, checked-clear, checked-occupied, or no-access
- ▸Reverse-geocode an address number on the map to pre-fill the check
- ▸Everything color-coded on the tactical map
ICS forms, generated from live data
The forms your agency already files — populated from the incident as it runs, not retyped afterward. Open, review, and print to PDF.
- ▸ICS 201 Incident Briefing, with a static map image of the incident area
- ▸ICS 202 Incident Objectives and ICS 203 Organization Assignment List
- ▸ICS 214 Activity Log, seeded from the live activity stream
- ▸ICS 209 Incident Status Summary, with agency cost information
- ▸ICS 221 demobilization checkout with authorization sign-offs
Built for California SEMS
Elect NIMS only, or NIMS plus the California Standardized Emergency Management System. When SEMS is on, the platform maps your structure to the statutory framework.
- ▸Pick the incident SEMS level — field, EOC, operational area, or state
- ▸Map ICS sections to SEMS EOC functions
- ▸Work the state cost-recovery certification checklist
- ▸Track mutual-aid jurisdictions on the incident
After-action reporting that writes itself
California requires an after-action report within 90 days of an incident under CCR Title 19 §2450. GovResponse tracks the deadline and assembles the report from what already happened.
- ▸The six required narrative sections, in one place
- ▸An operational rollup — resources, needs, shelters, damage, and the ICS-214 activity log
- ▸A 90-day Cal OES deadline banner computed from the incident close date
- ▸A field to record when the report was submitted to Cal OES
FEMA cost recovery, from the first deployment
The 2025 FEMA equipment rate codebook is built in. Cost accrues as resources work, so the reimbursement packet is ready when demobilization is.
- ▸Auto-calculate cost from deployment to release using FEMA hourly and mileage rates
- ▸Override usage hours or miles when you need to
- ▸Capture cost holdback and authority sign-off at demobilization (ICS 221)
- ▸Roll totals into the ICS 209 and the after-action export
The same platform, offline, in the field
GovResponse is a progressive web app. The field runs the same software on any phone or tablet — and it keeps working when the signal drops.
- ▸Install to the home screen — no native app, no app store
- ▸Edits queue locally and replay on reconnect
- ▸Report needs, update status, and check addresses from the scene
- ▸Real-time chat with command when you are connected
Built for the record, honest about the rest
Access is org-scoped and enforced at the database with row-level security. Authentication is handled by Clerk with multi-factor support, and every change is written to a tamper-resistant audit log. Data is encrypted in transit and at rest, with the primary store pinned to a California region.
- ✓Row-level security on every table
- ✓Clerk authentication with MFA support
- ✓Audit trail on every create, update, and delete
- ✓Encryption in transit (TLS 1.3) and at rest (AES-256)
- ✓California data residency on the primary store
- ✓Archive export — HTML, JSON, and CSV — before deletion
- ○No CJIS, FedRAMP, SOC 2, or StateRAMP certification
- ○Encryption is not FIPS-validated end to end
- ○No formal WCAG 2.1 AA audit or VPAT
- ○No third-party penetration test on record
We'd rather tell you exactly where we stand than imply a certification we don't hold. Talk to us about your agency's specific requirements.
See it on your own incident types
We'll walk your team through the platform using the kinds of incidents you actually run — and help you decide if it's the right fit.
Request a Demo