NIMS/ICS common mistakes
NIMS/ICS · Understand the traps and how to avoid them.
Choosing 'Command' as the answer whenever a question asks which ICS functional area handles a task, even when the task is really about resource ordering, tactical operations, or logistics support.
Candidates treat 'Command' as a catch-all because it is the most visible part of ICS. In practice, Command sets objectives and priorities but does not personally perform operations, planning, logistics, or finance/administration work; those belong to the General Staff sections.
What to do instead
Memorize the five functional areas by their core output: Command sets objectives and approves the Incident Action Plan; Operations does the tactical work; Planning tracks situation status and produces the IAP; Logistics provides resources and support; Finance/Administration tracks costs and compensation. For each practice question, name the output being requested before selecting a section.
Confusing the Command Staff (Safety Officer, Public Information Officer, Liaison Officer) with General Staff section chiefs, and assigning them command authority over Operations.
The titles sound senior, so candidates assume they command resources. In fact, Command Staff advise and support the Incident Commander and have no operational authority; only the IC and the Operations Section Chief direct tactical resources.
What to do instead
Use the 'advisory, not authoritative' test: Safety, PIO, and Liaison advise the IC. Remember the Safety Officer can halt unsafe actions through the IC's authority, not by bypassing the chain. Drill the three Command Staff roles against the four General Staff roles until the boundary is automatic.
Selecting 'Unity of Command' or 'Chain of Command' when the scenario actually describes 'Unity of Command' violations versus 'Span of Control' problems, or vice versa.
The NIMS management characteristics have overlapping everyday meanings. Unity of Command means each person reports to one supervisor; Span of Control concerns how many subordinates one supervisor can effectively manage (commonly cited as 3 to 7, with 5 as a working target). Candidates read 'too many people reporting to one chief' and wrongly pick Unity of Command.
What to do instead
Build a one-line definition and a distinct trigger phrase for each characteristic. If the stem involves a person receiving orders from two supervisors, it is Unity of Command. If it involves one supervisor with an unmanageable number of reports, it is Span of Control. Write the trigger phrase next to each characteristic in your notes.
Treating the Incident Commander as always the highest-ranking or first-arriving official, and assuming command automatically transfers to a senior officer.
Candidates import hierarchical assumptions from routine rank structures. Under ICS, command transfers only through a deliberate, documented process, and the initial IC may be a junior officer or single resource until a formal transfer occurs.
What to do instead
Learn the transfer-of-command steps: the incoming IC is briefed, assumes command, and notifies all affected parties; a transfer briefing and notification are required. The outgoing IC remains accountable until the transfer is complete. Answer questions by asking whether a formal transfer has occurred, not who holds rank.
Mixing up the Planning Section's situation unit and resources unit outputs, or stating that Operations writes the Incident Action Plan.
The IAP is a Planning Section product, but Operations executes it and Logistics supplies it, so candidates blur authorship. The Resources Unit maintains resource status and check-in; the Situation Unit maintains situation displays and forecasts.
What to do instead
Anchor each unit to its product: Resources Unit equals check-in and status tracking; Situation Unit equals maps, displays, and forecasts; Documentation Unit equals the incident file; Demobilization Unit equals the release plan. Remember the Planning Section Chief assembles the IAP from unit inputs and presents it at the planning meeting.
Describing the Operations Section as one undifferentiated block and failing to recognize Branches, Divisions, Groups, and Strike Teams or Task Forces when the scenario calls for them.
Candidates learn the section names but skip the internal organization, so they cannot map a scenario's geographic or functional split to the right structure. Divisions are geographic; Groups are functional; Branches sit above them when span of control requires it.
What to do instead
Learn the Operations building blocks as a hierarchy: Strike Team is same type and kind with a leader; Task Force is mixed resources with a leader; Division is geographic; Group is functional; Branch groups Divisions or Groups. Practice labeling a scenario by asking 'geographic or functional?' and 'does span of control require a Branch?'
Assigning cost tracking, compensation claims, and time recording to Logistics instead of Finance/Administration.
Both sections deal with 'resources,' so candidates conflate them. Logistics covers ordering, receiving, supporting, and demobilizing resources; Finance/Administration covers time, cost, compensation, and claims.
What to do instead
Use the 'people versus money' split: Logistics gets people and equipment where they are needed; Finance/Administration tracks what it costs and pays for injuries or damage. Memorize the Finance/Administration units: Time, Procurement, Compensation/Claims, and Cost.
Answering that NIMS management characteristics apply only to large incidents or only to fire service incidents, and claiming ICS is optional for some disciplines.
Candidates generalize from wildland fire history and assume ICS is a fire-specific or large-event tool. NIMS is a national framework intended for all hazards and all disciplines, and the management characteristics apply at every incident size.
What to do instead
Remember that ICS scales from a single resource to a complex incident and applies to public works, public health, law enforcement, and private-sector responders. When a stem asks whether a characteristic applies, the default is yes across sizes and disciplines unless the stem describes a specific exception.
Confusing 'Manageable Span of Control' with 'Modular Organization' or 'Comprehensive Resource Management' when the scenario describes scaling the organization up or down.
Both characteristics concern organization size, so candidates pick the wrong label. Modular Organization means the structure expands and contracts to match the incident; Comprehensive Resource Management means categorizing, ordering, tracking, and demobilizing resources.
What to do instead
Use the 'structure versus stuff' test: Modular Organization is about the shape of the org chart changing; Comprehensive Resource Management is about the resources themselves being typed, ordered, tracked, and released. Read the stem for words like 'expand,' 'contract,' or 'activate' for Modular, and 'type,' 'order,' 'track,' or 'demobilize' for Resource Management.
Treating the Liaison Officer as the public spokesperson or the Safety Officer as the person who approves the Incident Action Plan.
The Public Information Officer handles public and media information, while the Liaison Officer coordinates with assisting and cooperating agencies. The Safety Officer monitors safety and has emergency authority to stop unsafe acts; the IC approves the IAP.
What to do instead
Attach one audience to each Command Staff role: PIO talks to the public and media; Liaison talks to other agencies; Safety talks to the IC about responder safety. For IAP approval, always answer Incident Commander. Practice with stems that name an audience and ask which role is responsible.