Quick Reference
Right ≠ mastered
A lucky guess and a well-reasoned answer can both be “correct.” They should not receive the same confidence rating.
Wrong ≠ one problem
A wrong answer can come from missing knowledge, faulty reasoning, bad method selection, careless execution or failure to retrieve under pressure.
Time is a category
Questions you know but cannot finish quickly enough are performance errors, not simply “careless mistakes.”
Repeated errors matter
When the same mechanism appears three times, stop drilling random questions and repair the mechanism.
1. Record the Mock Before You Review It
Immediately after submitting, write down the raw result and your own experience. Record total score, subject scores, approximate time pressure, sections where you felt rushed, and any questions you remember guessing on. Do this before opening the answer review, because once you see the correct options your memory of the decision process becomes less reliable.
| Metric | What to record | Why it matters |
|---|---|---|
| Total | Correct / attempted | Baseline performance. |
| By subject | Biology, Chemistry, Physics, English, Logical Reasoning | Shows where the largest mark pools are moving. |
| Time | Where you slowed down | Separates knowledge weakness from pacing weakness. |
| Confidence | Sure / 50-50 / guess | Reveals false confidence and lucky answers. |
2. Classify Every Miss
Use a small set of labels so your log remains actionable. The labels below deliberately describe causes, not emotions.
Knowledge gap
The fact, definition or relationship was absent.
Concept gap
The information was known but the underlying relationship was misunderstood.
Method error
The wrong equation, pathway, grammatical rule or reasoning procedure was chosen.
Execution error
Units, signs, arithmetic, wording, bubbles or reading caused the miss.
Retrieval failure
You had learned it but could not retrieve it under exam conditions.
Time failure
You knew enough to solve it but the available time collapsed.
Do not create ten labels. The goal is to make the next action obvious.
3. Review in Three Passes
Pass one: wrong answers. Repair every incorrect item. For each one, write a one-sentence explanation of why the correct option is correct and why your chosen option is not.
Pass two: lucky correct answers. Revisit questions where you guessed or were 50/50. If you cannot explain the answer without the options in front of you, mark it as a retrieval or concept risk.
Pass three: slow correct answers. Find questions that consumed excessive time even though you eventually got them right. These are efficiency problems that can become wrong answers when the paper is harder.
4. Look for Patterns, Not Isolated Mistakes
Suppose your mock contains seven chemistry misses. If the labels are K, C, C, C, M, C, X, the useful finding is not “I got seven chemistry questions wrong.” It is “four misses came from the same concept family.” That should change your next study block.
| Pattern | Interpretation | Next move |
|---|---|---|
| Many K errors in one chapter | Coverage / memory problem | Compact relearn + spaced retrieval. |
| Many C errors | Model of the concept is wrong | Re-teach from first principles, then apply. |
| Many M errors | Method selection is weak | Practice identifying the tool before solving. |
| Many X errors | Execution is unstable | Add a short checking routine and slower final 5 seconds. |
| Many T errors | Pacing or decision process is weak | Use timed sets and skip/return rules. |
5. Track the Trend Across Mocks
One mock can be noisy. A sequence is more informative. Track subject accuracy, repeated-topic errors and time losses across several tests. If a concept that was weak becomes stable in mixed practice, that is evidence the repair worked. If the same error keeps returning, the repair method is probably insufficient.
A simple spreadsheet can contain: date, mock number, total, subject scores, K/C/M/X/R/T counts, top three weak topics, and the repair assigned. You do not need elaborate analytics; consistency beats dashboard decoration.
6. Turn the Diagnosis Into a Seven-Day Plan
After reviewing a mock, choose no more than three repair priorities for the next week. More than that usually turns the plan into a wish list.
- Priority A: the largest recurring concept or knowledge weakness.
- Priority B: the most expensive execution or method error.
- Priority C: the biggest time-management leak.
Then assign each priority a verification test. A repair without verification is a hope. If your weak topic was equilibrium, the verification is not another page of notes; it is a fresh mixed set later in the week where you have to retrieve and apply equilibrium ideas without a chapter label.
Frequently Asked Questions
PM&DC — Public Notice regarding MDCAT-2026 · PM&DC — Uniform Curriculum MDCAT-2025 (official PDF) · PubMed — Testing enhances learning: a review
Scope: scientific explanations are written for student use and simplified where appropriate. Exact exam wording, syllabus scope and current administrative rules should be checked against PM&DC documents.