LESSON 14.4 — Error Notebook and Root-Cause Loop
A. Standard Map
| Step | Input | Output |
|---|---|---|
| Capture | Wrong/skipped question | Logged error entry with snapshot |
| Tag | Logged error entry | One primary class (C/R/P/A/L) |
| Root cause | Tag + review | One-line cause statement |
| Corrective action | Root cause | Template action (re-read / drill / unit card) |
| Reattempt | Scheduled date | Closed or re-open row |
| Audit | Weekly dashboard | Top 3 tags driving mark loss |
Classes: C=concept · R=recall · P=process · A=arithmetic · L=reading/logic
B. Why It’s Used
Without closure loop, PYQ volume only repeats errors faster.
C. Mechanism in Words
- Log within 24 h of attempt — memory decays fast.
- One primary tag only — secondary tags go in notes field.
- Write root cause as falsifiable (“confused float with TE” not “didn’t know”).
- Assign corrective action from template library — no blank “study more”.
- Reattempt on spaced schedule: +2d, +7d, +21d until closed.
- Weekly audit: if one tag >30% of errors, that tag gets a dedicated block next week.
D. Core Concept Explanations
D1. Error Taxonomy (Concept, Recall, Process, Arithmetic, Reading)
Concept = wrong rule. Recall = right rule, wrong fact. Process = right rule, wrong step order. Arithmetic = slip. Reading = misread stem/MSQ scope.
D2. Root-Cause Tagging Protocol
Ask: “If I faced this tomorrow, what single fix prevents repeat?” Tag matches that fix type.
D3. Corrective Action Templates
| Tag | Template |
|---|---|
| C | Re-read C-subsection + 3 Q family set |
| R | Flash card + 5 rapid Direct |
| P | Flowchart + 2 Application |
| A | Unit sheet + 5 calc drills |
| L | Highlight stem keywords exercise |
D4. Spaced Reattempt Schedule
+2 days (same variant) → +7 (new PYQ same family) → +21 (mock mix). Close when 2 consecutive correct with time gate.
D5. Weekly Audit Dashboard
Columns: tag count · families affected · marks lost estimate · action assigned. Sort by marks lost.
E. Worked Workflows and Practice Drills
Error: 2023 MSQ PERT — selected path with longest TE instead of zero float.
| Field | Entry |
|---|---|
| Tag | P (process) |
| Root | Confused longest TE with critical path |
| Action | Draw float table for 3 networks; reattempt 2 MSQ +7d |
| Close | Both MSQ correct within 5 min → Closed |
If second reattempt fails → reopen, tag still P, escalate to tutor/video, +7d again.
F. Design Criteria
| Element | Fact |
|---|---|
| Log delay | ≤24 h |
| Reattempt | +2d / +7d / +21d |
Code Comparisons
| Diary | Notebook loop |
|---|---|
| Lists mistakes | Closes them |
G. Application Zones
Every mock → error log → weekly audit → next week’s Tier 2 slots.
H. Common Confusions
- Logging without reattempt = diary, not system.
- Multiple primary tags = unfocused fix.
- “Careless” is not a tag — use A or L.
- Closing after one correct without time gate.
- Ignoring reading errors on MSQ (L tag).
- Audit skipped → same tag repeats weekly.
I. Compare & Contrast
Tag drives action template — not mood.
J. Memory Hooks
Tag before reattempt · Five classes CRPAL · Close or repeat
K. Revision Ladder
Open notebook → process 5 oldest open rows → run audit → assign next week block.
L. Exam Traps
| Trap | Correction |
|---|---|
| No notebook | Start same day |
| Vague root cause | Falsifiable one-liner |
| Re-read whole chapter for one C error | Family drill only |
| Instant reattempt same hour | Spaced schedule |
| Never close rows | Inflated backlog |
| Only NAT errors logged | MCQ −⅓ hurts too |
| Copy answer without method | Log method gap |
| Skip MSQ partial analysis | L tag + option proof |
| Weekly audit optional | Mandatory 30 min |
| Error volume pride | Mark-weighted audit |
M. Answer-Writing Cues
Log entry: “Q[ref] · Tag [ ] · Root: [ ] · Action: [ ] · Reattempt [date].”
Audit: “Top tag [ ] = [%] errors · Next week block = [ ].”
N. PYQ Integration (2007–2026 verified)
| Error hotspot | Typical tag | Fix |
|---|---|---|
| PERT float MSQ | P | Float table drill |
| PCU/ECS swap | C | Compare table |
| U-value units | A | Unit card |
| MSQ over-select | L | Proof-each-option |
O. Mini-Check — Lesson 14.4 (5 Questions)
Q1 (MCQ): Wrong formula but right numbers plugged. Tag? Answer: (a) Concept
Q2 (MCQ): Knew rule, wrong NBC threshold. Tag? Answer: (b) Recall
Q3 (MCQ): Correct method, 10² entered as 1000. Tag? Answer: (d) Arithmetic
Q4 (MSQ): Valid notebook rules? (a) One primary tag (b) Reattempt same hour (c) Spaced schedule (d) Weekly audit (e) Vague “study more”
Answer: (a), (c), (d)
Q5 (MSQ): Row closed when? (a) One lucky correct (b) Two consecutive correct within time gate (c) Never (d) Copy solution
Answer: (b)