For agencies & organizations
What the platform does operationally, in the language of people who run responses — including what it does not claim.
What an agency should know, and should have
The first list is what the platform is and is not, in the terms an agency is accountable for. The second is the material an agency already owns that has to be in hand before anything can be configured — bring it to a demonstration and the conversation starts from your own operations rather than ours.
What it does, and what it does not claim
Read this before an evaluation meeting, so no expectation is set that the platform will not meet.
- It works alongside 911, PSAP, CAD, MDT and radio — it does not replace, dispatch or write into any of them.
- It is configured, not installed: roles, incident categories, exclusions, distances and alert rules are set per agency.
- Nothing is shared with partner organizations unless the agency switches that sharing on.
- Records are held behind role-based access, sensitive fields can be restricted further, and access to them is audited.
- The public page a community gets and the operational record are separate: publishing a page exposes nothing internal.
- Alerting is routed by trigger, recipient permission and priority — an agency's own policy decides who is told what.
- Hazard modelling and planning scenarios are labeled as planning, with their assumptions and missing inputs stated.
- No response-time, survival or cost result is claimed. Any agency judging it should measure against its own baseline.
- Integration with an existing system is a configuration project with the vendor, not an automatic switch.
- Training, an administrator on the agency side, and a review of the alert rules are part of standing it up.
What your agency already holds
Gather this first; every setting below is answered from it rather than asked for again later.
- A named administrator and a named operational owner on the agency's side.
- The service area, stations and unit identifiers the agency wants covered.
- The incident types it responds to, and the categories it would exclude from routing.
- Its alert rules: how far, how many people, and how long before a call escalates.
- A resource inventory — AEDs, kits, hydrants, shelters, access notes and their owners — or the person who holds it.
- The contacts who should be alerted for a given resource, and the permission they gave to be contacted.
- Its privacy position: which fields may be published, which stay internal, and who may read a record.
- The baseline it already measures: time to first aid, AED before crew, handoff completeness.
- The constraints of its CAD, radio and records systems, so the boundaries are stated up front.
- The questions its board, council or medical director will ask, so they are answered in writing.
- Structured intake with location, patient status, hazards and media captured at the source
- Pre-arrival briefing from the intake, bystander entries and the address's own history
- Nearest mapped resource returned with access detail, hours and a route, from the call's own screen
- One record read by every service on the call, each entry carrying its own confirmation level
- Bystander, caller and witness entries reaching the responding units directly rather than by relay
- Guided steps read aloud with spoken pacing, attached to the incident type and to the resource
- Resource register with coverage totals by area, inspection and expiry dates, and alert contacts
- Incident timeline, structured handoff and after-action reporting assembled from the call itself
- Alerting routed by trigger, recipient permission and priority, under agency policy
- Hazard monitoring and planning scenarios labeled as planning, with assumptions and missing inputs stated
- Roles, categories, exclusions, distances and publication rules configured per agency
- No CAD coupling, no installed agent, no write path, and no dependency in an agency's chain of response
This part is written for the people who would have to run it: dispatch managers, EMS and fire-rescue leadership, law enforcement, emergency management, search and rescue, receiving facilities, and the organizations that hold the equipment a response depends on. It sets out what changes in a response and where, what an agency gains in information and when, what the platform does and does not claim about outcomes, what each service line gets first, what an agency can measure to judge it, how it can be adopted in phases, and the hard questions an evaluation actually raises — answered here rather than deferred to a sales call.
Who it serves and who it covers: citizens, dispatch, emergency management, EMS, fire-rescue, law enforcement, search and rescue, water rescue, crisis teams and animal control. Applications range from a bystander at a collapse to an emergency-management center running a hurricane, and the same record, map and communication layer serves each of them, with access following their role. The audience material sits at the end of this section, under Who it serves and who it covers.
The short version: it gives a responding unit what it does not have today at the moment it matters — a structured report instead of a paragraph, the nearest piece of equipment with an access note and a route, an address's own history, and entries from the people standing there arriving as they happen rather than being relayed. It gives a community a way to use what it already owns, and gives it a register, a coverage picture and a planning layer it can argue with because the assumptions are written down.
What it does not do is any of the following: it does not take the place of 911, PSAP, CAD, MDT or a radio system; it does not dispatch units; it does not issue official warnings; it does not write into an agency's CAD; it does not require an agency to change its systems, staffing or procedures; and it does not claim a response-time, survival or cost result, because none has been measured here. The measures an agency would use to test it against its own baseline are listed further down this section.
Stated for the platform as built, subject to the configuration decisions of the community or agency using it. Integration is a configuration project an agency decides on, and an agency is named here as a user only where that agency has said so.
Before you read any further
Four answers that decide whether the rest of this section is worth your time: what it asks of your agency, what it leaves in your hands, how a first deployment works, and what makes a demonstration useful rather than a sales call.
- No CAD, MDT or radio replacement — the platform sits alongside what you run
- Nothing installed on dispatch or apparatus machines
- No write path into your CAD, and no dependency in your chain of response
- No change to your procedures required to try it in one area
- Which incidents route to your people, and which categories are excluded
- Alert radii, nearest-N, escalation timeouts and quiet hours
- Who may read a record, which fields are restricted, and what is audited
- Whether anything is published publicly, and what partners can see
- A pilot in one area or one service line, using the systems you already have
- Your roles, categories and alert rules configured with you, not for you
- Partner organizations added as your policies allow — nothing shared by default
- Phased expansion once the measures below are read against your own baseline
- A call type you want to test, and an area to test it in
- The baseline you already measure: time to first aid, AED before crew, handoff completeness
- Your radio and CAD constraints, so the boundaries are stated up front
- The questions your board or council will ask, so they are answered in writing
Nothing above is an outcome claim. No response-time, survival or cost result has been measured here, and the measures an agency should use to test it against its own baseline are stated further down this section.
Pick the kind of agency or organization
The same platform, read from twelve different seats. Choose one to see what it mainly does for that team and which features carry the weight.
Fire & rescue
Pre-arrival detail on the call, the nearest equipment and how to reach it, and a shared record the crew reads on the way rather than a verbal summary on arrival.
Every registered AED, kit, hydrant, shelter and unit on one operational map, with access detail and routing.
Verified nearby responders alerted for eligible incidents only, under your rules and exclusions.
Photographs, video, audio, text and quick options shared by callers and bystanders straight to the responding units, each with its own confirmation level, plus multiway video between everyone on the call.
BOLOs, hazard warnings, evacuation and shelter-in-place notices, routed by configured trigger and permission.
Step-by-step guidance with read-aloud and voice pacing, attached to the incident and to the resource.
Structured intake that keeps working during surge, with Always Answered PSAP gathering and organizing details.
Timeline, structured handoff and after-action reporting built from the record during the call.
Everything configurable: roles, feature selection, automation levels and escalation, per agency.
Scenario planning for fire, flood, surge, hazmat, outage, evacuation and casualty demand, labeled as planning.
Built to sit alongside PSAP, CAD and MDT operations, with integration options discussed per deployment.
Participating organizations decide which features are appropriate for their jurisdiction, and how their operational requirements would be accommodated. Integration with existing systems is a configuration project rather than an automatic switch, and not every capability suits every agency configuration — a demonstration is the place to work through what would actually fit.
Ask for a presentation or a working demonstration and we will walk through the consoles, the resource pull, the alerting rules and the modeling layer with your jurisdiction in mind.
How it changes a response, stage by stage
The same call, worked the way the platform is built to work it. Each row states what changes, and what an agency can watch to see whether it changed.
A structured report — what happened, how many people, whether the patient is breathing, whether there is bleeding, where — is captured as separate fields rather than one paragraph of free text, and the location arrives with it as a dropped pin, a typed address or a device fix.
Intake completeness, and the time between the call starting and a unit having something actionable.
Follow-up answers and any media the caller already added sit on the call. Where Always Answered is enabled, a report can be filed and organized while every call taker is occupied, so a busy period produces a queue rather than a lost call.
Calls that arrive with the detail already separated, and calls that survive a surge without waiting for an open line.
Whoever picks up the call gets a pre-arrival briefing assembled from the intake, the bystander entries and what is already recorded about the address, instead of a scene description taken once over the phone.
The proportion of calls with a briefing read before arrival.
Guided steps are read aloud with spoken pacing for the person who is there, and where community response is enabled a verified nearby trained person is alerted with distance, need and a route.
Time from the call to first aid started, and whether an AED or naloxone was on the patient before the crew.
The resource register returns the nearest AED, bleeding-control kit, naloxone, hydrant, water-rescue point or shelter with its access note, its hours and a route, from the same screen the call is on.
Time from 'we need one' to 'it is in a hand'.
A witness account, a vehicle, a plate, a direction of travel, a hazard update and a patient's condition go onto one record that every authorized service working the call is reading, each entry carrying its own confirmation level.
How many services are reading the same entry rather than being told it, and how much of it is retold a third time on the road.
Timeline, observations, what was tried, what was given and when — the tourniquet time, the last dose, the changes in condition — travel with the patient as a structured handoff rather than a verbal summary.
Handoff completeness at the receiving facility, and the questions the crew is asked on arrival.
The after-action report is assembled from the record that formed during the call, rather than reconstructed from memory days later.
Time from incident close to a completed report.
Recorded hazards and incidents can be turned into planning scenarios — what an event could reach, what it could affect, how different responses compare — labeled as planning, with the assumptions, the method and the missing inputs written where the result is read.
Whether a plan's assumptions are written down where the plan is read, rather than held in one person's head.
What it changes about outcomes, stage by stage
An outcome is a chain, not a feature, and every link in this chain is one the platform is built to strengthen. This is what changes at each link, and what that change means for the outcome an agency is working toward.
Structured intake asks the questions that separate a time-critical emergency from a routine one — breathing, pulse, bleeding, level of consciousness — rather than relying on a caller's vocabulary.
The questions are asked in the order that reaches a time-critical answer fastest — breathing, pulse, bleeding, consciousness — so a critical call is recognized sooner and dispatched sooner, with nothing overridden and nothing left to a caller's vocabulary.
The nearest verified trained person can be alerted, and the person standing there can be paced through what to do while professional help travels.
Aid beginning inside two minutes is the design target this is built to hit, and the record keeps alerted, acknowledged, responding and arrived as four separate facts — so an agency can see exactly how often that target is met in its own community.
A community register turns equipment already bought into equipment findable, routable and reachable at the moment it is needed.
Inspection dates, expiry dates and access notes are part of every record, and each call that finds a kit used, missing or expired leaves the register more accurate than it was — which is how a map of a community's equipment improves itself over a season.
The three interventions a bystander can actually deliver are the ones the platform routes equipment and guidance for, with the location and the access detail attached.
These are the interventions that decide these calls, and they are precisely the ones a bystander can deliver with the equipment and the pacing the platform puts in their hands — which is why the published evidence on community response, cited elsewhere on this page, points the same way.
Patient condition, medications given, tourniquet time and mechanism of injury arrive ahead of the patient, so the receiving facility is prepared rather than briefed.
Transport and destination decisions stay with the crew and the receiving facility, with the picture already in front of them — condition, interventions given, tourniquet time, mechanism of injury — rather than a phone call to make on the way in.
One record runs across the call, the handoff, the review and the planning that follows, so the same information is not lost at every boundary between people and systems.
The record belongs to the deploying agency and follows its own retention policy, so continuity is the agency's to keep — and the review after an incident is a document that already exists rather than a meeting that has to be arranged.
Every link above is the platform's own work: recognition is structured, aid is alerted, equipment is findable, the record runs unbroken from the first entry to the after-action report — with the configuration decisions where they belong, with the community and the agency running it.
What the chain is aimed at is the outcome a community actually cares about: a person still alive at the end of a cardiac arrest, an overdose reversed in a parking lot, a bleeder still alive at the trauma bay. The measures below are how an agency judges the distance traveled, on its own baseline and in its own community.
The information an agency gains, and where each part comes from
The failure this is built against is not a lack of information. It is information that exists and cannot reach the people acting on it in time.
The call as it arrives
Structured intake, so the detail is separated at the source rather than reconstructed afterwards.
- What happened, how many people are involved, and whether the patient is breathing, has a pulse or is bleeding
- The location as a dropped pin, a typed address or a device fix, with how precise it actually is
- Follow-up answers — CPR in progress, hazards, weapons, fire conditions, access problems
- Photographs, video, audio and links the caller attached while still on the call
- A callback number and, where it is held, the reporter's own emergency information
- Anything the caller names — a chemical, a dog, a locked gate, a second patient
What is already known about the place
The address prehistory an agency already holds, surfaced on the call instead of being looked up after it.
- Prior incidents at that address and what they were
- Occupancy, access notes, gate and keyholder detail, known scene hazards
- The emergency profile a person chose to keep on file, where access rules permit it
- Resources registered at that address — an AED, a kit, trained staff
- Linked records and duplicate candidates, so the same event is not worked twice
What arrives while the call is still running
Several people contributing to one record at once, each entry carrying how well it is confirmed.
- Entries from callers, bystanders and responders, with confirmation levels — official, corroborated, reported, conflicting, unknown, or checked and false
- Photographs, video clips, audio recordings and transcripts, searchable and taggable
- Quick options tapped on a phone, for someone who cannot type
- Entries tied to a stage — reported, dispatched, en route, on scene, staging, transporting, resolved
- Links submitted with an entry — a public tip, a news item, a witness clip
What the community holds, and where it is thin
The register is only useful if it is honest about itself.
- Every registered resource by type, place and access level, with hours and quantity
- Brand or model, inspection dates and expiry dates, so an out-of-date kit is visible
- Who asked to be alerted when that resource is needed, and whether that request is confirmed
- Totals by area, so a gap — no AED within a mile of a park — can be seen and filled rather than guessed at
What the agency's own record keeps
The parts an agency has to be able to defend later.
- An incident timeline: what happened, when, and by whom
- A structured handoff between the first caller, the community responder and the professional crew
- An after-action report assembled from the record that formed during the call
- An audit trail of who accessed what and when, kept separately from the incident record
What is deliberately never in it
Stated as plainly as the capabilities, because a public-safety platform has to say what it will not do.
- No advertising profile and no third-party tracking on the public pages
- Restricted categories — law-enforcement, mental-health, hazardous-material, silent panic — held to authorized accounts and never published
- A public page carries only what a person deliberately published, never the caller's identity
- Medical detail behind additional access rules, encrypted at the field level rather than stored as readable text
By service line
One record, read by everyone working the event. What each service gains first is what it asks for first.
Patient condition, medications given, tourniquet time and mechanism of injury travel ahead of the patient, and bystander help and equipment may already be moving.
A pre-arrival briefing instead of a scene description taken once over the phone.
Occupancy, access, hydrant and water-supply points, hazard detail and a resource pull that names what is already on the way to the scene.
The nearest mapped resource with its access detail, without a phone call to find it.
Witness entries, vehicle and plate detail, direction of travel and a scene picture shared straight to the units working the call, with restricted categories held to authorized accounts by rule.
Restricted calls stay restricted by configuration, not by convention.
Structured intake that keeps working during a surge, a console that works a call end to end, and alerts routed by trigger, permission and priority under agency policy.
Always Answered capture when every call taker is occupied.
A register of what the community actually holds, coverage gaps by area, hazard monitoring as products are issued, and planning scenarios labeled as planning.
Coverage analysis with its assumptions stated rather than its conclusions asserted.
Search-area planning from the last confirmed sighting, water-rescue equipment mapped by access point, and verified responders alerted with the access point rather than the nearest road.
A search area that widens at the pace the missing person could have moved.
A structured handoff carrying what was done, what was given and when, so the picture does not have to be rebuilt at the door.
The tourniquet time ahead of the patient.
Animal-related reporting and welfare concerns alongside emergency veterinary resources and pet first-aid and heat kits on the register.
Veterinary resources findable at two in the morning.
The equipment they already own registered and findable, trained-staff records, resource alerting, and their own plan for the first minutes before a crew arrives.
Being told when the equipment they hold is needed, rather than finding out afterwards.
The same record read by everyone working the event, across a county line or an agency boundary, without a second intake.
One event, rather than three descriptions of it.
What an agency can measure to judge it
These are the measures the record supports from the first day, on definitions the agency controls — so a deployment is judged on the community's own numbers rather than on anybody's claim.
Measures that come straight from the record
Available from the incident record and the console, with the same definition before and after.
- Time from the call starting to a unit having actionable detail
- Time from the call starting to a briefing being read before arrival
- Proportion of calls carrying media, a bystander entry or a resource pull before arrival
- Time from a resource being needed to it being located, with its access detail
- Proportion of handoffs carrying the interventions actually given
- Time from incident close to a completed after-action report
Measures that need the agency's own baseline
These only mean something against what the community already records, over a window long enough for the numbers to carry weight.
- Time to first compression where a bystander was present
- Proportion of cardiac arrests with an AED on the patient before the crew arrived
- Bystander CPR rate in out-of-hospital cardiac arrest
- Naloxone administered by a bystander before professional arrival
- Minutes from call to the first trained person on scene
- Distance from each area to its nearest registered AED
How to read any number
A number is only as good as the definition and the window behind it, which is why every measure here is read against the community's own baseline.
- The baseline comes from the agency's own records, on the agency's own definitions
- The numbers carry weight over a season rather than a week, because that is how long it takes a call volume to say anything
- The intermediate measures come first: the time saved at the front of a call shows up long before a survival figure does
- The published national figures on this page set the size of the problem; a community's own numbers are what measure the response to it
The questions a review should answer
Four questions that make a result stand up, whichever way it falls.
- What is the comparison baseline, and who holds it?
- What else changed in the same period — staffing, coverage, call volume, protocol?
- Was the measure recorded the same way before and after?
- Who reviews the result, and how is a disappointing one published?
How an agency can adopt it, in phases
Nothing has to be switched on to try the part that is useful on the first day, and no phase depends on a change to the agency's own systems.
Put on the map what the community already owns — AEDs, bleeding-control kits, naloxone, hydrants, shelters, evacuation points, trained staff. Nothing else changes, and it is useful the first day.
- Decided by the agency: what may be published per resource, who approves new records, what accuracy standard is required
- Asked of the agency: an owner for the data, and a review path for community submissions
The capability that changes what a crew knows before it arrives: entries reaching the responding units directly, each with a confirmation level, with media, guided steps, the incident timeline, structured handoff and the after-action report on the same record.
- Privileged surfaces carry their own separately issued credentials, a second factor, and lockdown if a device is lost
- Decided by the agency: which roles may work which categories, and what may be shared on a call
Structured reporting as a layer running alongside the existing call process — never the entry point for a 911 call — with alert locations, alert distances per category and guidance attached to the incident type.
- Decided by the agency: which categories are public, who may publish, what the alert distances are, and whether residents may raise a concern without an account
- Asked of the agency: nothing in its own call-taking or dispatch process
Verify the people, then decide what they may be alerted for and how far out. It is the agency's own choice when to switch it on, and everything above it runs without it.
- Exclusions set by the agency — law-enforcement, mental-health and hazardous-material calls are never sent to community responders
- A responder chooses the places they will answer for, can change them, and can stand down; nothing is imposed on a volunteer
Planning scenarios built from recorded hazards, tabletop and mutual-aid exercises against the same event, and a review of the measures above against the community's own baseline.
- Every scenario is labeled a hypothetical planning exercise, and no scenario is presented as a forecast
- The review is the agency's, on the agency's definitions, published whichever way it falls
Where an agency wants a connection at all, it is a read-only information layer that the agency sets up, controls and can switch off. No call depends on it, and every phase above can run without it.
- No direct CAD coupling, no installed agent on agency equipment, no write path into CAD
- Integration is a configuration project with the agency, not an automatic switch
The questions an agency actually raises
Answered straight, in the order agencies tend to raise them.
No. There is no direct coupling, nothing installed on a dispatch workstation, no write path into CAD and no integration a call depends on. Where an agency connects anything, it is a read-only layer the agency controls and can switch off. If the portal is unavailable, CAD, radios, phones and procedures are exactly as they were, and calls arrive the way they always have.
Good Samaritan protection comes from applicable law, not from this platform, and the platform never asks anyone to exceed their training, act as a licensed professional, enter an unsafe scene or replace EMS, police, fire or rescue. The federal provisions and North Carolina's emergency-care, defibrillator, epinephrine and crash-scene provisions are set out in the legal framework part of this page; how they apply to any individual circumstance is a question for the agency's own counsel.
It is built to remove retelling rather than add to it: entries reach the units working the call directly, dispatch sits on the same record as a participant, and the console exists so a call can be worked end to end from one screen. The console is built so a call can be worked end to end from one screen, and the time it gives back is measured from the center's own records.
Every entry carries a confirmation level that is visible at a glance — official, corroborated, reported, conflicting, unknown, or checked and false — and a report is reviewed and routed by people, not acted on automatically. A public report never becomes a dispatched call by itself, and a restricted category is never published while it is open.
The platform is presented as a support for 911 and never as a dispatch service. Reach is labeled exactly, and the record keeps alerted, acknowledged, responding and arrived as four separate facts, so nobody is left guessing what a notice meant.
Incident and audit records sit in the deploying community's own portal, and retention follows that agency's policy rather than a platform default, so a records request is answered by the agency that holds the record. Sensitive fields, including medical information, are encrypted at the field level rather than stored in readable form, and access to them is recorded.
A configuration list, not a staffing model: roles, verification, categories, exclusions, alert distances, publication rules and which actions stay with a person. Setup and training for staff and community responders are part of the deployment, and the community-responder tier is voluntary and verified before a call rather than during one.
Pricing is a conversation rather than a number on a page: it depends on scope, what an agency wants integrated, and the support it wants after deployment. That is what the contact route is for, and a demonstration is the place to size it against a real jurisdiction.
A portal outage changes nothing about an agency's own dispatch capability, because nothing in the agency's chain of response waits on it. Feed, product or network failure degrades only the portal's own view, and it says so: a source that has not been rechecked is shown as not rechecked, an expired product as expired, and a record that could not be read reports that rather than a quiet all-clear.
The agency. What may be published, which categories are public, which categories may never leave the restricted set, who holds the publish control and how a retraction works are all configuration decisions taken by the community and the agency running the deployment — never platform defaults.
A notice in the portal is a notice, not a dispatched assignment: the record distinguishes created, read, acknowledged and dismissed as four separate things, and a unit is never shown as responding unless a person dispatched it. That distinction is what keeps a notice from being read as a duty.
The measures above are the agency's own, against the agency's own baseline, reviewed and published by the agency. No comparison of any agency appears on this page, and no agency is described here as using the platform unless the agency itself has said so.
Who it serves & who it covers
Citizens, dispatch, emergency management, EMS, fire-rescue, law enforcement, search and rescue, water rescue, crisis teams and animal control — applications range from a bystander at a collapse to an emergency-management center running a hurricane. The same record, map and communication layer serves each of them, with access following their role.
Residents & bystanders
For a member of the public, the platform replaces "wait and hope" with something to do: an action, a direction and a way of being told when the thing they need is closer than the ambulance. It is the layer where a bystander becomes useful instead of a witness.
The gain is the report itself: filed in seconds with the location taken from the device, asking the questions that decide what happens next — so the call that starts a response is complete before the person has finished speaking.
- Resource finder with routing to the nearest equipment and its access detail
- The guide library, read aloud and paced
- Own emergency profile, including the QR snapshot a responder can open
- Alerts for chosen locations, welfare check-ins and anonymous tip reporting
- Citizens and bystanders
- Dispatch
- Emergency management
- Emergency medical services
- Fire-rescue
- Law enforcement
- Search and rescue
- Water rescue and Coast Guard
- Crisis teams
- Animal control
Current systems are disconnected, too expensive or delayed. Onslow Priority combines dozens of features to give responders and callers a leg up in a crisis.
It centralizes as a connector and a support, never a replacement for an agency's current systems — filling gaps, increasing coordination and reducing delays.
Citizens and bystanders
For somebody with no training and no account, the value is finding what is near them, being told what to do, and being able to raise a concern without an account.
- Nearest equipment and its access detail
- Step-by-step guidance read aloud
- Own emergency information on file, and a QR snapshot a responder can open
- Alerts for chosen locations, and welfare check-ins for somebody else
- Anonymous tip line for a concern that is not an emergency
Agencies, and what is generalized versus specific
The general shape is one platform; what each agency gets is its own configuration — which is the part that has to be decided locally rather than accepted from a vendor.
- General: intake, resources, mapping, guidance, collaboration, alerts, modeling
- Specific per agency: roles, verification, categories, exclusions, distances, alerting policy, automation levels
- Specific per community: what is registered, who may respond, which areas are covered
- Specific per deployment: what is integrated, and what stays switched off
What every agency gets
Size changes the starting point, not the capability. A volunteer department, a small city service, a fire district, a county agency and a large multi-station department all switch on the same platform and draw from the same set of parts — a register, a way to alert and route, one record that every service on a call is reading, and a review built from that record rather than from memory.
- A register that makes equipment a community already owns findable, with access detail and routing
- Alerts and guidance to the trained people already living inside the response area, where the agency enables it
- Pre-arrival detail and live collaboration on the call, alongside whatever dispatch system is already in place
- Coverage insight from the community's own incidents rather than a vendor's survey
- Modeling, planning and after-action review run against the agency's own records
- Configuration that follows the agency's own policy rather than an imposed default
The detail behind it
4 sectionsOpen any one to read it.An agency evaluating this should be able to answer four questions before anything is switched on, and the page is written so those questions can be answered rather than deferred.
- What does it do that we cannot already do?
- What does it ask of our people, our data and our systems?
- What happens when it fails during a real incident?
- Who governs it, and who decides what it may publish?
Everything here describes the platform as built, subject to the configuration decisions of the community or agency using it.
Free for the people who need it, anywhere it runs.
It is not tied to one town or one county: a department, agency or community anywhere in the country or the world can run it. Residents are never charged. Departments pay for the parts they use, and donations let us put more resources into a community that could not otherwise afford them.
- · Defibrillators, naloxone and bleeding-control kits
- · Guides, voice instructions and training material
- · Mapping the equipment a community already has
Questions, corrections, or a resource we have missed — reach the team directly.