11.5 Run an Error Log and Remediation Cycle
Key Takeaways
- An error log turns missed questions into patterns you can repair, instead of a growing pile of red marks.
- Label each miss by domain, root cause, the correct rule, and a specific next drill — not just 'wrong.'
- Sort the root cause into knowledge gap, careless/reading error, or timing error, because each needs a different fix.
- Corrections-exam errors often come from ignored instructions, unsupported assumptions, weak chronology, or unprofessional judgment.
- Weekly remediation should produce a concrete new practice action, not just a longer list of mistakes.
Why a Log Beats Re-Reading Answers
Most applicants 'review' by reading the answer key and nodding along. That feels productive but rarely changes the score, because it never identifies why the miss happened or how to prevent it. An error log fixes this by treating every missed (or guessed) item as data. The goal is to convert scattered mistakes into a small number of patterns you can deliberately repair.
Log each miss with five fields:
| Field | What to record | Example |
|---|---|---|
| Item / domain | The question and its domain | Math — ratio problem |
| My answer vs. correct | What you chose and what was right | Chose 3 officers; correct 2 |
| Root cause | Knowledge gap, careless/reading, or timing | Careless — divided by wrong number |
| Correct rule | The rule or principle in one line | Inmates ÷ ratio = officers |
| Next drill | The specific action to fix it | 10 ratio problems, untimed, then timed |
Writing the correct rule in your own words is the step that locks in learning; copying the explanation verbatim does not. A log with these fields turns 'I got 12 wrong' into 'I have three careless math slips and two SJT judgment misses' — and that is something you can actually fix this week.
Sort the Root Cause — It Decides the Fix
Every miss has one of three root causes, and each demands a different remedy:
- Knowledge gap — you did not know the rule, formula, or format. Fix: learn the content, then drill it (e.g., master the report-writing structure, then write three reports).
- Careless / reading error — you knew the material but misread the question, ignored an instruction, made an arithmetic slip, or assumed a fact not given. Fix: a process habit — read the full stem, underline what is asked, and sanity-check the answer. This is the most common and most fixable category.
- Timing error — you ran out of time or rushed into mistakes. Fix: pacing practice and the flag-and-move habit from 11.4.
Corrections entrance items have signature traps that show up in the log again and again:
- Ignored instructions — answering an SJT 'best response' question with the 'worst' option, or skipping a multi-part directive.
- Unsupported assumptions — answering a reading or rule-application item from prior knowledge instead of from the passage only.
- Weak chronology — a report-writing answer that is out of time order or mixes in opinion and conclusions instead of facts.
- Unprofessional judgment — an SJT choice that escalates, bypasses policy or the chain of command, uses force before verbal options, or fails to document.
When the same trap appears two or three times, it is no longer bad luck — it is a habit to retrain.
The Weekly Remediation Cycle
Run the log on a weekly loop so it drives your next study block instead of just recording history:
- Collect every miss and guess from the week's practice into the log.
- Cluster them by domain and by root cause. Count the clusters.
- Diagnose the top one or two patterns — for example, 'careless math slips' and 'SJT picks the escalating option.'
- Prescribe a specific drill for each pattern and put it on next week's calendar: e.g., a timed ratio set with mandatory sanity-checks, and ten SJT scenarios where you write one line of reasoning for the best and worst options.
- Re-test later — pull a few items of that exact type and confirm the pattern is shrinking. If it is not, the diagnosis was wrong; look again.
The non-negotiable rule: every remediation cycle ends with a new practice action, not a longer list of mistakes. A log that only grows is a diary; a log that produces next week's drills is a study engine. Over a four- to eight-week plan, this loop is usually what moves the needle most — it concentrates your limited hours on the precise few error patterns standing between you and a clean, well-paced exam.
A Filled-In Error-Log Row, Start to Finish
To see the whole cycle in one example, follow a single miss from practice to repair:
| Field | Entry |
|---|---|
| Item / domain | SJT — inmate offers to 'handle' a rule violation 'quietly' |
| My answer vs. correct | Chose 'make a mental note for later'; correct was 'follow policy, secure item, document' |
| Root cause | Knowledge/judgment — treated an unwritten note as acceptable action |
| Correct rule | Corrections judgment defaults to safety, policy, chain of command, de-escalation, and documentation |
| Next drill | 10 SJT scenarios; for each, write one line naming the best and worst option and why |
A week later this applicant pulls five fresh SJT items and gets all five right by consciously scanning for the safe-policy-aligned-documented option — the pattern has shrunk, so it leaves the active list. Contrast that with the common non-strategy: marking the item wrong, reading the explanation once, and moving on. That applicant will miss the same kind of item again because nothing changed their reflex. The log works precisely because it forces a named rule and a scheduled drill, not just recognition.
Keep your log short and honest — five clear rows that each spawn a drill beat fifty vague rows that spawn nothing — and retire a pattern only after a fresh re-test confirms it is gone.
What is the purpose of recording the 'root cause' for each missed question?
You repeatedly answer reading and rule-application items using outside knowledge instead of the passage. What error pattern is this?
What must every weekly remediation cycle end with?