Incidents and command structure
Set up an incident and define its work. Connect duty stations to staffing needs and the people assigned.
Create and review an incident
Before people are assigned, an incident needs a shared record of the work to be done. An incident has its own ID and dates. Coordinators add duty stations and define the work. The setup follows a review process before it is used.
A saved incident template can supply a starting structure. Its version stays with the draft. Creating the draft does not deploy people.
Units, duties, and supervision
Responders need to know where they fit and who supervises their work. Units and duty assignments describe who does what at the incident. Assignments have start and end dates. A supervisor can change without losing the earlier relationship.
Incident organization reports show the structure at a chosen time. Deployment reviews use the dates during which a supervisor was responsible.
Staffing needs and team requests
A coordinator first needs to describe the help the incident requires. A staffing need defines the position to fill. It includes the required dates and number of people. Specialties can narrow the requirement.
Team templates define positions and leaders for a group. They can represent force packages or force modules. Accepted members stay linked to the template version used.
Resources and shared operational work
An incident may need people and supplies from several teams. Resource requests ask for personnel, equipment, or supplies. A request can be routine or urgent. Its decisions stay in history.
A shared conversation lets staff discuss the incident in context. Sharing a thread does not grant access to records the reader cannot otherwise open.
Keep the history when work changes
Incident plans change as the response develops. Staff still need to understand what happened earlier. Changing incident dates or withdrawing a need leaves a record. The history shows who acted and when.
Ending the incident must account for its open work. Deployment orders and equipment holds remain separate records. A closed screen is not proof that those obligations are complete.