How it works
Safer incidents through smarter systems
Put responder and public safety first by making incident management faster and less error-prone — connecting information systems and using AI with clear eyes about its limits.
One picture per question.
Each diagram follows one kind of information from where it enters to everywhere it is read. Signed in with an incident selected, every step that names a screen opens it.
What goes into an Incident Decision Support Briefing
Where does every fact in the report come from?
A report is assembled on demand from dozens of trusted sources: federal fire data, official health care and specialty listings, aviation records, weather, terrain, roads and coverage maps, and the facilities’ own websites. Every facility it names is kept in a directory that every incident shares and improves. Each fact shows where it came from and how sure we are of it, and anything we are not sure of waits for a person to confirm it instead of being printed as fact.
A check-in, typed once
Somebody scans the QR code on the check-in sign. Where does what they type end up?
One public form, filled in on a responder’s own phone with no account and no app, becomes the record that the roster, the readiness board, the license check, the Medical Plan, the unit log, the messaging channels, the assignment board, the demob request and the transition briefing all read. Nobody retypes it.
The board becomes the plan
What turns the Tactics board into the documents an incident runs on?
Locations imported from the incident’s own map, resources from the orders that brought them, and people from their check-ins all meet on one board, held for one operational period at a time. What is on it becomes the Medical Plan, the unit log, the C&G/Safety map, and the paperwork that releases somebody at the end of their assignment.
Where a position comes from, and what an IWI does
How does a crew’s location reach the map, and what changes when somebody is hurt?
Crews report where they are in whatever way works where they are: a text in their own words, a location pin, a text message, a satellite tracker, a phone that shares its location, or a radio call that Comms enters. Every report lands on one record per resource that shows where it came from and how old it is, and that record feeds every map, list and outside system. A call for help turns the same picture into an incident within an incident, with its own shared report, its own alerts and its own entries in the log.
How a failure reaches a human
Public-safety software must never fail quietly. How does a problem reach a person before it reaches the field?
Three layers, each watching the one inside it: the app records every problem where a person can see it, monitoring outside the app watches the things that matter most and decides when something is bad enough to wake somebody, and a service fully independent of ours makes sure a person hears about it, because a watcher that goes down with the system cannot report the outage. Eight of the pieces below exist today; ten are planned, and are drawn as planned rather than as though they already run.