For responders and EOCs
Turn incoming SOS alerts into owned, tracked incidents.
ResQNet's second half is an operations portal for the people who respond: rescue teams, NGOs, local authorities and emergency operations centers. It runs on the web and on mobile.
Who it's for
Teams who answer emergencies.
Rescue teams
See incoming SOS alerts, take ownership and record progress on scene.
NGOs and relief groups
Coordinate volunteers responding to people who are cut off.
Local authorities
Publish alerts and keep an accountable record of the response.
Emergency operations centers
One queue, one map and one timeline for every incident.
Operations portal
What responders get.
Each item below exists in the codebase today and is enforced on the server, not only in the interface.
Incident queue and workflow
Every SOS that reaches the server becomes an incident that moves through a fixed sequence: reported, acknowledged, assigned, en route, arrived, assisting, resolved. It can also be stood down with a reason. Resolved and stood-down are final.
Assignment
Assign and reassign responders. Only the assigned responder records on-scene progress, unless a coordinator with assignment permission does it for them.
Nothing silently disappears
An incident stays in the queue until a responder closes it, even if the person marks themselves safe or cancels. That change is shown on the timeline, and the dashboard shows the oldest unacknowledged incident.
Map and situational view
Incidents on a map with approximate positions. Exact location and the SOS message appear only in the detail view, for staff with respond permission.
Alerts and disaster sources
Publish and update emergency alerts, with per-source publishing permissions. Alerts can be signed so phones can verify an official alert they receive over the mesh.
Permissions and audit trail
Separate monitor, respond and assign permissions, enforced on the server. Monitor-only staff never see the message, phone number or notes. Every staff action is written to an audit log.
Current limitations
- The portal is built and covered by automated tests, but it is not deployed and has not been used in a real response.
- Staff get no real-time updates or push notifications yet.
- It has not been tested with real screen readers.
- No government or official emergency-response system is integrated with ResQNet today, and no agency uses it.
- Organization management (multiple agencies, their own staff) is not built yet.
If you run emergency response and want to talk about pilots, integration or how the workflow fits your procedures, we'd like to hear from you.