How an incident moves from draft to closed, how to hand it to another officer, and how a non-author's edit is staged for the author's approval.
Loading…
Every incident carries a status, and that status only ever moves forward: no report slides back into an earlier state by accident, and no stray edit overwrites a report someone already signed off on.
A real incident (not a training drill) moves through up to seven states, in order: Draft → Report Finalized → Handed Off → In Reconstruction → Ready for Review → Under Review → Closed.
Most incidents never need the middle states. If the officer who ran the call also writes it up, the record goes from Draft to Report Finalized and then closes directly with Close incident (below); the handoff and review states exist for the case where someone else does the reconstruction. A training drill takes a shorter path: Draft → Finalized → Under Review → Closed.
If the officer who ran the call is not the one who will write the final report, use Hand Off from a finalized incident. Pick a recipient from the department roster and an optional note; the incident moves to Handed Off. The recipient sees Accept Handoff; accepting moves it to In Reconstruction, where only they (or an admin) can finish it. Finishing moves it to Ready for Review and notifies the original author that the reconstruction is ready.
The notification bell shows each step — "Incident handed off to you" for the recipient, "Handoff accepted" and later "Reconstruction ready for review" for the author — and clicking one opens the incident directly.
From Report Finalized through Ready for Review, a secondary Close incident button is available to the author, the current owner, or an admin. It skips whatever review steps remain — a shortcut for when the rest of the pipeline doesn't apply. The normal Under Review → Closed step still completes review the usual way, and closing does not lock the incident: it stays open, editable, and exportable.
Closed is the one state with a way back. The author, or an admin, can reopen a closed incident, returning it to an editable rework state and notifying the current owner — a separate, gated action, not a routine pipeline step, and not available to anyone else.
Once a report is finalized, only the author (or an admin) can edit it directly. Anyone else who edits the same incident sees a notice that the edit will be staged instead of applied. The author is notified ("Change request submitted"), opens the request, and sees a changed-fields-only comparison of what's proposed against what's there now — then Approve Changes, which applies the edit, or Revert Changes, which discards it. The proposer is notified either way.
If the record moved underneath the request while it was waiting, approval is refused rather than silently applied over the newer version, and the reviewer is pointed at the current values instead.
Draft incidents never appear in trend analytics — a report only counts once it has left Draft.