Treat SRO study as decision training. Master the anatomy of an LCO — Condition, Required Action, Completion Time measured from discovery — classify events by walking the EAL scheme barrier by barrier to the highest threshold met, approve reactivity plans only after restating the requirement, current value, trend, and end state, and document every deviation and turnover so a successor can reconstruct your reasoning. Grade yourself on observable behaviors in written scenarios; rubric milestones show which domain to rework.
Where SRO Work Departs From RO Work: Directing Versus Manipulating
An SRO license covers supervising the operation of reactor controls, not only manipulating them. Studying that difference changes what you practice: interpreting requirements, directing evolutions, and owning the consequence of each decision.
The NRC licenses individuals who operate or supervise the operation of reactor controls at commercial power plants, and that word 'supervise' marks the boundary between an RO license and an SRO license. RO-level work centers on manipulating controls within approved procedures. SRO-level work adds direction: assigning the crew's roles, authorizing evolutions, and answering for the plant state that results. When you study any system, study it twice — once as the person operating the component and once as the person deciding whether the evolution should proceed under current conditions.
This distinction reshapes how you read practice questions. An SRO-oriented item presents a plant condition and asks what the shift should do, not which switch moves where. Build the habit of naming the decision before any action: 'the decision is whether to continue this surveillance to completion.' Then evaluate that decision against Technical Specifications, procedure prerequisites, and equipment or radiological constraints. Once you can articulate the decision cleanly, the correct manipulation usually falls out of the procedure the SRO directs the operator to use.
Reading an LCO as a Decision Tree: Condition, Required Action, Completion Time
Technical Specifications are structured as LCOs with Conditions, Required Actions, and Completion Times measured from the moment a requirement is not met. Practice reading them as a decision tree, not as prose to memorize.
Worked scenario: a two-train engineered safety feature has one train declared inoperable at power, and — in this simplified illustrative example — the LCO gives a 72-hour Completion Time to restore it before a required mode change. The plausible mistake is reading that window as 'time available to repair.' The better reading is that the Completion Time is the time to reach the Required Action's end state, measured from discovery, and the clock does not pause for good-faith repair efforts. Missing the window means the mode-change action governs, which reshapes the whole shift plan.
The deeper difficulty is interaction between LCOs. An inoperable train in one system can disable functions in others — a lost support system can render dependent systems inoperable too — so entering one Condition may obligate you to enter a second concurrently. Drill this by tracing dependencies whenever you declare something inoperable: state which LCOs are entered, in what order, and whether their Completion Times run in parallel. If your trace ends at the first LCO, you have practiced declaration, not SRO-level interpretation.
Classifying Events With the EAL Matrix Instead of First Impressions
Emergency classification is threshold-driven: each licensee's NRC-approved EAL scheme maps plant conditions and fission product barrier status to declared levels. Practice working the matrix deliberately, classifying to the highest threshold met.
Worked scenario: a radiation monitor trend rises while indications suggest a leak from a primary system. The plausible mistake is classifying on first impression — latching onto the earliest threshold that seems to fit, or classifying low because mitigating actions look effective. The better decision is to walk the EAL scheme barrier by barrier (fuel cladding, reactor coolant system, containment), cite the specific threshold language met, and declare the highest level satisfied. Why it matters: a declaration triggers notifications and protective action recommendations, and hesitation compresses every downstream timeline.
Because thresholds are defined in each site's approved scheme, learn the classification logic generically but verify specifics against the scheme applicable to you. A reliable drill: on paper, describe a condition using barrier language — 'activity consistent with cladding damage, no RCS breakthrough' — then classify it and quote the threshold. If you cannot quote the threshold you relied on, your classification rests on a symptom rather than the scheme's actual logic, and that gap shows immediately under time pressure in scenario practice.
Approving Reactivity Plans: Margins, Modes, and Assumptions to Verify
SRO-level reactivity work means approving plans and verifying assumptions: dilution versus boration direction, required shutdown margin, mode-dependent limits, and the sources and trends behind the numbers an operator proposes to use.
Anchor your study in named concepts: reactivity balance, boron dilution versus boration, required shutdown margin, and mode-dependent reactivity requirements. As the SRO, you approve reactivity changes and check the assumptions behind them: where the dilution water comes from, what the margin calculation assumes, and whether the plant can absorb an error in the plan. The operator executes the manipulated variable; you own the question of whether the plan is safe to execute at all in the current mode and lineup.
A conceptual slip worth guarding against is treating reactivity limits as fixed constants. Required values are specified per operating mode in plant documents, so a margin acceptable in one mode may not satisfy the requirement in another, and reduced-inventory conditions change the picture again. Practice the restatement habit: before approving any plan, say aloud the requirement, the current value, the trend, and the completion condition. If any of the four is missing, the plan is not yet ready for your approval.
Deviation Authority, Turnover, and Making Decisions Traceable
Procedure adherence is graded in many programs: continuous-use documents are followed step by step, reference documents guide specific tasks, and deviations require SRO authorization plus documentation. Turnovers and logs make your decisions traceable.
Procedure use is typically graded — continuous-use documents followed step by step, reference documents consulted for a task — and many programs assign the deviation decision to the SRO within defined limits. The key study point is that a deviation has two halves: the operational judgment that a specified path is unavailable or unsafe, and the documented basis explaining what was done and why. An undocumented deviation, even a technically sound one, becomes untraceable the moment the shift changes, which is exactly when someone else must reconstruct your reasoning.
Treat shift turnover as structured documentation rather than conversation. A usable turnover transfers plant status, equipment lineups, in-progress evolutions, open LCO Conditions and their running Completion Times, and any standing directions you have given. Practice it by writing a turnover from a scenario worksheet, then having a partner reconstruct your plant picture from your notes alone. Anything they cannot reconstruct is a documentation gap — find it now, on paper, where it costs a few minutes instead of during a real transition.
| Decision area | RO-level question | SRO-level question | What the SRO verifies |
|---|---|---|---|
| Reactivity change | Which steps execute the dilution or boration? | Should this plan proceed in the current mode? | Required margin, dilution source, trend, completion condition |
| Surveillance | How is the test performed? | Should the surveillance start, continue, or stop? | Prerequisites and LCO implications of a failed test |
| Equipment inoperability | Which components are affected? | Which LCO Conditions apply? | Support-system dependencies and running Completion Times |
| Abnormal condition | Which symptoms and alarms are present? | What is declared, and to whom? | EAL threshold language and notification obligations |
Paper-Scenario Exercise With a Self-Check Rubric
Run one abnormal condition on paper under a fixed clock: classify, enter LCOs, direct actions, and log. Score the written product against a five-point rubric; repeated top scores are the milestone, and low scores name the domain to rework.
Exercise: take one abnormal condition on paper — a leaking system, an inoperable train, a rising monitor — and produce, in order, your classification decision, your LCO entries, the actions you direct, and the log entries you would make. Time-box it to a fixed short interval, then score it against the rubric below. Expected observations: your written product names thresholds and LCO Conditions explicitly, your action list distinguishes decisions from manipulations, and your log entry stands alone as a record a successor could reconstruct.
- You stated the decision — continue, terminate, or enter a Condition — before describing any manipulation.
- You named the LCO number and Condition before quoting any Completion Time.
- You traced at least one support-system dependency before finalizing your LCO entries.
- Your classification cited threshold language from the applicable scheme, not a symptom alone.
- Your log entry states what was done, why, and under whose direction.
- Scoring 5 of 5 repeatedly is your milestone; below 3, return to that domain's fundamentals before more scenarios.
Adaptable Preparation Sequence and Readiness Checks
Sequence your preparation in phases — systems as decisions, Technical Specification structure, EAL logic, daily scenarios, targeted repair — and expand or compress phases around your own schedule. Judge readiness by demonstrated behaviors, not elapsed hours.
A workable sequence: first, map each major system to the decisions it supports rather than to its components alone. Second, drill LCO anatomy — Condition, Required Action, Completion Time — until reading one is mechanical. Third, drill EAL logic barrier by barrier. Fourth, run a paper scenario daily under the Section 6 rubric. Fifth, identify your weakest domain from rubric scores and loop back through its fundamentals before adding new scenarios. Compress or stretch any phase to fit your circumstances; the order matters more than the calendar.
Readiness checks you can apply tonight: restate any LCO you open as condition, action, and completion time without re-reading; classify a written condition while quoting the threshold; write a documented deviation rationale in three sentences; and rebuild a plant status picture from a turnover sheet alone. Administrative matters — eligibility, applications, scheduling, and requalification oversight — are set by the NRC's operator licensing program, so use the issuer's page as the reference for those details rather than third-party summaries. You can reinforce scenario practice with free practice sets and broader study guides.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.