Mock exams: practice with help, test without it

0:00 Mock exams

Here's a story. A candidate scores seventy-two per cent on his first mock and feels ready. Then he admits something: during the mock, he checked two formulas in his notes. Just two. On his next mock, under strict conditions, he scores sixty-one. That eleven-point gap is the difference between feeling ready and being ready. In this lecture, you'll learn the purpose of mock exams, the rule practise with help, test without it, how to set up realistic conditions, when to take mocks, and how to review a mock step by step.

0:40 Why it matters

Why does this matter? Because a mock exam is the only way to measure your readiness honestly before the real thing. It tests knowledge, but also stamina, pacing, focus and your response to pressure over the full length of the exam. Topic tests can't do that. A well-run mock also reduces anxiety, because exam day becomes familiar rather than frightening. And the review afterwards is one of the most valuable study sessions you'll ever have.

1:13 Practise with help, test without it

Here's the concept: practise with help, test without it. While you're learning, use every aid that helps you understand: notes, textbooks, tutors, AI assistants, explanations. That's good practice. But a mock is a test. Remove every aid. If you use help during a mock, even once, the score overstates your readiness and hides exactly the gaps you need to find. Here's the key idea: an inflated mock score is worse than no score, because it gives you false confidence at the moment you most need the truth.

1:51 The dress rehearsal

Here's an analogy. Think of a dress rehearsal in the theatre. The actors have rehearsed scenes for weeks with scripts in hand and the director stopping them. But the dress rehearsal is different: full costume, full lighting, no stopping, start to finish. It's the only time they find out that the costume change takes too long or the second act drags. A mock exam is your dress rehearsal. If you stop to check your script halfway through, you'll never find the problems that only show up on opening night.

2:30 Realistic conditions

Now realistic conditions. Same length, same number of questions, same timing and breaks as the real exam. Same time of day if possible. Permitted materials only, such as the approved calculator, and nothing else. No notes, no AI assistants, phone in another room. If your exam is online proctored, rehearse that too: clear desk, webcam angle, ID ready. Don't pause the clock. And record your score and time per section before you look at the answers, along with how you felt: energy, focus and anxiety.

3:07 When to take mocks

When should you take mocks? Not too early, when you haven't covered the syllabus and the score just demoralises you. And not only in the final week, when there's no time to act on what you learn. A common pattern is the first full mock after you've covered most of the syllabus, then one or two more spaced across the final weeks, with at least several days between them to fix what each one reveals. Check that your final mock is a few days before the exam, not the day before, so you can rest.

3:48 Worked example 1: Dubai candidate (illustrative)

A simple worked example. A candidate preparing for a management accounting certification in Dubai scores seventy-two per cent on his first mock, but realises he checked two formulas in his notes during the test. On his second mock, under strict conditions, he scores sixty-one. The honest score reveals gaps in two areas that he then targets. By his fourth strict mock, he's consistently above his target, and he passes the real exam.

4:19 Worked example 2: Amina in Lahore (illustrative)

Now a realistic scenario, illustrative. Amina is preparing for a project management certification in Lahore. Her first strict mock is sixty-four per cent against a target she set of seventy-five. She resists the urge to immediately take another mock. Instead she spends four hours reviewing it with the template. She finds her lowest domain carries a large weight, that eleven errors were misread questions, and that she was ten minutes behind at the halfway checkpoint. She sets three fixes: fifty interleaved questions in that domain, underlining qualifiers, and a pacing rule. Her second mock, ten days later, is seventy-three. Her third, seventy-nine.

5:03 Reviewing a mock

Reviewing a mock is where the value is. Do it within forty-eight hours, while you remember your thinking. Look at your score by domain against the weights. Count errors by type. List confident errors. Check your pacing against checkpoints. Then choose just three fixes before the next mock. Not twenty. Three, specific and actionable. For example: forty interleaved questions on domain C, underline qualifiers in every stem, and flag any question after two minutes. Then schedule the next mock far enough away to actually make those fixes.

5:41 Watch me: mock review

Watch me do it. I fill in the mock review template for an illustrative mock. Score: sixty-eight per cent, against a target of seventy-five. Time left at the end: none, and I rushed the last eight questions. By domain: A seventy-five, B seventy, C fifty-five, D eighty. Domain C carries twenty-five per cent of the weight, so it's my first fix. Errors by type: six knowledge, five misread, three calculation, four time pressure. Confident errors: four, three of them in C. Three fixes: domain C interleaved practice, a pacing rule at the halfway checkpoint, and a formula recall routine. Next mock: in twelve days.

6:26 Using mocks to judge readiness

How do you use mocks to decide whether you're ready? Look for a pattern, not a single score. Several strict mocks at or above your target, a margin above any published pass mark, no domain far below the rest, and finishing with time to spare. Check that your strict mock scores are consistent, not swinging wildly. And be honest about quality: a mock from a reputable source, taken strictly, is evidence. A mock taken with peeks isn't. If the evidence isn't there, it may be wiser to adjust your plan or your date.

7:06 Common mistakes

Common mistakes. Taking mocks with notes or AI open. Pausing the clock. Taking mocks too early or only on the last day. Taking mock after mock without reviewing. Checking answers before recording your score and timing. Choosing twenty fixes instead of three. Using the same mock twice and trusting the score. And taking a mock the day before the real exam, which tires you and can shake your confidence for no benefit.

7:37 Recap and try this now

Let's recap. Mocks measure readiness honestly, if you practise with help and test without it. Mirror the real exam's length, timing, materials and set-up. Take your first mock after covering most of the syllabus, and space the rest. Review within forty-eight hours, by domain, error type, confidence and pacing, and choose three fixes. Your try this now: schedule your next strict mock in your calendar at the same time of day as your exam, print the protocol from the lesson, and prepare the review template. Next, we'll turn your data into decisions with a readiness dashboard.