NWCG S-231 Study Guide: Single Resource Boss Decisions

The most useful way to prepare is to rehearse the full supervisory decision chain: size up conditions, set controls with explicit trigger points, brief the crew completely, document decisions, and re-run the loop when conditions change. Work paper scenarios until each step is deliberate and verifiable.

Sorting out the course label: S-230, S-231, and what you are studying

NWCG numbers single resource boss courses by resource type. Crew Boss and Engine Boss are conventionally different courses, and this guide teaches crew supervision content, so verify your enrolled course title on the NWCG page before relying on any study material.

The conventional split is worth understanding because it changes what you study. Crew Boss is the course commonly referenced as S-230, while S-231 is the Engine Boss (Single Resource Boss) course, which layers engine-specific operations on top of shared single resource boss concepts. The NWCG source page for this guide could not be retrieved when this material was compiled, so the exact catalog entry behind any given site or course number should be checked directly against the NWCG training course page rather than assumed from a course code on a schedule, a certificate, or a study product.

Practically, this matters in two ways. First, confirm which course you are actually enrolled in before buying study time with the wrong material: if your class is engine-focused, you will need pump, hose, and engine positioning content that crew supervision material does not cover. Second, recognize that the shared core — size-up, risk management, briefings, and documentation — overlaps heavily between the resource types, so a crew-focused study approach remains useful even if your course turns out to be engine-labeled. When in doubt, the NWCG course page is the authority for current titles, prerequisites, and scope.

Where the single resource boss role starts and ends

The single resource boss supervises one assigned crew, translating tactical direction from the division or group supervisor into work assignments while managing crew capability, welfare, and safety through the operational period.

The role combines tactical supervision with personnel oversight. You receive an assignment, inspect its feasibility against current conditions, divide it into crew tasks, assign qualified personnel, and then monitor progress, fatigue, and hazards rather than performing crewmember tasks yourself. Communication runs in both directions: direction comes down the operations chain, and condition changes, resource status, and incidents go back up it in a form your supervisor can act on immediately.

Boundary clarity matters when a request exceeds your scope. A crewmember executes tasks but does not assign them or set controls for others. A task force or strike team leader combines several resources under one leader and carries broader coordination duties. If a scenario offers you an objective beyond one resource — coordinating multiple crews, reassigning another boss's personnel, or changing division-level tactics — recognize that the decision belongs higher in the chain, and frame your action as a recommendation and a report rather than an order.

Turning size-up observations into a defensible tactic

Size-up converts observations of weather, topography, and fuels into a tactical judgment: what the crew can accomplish, what it must avoid, and which observed conditions should change the plan.

Name the three drivers explicitly when you practice. Weather supplies wind and humidity trends, topography supplies slope and aspect, and fuels supply loading and continuity — and their interactions set expected fire behavior. In a worked example, a crew assigned to direct attack on a fire backing downhill may have a sound tactic; the same assignment on the fire's wind-facing upslope side is a different problem entirely. Practice writing size-up as three linked statements: observation, implication for fire behavior, action the crew will take.

Tactics must also fit the incident objectives and the crew's actual capability, not just physical feasibility. A tactic that conflicts with the operational period's stated objective, exceeds crew endurance, or depends on a resource you do not control is not a valid answer even if it would work in the field. When you evaluate an exam-style scenario, check the tactic against all three filters — fire behavior, incident objectives, and crew capacity — and be ready to state which filter the proposed tactic fails.

LCES versus the risk management process: related but not interchangeable

LCES names the four standing controls a boss maintains — lookouts, communications, escape routes, and safety zones — while the risk management process is the repeatable decision loop used to set and revise those controls.

The distinction shows up whenever a scenario introduces change. LCES describes a state you maintain; the risk management loop — size up the situation, assess hazards, identify controls, make the decision, and evaluate — is the procedure that produces and updates that state. A memorized LCES checklist tells you what must exist at any moment, but it does not tell you when to rebuild it. When a scenario presents a wind shift, spotting across the line, or a fatigued crewmember, the expected reasoning is that the loop restarts, not that the original controls simply persist.

Apply this by mapping, for every hazard you identify in practice, a specific control and a trigger that voids it. For example, a lookout posted to watch a predicted wind change is paired with a defined wind condition that sends the crew to the escape route. This pairing — hazard, control, trigger, and who communicates the trigger — is the structure to rehearse on paper until you can produce it quickly for any assignment a scenario hands you.

Safety zone or deployment site: planning the wrong one is a costly confusion

A safety zone allows the crew to survive the flame front without shelter deployment; a deployment site is the last-resort fallback when escape fails. Planning for one when conditions require the other is a consequential distinction.

A safety zone is an area sized against expected fire behavior, cleared or naturally free of fuels, reachable by the escape route, large enough for the crew plus any equipment, and positioned where fire behavior is survivable. A deployment site is a location where a fire shelter offers a chance of survival only because escape failed — a far lower standard. In this simplified worked example: a crew is building line on a roughly thirty percent slope where the briefing estimates significant flame lengths on that slope under the forecast wind. The nearest option is a roadside pullout of about forty meters across, partially enclosed by brush. The plausible mistake is accepting the pullout because it is paved and nearby. The better decision is recognizing that expected fire behavior on the slope and the surrounding brush make that margin inadequate, relocating the designated safety zone to the larger open ridgetop area identified earlier, resetting the escape route to reach it, and stating the trigger — the forecast wind change — that sends the crew that way. Adequate separation is a function of expected fire behavior and surrounding fuels, so it must be checked, not assumed from surface type.

Use this comparison when you practice, and force yourself to justify which category each scenario location belongs in. After any scenario, run the check in reverse: given the safety zone you chose, could the escape route actually deliver the crew there within the time the expected fire behavior allows? If either side of that pairing fails, the whole set of controls needs rebuilding — which is exactly the reasoning chain to narrate in your practice answers.

Briefings, handovers, and the documentation the boss owes

An assignment list such as the ICS-204 carries the task and special instructions; the boss's briefing translates it into crew-level action, and an activity log such as the ICS-214 records decisions and reasons up through the after action review.

A complete crew briefing covers the task and its purpose, the LCES controls with named lookouts and stated trigger points, the communications plan including channels and check-in expectations, the medical plan summary including evacuation route and nearest medical point, adjacent resources and their locations, identified hazards, and what to do if communications fail. Close it with verification: have crewmembers read back the escape route, trigger, and channel. Worked scenario two: a relief boss takes over mid-operational-period through a brief verbal handover, then tells the crew simply to hold and improve the line. The plausible mistake is treating the handover as complete because the task was passed along — the trigger point for the forecast wind change, the medical route, and the location of the replacement lookout never reached the crew. The better decision is a structured handover covering task, controls, contingencies, and medical information, followed by having the crew restate the escape route and trigger before work resumes. A crew acts on what was said to them, not on what the previous boss knew.

Documentation carries the same judgment standard. The unit log captures decisions and their reasons, hazard changes, injuries and near misses, and major tactical shifts — entries that reconstruct why the crew did what it did. Radio traffic, by contrast, carries the immediate report: condition change, action taken, resources affected. A useful self-test is whether each log entry states a decision and a reason; 'worked on line' documents activity but not judgment. Close the operational period with an after action review — what was planned, what happened, why the difference occurred, what changes next — and feed each named hazard from the review into the next period's briefing as a control. That linkage is the supervisory habit the role demands.

A briefing-rebuild drill, a scoring rubric, and an adaptable sequence

Run a weekly briefing-rebuild drill on paper scenarios, score it against a rubric, then trace every exam-style item through the risk loop before moving to timed mixed practice.

The drill: take any paper scenario with an assignment and a forecast change. Draft the LCES set, the trigger points, and a full briefing outline as if you would deliver it aloud. Score yourself with the rubric below on two consecutive drills before advancing. A realistic sequence: first phase, course-label verification plus role boundaries and size-up structure; second, the risk loop with hazard-control-trigger mapping; third, briefing drills and the safety zone versus deployment distinction; final phase, timed mixed scenarios plus log-writing practice. Revisit earlier phases whenever a rubric item keeps failing.

Readiness checks you can apply honestly: you can narrate observation, implication, and action for an unfamiliar scenario in under a minute; you can state which of the three filters a flawed tactic fails; your rubric score hits every item twice in a row; and you can rebuild a complete LCES set after a scenario injects a wind change without restarting from the acronym. Rubric and drill scores are learning milestones only — they measure practice quality, not a passing prediction. For current course titles, prerequisites, and administrative details, rely on the NWCG course page rather than secondhand summaries.

• Hazard-to-control pairing: every identified hazard has a specific control, not a general reference to LCES
• Triggers stated: each control includes the condition that voids it and who announces it
• Escape and zone linked: the route reaches the chosen zone within the time expected fire behavior allows
• Briefing completeness: task, controls, comms, medical route, adjacent resources, and comm-failure plan all present
• Verification present: crew read-back of route, trigger, and channel appears in your outline

References and further reading

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

• nwcg.gov

Continue your preparation

• Wildland Fire Crew Boss Nwcg S 231
• Study Guides