Study Guide

NFPA 1006 Core: Decision Layer Study Plan

Study the Technical Rescuer Core as decision-making skills: rescue vs. recovery, size-up, PPE logic, and documentation — one decision layer across specialties.

Updated September 20269 min readStudy GuideFire Med Exam
Anthony Spencer

Anthony Spencer

Fire Med Exam Editorial Team

Study the Technical Rescuer Core as a set of decisions that repeat in every specialty: assess the scene, control hazards, choose protection, commit to rescue or recovery, manage the victim, and close out with documentation. Practice each decision as a written choice with reasons attached, not as a definition to memorize, so the same sequence transfers from a vehicle scene to a water or confined-space scene.

Why the core competencies are a decision layer, not a warm-up chapter

The core content of NFPA 1006 describes actions a rescuer must perform before and around any specialty technique: assessing incidents, identifying and controlling hazards, selecting protection, and managing victims across disciplines.

If you read the core material as background trivia, you will memorize lists without knowing when each item applies. Instead, read every core statement as a fork in the road: it asks you to notice something about the scene and then choose an action. A hazard is not just 'identified' — it is identified, evaluated, and either isolated, controlled, or accepted as a reason to change the plan.

A practical way to anchor this is to take one familiar setting, such as a vehicle resting against a guardrail on a grade, and walk the whole core sequence across it: size-up, hazard control, protection, victim status, and termination. Then repeat the same sequence in a different setting, such as a person in fast-moving water. The overlapping steps are the core; the settings are the specialties.

Rescue versus recovery: the decision that changes everything downstream

A rescue means a viable victim can be reached and treated; a recovery means the focus shifts to locating and removing a deceased person under conditions rescuers are not asked to risk their lives for.

This distinction is not a single fact — it is a judgment assembled from scene information: elapsed time, signs of life, environment, and resources on scene. Compare the modes directly. In rescue mode, speed is a survival factor, aggressive techniques are justified, and rescuers accept elevated risk for a savable person. In recovery mode, risk to rescuers drops toward minimal, timelines extend, and methods become slower and more deliberate.

Worked scenario: a caller reports a vehicle off the road into a farm pond; bystanders estimate the driver has been submerged well over an hour, no one saw movement after entry, and a dive-capable team is two hours out. A plausible mistake is leaving the mode unstated while awaiting confirmation. The better decision is stating a mode in writing: warm water and elapsed time without witnessed movement support deliberate, low-risk recovery operations pending medical or authoritative input. It matters because an unstated mode produces inconsistent risk decisions mid-incident.

  • Rescue mode: viable victim plausible, speed matters, rescuer risk justified by survivability
  • Recovery mode: survivability not plausible, rescuer risk minimized, methods slow and controlled
  • Cold water is treated as extending plausible survivability, so identical elapsed times can support opposite modes at different water temperatures
  • The mode is set by scene evidence and medical or authoritative input, not by hope or by who is on scene
Decision pointRescue modeRecovery mode
Time pressureSpeed is a survival factor for the victim; rapid access justifiedTimelines extend; deliberate, methodical work is preferred
Rescuer risk toleranceElevated risk justified only by plausible survivabilityRisk driven toward minimal; no heroic exposure for non-viable outcomes
Victim contactImmediate assessment, treatment, and packaging prioritiesCareful location, documentation, and respectful removal
Scene preservationSecondary to life safety and rapid accessPreservation matters more; slower operations protect evidence and scene integrity
Typical justification to recordSigns of survivability, elapsed time, environmental factorsAbsence of survivability indicators, medical or authoritative determination

Size-up as a written product, not a feeling

Size-up in the core sense is a structured reading of the scene: what happened, what is still happening, what hazards exist, what resources are present, and what the victim's status suggests about the operating mode.

Treating size-up as a word to recognize produces lists without application timing. Instead, produce one in writing for every practice scenario and force each element to appear: mechanism and history, ongoing hazards, victim location and status, access and egress, weather and environment, resources on hand and en route, and a preliminary operating mode. When you write it, gaps become obvious — you notice you never recorded how unstable the load is, or that no one confirmed the number of victims.

Worked scenario: a worker is reportedly trapped under a partially collapsed excavated wall at a residential site after recent rain, the vertical face is unshored, and neighbors urge rescuers to 'just start digging.' A plausible mistake is absorbing that urgency and treating void entry as the default action. The better decision is to write the size-up first: uncontrolled vertical face, saturated soil, no shoring, victim location unconfirmed — supporting area control, specialized resources, and preventing further entrapment. That written record is what converts urgency into a defensible plan.

Hazard control: isolating, removing, and accepting are three different choices

Core hazard knowledge is not just recognition. Each hazard you identify requires a decision: eliminate it, isolate people from it, control it with equipment or technique, or accept it deliberately with justification.

Compare two hazards. A downed electrical line at a vehicle incident is usually treated by isolation — deny entry to the hazard zone and wait for utility control — because rescuers cannot neutralize it themselves. A shifting vehicle on its side on a grade, by contrast, invites active control: stabilization before any victim contact, because the hazard will not resolve by waiting and the victim is directly exposed. Choosing isolation where control is needed — or the reverse — is exactly the judgment the core content exists to train.

Build a habit of naming the control category for every hazard you list in a practice size-up. Write 'isolation,' 'control,' 'remove,' or 'accept with reason' next to each item. When you review your own work, the rubric question is simple: does every hazard have a category and a reason? A hazard list without dispositions is an incomplete core answer, because recognition without disposition never produces a scene action.

PPE selection logic: matching protection to the hazard, not the discipline label

Protective equipment choices should follow from the specific hazards your size-up identified — impact, water, atmosphere, sharp edges, temperature — rather than from the name of the discipline you happen to be operating in.

The core teaches a transferable logic: read the hazard, derive the protection. A rescuer working at height over water needs fall protection for the edge work and water-related protection for the environment; neither item alone is 'the water rescue PPE' or 'the rope PPE' in a fixed sense. Practice deriving a PPE list from a hazard list and then checking each item against a specific hazard. If an item on your list answers no hazard, question it. If a hazard on your list has no matching item, that gap is a finding.

This logic also explains why borrowed habits are dangerous. A helmet appropriate for one environment may lack the protection a different environment demands; gloves that protect against abrasion may be a liability for fine tasks in cold water. Rather than memorizing discipline-specific kits, rehearse the derivation: for each worked scenario, list hazards, then list required protection item by item with the hazard it addresses. This habit transfers to any specialty chapter you study later.

Termination and documentation: what 'complete' means in the core sense

Closing a technical rescue incident means confirming all victims are accounted for, hazards are controlled or handed off, personnel are accounted for, equipment is restored, and the event is documented accurately.

Documentation is easy to neglect in study plans because it feels clerical, but in the core framework it is the record that your decisions were reasoned. Practice writing a short closing narrative for each scenario: operating mode chosen and why, hazards and their dispositions, resources used, victim outcome and handoff, and any deviations from the initial plan. Writing the narrative forces you to reconcile what you decided with what you actually recorded during size-up — and inconsistencies reveal where your reasoning was thin.

A useful comparison is the opening document versus the closing document. The size-up predicts; the termination narrative verifies. If your closing narrative says hazards were controlled, your size-up should show which hazards and which control methods. Build this pairing into every scenario you work. A self-check: can a reader reconstruct your decisions from your two documents alone, without you in the room? If not, your documentation habit needs work regardless of how sound your tactical choices were.

A scenario-first preparation sequence with readiness checks

Prepare by cycling through paper scenarios in escalating complexity: first write size-ups, then add hazard dispositions, then operating-mode decisions, then closing narratives, checking each cycle against a fixed rubric.

A workable sequence over several weeks: begin with short, single-hazard scenarios and practice only size-up writing until every element appears reliably. Add hazard dispositions next, then the rescue-versus-recovery fork with scenarios built around ambiguous time and environmental information, each answered with a written mode justification. Finally, add termination narratives and require the opening and closing documents to reconcile. For current edition and administrative questions about the standard, consult NFPA directly at nfpa.org.

Practical exercise: take three paper scenarios from different environments — a grade, moving water, and a confined volume. For each, within about fifteen minutes, write a size-up, list hazards with dispositions, state an operating mode with justification, and sketch PPE tied to specific hazards. Expected observations: missing victim count, missing environment trends, missing resource status. Those recurring omissions are your study list. Your readiness check: meet all five rubric points on two consecutive scenarios, then rotate in new environments — a learning milestone, not a predicted exam result.

  • Rubric point 1 — every size-up element present, including number of victims and environment trend
  • Rubric point 2 — every hazard carries a named disposition and a reason
  • Rubric point 3 — operating mode stated with scene-based justification, not hope
  • Rubric point 4 — each PPE item traces back to a named hazard
  • Rubric point 5 — closing narrative reconciles with the size-up without contradictions

References and further reading

Use these references to explore the concepts and check the latest information from the relevant organizations.

Continue your preparation

FAQ

Frequently Asked Questions

Practical answers to help you apply the guidance for Technical Rescuer Core (NFPA 1006).

How do I decide rescue versus recovery when survivability is genuinely ambiguous?
Write the reasoning instead of choosing silently. Record elapsed time, water temperature, and any medical or authoritative input, state the mode you are operating in, and note what information would change it — including that cold water can extend plausible survivability and keep an aggressive search justified. Escalate the determination to medical direction rather than guessing.
Should I memorize one PPE kit per rescue discipline?
A better habit is deriving protection from hazards. For each scenario, list the hazards your size-up identified, then name the protective item that addresses each one. Memorized kits still help as a starting checklist, but the derivation catches mismatches when a scene combines hazards from more than one environment.
What is the difference between hazard recognition and hazard control in the core content?
Recognition is identifying that a hazard exists; control is deciding its disposition: remove it, isolate people from it, control it with equipment or technique, or accept it deliberately with a recorded reason. A size-up that only recognizes hazards is incomplete, because no disposition means no scene action.
My rubric results keep missing one or two points. What should I change?
Look at which rubric point fails across scenarios. Omissions tend to cluster — commonly victim count, environment trends, or resource status. Drill scenarios that force the missing element: pick ones where that detail changes the operating mode, so the omission has visible consequences and the habit forms under stakes.
Do core competencies apply the same way inside every specialty discipline?
That is the premise of studying them as a decision layer: size-up, hazard disposition, protective equipment selection, operating-mode judgment, and closure recur regardless of environment, while the techniques and equipment details change by discipline. Testing yourself with scenarios from different environments is how you confirm the decisions transferred.

Keep Reading

Related Study Guides

Explore related guides and preparation topics.