If you're studying for the FEMA IS-700, IS-800, or ICS-100 exams — or you're a practicing emergency manager reviewing NIMS doctrine — the answer is straightforward: the resource management task that enables resource coordination throughout the incident is Track and Report. But knowing the answer is different from understanding why it works that way, and the distinction matters when you're actually running an incident.
This article breaks down what Track and Report does, how it fits into the six NIMS resource management tasks, and what happens operationally when it's done poorly.
The Six Resource Management Tasks and Where Coordination Lives
NIMS defines resource management as a set of six sequential tasks. All six contribute to an effective response, but only one spans the entire lifecycle of an incident from activation to demobilization:
- Identify Requirements — determining what resources are needed based on incident objectives
- Order and Acquire — requesting resources through proper channels (mutual aid, EMAC, federal)
- Mobilize — preparing resources and moving them toward the incident
- Track and Report — maintaining continuous visibility of resource status and location throughout the incident
- Demobilize — releasing resources in a planned, orderly sequence
- Reimburse and Restock — financial recovery and restoring resource inventories
Tasks 1–3 happen before resources arrive at the scene. Tasks 5–6 happen after the incident closes. Task 4 — Track and Report — is the only one that runs continuously from first assignment through final release. That's what makes it the resource management task that enables resource coordination throughout the incident.
What Track and Report Actually Does
Resource coordination breaks down when commanders don't know where their assets are, what condition they're in, or whether they're still available. Track and Report solves this through three mechanisms:
Resource Status Tracking
Every resource in a NIMS-compliant response has a status: Assigned, Available, or Out of Service. These statuses are updated in real time — or as close to real time as the situation allows — through the Incident Command Post, EOC, or coordination center. Without continuous status updates, a logistics section chief might request a resource that's already deployed elsewhere, creating gaps and duplication simultaneously.
Location Tracking
Knowing a resource is "Assigned" isn't enough. Commanders need to know where it's assigned. In large-area incidents — wildfires, hurricanes, multi-jurisdictional responses — resources can be spread across dozens of operational branches. Geographic tracking, whether via GPS, ICS Forms (particularly ICS-204), or WebEOC, gives the Incident Commander actual situational awareness rather than a list of names on a roster.
Reporting to the EOC and Coordination Layer
Track and Report doesn't just feed information up from field to ICP — it also bridges the ICP to the EOC and, where applicable, to state and federal coordination bodies. Resource reports generated during this task (status boards, T-cards, digital dashboards) are what allow mutual aid coordinators to see whether additional resources need to be requested or whether surplus resources can be released early.
Why This Task Enables Coordination Specifically
The key word in the exam question and in NIMS doctrine is "enables." Track and Report doesn't just support coordination — it makes coordination structurally possible.
Consider what coordination requires: two or more entities sharing situational awareness about the same set of resources and making decisions that don't conflict. Without a shared, continuously updated picture of resource status and location, you're not coordinating — you're guessing and hoping the other person guessed the same thing.
This is why major incident failures are often traced back to Track and Report breakdowns, not resource shortages. Post-incident reviews from Hurricane Katrina, the 2003 Cedar Fire, and numerous active shooter responses have documented cases where resources were available but couldn't be utilized because no one knew they were there.
The ICS Structure Dependency
Track and Report is executed primarily by the Logistics Section, specifically the Resources Unit within the Planning Section (under the Resources Unit Leader). The Situation Unit compiles ongoing status reports. The combination feeds the Incident Action Plan cycle — and the IAP drives every operational period's assignments. If Track and Report is weak, the IAP is built on stale data, which cascades into every tactical decision made by Operations.
Mutual Aid and Interstate Coordination
When incidents escalate to require mutual aid — either intrastate through local agreements or interstate through EMAC — the Track and Report function becomes the handshake between responding jurisdictions. A state emergency management agency receiving resources from three neighboring states needs standardized, real-time reporting to avoid assigning the same resource twice or releasing a critical asset too early. NIMS typing standards exist partly to make Track and Report interoperable across jurisdictions that may never have worked together before.
Common Failures in Resource Tracking
Understanding what goes wrong in practice helps clarify why NIMS emphasizes this task so heavily.
- Manual T-card systems that lag by hours: In fast-moving incidents, a T-card system updated every operational period (12 hours) means commanders are working with a picture that's already obsolete. Digital systems help, but require training and pre-incident agreement on tools.
- Status not updated on demobilization: A resource is released from an assignment but remains listed as "Assigned" on the status board. The next Operations Section Chief sees a false picture of available capacity.
- Out-of-service resources not reported up: Equipment that breaks down in the field sometimes doesn't get reported as Out of Service promptly, because field personnel don't want to report a problem. This leaves a gap in the resource picture at the command level.
- No single authoritative tracking system: Multiple agencies arrive with their own tracking tools and don't integrate them. The ICP ends up with four different resource lists that don't match each other.
Top Courses for Resource Management and Incident Coordination
If you're looking to build formal credentials in resource management — either for emergency management, HR, or organizational operations — these courses are worth considering:
Preparing to Manage Human Resources (Coursera)
Rated 9.6/10, this course covers the strategic side of resource planning and allocation — useful groundwork for anyone who needs to understand how resource requirements are identified and managed before an incident occurs.
AI-Powered HR: Master the Tools Transforming Human Resources (Udemy)
Rated 9.5/10, this course focuses on modern tooling for tracking and reporting on human resources — directly applicable to the technology layer of resource coordination in complex operations.
Certificate in Human Resources Management (Udemy)
Rated 8.6/10, this structured certificate program covers resource classification, credentialing, and deployment workflows — foundational concepts that map closely to how NIMS types and tracks resources in a response.
AI for Human Resources (Coursera)
Rated 8.5/10, this course addresses how AI tools are changing resource status monitoring and predictive allocation — increasingly relevant as EOCs move toward automated resource dashboards.
FAQ
Which resource management task enables resource coordination throughout the incident?
Track and Report. This is the NIMS resource management task that runs continuously from resource activation through demobilization, maintaining real-time visibility of resource status, location, and availability. It's the only task that spans the entire incident lifecycle rather than occurring at a specific phase.
What are the six NIMS resource management tasks in order?
The six tasks are: (1) Identify Requirements, (2) Order and Acquire, (3) Mobilize, (4) Track and Report, (5) Demobilize, and (6) Reimburse and Restock. Track and Report is the fourth task but the only one that continues across all operational periods.
What is the difference between resource tracking and resource coordination?
Resource tracking is the process of maintaining current status and location data for all assigned resources. Resource coordination is the broader function of ensuring resources are allocated effectively across multiple operational branches or jurisdictions. Tracking enables coordination — you can't coordinate what you can't see.
Who is responsible for Track and Report during an incident?
In an ICS structure, primary responsibility falls on the Resources Unit Leader within the Planning Section. The Logistics Section supports by managing the physical movement of resources. The Situation Unit compiles status reports into the Incident Action Plan. In an EOC context, the responsibility typically sits with the Resource Coordination function or desk.
What tools are used for resource tracking in NIMS?
Common tools include ICS T-cards (manual), WebEOC (digital), and ROSS (Resource Ordering and Status System) at the federal level for wildland fire. Many jurisdictions also use Veoci, Frontline, or custom GIS dashboards. The tool matters less than ensuring all responding agencies use the same system and update it consistently.
Is this topic covered on the FEMA IS-700 exam?
Yes. The FEMA IS-700.b (NIMS: An Introduction) exam directly tests knowledge of the six resource management tasks and asks which task enables coordination throughout the incident. The correct answer is Track and Report. The IS-800.d (NRF) exam also covers this in the context of ESF coordination and federal resource management.
Bottom Line
The resource management task that enables resource coordination throughout the incident is Track and Report — not because it's the most complex task, but because coordination is structurally impossible without continuous, shared visibility of resource status and location.
For exam purposes, that's the answer. For practitioners, the more important point is that Track and Report failures are almost always procedural rather than technological. Agencies that do this well have trained their personnel on status update discipline, integrated their tracking systems before incidents occur, and established clear reporting timelines that feed into each IAP cycle.
If you're building expertise in resource management — whether in emergency management, operations, or organizational HR — the courses above offer structured frameworks for thinking about resource allocation, classification, and real-time tracking that transfer across contexts.