Professional Certification Exam Success · Practice questions and mock exams · lesson 10 of 21 · 12 min

Analysing results and adjusting your plan

Data-driven preparation

By the exam readiness phase, you have a lot of data: topic scores, mock results, error logs and confidence ratings. Using this data to adjust your plan is what separates efficient preparation from simply working hard.

Build a readiness dashboard

Readiness dashboard (illustrative)
                         Week 8   Week 10   Week 12   Target
Mock score               —        62%       71%       ≥ 75% (comfort margin)
Weakest domain score     —        48%       60%       ≥ 65%
Confidently wrong / mock —        14        8         ≤ 5
Time left at end         —        −3 min    +4 min    ≥ +5 min
SRS cards due daily      45       60        40        manageable
Error log items open     35       28        15        < 10

A dashboard shows whether you are converging on readiness and where to focus.

The 80/20 of final preparation

In the final weeks, prioritise:

High-weight domains where you are weak.
Recurring errors from your log.
Timing and technique issues.
Formulas and key rules you must recall instantly.

Resist the urge to "finish the textbook" or chase obscure topics with low weighting.

Deciding whether you are ready

Consider:

Are mock scores consistently above the passing standard with a margin (recognising that mocks are estimates)?
Are all domains at an acceptable level, or is one weak area pulling you down?
Are you finishing on time?
Do you feel you could explain core concepts without notes?

If the answers are mostly no with a week to go, consider whether rescheduling is possible and sensible. Check the awarding body's rescheduling rules, fees and deadlines well in advance. Sometimes a short delay with a focused plan is better than a rushed attempt; sometimes sitting the exam is wise because the experience itself is valuable and delays drain motivation. Decide deliberately, not in panic.

Adjusting the plan: a weekly review routine

Every week, spend 30 minutes:

Update the dashboard.
Identify the two biggest gaps.
Plan specific actions (questions, topics, techniques) for the next week.
Remove low-value activities.
Check wellbeing: sleep, stress, workload.

Worked example

Illustrative. A candidate in Islamabad preparing for an internal audit certification had mock scores rising slowly but one domain stuck below 50%. His dashboard showed that errors in that domain were mostly misapplication between two similar concepts. He created a comparison table of the two concepts, did 40 interleaved questions contrasting them, and explained the difference to a study partner. His domain score rose above 65% in the next mock, lifting his overall score above his target.

Plateaus

Scores often plateau for a while. Plateaus usually mean you need a different approach, not just more of the same: switch from reading to questions, from blocked to interleaved practice, from untimed to timed, or seek help from a tutor, mentor or study group on a stubborn topic.

Hands-on: build a readiness dashboard in a spreadsheet

Create one sheet with your raw data (question sets and mocks) and one "Dashboard" sheet.

Raw data columns: date, type (set/mock), domain, questions, correct, minutes, confident errors, error type counts.

Dashboard formulas (Google Sheets / Excel; adjust ranges):

Latest strict mock %:          =INDEX(Mocks!F:F, COUNTA(Mocks!F:F))
Average of last 3 mocks:        =AVERAGE(INDEX(Mocks!F:F,COUNTA(Mocks!F:F)-2):INDEX(Mocks!F:F,COUNTA(Mocks!F:F)))
Domain accuracy (domain in A2): =SUMIF(Sets!C:C,A2,Sets!E:E)/SUMIF(Sets!C:C,A2,Sets!D:D)
Weighted gap (weight in B2):   =B2*(1-C2)            (sort descending: top = biggest risk)
Seconds per question:           =SUM(Sets!F:F)*60/SUM(Sets!D:D)
Open error-log items:           =COUNTIF(ErrorLog!J:J,"No")

Add a line chart of mock scores with your target as a second series, and conditional formatting that turns any domain below target red.

Weekly review routine (20 minutes, same time each week):

1. Update the data. 2. Read the dashboard: what moved? what didn't?
3. Pick the top weighted-gap domain and the most common error type.
4. Decide 1–3 changes to next week's plan (not more).
5. Write one sentence: "Am I on track for the exam date? If not, what changes?"

Readiness decision (final weeks): several strict mocks at or above your target with a margin over any published pass mark, no domain far below the rest, finishing on time, and falling confident errors. If not, adjust scope, add targeted hours, or consider moving the date while the awarding body's rules allow.

Common mistakes

Ignoring data and studying what feels comfortable.
Trying to cover everything equally in the final weeks.
Treating one mock score as definitive.
Making rescheduling decisions in panic at the last minute.
Continuing the same method during a plateau.

Quick self-check

Build your readiness dashboard today with whatever data you have. What are the two biggest gaps, and what will you do about each this week?

Using peers and tutors for feedback

Data from your own practice has limits. For written answers or complex judgement questions, ask a tutor, mentor or study partner to review a sample and explain what they would change. External feedback often reveals blind spots, such as consistently answering from the wrong perspective or missing the requirement, that self-review misses.

Worked example: adjusting the final three weeks

Illustrative. Three weeks before her exam, a candidate's dashboard showed a mock score of 70% against a target of 75%, with timing fine but one domain at 55%. She moved all new-content study to that domain for one week (80 targeted questions, comparison tables and two tutor sessions), kept a daily flashcard habit for other domains, and took a strict mock at the end of week two. The weak domain rose to 68% and her overall score to 76%, and she used the final week for light mixed review and rest.

Video lecture: Analysing results and adjusting your plan

Lecture coming soon · 13 chapters · about 8 minutes. Read the full transcript below.

Analysing and adjusting
Why it matters
The readiness dashboard
The approach panel
The 80/20 of final prep
The weekly review (20 minutes)
Worked example 1: Islamabad candidate (illustrative)
Worked example 2: Sophie in Manchester (illustrative)
Breaking plateaus
Watch me: the dashboard
Am I ready?
Common mistakes
Recap and try this now

Lecture transcript

Analysing and adjusting

Here's a question that keeps candidates awake at night: am I ready? Most people answer it with a feeling. I think I'm nearly there. I'm not sure. I feel behind. But feelings are unreliable, especially under stress. Your practice data can give you a much better answer. In this lecture, you'll learn how to build a readiness dashboard, focus on the twenty per cent of work that drives most of your final improvement, decide whether you're ready, run a weekly review, and break through plateaus.

Why it matters

Why does this matter? Because in the final weeks, time is your scarcest resource. Every hour has to go where it will make the biggest difference to your score. Without data, candidates tend to study what they enjoy or what they already know, because it feels good. With data, you can see which high-weight domain is weakest, which error type keeps repeating, and whether your pace is on track. Data turns anxiety into a plan.

The readiness dashboard

Here's the concept: a readiness dashboard. It needs only a few numbers. Your latest strict mock score, and the average of your last three. Accuracy by domain, set against each domain's weight. Your weighted gap, which is weight times the percentage you're missing, so the biggest risks rise to the top. Your average time per question against the pace you need. Your confident errors. And your open error-log items. Here's the key idea: you're not collecting data for its own sake. Every number should lead to a decision about next week.

The approach panel

Here's an analogy. Think of a pilot's instrument panel on approach to landing. The pilot doesn't check every instrument equally. They focus on a few that matter most right now: altitude, speed, heading, and the glide path. If one drifts, they make a small correction early, rather than a big one at the last second. Your dashboard is your approach panel. In the final weeks, check a few key instruments every week, and make small, early corrections.

The 80/20 of final prep

Now the eighty-twenty of final preparation. In the final weeks, most of your remaining improvement usually comes from a small number of things. High-weight domains where you're weak. Recurring error types, like misreading questions or calculation slips. Timing problems. And must-know formulas and rules you keep forgetting. Notice what's not on the list: rereading everything, starting new resources, or perfecting domains you're already strong in. Treat the eighty-twenty as a rule of thumb, not a law. But it's a good guide to where your hours should go.

The weekly review (20 minutes)

Next, the weekly review. Twenty minutes, same time every week. Update your data. Read the dashboard: what moved, and what didn't? Pick the top weighted-gap domain and the most common error type. Decide one to three changes to next week's plan. Not more. Then write one sentence: am I on track for my exam date, and if not, what changes? That sentence matters. It forces an honest decision early, instead of a panicked one late.

Worked example 1: Islamabad candidate (illustrative)

A simple worked example. A candidate in Islamabad preparing for an internal audit certification has mock scores rising slowly, but one domain is stuck below fifty per cent. His dashboard shows that most errors in that domain are misapplication between two similar concepts. He creates a comparison table of the two, does forty interleaved questions contrasting them, and explains the difference to a study partner. His domain score rises above sixty-five per cent in the next mock, lifting his overall score above his target.

Worked example 2: Sophie in Manchester (illustrative)

Now a realistic scenario, illustrative. Sophie is preparing for a finance certification in Manchester, three weeks before her exam. Her dashboard shows: last three mocks averaging sixty-eight per cent, target seventy-five. Her largest weighted gap is a domain worth twenty per cent where she's at fifty-eight per cent. Her most common error type is calculation slips. And her pace is fine. She drops a planned re-read of the whole syllabus. Instead: ten hours on the weak domain, a checking routine for every calculation, and daily formula recall. Her final two mocks are seventy-six and seventy-nine per cent.

Breaking plateaus

Plateaus happen to almost everyone. Scores stop rising for a couple of weeks and motivation drops. Before you panic, check a few things. Is your practice still challenging, or are you repeating familiar questions? Are you reviewing properly, or just doing volume? Is one error type dominating? Are you tired? The fix is usually a change of method, not more of the same: switch from blocked to interleaved practice, attack the top error type, get feedback from a tutor or peer, or take a genuine rest day. And look at the trend over several weeks, not day to day.

Watch me: the dashboard

Watch me do it. I build an illustrative dashboard. On the raw data sheet, I have twenty question sets and three mocks. On the dashboard sheet, I calculate the average of the last three mocks: sixty-nine per cent. Then domain accuracy with SUMIF: correct divided by questions for each domain. Then the weighted gap: weight times one minus accuracy. I sort by weighted gap. Domain C rises to the top, with a gap of about nine points of weight. I add conditional formatting so any domain below my target turns red. Then I write my one sentence: not yet on track; ten extra hours on domain C this fortnight.

Am I ready?

Deciding whether you're ready is the final use of your dashboard. Look for several strict mocks at or above your target, with a margin over any published pass mark. No domain far below the rest. Finishing on time. Confident errors falling. If that's your picture, trust it, and use the final days to consolidate and rest. If it isn't, it's not a failure to adjust: you might narrow your focus, add targeted hours, or consider moving your exam date, if the awarding body's rules and fees allow. Decide with the data, and decide early.

Common mistakes

Common mistakes. Deciding readiness by feeling alone. Tracking only overall scores and missing a weak heavy domain. Collecting data without changing the plan. Making ten changes at once. Polishing strong domains because it feels good. Starting new resources in the final weeks. Panicking over one bad mock instead of looking at the trend. And leaving the decision to move an exam until it's too late to do so without penalty.

Recap and try this now

Let's recap. Replace feelings with a simple readiness dashboard: mock averages, domain accuracy against weights, weighted gaps, pace, confident errors and open error-log items. Focus final weeks on the eighty-twenty. Review weekly, make one to three changes, and write your one honest sentence. Break plateaus by changing method. Decide readiness with data, and early. Your try this now: build the dashboard in the lesson with your current data and run your first twenty-minute weekly review this weekend. Next module: exam technique by question type.

Key takeaways

Track readiness with a dashboard: mock scores, weakest domain, confident errors, timing and open error-log items.
In the final weeks, prioritise high-weight weak domains, recurring errors, timing and key formulas.
Decide deliberately about readiness and rescheduling, knowing the rules and deadlines in advance.
Break plateaus by changing method, not just adding hours.

Try it

Create a readiness dashboard with your current data and complete a 30-minute weekly review routine, writing actions for your two biggest gaps.