Recommended resources
The freely available resources this lesson will direct you to.
Hello! In the last lesson, you made active-recall questions and a concise revision sheet for one assessed topic. Now you’ll use those questions under a time limit, without the answers in view. The aim is not just to find out which answers are wrong, but to identify why—so your next study session addresses the right problem.
Allow about 40 minutes, including a 16-minute closed-book attempt. Use a topic from an upcoming university assessment rather than an unrelated coding challenge.
Make the practice resemble the assessment
A question can feel manageable when your notes are beside it and become much harder when you must produce the answer independently. A short, timed attempt exposes that difference while leaving time to learn from it.
Learn How To Ace Every Exam (in 6 minutes)
Watch Learn How To Ace Every Exam (in 6 minutes) from Evolving Medic, MD, for its advice on practising under exam-like conditions and reviewing wrong answers.
Watch timed practice for the idea of matching assessment conditions. Then watch answer review for three initial questions to ask about an error: Did I misread the prompt, overcomplicate it, or lack the knowledge? We’ll use a more precise set of causes after your attempt.
Set up your attempt now. Choose three to five prompts from the question sheet you made last lesson, or use suitable questions supplied for your course. Include at least one prompt that makes you apply the topic—for example, tracing an algorithm or explaining a decision—not only recall a definition. Select an amount you can reasonably attempt in 16 minutes; this is a short practice session, not a full mock exam.
Put your revision sheet, solutions, and other notes out of sight. Keep the questions, blank paper or an answer document, and a timer. Use a calculator or coding tool only if it would be permitted in the assessment you are practising for. Before starting, write down the topic and your start time. These conditions make the result interpretable: a solution found by checking notes during the attempt cannot tell you what you could retrieve unaided.
Run the closed-book attempt
Set a timer for 16 minutes and stop reading this lesson while you work. Answer the selected questions without consulting solutions. Show enough reasoning that you can later tell where an answer went wrong. If you are stuck, record your best attempt, mark the question, and move on; return to it if time remains. When the timer ends, mark where you stopped and write your finish time before opening your notes.
Do not correct your answers yet. A blank response, an uncertain guess, and a confident but incorrect answer provide different clues. Preserving your original attempt helps you distinguish them.
Diagnose the cause, not just the wrong answer
First, compare each response with your verified revision sheet or course solution. Check correct answers too: if you guessed, mark them as uncertain rather than treating them as secure knowledge. For a wrong, incomplete, or uncertain response, locate the first point at which your reasoning departed from a sound solution.
The University of North Carolina Learning Center describes this kind of check as metacognition: asking how you arrived at an answer and what you would do differently next time.
STEM Learning Strategies - The Learning Center
Read the “Metacognition” subsection of UNC’s STEM Learning Strategies for questions that help you inspect your reasoning, rather than simply count wrong answers.
In “Metacognition,” begin with the first paragraph’s discussion of mentally checking your understanding. Read the explanation and reflection questions through the last question, just before “The Study Cycle.” Focus on “How did I get to this answer?” and “What would I do differently?”
For a more specific vocabulary of causes, read the error-type table from Kwantlen Polytechnic University’s Learning Centres.
[PDF] Using Error Analysis Logs to Improve Your Learning
Read the “Basic Error Analysis by General Types” table on page 1. Its categories separate problems with concepts, application, steps, reading, and time—distinctions you can use immediately on your practice attempt.
On page 1, find the table headed “Basic Error Analysis by General Types.” Read the type-remedy rows, beginning with “Categorization Issues” and ending with “Generally,” immediately before the attribution. For now, focus on identifying the cause; the next lesson will address maintaining an error log.
Use the following distinctions to label your own attempt. Choose the primary cause supported by your written work, not a label that merely describes the outcome.
| Primary cause | Evidence to look for |
|---|---|
| Concept gap | You could not explain a necessary idea or condition, even after rereading the question. |
| Wrong application or category | You knew relevant ideas but chose the wrong method for this kind of question. |
| Procedural step | You chose the right method but applied a rule or sequence incorrectly. |
| Reading omission | The needed information was in the prompt, but you overlooked it or failed to answer one of its parts. |
| Time issue | You knew how to proceed but did not reach or finish the question because of your pace. Check whether an earlier concept gap actually consumed the time. |
For example, suppose your binary-search trace starts correctly: with indices 0 through 6, you inspect index 3, then correctly narrow the interval to indices 4 through 6. If you next inspect index 4 rather than the new midpoint, your written steps support procedural step. If instead you did not know why the search could discard part of a sorted list, concept gap is the more useful diagnosis. The same wrong final answer need not have the same cause for every student.
Spend about nine minutes checking and annotating your attempt. Beside each wrong, incomplete, or uncertain answer, write the correct answer or missing step, a primary cause, and one short piece of evidence from your work. If two causes genuinely contributed, note a secondary cause too, but do not let “I made a mistake” stand in for an explanation. Where no solution is available, check against your course material and mark any conclusion you cannot yet verify as unresolved.
Takeaway
You have now practised retrieval under a time limit and examined the result while your reasoning is still visible. A score tells you how many answers need work; a cause tells you whether to revisit a concept, practise a procedure, read prompts more carefully, or adjust your pacing.
Keep your original answers and brief annotations. In the next lesson, you’ll turn those diagnoses into an error log and schedule targeted revision for the patterns that recur.