Coming Soon
Incident Back Office
Large-incident logistics, planning and finance/administration. Give the EOC, ICP and support organization one place to coordinate people, resources, facilities, vendors, procurement and incident cost while field operations continue in Resgrid.
Coming Soon
Paid add-on when launched
Coming soon. This capability is not available yet.
Incident Back Office will be offered as a paid add-on when launched. The complete module is coming soon and is not available today.
What this capability will deliver
Designed around the real operational work already managed in Resgrid.
Operational periods and organization
Build an ICS-aligned organization, assign internal and external participants, manage operational periods and preserve approved plans and activity records.
Resource and support logistics
Coordinate requests, fills, check-in, movement, staging, demobilization, supply, ground support and communications with projected needs and accountable status.
Facilities and human support
Manage camps, lodging, feeding, water, sanitation, transport and vendor capacity across operational periods and concurrent incidents.
Procurement, time and incident finance
Track agreements, requisitions, purchase orders, receiving, invoices, budgets, time, equipment cost, claims, reimbursement and closeout evidence.
How work will move through Resgrid
From the first operational fact to a complete, auditable outcome.
Establish the period and support organization
Create the operational period, objectives, deadlines, ICS-aligned positions, facilities, cost codes, and controlled workspaces. Assign internal personnel, external partners, trainees, and ad hoc participants without adding every visitor to the department roster.
Turn needs into accountable resource work
Capture a need, request, order, or support task; route it to the responsible position; project when it is required; record sourcing and commitment; and preserve status through arrival, check-in, assignment, movement, and release.
Coordinate the systems that keep people operating
Manage camps, lodging, feeding, water, sanitation, medical support, transportation, fuel, communications, supply, caches, receiving, vendor capacity, and concurrent-incident commitments from role-specific queues.
Capture procurement, time, cost, and claims
Connect agreements, requisitions, purchase orders, receipts, invoices, personnel time, equipment use, expenses, injuries, claims, cost share, budget, and forecast facts to the incident and period that created them.
Publish the incident action plan and leave a defensible closeout
Assemble IAP content from authoritative sources, publish approved period packages, track documentation, transfer unresolved commitments, demobilize resources, reconcile cost, and retain the RMS-backed incident record.
Technical and operational depth
Designed around lifecycle, authority, evidence and failure modes—not only screens.
ICS-aligned planning without a second responder roster
Incident Back Office creates the temporary organization required by a major incident while reusing Personnel, Units, Calls, command assignments, and mutual-aid sources. Position workspaces show the queues, alerts, deadlines, and decisions relevant to Planning, Logistics, and Finance/Administration.
- Operational periods, objectives, planning cycle, meetings, deadlines, approvals, publication, and transition
- ICS positions, reporting lines, vacancies, deputies, assistants, trainees, task books, and external participants
- Reusable teams and mission packages with projected staffing, equipment, transport, lodging, and support
- Role-routed notifications and workflows based on incident position rather than department-wide access
- IAP forms and daily summaries compose owning-module data and preserve approved RMS snapshots
Resource and support logistics through demobilization
The feature distinguishes a need, request, order, resource, assignment, and support task so a whiteboard status cannot silently become an order. Each transition records authority, responsible position, timing, quantity, location, source, and downstream commitments.
- Need intake, priority, sourcing, fill, substitution, approval, ordering, cancellation, and exceptions
- Check-in, qualification, inspection, staging, assignment, movement, release, checkout, and demobilization
- Supply, property, receiving, fleet, fuel, travel, lodging, feeding, water, and sanitation queues
- Inbound arrival callouts tell sections what is coming; projections show what future periods require
- Bounded offline capture and conflict-aware synchronization for approved mobile workflows
Incident finance connected to operational commitments
Finance does not begin after demobilization. Agreements, vendor capacity, orders, receiving, time, equipment use, expenses, claims, budget, forecast, reimbursement, and cost share link as the incident creates commitments, with protected data applied where required.
- Vendor catalog, engagement, requisition, purchase order, receiving, invoice, dispute, approval, and payment plan
- Personnel time, equipment time, mileage, fuel, expense, injury, claim, compensation, and exceptions
- Budget, encumbrance, actual, accrual, forecast, burn rate, cost code, funding, and reimbursement views
- Host-incident and responding-agency facts join through resource-order and deployment contracts
- Closeout verifies open orders, missing time, unmatched receipts, claims, retained evidence, and ownership
One connected operating picture instead of another data silo
Other options
EOC platforms, spreadsheets, whiteboards and incident-business tools often divide planning, logistics and finance from the live responder roster, unit status, inventory and incident record. Each section maintains its own version of the incident.
The Resgrid approach
Incident Back Office will share the Resgrid department, Calls, Units, Personnel, command assignments and source records while giving Logistics and Finance/Administration their own controlled workflows and permissions.
What this can replace or consolidate
Reduce separate systems without hiding where specialist tools still belong.
Section-specific incident spreadsheets
Replace separate Planning, Logistics, Facilities, Supply, Ground Support, and Finance workbooks with controlled shared facts and role-specific views.
Resource whiteboards and status boards
Keep the rapid picture while adding authority, history, projected need, ownership, timestamps, and source records behind each status.
Document logs and IAP file shares
Compose period packages from authoritative data, preserve approvals and versions in RMS, and track documents through closeout.
Disconnected purchase and cost workbooks
Link commitments, receiving, invoices, time, equipment, claims, reimbursement, cost share, and closeout to the operational activity.
Built into the Resgrid system
The module will connect with Dispatch/CAD, IC, RMS forms and evidence, Contacts and vendors, Inventory, Checklists and Work Orders, deployments, Workforce costing, Maps, Workflows and department reporting.
Dispatch / CAD
Incident Command
Records / RMS
Personnel & Units
Inventory
Readiness
Deployments & Costing
Maps & Workflows
Important scope and system boundaries
Clear limits prevent another vague all-in-one promise.
Back-office coordination does not replace field command
Dispatch and Incident Command continue to own live Calls, Unit status, tactical command, and field assignments. This module owns planning, support, logistics, business, and closeout workflows.
Incident finance is not general accounting
It tracks incident commitments, costs, reimbursement evidence, forecasts, and closeout; it does not replace a general ledger, accounts payable, payroll, bank reconciliation, or agency financial controls.
External authority systems need explicit contracts
MARS, state systems, financial systems, and partner EOC tools require reviewed interfaces. Where none exists, Resgrid uses export or manual handoff and records observed external state.
Less duplicate work, more time and budget back
One connected back office will reduce repeated check-in, resource and cost entry; expose shortages and commitments sooner; accelerate operational-period planning; and leave a defensible closeout package without rebuilding the incident from section spreadsheets.