Incident Lifecycle

ImpactGrid incidents move through five states: Draft, Active, Paused, Closed, and Archived.

Typical lifecycle

1. Create the incident as a draft and enter command information.
2. Prepare maps, preplans, teams, and assignments.
3. Activate the incident when operations begin.
4. Pause it if work is temporarily suspended, then resume when appropriate.
5. Close it when operational work is complete.
6. Archive it when it no longer needs to appear in normal working lists.

Incident templates can capture reusable setup—including outdoor zones, markers, GIS layers, teams, and an associated preplan—to speed up recurring operations.

Caution

Lifecycle effects and recovery procedures are pending hands-on verification. Follow your incident command policy before changing the status of an active operation.