Workflow step 5: Document & close · Incident workspace

Name an incident and track PACE, ICS forms, checklists, and scratch pad data — export one close-out packet. Works offline after your first visit.

← Emcomm workflow · All tools

Incident Workspace

The incident workspace is a local packet of ICS forms for one named event. It shows which worksheets already have data on this device and exports a single text bundle for debrief.

New period wizard

Open each tool below to fill forms — this page reads saved data from your browser automatically.

How the workspace fits the workflow

Name the incident the same way on every form (ICS-201 briefing, 202 objectives, 205 radio plan, 213 messages, 214 log, 217 resources, 221 demob). This page is the table of contents. Nothing is uploaded; clearing site data deletes the packet, so export before you wipe the browser.

Walk the five-step deployment workflow, then close out with demob. County-agnostic: East Tennessee nets are the worked example, not a requirement.

See also: ICS forms offline

Common questions

What is the incident workspace?

A dashboard that reads saved PACE, ICS, and checklist data from your browser and exports one close-out packet.

Can two operators share one workspace?

Each browser has its own storage. Export the packet and import or paste on the second device; there is no cloud sync.