Study guide

Comparing Directives and Scenario Details

Corrections Officer Entrance Exam Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: Agency-Specific Corrections Officer Exams and the Hiring Process

1.1 No One National Format 1.2 The Controlling Source Rule 1.3 Vendor, Civil-Service, and Agency-Written Paths 1.4 The Written Test Is One Selection Step 1.5 Common Follow-Up Screens 1.6 Study Orientation for Variable Processes

2 NCOSI, NCST, and Civil-Service Formats: Domains, Timing, and Score Use

2.1 Current IOS NCOSI Format 2.2 Stanard NCST Skill Areas 2.3 Civil-Service and Agency Variants 2.4 Timing and Administration Details 2.5 Score Use, Cutoffs, and Eligibility Lists 2.6 Domain Map for Study Planning

3 Reading Comprehension: Policies, Procedures, Reports, and Directives

Extracting the Controlling Rule Following Procedure Sequence Identifying Exceptions and Limits Reading Reports for Facts, Time, and Source Avoiding Outside Assumptions Comparing Directives and Scenario Details Reading Under Time Pressure

4 Problem Solving: Rule Application, Priorities, and Workplace Decisions

Using Provided Facts to Choose Actions Prioritizing Safety, Security, and Accountability Resolving Conflicting Instructions Professional Workplace Decisions Resolving Conflicts and De-Escalating Problems Avoiding Unsupported Conclusions in Decisions

5 Grammatical and Written Competency: Professional Correctional Language

5.1 Grammar as a Tested Corrections Skill 5.2 Sentence Clarity and Plain Meaning 5.3 Tone, Respect, and Professional Voice 5.4 Spelling, Punctuation, and Mechanics That Affect Meaning 5.5 Objective Wording and Fact-Based Communication 5.6 Clear Instructions, Notices, and Shift Messages

6 Report Writing: Incident Chronology, Observation, and Factual Documentation

6.1 Report Writing as an Entrance-Exam Skill 6.2 Incident Notes and Observation Capture 6.3 Chronological Order and Time Anchors 6.4 Witness, Action, and Result Documentation 6.5 Facts, Observations, and Supported Inferences 6.6 Incident Narrative Assembly and Review

7 Math: Counts, Schedules, Ratios, Tables, and Basic Correctional Calculations

7.1 Math as an Agency Variant 7.2 Counts, Totals, and Differences 7.3 Schedules, Time Intervals, and Shift Logic 7.4 Ratios, Rates, and Staffing Comparisons 7.5 Tables, Rosters, and Log Interpretation 7.6 Checking Work and Avoiding Unsupported Calculations

8 Behavioral Orientation: Stress, Interpersonal Ability, Teamwork, Assertiveness, and Integrity

8.1 Behavioral Orientation on the NCOSI 8.2 Stress Tolerance Under Routine Pressure 8.3 Interpersonal Ability and Respectful Communication 8.4 Team Orientation and Reliability 8.5 Assertiveness Without Aggression 8.6 Ethics, Integrity, and Consistent Work Style

9 Situational Judgment: De-escalation, Policy Adherence, and Professional Discretion

9.1 SJT Mindset, Values, and Effective Behaviour 9.2 Policy Adherence and the Limits of Discretion 9.3 De-escalation, Communication, and Control 9.4 Incident Response Priorities and Notification 9.5 Avoiding Heroics, Avoidance, and Retaliation 9.6 Ethics, Accountability, and Professional Boundaries

10 Observation, Memory, Security Awareness, and Detail Recall

10.1 Observation as an Agency Variant and Cross-Test Skill 10.2 People, Location, Time, and Movement Details 10.3 Contraband, Security Awareness, and Risk Clues 10.4 Memory Encoding, Rehearsal, and Recall Method 10.5 Safe Note-Taking and Report Detail Preservation 10.6 Detail Recall Practice, Review, and Error Control

11 Study Plan: Practice Strategy, Error Review, and Agency Announcement Checklist

11.1 Map the Agency Announcement First 11.2 Build a Four- to Eight-Week Calendar 11.3 Match Practice to Vendor and Test Type 11.4 Use Timed Practice Without Fake Score Goals 11.5 Run an Error Log and Remediation Cycle 11.6 Maintain an Announcement Checklist

12 Final Review: Test Day, After the Written Exam, Background, Fitness, and Academy

12.1 Final Seventy-Two-Hour Review 12.2 Identification, Admission, and Delivery Rules 12.3 Timing, Stress, and Answer Review During the Written Test 12.4 Results, Eligibility Lists, and Next Notices 12.5 Background, Medical, Psychological, and Interviews 12.6 Fitness, Academy, and Continuing Readiness

Comparing Directives and Scenario Details

Key Takeaways Explain This Topic AI

A common item type gives a directive plus a scenario and asks whether the scenario complies, violates, or is silent.

Read the directive's conditions as a checklist and test the scenario against each condition in turn.

A violation occurs when any required condition is unmet or any limit is exceeded — one failed condition is enough.

Watch the actor and authority: an action correct for one role may violate the directive if done by the wrong person.

Match the scenario's exact facts (times, roles, amounts) to the directive's exact conditions before deciding.

Last updated: June 2026

The directive-versus-scenario item

A frequent and high-value reading item gives you a directive (a rule with conditions) and a scenario (a short account of what someone did), then asks whether the action complied with the directive, violated it, or whether the directive is silent on the point. This mirrors real supervisory review: a sergeant reads a post order and an officer's account and decides whether procedure was followed. The skill is comparison — lining up the scenario's facts against the directive's conditions and judging the fit precisely.

The core technique is to convert the directive into a checklist of conditions. Most directives bundle several requirements: a triggering condition (when the rule applies), an actor (who must act), a required action, a limit (how much, how long), and sometimes a documentation or notification step. Break them apart. Then walk the scenario through each box and mark it met or unmet. A scenario complies only if it satisfies every applicable condition; it violates the directive if any one condition fails. This is an AND relationship, not a vote — three satisfied conditions do not outweigh one that is broken.

Build and apply the checklist

Consider the directive: "Before issuing tools from the maintenance cabinet, an officer must (1) verify the worker's ID against the work order, (2) record the tool number and time in the tool log, and (3) confirm the matching shadow board has an open slot. Tools must be returned and logged by end of shift."

The checklist:

Condition Requirement Met in scenario?

Trigger Issuing a tool from the cabinet (depends)

Verify ID checked against work order ?

Record Tool number and time logged at issue ?

Confirm Shadow board slot is open ?

Return Tool returned and logged by end of shift ?

Now a scenario: "Officer Pratt checked the worker's ID against the work order, confirmed an open slot on the shadow board, and handed over the drill. Pratt planned to log the tool number after lunch."

Work it: Conditions 1 (verify) and 3 (confirm slot) are met. But condition 2 requires recording the tool number and time at issue, and Pratt deferred logging until after lunch — that condition is unmet. Therefore the scenario violates the directive, even though two of three issuance steps were done correctly. One failed condition is decisive. A distractor that says "complies, because Pratt checked the ID and the board" rewards partial compliance, which the directive does not allow.

Actor, authority, and limits

Two facts to watch closely are who acted and how much was done. Many directives assign an action to a specific role or require approval from a supervisor. If the scenario has an officer doing what only a supervisor may authorize, that is a violation regardless of how reasonable the action was. Likewise, limits are bright lines: "no more than two," "up to fifteen minutes," "within the dayroom only." If the scenario crosses a numeric or spatial limit, it violates the directive even if the intent was good.

A reliable routine:

List the directive's conditions, including actor, action, limits, and documentation.

Read the scenario and check off each condition as met or unmet.

Flag any limit exceeded and any action taken by the wrong role.

If every applicable condition is met, the scenario complies; if any fails, it violates.

If the directive never addresses the scenario's issue, the answer is that it is silent — do not invent a rule.

Traps to expect

The top trap is partial-compliance credit — choosing "complies" because most conditions were satisfied. The directive's conditions are joined by AND, so partial is not pass. A second trap is the role swap , where the scenario's action is fine in substance but done by someone without authority. A third is the limit creep , where times or counts inch past the stated cap. And a fourth is reading a violation into silence — if the directive does not govern the scenario's facts, the right answer is silence, not violation. Test every condition against the exact facts, and let the weakest link decide.

Three options usually appear on these items — complies, violates, or the directive is silent — and learning to tell the third apart from the first two is what separates strong readers. "Silent" means the directive simply does not address the scenario's issue: it neither permits nor forbids the action, so you cannot grade compliance against it. Candidates often force a silent scenario into "violates" because the action feels irregular, or into "complies" because nothing stopped it; both invent a rule the directive never stated.

When you finish your checklist and find the scenario's central question is not covered by any condition, "the directive is silent" is a legitimate and often correct answer. The discipline is identical to the previous section's: do not fill gaps. A directive controls only what it speaks to, and the exam expects you to recognize where its words run out rather than to extend them by assumption.