📄️ Overview
Incident Back Office runs the side of a large incident that dispatch and incident command do not: who is on the incident and where they sleep, what has been ordered and when it arrives, what everything costs and who pays for it, and what partner agencies need to see. It is built around the Incident Command System sections — Command, Planning, Logistics and Finance/Administration — and works alongside the Incident Command board and dispatch calls without changing them.
📄️ Getting started
This page walks an administrator through setting up Incident Back Office for a department, and then through running a first incident from activation to the first desk check. Each step links to the page that covers it in depth.
📄️ Activation and command
An activation says "this department is running the back office for this incident". Everything else in the module hangs off it.
📄️ Planning and organization
Operational periods and the plan
📄️ Logistics
The Logistics desk opens on the section's numbers — open, critical and overdue requests, fills en route, people needing lodging, beds held and free tonight, open service tickets — and the arrivals expected in the next 2, 6, 12 and 24 hours.
📄️ Finance
The finance desks need the Incident finance desks module switch (on by default). The Finance desk shows committed spend and open commitments, yesterday's cost and the cost to date, time waiting to be certified or approved, invoice exceptions, and each budget line against its committed spend. A line past its threshold is highlighted.
📄️ Coordination
Coordination needs the Coordination boards module switch (on by default) and the View coordination boards permission.
📄️ Settings
Incident Back Office → Department setup → Settings (department administrators) holds the module's department policies. Each policy is saved on its own; empty values use the defaults below. Every number is yours to set — nothing in the module hard-codes a threshold.