Mock exam analysis, step by step: turning a score into a plan

Why analysis matters more than the score

A mock is a rehearsal and a test, but mostly it is a source of data. The score is the least useful number in it. Two people with the same score may need completely different weeks of study. A systematic analysis tells you which.

Plan for the analysis to take about as long as the mock itself. For a three-hour mock, set aside two to three hours the next day. The mock tests guide covers when to start.

Step 1: score by domain

Look at your percentage in each domain, not just overall. Find the lowest two or three, and check how far the lowest is from the others. A big gap points to a content problem in one area. If every domain is similar and your score is lower than you want, the issue is more likely technique or timing. Performance analytics shows the breakdown for each attempt.

Step 2: time

Split the exam into blocks, for example every 25 questions in a 150 question exam, and note how long each block took. Look for two patterns. A fast start and a slow middle suggests you got stuck on hard items. A steady pace with a rush at the end suggests you spent too long early. The time management guide offers targets for each block.

Step 3: sure but wrong

If you rated your confidence, count the questions you were sure about and got wrong. These are your most useful items. They show beliefs that need correcting. If you did not rate confidence in the mock, think back and mark the ones that surprised you.

Step 4: answer changes and flags

If your platform records answer changes, count how many went from wrong to right and how many from right to wrong. If right-to-wrong changes outnumber the others, you are over-editing out of doubt, and the fix is to change an answer only when you can state a reason. Also look at flagged questions: what share did you get right when you came back to them?

Step 5: classify each miss

Go through every wrong answer and assign one cause: knowledge gap, misread, rushed or guess, as in the error log. Count the causes. The biggest group is your main target. A mock where most misses are misreads calls for technique practice. A mock where most are knowledge gaps calls for topic review.

Step 6: three fixes

Choose only three. For example: repair fluids and electrolytes with 60 questions and 10 cards; read the last line of each stem first; and take the next mock with a 20-minute buffer for flagged questions. Write them at the top of your plan. The next mock then tests whether the fixes worked.

A worked analysis of one mock

Say you scored 64 percent on a 150-question mock. By domain: fundamentals 72, infection control 70, pharmacology 55, medical-surgical 66, cardiorespiratory 58, emergency 62, maternal 68, mental health 60, ethics 74, public health 64. Pharmacology and cardiorespiratory stand out. By time, you took 38 minutes for the first 25 questions, 30, 29, 31, 28 and 22 for the last stretch, finishing with 25 minutes to spare. You started slowly and ended rushed, so the first block ate time. You were sure but wrong on 14 questions. You changed 12 answers, with five wrong-to-right and seven right-to-wrong.

The findings translate into fixes: do a pharmacology and cardiorespiratory repair week; aim for 30 minutes per 25 questions from the start, flagging early; and stop changing answers without a stated reason. Of the 14 sure-but-wrong items, review each belief that led you astray. The numbers are invented for illustration.

Handling a disappointing mock

A low score hurts. Wait an hour before analysing, and then treat it as data. A mock a few weeks before the exam is supposed to find your weak points. Remind yourself that scores vary with set difficulty, tiredness and luck, and compare trends over several attempts. If the result frightens you, talk to a colleague or mentor, then go back to your three fixes.

A spreadsheet that does the counting

A simple sheet saves time. Columns: question number, domain, your answer, correct answer, right or wrong, confidence, time taken if recorded, flagged, changed, cause. After the mock, fill in the right-or-wrong column from your results, add confidence if you rated it and add causes for the wrong ones. Then use a pivot table or simple filters to count wrong answers by domain, by cause and by confidence. This takes thirty minutes the first time and fifteen after that, and it converts a pile of impressions into numbers you can trust.

If you prefer paper, a page divided into four boxes works: domains, time, confidence and causes. Fill each box with the counts. The aim is the same.

The second mock tells you more than the first

The first mock gives you a baseline and often a shock. The second shows whether your fixes work. Put the three fixes at the top before you sit it, and check each one afterwards: did the weak domain improve, did the pacing hold, did the sure-but-wrong count fall? If a fix failed, ask why before choosing another. Sometimes the fix was too vague, for example “revise pharmacology” instead of “do 60 pharmacology questions and make 20 cards”.

Scheduling mocks and analysis in your calendar

Plan the mock and its review as a pair. A three-hour mock on Saturday morning, a rest day, and a two-hour analysis on Monday works for many people. Book both slots at the start of the week. Do not run a mock when you are unusually tired or ill, since the result will mislead you. After the analysis, update the plan for the week at once, while the findings are fresh.

Using platform data

If your question platform shows time per question, domain breakdowns and attempt history, use them. In Meddex, the results report shows domain-wise performance, time analysis and a comparison across attempts, which makes steps one, two and the comparison table quicker. The causes of error and your confidence ratings still need your own judgment, because the platform cannot know why you chose an option. Combine the data with your own notes for the best picture.

Sharing your analysis with a mentor

If you have a mentor, a colleague or a study partner, bring them your three fixes and the numbers behind them. A second opinion can catch a misdiagnosis, such as calling a knowledge gap a technique problem. Keep it brief: five minutes, one page. Ask what they would try first and why, then decide for yourself.

Notes to keep after each mock

After the analysis, write a short note for your future self: the score, the weakest domain, the main cause of error, the three fixes and a line on how you felt. Read the notes before your next mock and again in the last week. They remind you what has worked and what has not, and they show your progress in a way a single score never does.

Compare attempts

Keep a simple table: date, score, weakest domain, main error cause and the three fixes. After the second and third mock you can see whether the weakest domain moved and whether the main cause changed. If it did not, change the fix, not just the effort. Do not judge by one mock, because difficulty varies from set to set.

Frequently asked questions