Guide
Why practice problem questions beat passive revision (and how to get useful feedback)
Reading model answers is not the same as writing them under pressure. Build a weekly PQ habit, know what “good” feedback looks like, and use tools that comment on your wording—not someone else’s.
Published 18 March 2026
You already know you "should" do past papers. The trap is stopping after you skim the examiner report—or worse, reading a model answer while telling yourself you "would have got there." In the hall, there is no narrator: you either select issues, state law cleanly, and apply it to ugly facts, or you do not. Passive revision exaggerates ability; timed drafting reveals it.
What moves marks is frequency + specificity. Frequency comes from short, repeated sessions. Specificity comes from feedback that says, in effect: your Issue framing is fuzzy here; your Rule is over-long; your Application narrates instead of testing. That is a different product from a chatbot that writes a fresh answer you cannot safely submit. IRAC Coach is intentionally the first kind—coaching on your attempt.
Make this week’s PQ count for something measurable
Upload a timed attempt while it is still fresh. You will see where your IRAC legs are uneven, what to rewrite first, and what a strong snippet in that section tends to look like—for your fact pattern, not a generic paragraph.
Ideal after weekly past-paper reps. Pair with your module’s learning outcomes so you stay syllabus-honest.
Passive vs active revision
Highlighting notes feels productive; it rarely rehearses selection under uncertainty. A written attempt forces issue-spotting, authority selection, and application in one pass—the bundle your degree actually grades.
What useful feedback looks like
Praise without location is useless. Useful feedback ties comments to structure: does IRAC hang together? Is Rule doing too much? Does Application use the test you stated? If tutors are oversubscribed, a tool that returns section scores and rewritable prompts can keep the cadence high—provided your institution allows that workflow.
If Application keeps coming back "thin," drill it deliberately with our Application deep-dive.
A routine that survives term-time chaos
- One question, exam-realistic timer, no mid-sentence polishing.
- Note where you hesitated before you peek at any notes.
- Compare your issues and application moves to structured feedback—not only to a model skeleton.
- Rewrite the weakest IRAC leg only, then repeat the full question later in the week.
As exams approach, stack in time-pressure tactics so the routine holds when adrenaline arrives.
Stop guessing whether this week’s draft improved
Run the same PQ twice in a fortnight with feedback between attempts—you should see Application depth and issue confidence shift before your marks even come back.
