A mock score is incomplete feedback until it becomes next week’s calendar. Here’s the handoff from percentage → error log → focus list → scheduled repairs.
The most expensive study session of the month ends with a number. Then life continues. The number becomes a vibe: proud, ashamed, or numb. By Thursday the vibe is gone and the misconceptions remain.
Hattie and Timperley’s feed-forward question — where to next? — is the missing half of every mock. Zimmerman’s self-regulated learning cycle demands a reflect → plan transition. This article is that transition as a checklist.
The 24-hour rule
Within a day of the sit (while your thinking is still recoverable):
- Mark cold
- Build or update the error log (misconception / slip / time / gap)
- Star high-weight misses
- Cap next week’s repair queue at 3–5 items
- Assign methods and durations
- Place them on the calendar before you open entertainment
If step 6 fails, the mock mostly bought emotion.
| Score artifact | Plan artifact | If you stop early |
|---|---|---|
| Percentage | Mood | No behavior change |
| Error log | Diagnosis | Still no sessions |
| Focus list + methods | Intention | Intention dies |
| Calendar blocks | Behavior | Learning can move |
Different errors, different weeks
A week of more papers will not fix a misconception. A week of only re-reading will not fix a time fault. Match method to type or the plan is cosplay.
Method menu (paste beside your planner)
- Misconception → guide/tutor encode + generative notes + teach-back
- Slip → targeted retrieval + similar item later
- Time fault → timed section + triage rules drill
- Gap → prerequisite encode loop before another full paper
Write the method on the focus line itself: Acid buffers — misconception — guide encode 45m — teach-back. Vague lines (“study buffers”) invite vague weeks.
Sample seven-day plan after a messy mock
- Day 0 evening: log + focus list (30–40m)
- Day 1: deep encode on top misconception (45m)
- Day 2: retrieval block including slip items (20m)
- Day 3: comparison practice on near-twin confusion (30m)
- Day 4: timed section for pacing (35m)
- Day 5: mixed questions on starred concepts (30m)
- Day 6: light retrieval + sleep
- Day 7: micro teach-backs; decide if another full paper is earned
“Earned” means open misconceptions were actually repaired on production checks — not merely scheduled.
Score chasing
Sitting another full paper immediately to ‘get a better number’ often skips the only phase that raises the next number: repair. Patience here is performance later.
Prioritize by weight, not by shame
Students often repair the miss that embarrassed them most, not the miss that costs the most marks. Invert that. Star syllabus-heavy, high-frequency themes first. Put ego injuries second unless they are also high-weight.
A quick sort:
| Miss profile | Priority | Why |
|---|---|---|
| High-weight + misconception | P1 | Biggest next-score lever |
| High-weight + time fault | P1/P2 | Marks left on the table |
| Low-weight + slip | P3 | Cheap retrieval fix later |
| Prerequisite gap under many items | P0 | Unlocks multiple repairs |
Use dashboards without worshipping them
Update focus topics from the log. Check whether mastery signals move after repairs. If dashboards stay red while you “followed the plan,” your methods are wrong or your production checks are dishonest — change methods, don’t only add hours.
Parents and teachers
Share the plan language (“three repairs, scheduled”) instead of only the percentage. Percentages invite judgment. Plans invite support.
Ask: “What’s the top misconception and when is the encode block?” That question is more useful than “Are you disappointed?”
Fine scores still need a plan
A 78% with two fragile near-twins can become a 60% under a nastier paper. Log near-misses and time stress even when the headline feels fine.
Mocks that steer the week
Sukrat Mock Exams plus Study Planner and Dashboards are built for this handoff — score → focus → calendar. Product page: /products/features/mock-exams
Write the plan where you will see it
The focus list belongs on the planner, not in a chat transcript. Each line should survive a tired Tuesday:
Concept � error type � method � duration � done check
Example: Buffer curves � misconception � guide encode 45m � 90s teach-back
If a line cannot fit that template, it is not ready to schedule. Vague intentions are how mock insight evaporates by Wednesday. After Day 7 teach-backs, strike closed items and decide whether a section or another full paper is earned � earned means production checks passed, not vibes improved.
FAQ
What if the score was fine?
Still log near-misses and time stress. Fine scores hide fragile edges. Convert those edges into light retrieval and one mixed set — not complacency.
What if everything failed?
Prerequisites and highest-weight topics only. A tiny honest plan beats a fantasy overhaul. One repaired pillar beats twelve untouched collapses.
Can AI draft the week?
Yes as a draft after you classify errors. You must still place calendar armor and do the production checks. Do not outsource the classification step.
How soon until another full paper?
After focus items pass production checks — often 5–10 days mid-term, sometimes longer after a schema wipeout. Sections can bridge earlier.
What if I don’t have time for a seven-day plan?
Keep the 24-hour rule and three focus items. Compress days; do not skip the log → calendar handoff.
Related reading
- Error Logs After Mock Exams
- How Often to Sit Full Papers
- Full Papers Train Transfer
- Weekly Review
- How to Use a Focus List
- Timed Practice Builds Exam Stamina
Keep going across Sukrat
The score is the start
Mocks are diagnostic instruments. The percentage is a headline; the week that follows is the article.
Log errors. Cap the focus list. Match methods. Put repairs on the calendar. Re-check with production before you chase another sit.
If the plan never becomes a Tuesday block, the mock never became learning.