Treat each FEMA Independent Study course as a lesson in layered response structure: learn what belongs to on-scene incident command, what belongs to off-scene support, and what belongs to nationwide doctrine, then test yourself with scenarios before sitting a final exam.
What the Independent Study Program actually provides and how to set it up
The Independent Study Program is NDEMU's self-paced online catalog for people with emergency management responsibilities and the general public, delivering completion certificates, IACET-standard CEUs, and transcripts through the NDEMU Student Portal.
The catalog spans broad foundations through specialized security topics: the program page highlights Critical Infrastructure Security and Resilience training for the critical infrastructure community and Active Shooter, Targeted Violence, and Mass Casualty Events training covering prevention and response. A Professional Development Series bundles a set of courses into a recognized sequence, which matters if your goal is a documented progression rather than isolated certificates.
Before studying content, set up the administrative scaffolding so nothing is lost later: register for a FEMA SID, keep your course records consistent with that ID, and learn where the NDEMU Student Portal lets you download completion certificates or request copies of your IS transcript. CEU values are listed per course in the catalog according to IACET standards, so note them if you track continuing education. For administrative specifics such as enrollment steps, use the issuer's own pages; this guide focuses on the learning content itself.
Why ICS and NIMS vocabulary gets tangled: the layer problem
ICS is the on-scene management system; NIMS is the nationwide doctrine that contains ICS alongside EOCs, multiagency coordination groups, and joint information systems. Study items reward placing each term in its correct layer.
NIMS organizes doctrine into broad components, including resource management, command and coordination, and communications and information management. Inside command and coordination sit several distinct structures: ICS for field operations, emergency operations centers for off-scene support, multiagency coordination groups for senior-level prioritization, and joint information systems for public messaging. Because all four use coordination language, memorizing definitions as flat list items makes them interchangeable in your head.
ICS itself has named features you should be able to define and apply: a modular organization that expands and contracts with the incident, management by objectives, incident action plans, manageable span of control, and unified command when agencies share jurisdiction. A useful study habit is writing each feature as one sentence plus one example of when it activates. If you cannot invent a fresh example for a term, you know it as a phrase, not as a concept, and scenario questions will expose that gap.
Worked scenario: campus flooding — who commands and who supports?
A flood on a college campus forces a choice between on-scene ICS and an activated EOC. The plausible error is routing tactical decisions through the EOC; the better structure separates field command from support.
Scenario: flash flooding has isolated two dormitories at a college where you supervise security. Water is rising, one road is closed, and the college president wants status reports every fifteen minutes. A plausible mistake here is declaring the EOC 'in charge' and issuing evacuation directions from the operations center. That conflates two layers: the EOC is an off-scene support structure, while the incident itself needs on-scene incident command to direct tactical actions like evacuations and road closures.
The better decision is to establish incident command at the scene with a clear set of objectives — account for occupants, move people from the isolated dormitories, and protect access routes — while the EOC, if activated, handles resource ordering, policy questions, and executive reporting. Why it matters: when tactical decisions travel upward to an EOC, response slows because the people closest to the incident lose decision authority, while the EOC drowns in details it was never designed to manage. Draw this split on paper until it is automatic: field command decides tactics; the EOC supports with resources and policy.
Worked scenario: armed intruder — role boundaries for security staff
Active shooter study content emphasizes prevention, protective options, and coordinated response. A paper scenario shows why a guard's correct actions follow the facility plan and law enforcement roles, not personal heroics.
Scenario: you are an unarmed guard in a retail corridor when you hear gunfire two storefronts away. A plausible mistake in this paper exercise is leaving your assigned communications role to search for the shooter or to physically confront them. That error abandons the two things only you can provide at that moment: accurate information to responders and guidance to the people nearby. Confrontation by an unarmed officer also adds a casualty risk the situation does not require.
The better decision, consistent with the protective options taught in active shooter training — run, hide, fight as individual choices when directly threatened — is to follow the facility emergency action plan: direct people toward evacuation or shelter as the plan specifies, relay location, description, and direction-of-travel details to law enforcement, and be prepared to hand responding officers the information they need, including keys and floor knowledge. Why it matters: response to a targeted violence event is designed as a system, with law enforcement handling neutralization and facility staff handling information and movement. Studying the scenario on paper, with your facility's plan beside you, trains the decision before you ever need it.
Resource requests: typing, credentialing, and ordering through proper channels
NIMS resource management describes resources as typed, credentialed, and ordered through established channels. Scenario items test whether you request what is actually needed through the correct path instead of improvising.
Resource typing gives capabilities standardized definitions, so a request for a 'pump team' becomes a request for a specific, catalogued capability with defined qualifications and capacity. Credentialing then verifies that the personnel attached to those resources hold the qualifications the type requires. In a study scenario, the disciplined answer usually involves specifying the capability needed rather than a vague noun, because vague requests produce resources that arrive unable to do the job.
Mutual aid is the mechanism for obtaining resources from other jurisdictions or organizations under pre-established agreements, and it differs from one-way assistance in that it is structured, documented, and coordinated. A plausible scenario mistake is a field supervisor telephoning a counterpart agency directly and committing resources outside any agreement. The better pattern is to identify the capability gap, order through the established resource channel — typically the logistics function or EOC depending on scale — and let the agreement structure govern the exchange. Practicing this ordering chain on paper builds the habit that a resource request is a documented process, not a favor between acquaintances.
One table that keeps the coordination structures straight
Four structures — ICS, EOC, MAC group, and joint information system — answer different questions. Pinning each to its question and location prevents the substitutions that scenario items are designed to catch.
Use the table as a retrieval drill, not a reading exercise. Cover the right-hand columns, read the structure name, and recite its question, location, and a fresh example from your own workplace. When a study scenario describes senior officials setting priorities across agencies, you should reach for the MAC group row; when it describes tactical decisions at the scene, the ICS row; when it describes public messaging across organizations, the JIS row.
The most instructive check is the boundary cases. An EOC and a MAC group both sit off scene, so ask who is deciding: the EOC coordinates support and resources for one jurisdiction's response, while a MAC group of agency executives resolves competing priorities and allocates scarce resources among agencies. If your example sentences for two rows sound identical, rewrite them until they differ. That rewrite is where the real learning happens, because scenario questions hinge on exactly these distinctions.
| Structure | Core question it answers | Where it operates | Illustrative example |
|---|---|---|---|
| ICS | Who directs on-scene tactical operations? | At the incident | A single incident commander runs a building evacuation and sets tactical objectives |
| EOC | How does the jurisdiction support the incident off scene? | Off scene, jurisdiction level | Staff coordinate resource ordering, policy decisions, and executive reporting during a flood |
| MAC group | How do agency executives resolve competing priorities? | Off scene, senior officials | Executives decide which of several jurisdictions gets scarce heavy-lift equipment first |
| JIS / JIC | How is public information coordinated across organizations? | Off scene, communications | Agencies align their public messages so evacuation routes are reported consistently |
A self-check rubric and an adaptable preparation sequence
Grade yourself with a rubric that rewards correct structural placement, then sequence study from foundational framework courses to specialized security topics, using each final exam as application rather than memorization rehearsal.
A realistic sequence: first, register your FEMA SID and skim the Independent Study catalog to pick the courses your role requires, listing their CEU values. Second, take the foundational framework courses before specialty ones, since active shooter and critical infrastructure content assumes you understand command and coordination basics. Third, after each course, write your one-page term map and run one scenario per structure before attempting the final exam. Fourth, download each certificate from the NDEMU Student Portal as you finish, so your transcript and records stay current. Adjust the order to whatever your employer or licensing authority requires; the sequence above is a learning order, not a mandate.
For readiness checks, apply this rubric to any practice scenario you write or encounter. Score each item from your own work: a passing self-check means you can name the correct structure and state why the adjacent structures do not fit; you can write one objective sentence for the incident commander; you can trace a resource request from field need to order placement; and you can state your role-specific actions in a targeted-violence scenario that are consistent with a facility plan. Reaching every item on the rubric is a learning milestone showing your mapping is solid — it is not a prediction of any exam outcome, and it does not replace completing the courses themselves.
- Structure placement: correct structure named, plus one sentence on why the adjacent structure does not fit (self-check target: 4 of 4 scenarios).
- Objectives: one written objective sentence per scenario, phrased as an outcome rather than a task list.
- Resource chain: a resource request traced from capability gap through the proper ordering channel without skipping a step.
- Role boundaries: targeted-violence actions stated that match a facility emergency action plan and preserve the information role.
- Records: certificate downloaded from the NDEMU Student Portal and CEU value noted for every completed course.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.