Skip to main content

​
From call to incident

A call is a report from the public. An incident is what Control decides to do about it. ATTACHED and RESOLVED are final. A call cannot be detached or moved to another incident. Converting a call creates the incident with the call’s location and description, and the priority and type Control chooses. An incident can also be created directly, with no call.

​
An open incident

An incident has two states, OPEN and CLOSED. While it is open:
  • It can be edited. An edit replaces priority, type, location, description and control notes together.
  • Units can be assigned and released. Several units can attend; each unit attends one incident at a time.
  • More calls can be attached.

​
Units on an incident

Only Control moves a unit onto or off an incident. In between, the crew or Control can move it among the assigned statuses. Closing the incident releases every unit at once.

​
Closing

POST /api/cad/incidents/{id}/close does three things in one transaction:
  1. Releases every assigned unit to AVAILABLE, or OFF_DUTY if it has no crew.
  2. Marks the incident CLOSED and stamps closedAt.
  3. Records one UNIT_REMOVED event per unit and an INCIDENT_CLOSED event.
Attached calls stay attached. A closed incident cannot be edited, and nothing can be assigned or attached to it.
A closed incident’s units list is empty, because those units have been released. To see who attended, read the incident’s events.
Closing records no outcome or reason. That is a known gap.

​
Reopening

POST /api/cad/incidents/{id}/reopen sets the incident back to OPEN and clears closedAt. It does not bring back the units that were released; Control assigns again.

​
The event trail

Each step leaves an event, readable with GET /api/cad/events?incidentId=..., oldest first. Each event carries detail with the before and after values, and actor: the display name of the user, the name of the service credential, or System.