ResponderStack

Software for coordinated action

When response matters,
the stack matters.

ResponderStack is building an integrated software stack for teams solving complex, real-world problems.

Explore ImpactGrid Why ResponderStack

Built for the people
who move toward the problem.

Stack 01 / Online

Product 01

01 — 01

ImpactGrid

Map the impact.
Move the teams.
Close the gaps.

An incident mapping and field-team coordination platform for organizing coverage, assignments, resources, and operational progress during disaster response.

Operational mapping Team coordination Field progress

ImpactGrid coordinates the response. It does not collect property-level damage classifications, loss estimates, or damage photographs.

IMPACTGRID / INCIDENT MAPIN THE FIELD
ImpactGrid incident map showing color-coded impact areas and their operational status
FIELD VIEW ImpactGrid mobile field view showing a team's assigned area and street checklist
MAP THE NEEDCOORDINATE THE RESPONSETRACK THE WORK

Full capability set

From command post
to street level.

ImpactGrid keeps the operational picture, team movement, and field progress connected throughout an incident.

01Incident commandBuild and maintain the operational record.
  • Create multiple incidents and move each through draft, active, paused, closed, and archived states.
  • Record the incident commander, contact information, command-post name and address, descriptions, and operational notes.
  • Maintain ICS command and general staff positions with assigned personnel and contact details.
  • Customize area terminology—such as Coverage Area or Sector—for the way each operation works.
  • Keep incidents separated by organization and protect destructive actions with confirmation steps.
02Operational mappingTurn an impact footprint into workable geography.
  • Draw and edit the overall incident boundary plus individual polygon or configurable-radius circular coverage areas.
  • Generate recommended subdivisions that account for roads, railways, and waterways, then preview, rename, and approve them.
  • Select multiple areas directly on the map for bulk status and team changes.
  • Search addresses; use street, satellite, or hybrid basemaps; enter fullscreen mode; and center on the current device.
  • Filter by status, focus by county, impact area, or live team, and retain permanent area and team labels.
  • Use status patterns and other visual cues so map state never relies on color alone.
  • Use an Ohio parcel-boundary overlay with parcel identification and links to county auditor information.
03Coverage and road trackingSee what is assigned, underway, and still open.
  • Track unassigned, assigned, in-progress, completed, needs-revisit, blocked, and cancelled area states.
  • Start, complete, reopen, resume, or flag work while recording Low, Normal, High, or Urgent priority plus instructions, preferred entrances, and access details.
  • Build street checklists automatically from map data and track individual roads from command or field views.
  • Measure geographic completion, road mileage, and street progress, including progress inside map popups.
  • Refresh road data without losing completed checks and bulk-update selected areas when plans change.
04Teams and member rosterOrganize the people moving through the operation.
  • Create individual teams or batches of numbered teams with colors, leaders, callsigns, radios, vehicles, phones, and notes.
  • Track available, assigned, in-field, returning, and out-of-service states; bulk-update status or radio channel.
  • Compare team workloads against the incident average and safely remove multiple teams.
  • Collect members through a public, regeneratable token link without requiring an authenticated account.
  • Maintain identity, contact, and emergency-contact details; assign multiple members and promote team leaders.
  • Return members to the unassigned roster automatically when a team is removed.
05Assignment planningBalance coverage before teams move.
  • Assign, reassign, or unassign individual areas while maintaining queue order and assignment instructions.
  • Select multiple areas and teams in a bulk assignment planner and preview the proposed plan before applying it.
  • Balance work using current workload, area size and priority, team location, road distance, and estimated travel time.
  • Exclude out-of-service teams and apply the approved assignment plan in one operation.
06Mobile field workspaceGive every team a secure operational view.
  • Issue secure team-specific links and QR codes that require no user login; rotate tokens to invalidate old links immediately.
  • Show incident and command-post details, team contacts, notes, assigned areas, dispatch addresses, and building assignments.
  • Start and complete outdoor areas or indoor zones, check streets from a phone, and view area-specific maps.
  • Provide preferred entrances, field instructions, and road directions with estimated time and distance.
  • Navigate from current GPS, the command post, or a defined fallback point.
07Live team locationsMaintain a current picture of field movement.
  • Let field teams opt into browser-based GPS sharing and allow command staff to enable or disable sharing per team.
  • Support multiple distinguishable devices reporting under one team with approximate GPS accuracy.
  • View live teams on the incident map and focus the map on a selected unit.
  • Use normal sharing or a rapid mode that reports every two seconds for one minute.
  • Remember the device’s sharing preference while the field workspace remains in use.
08Dispatch intakeMove address-based requests into field action.
  • Capture caller name, phone, address, and notes for incoming field requests.
  • Geocode and map intake locations while maintaining reviewed and unreviewed states.
  • Assign, reassign, or remove requests from teams as conditions change.
  • Show assigned requests in field workspaces, printed packets, and operational handoffs.
09Markers and GIS overlaysLayer critical context onto the incident map.
  • Place labeled markers for preplans, EOCs, shelters, staging areas, blocked roads, hazards, resources, and other points of interest.
  • Add operational notes to markers and remove them when they are no longer relevant.
  • Import GeoJSON points, lines, polygons, and feature collections.
  • Show, hide, and delete individual imported overlays without disturbing the incident map.
10Building preplansConnect outdoor command with indoor operations.
  • Maintain an organization-wide preplan library with facility addresses, tactical notes, floor-plan images, and multiple named floors.
  • Draw operational zones over floor plans or import them from GeoJSON, with names, priorities, and notes.
  • Create reusable team templates and attach a protected operational copy of a preplan to an incident.
  • Select rooms individually or by drag selection, bulk-update them, and balance selected zones across selected teams.
  • Assign, start, complete, reopen, or flag indoor zones through the same operational status workflow.
  • Place preplan markers on the outdoor map and give assigned field teams access to indoor floor plans.
11Dashboards and statisticsMeasure progress by geography, road, status, and team.
  • See geographic coverage, street completion, area statuses, team availability, and live locations on the command dashboard.
  • Review dedicated statistics for area coverage, road coverage, operational status, pace and timing, and team coverage.
  • Inspect area-by-area details in flat or team-grouped views.
  • Move directly from the active incident dashboard into maps, teams, dispatch, statistics, and printing.
12Handoff and activity historyPreserve context across operational periods.
  • Prepare a handoff with situation and command information, progress, priority actions, exceptions, deployment, dispatch, map, and recent activity.
  • Filter activity by time range, category, event type, search text, and newest or oldest order.
  • Retain audit records for significant incident, map, team, assignment, status, marker, and GIS-layer changes.
13Printing and field packetsTurn the live picture into field-ready paper.
  • Print incident overviews, operational maps, deployment status, team rosters, contacts, and ICS rosters.
  • Produce individual team assignment sheets, assigned-address lists, area maps, and road check-off sheets.
  • Batch-print the first pages of team packets for faster command-post distribution.
14Organizations and securitySeparate access without slowing field intake.
  • Run multiple organizations, switch between authorized organizations, and manage organization members.
  • Assign Administrator, Incident Commander, Operations, Team Leader, Team Member, or Viewer roles.
  • Support platform super administrators, Authentik OIDC/SSO, and optional local account authentication.
  • Control user activation and local passwords; users without organization membership receive no incident access.
  • Keep incident-scoped field, registration, and intake links available without full user accounts.
15Installable response platformWork across command and field devices.
  • Use a responsive dark operational interface across desktop, tablet, and mobile screens.
  • Install ImpactGrid from its web-app manifest with branded browser, Apple home-screen, PWA, and Android maskable icons.
  • See an online or offline connection indicator when network conditions change.
  • Submit feedback inside the application and review it through platform administration.
  • Monitor deployments through a dedicated health-check endpoint.

From the field

SCARES SITREP #01 — PERRY COUNTY, OH — AUG 2026

“This system was extremely advantageous for the damage assessment teams, especially those unfamiliar with the area.”

During flood damage assessment in Perry County, Ohio, Shelby County Amateur Radio Emergency Service teams worked from ImpactGrid-generated coverage areas—printed maps with clearly defined road names, paired with a QR code that loaded the assignment straight to a team's phone.

Don W. Mumford, KF8CLU Shelby County Amateur Radio Emergency Service
Read the full situation report

Questions and support

The quick answers.
The right next step.

ImpactGrid is built for practical response work. These answers cover the product, field access, connectivity, security, and how to reach us.

01What does ImpactGrid do?

ImpactGrid coordinates incident geography, coverage areas, teams, assignments, road checks, dispatch requests, indoor operations, and field progress in one shared operational picture.

02Is ImpactGrid a property damage-assessment database?

No. ImpactGrid coordinates the response operation. It does not collect property-level damage classifications, loss estimates, or damage photographs.

03Do field teams need a full user account?

No. Teams can use secure, incident-scoped field links and QR codes without a full login. Command and administrative access remains protected by organization membership and role-based permissions.

04Can ImpactGrid be installed on a phone or tablet?

Yes. ImpactGrid is an installable web app with branded home-screen icons and responsive layouts for desktop, tablet, and mobile devices.

05Does ImpactGrid work without an internet connection?

ImpactGrid detects and displays lost connectivity, but full offline operation is not currently claimed. An active connection should be available for operational updates and synchronization.

06Is team location sharing required?

No. Browser-based GPS sharing is opt-in for field teams, and command staff can enable or disable location sharing by team. The map can distinguish multiple participating devices.

07Can multiple organizations use the platform?

Yes. ImpactGrid separates organizations, incidents, memberships, and roles so authorized users see only the operational information available to their organization.

08How do I get help with ImpactGrid?

Email [email protected]. Include the incident or organization name, what you were trying to do, and any error message you received.

ResponderStack contact

Questions, support,
or next steps?

For general inquiries, start with info. For ImpactGrid support issues, send the details to support.

[email protected] [email protected]

The long view

02 — MISSION

One connected stack.
Every critical moment.

Critical work is too often slowed by disconnected tools and fragmented information.

ResponderStack is being built as a complete operational layer—giving teams the clarity to see what’s happening, the coordination to move together, and the confidence to act.

01ImpactGridAVAILABLE FIRST
+The stack growsMORE TO COME