Why solution worship fails
Reading explanations feels productive. It rarely changes the next mock’s eye movement. VARC improvement needs a forensics sheet, not a story you agree with.
The one-page mock forensics sheet
For each RC set, record:
- Finished? (Y/N)
- Spine correct? (write yours vs ideal one-liner)
- Top trap (S/R/H/P)
- Regressions (count)
- Stem type (detail / inference / tone / purpose)
Five fields. Two minutes per set. Patterns emerge by the third mock.
Classify misses without drama
- Spine miss: you misunderstood the argument’s pivot.
- Stem miss: spine okay; hinge word misread.
- Trap miss: spine and stem okay; option seduced you.
- Time miss: knew the idea; clock killed the loop.
Different misses need different drills. Trap misses need elimination reps. Spine misses need tagging paragraphs. Time misses need forward pacing—not more vocabulary.
The regression column is non-negotiable
If regressions rise on hard passages, your “accuracy problem” may be a throughput problem. Fix movement before debating answer choices.
Do not aggregate too early
A single mock is noise. Four mocks reveal whether your traps cluster on inference or on detail. Train the cluster.
Prescription mapping
| Pattern | Prescription | |--------|----------------| | High regressions | Forced-forward drills, shorter blocks | | Inference traps | Predict-before-options sets | | Detail traps | Stem highlighting, not faster reading | | Time misses | Attempt budget down, triage up |
Coach vs self-review
Coaching explains traps beautifully. Self-review counts them. You need both, but counting comes first—otherwise you admire the trap without avoiding it next week.
Weekly rhythm
- Mock weekend
- Forensics Monday
- Drill Tuesday–Thursday (one pattern only)
- Light prose Friday
- Repeat
Mocks are expensive. Analysis is how you stop paying twice.