How to run a weekly MRCPCH revision review

Run a weekly MRCPCH revision review by comparing the week's plan with evidence from actual study: syllabus coverage, first-seen question performance, repeated error causes, delayed retrieval, unfinished review and available time. Keep what worked, identify one main constraint, and convert it into a small number of specific actions for the next seven days. Do not rewrite the entire timetable after one poor session or carry forward every missed task unchanged.

A weekly review is the steering mechanism between a long-term plan and daily revision. It should produce decisions, not a diary of everything that happened. The useful output is a shorter, more realistic next-week plan based on what the candidate can now retrieve, apply and sustain.

This guide is for Foundation of Practice (FOP), Theory and Science (TAS) and Applied Knowledge in Practice (AKP) preparation. The framework is a PaedVault editorial tool, not an RCPCH requirement, and it contains no clinical instruction.

The direct answer: review evidence, then change one constraint

At the same point each week, answer five questions:

1. What did I actually complete?
2. What evidence shows learning rather than exposure?
3. Which error or bottleneck repeated?
4. What changed in my available time or exam context?
5. What are the few next actions that follow from this evidence?

Use the answers to preserve, stop, reduce, increase or reschedule work. A review that produces no change may still be valid when the plan is working. A review that changes everything every week usually destroys continuity.

A revision plan is a hypothesis about what will help. The weekly review tests that hypothesis against coverage, retrieval, question reasoning and real capacity.

RCPCH publishes the current syllabus and question formats, but it does not prescribe weekly study reviews, topic quotas or timetable templates. The method below is an evidence-informed planning system rather than official examination guidance.

Why review weekly rather than plan once?

An eight-week or twelve-week plan is created with incomplete information. The candidate does not yet know:

• which topics will produce recurring errors;
• how long careful question review will take;
• how shifts and other commitments will affect capacity;
• which resources will prove useful;
• whether retrieval survives a delay; or
• when timed practice should replace focused repair.

Without a review point, the original plan becomes a backlog. Missed work is pushed into the next week, strong topics keep receiving habitual attention, and weak areas remain labelled broadly rather than diagnosed.

A weekly interval is a practical editorial choice, not a research-defined optimum. It is long enough to collect several study observations and short enough to correct direction before a large part of the preparation period has passed.

The adaptable eight-week MRCPCH plan provides a longer horizon; the weekly review exists to revise that horizon without abandoning it.

What self-regulated learning research supports

Planning, monitoring and reflection form a cycle

A 2026 systematic review included 45 observational studies and 15,100 health-professions students. Self-efficacy, strategic approaches, behavioural regulation, metacognitive monitoring and autonomous motivation were among factors associated with better academic outcomes. The authors emphasised variation in study quality and called for longitudinal intervention research, so the associations should not be treated as proof that one weekly template causes higher scores.

A separate meta-analysis of 61 studies in undergraduate and graduate medical education found a positive association between self-regulated learning strategies and overall learning outcomes. The association was stronger for affective outcomes than for test scores and other outcomes. This supports a planning-monitoring-adjustment cycle, but it does not validate a particular MRCPCH checklist.

Self-regulation can be trained

A meta-analysis of 49 university-student studies found that extended self-regulated learning programmes improved academic performance, learning strategies and motivation on average. Effects varied by training design and student characteristics. Programmes that included feedback, learning protocols or other forms of metacognitive support showed different patterns of benefit.

The practical implication is not that candidates need a complex productivity system. A short, repeated protocol can prompt the important behaviours: set a goal, inspect evidence, adjust the method and allocate resources.

Reflection without a decision is incomplete

A systematic review of self-regulated learning in clinical contexts identified goal setting, monitoring, coaching, learning plans and supportive tools, while also noting limited support for self-evaluation in the included interventions. The clinical workplace differs from independent MRCPCH revision, but the limitation is useful: recording an experience is not the same as deciding what to do next.

For exam preparation, every reflection should end with an observable next action.

Use the RESET weekly review

RESET is a PaedVault editorial framework:

1. R - Record what happened
2. E - Evaluate learning evidence
3. S - Select the main constraint
4. E - Engineer the next week
5. T - Trigger the next review

R - Record what happened without reconstructing the whole week

Use existing evidence rather than writing a long narrative. Collect:

• planned and completed sessions;
• syllabus areas attempted;
• number of first-seen questions completed and reviewed;
• recurring error categories;
• delayed retrieval checks;
• timed-practice observations;
• unfinished feedback or review debt; and
• material changes in shifts, leave or other commitments.

Keep volume separate from learning. "Completed 120 questions" describes activity. "Three interpretation errors repeated in mixed sets, and two corrected principles were retrievable four days later" describes evidence.

Do not penalise a deliberately smaller week that completed its learning loops. The daily question-target guide explains why question count should follow review capacity rather than act as the main achievement measure.

Use a minimum data set

Area	One useful measure
Coverage	Syllabus units sampled or repaired
Retrieval	Delayed prompts answered without notes
Questions	First-seen attempts with review completed
Errors	Causes that repeated, not only wrong totals
Timing	Where pace or attention deteriorated
Capacity	Planned sessions that were realistically available
Debt	Important feedback still unresolved

More tracking is not automatically better. If a field never changes a decision, remove it.

E - Evaluate evidence of learning

Ask whether the week's activity improved one or more of these:

• breadth across the current syllabus;
• retrieval after a delay;
• discrimination between plausible options;
• reasoning on first-seen questions;
• explanation of incorrect and uncertain answers;
• timing stability; or
• consistency under the week's real working conditions.

Compare similar evidence. A short focused repair set should not be compared directly with a full mock score. A familiar repeated set should not be treated like first-seen mixed questions.

Use confidence as a second signal

For each important result, compare confidence with performance:

• high confidence and correct reasoning: likely maintenance;
• low confidence and correct reasoning: knowledge may be usable but not yet trusted;
• high confidence and incorrect reasoning: priority calibration problem;
• low confidence and incorrect reasoning: visible gap requiring support.

The confidence-calibration guide provides a fuller method for finding confident errors and correct guesses.

Separate an outcome from its cause

"Score fell" is an outcome. Possible causes include:

• a broader or harder set;
• incomplete topic coverage;
• repeated knowledge gaps;
• misreading the lead-in;
• answer changes without evidence;
• time pressure;
• rushed feedback; or
• poor study conditions.

Choose the next action from the most plausible repeated cause, not from the emotion created by the score.

S - Select one main constraint

The weekly plan usually fails at one dominant point. Examples include:

• too many new questions for the available review time;
• weak syllabus coverage despite high question volume;
• repeated errors left as isolated notes;
• no delayed retrieval;
• overlong sessions after shifts;
• resource switching;
• timed blocks introduced before reasoning is stable; or
• a schedule that assumed capacity that never existed.

Name the constraint in operational language:

• weak: "I need more discipline";
• stronger: "Two of four sessions ended with explanations unread because each set was too large."

The stronger statement suggests a testable change: reduce each set, protect review time and measure whether review debt falls.

Do not select five main constraints. Secondary issues can be parked for later unless they prevent the primary change.

E - Engineer the next seven days

Build the next week from actions, not intentions. Each action needs:

• a task;
• a boundary;
• a trigger or placement;
• evidence of completion; and
• a fallback version.

Example:

Element	Plan
Task	Repair the repeated interpretation error
Boundary	Two sets of eight first-seen questions
Placement	Tuesday and Friday before new-topic work
Completion evidence	Every error reviewed and retested
Fallback	One set of five plus a delayed retrieval prompt

The fallback prevents one disrupted day from turning the whole week into failure. The rota-proof MRCPCH plan explains minimum, standard and extended study modes for variable shifts.

Preserve three types of work

A balanced week often contains:

1. Repair: focused work on a current weakness.
2. Coverage: first contact with planned syllabus material.
3. Maintenance: delayed and mixed retrieval of previously studied material.

The ratio changes with exam proximity and current evidence. These are planning categories, not official RCPCH phases.

The topic stopping-rule guide helps decide when a unit should move from focused Repair into Verify or Maintain.

Limit the number of priorities

Choose:

• one main learning problem;
• one coverage commitment;
• one maintenance commitment; and
• one process experiment.

A process experiment might be "reduce new questions from 20 to 12 and measure whether all important feedback is completed". Change one major variable where possible. If resources, session length, question volume and topic mix all change together, the next review cannot identify what helped.

T - Trigger the next review

Book the next review before closing the current one. Record:

• date and time;
• the evidence that will be available;
• the process experiment being tested;
• the condition for keeping the change; and
• any time-sensitive official information to recheck.

Example:

Next Sunday, keep the smaller question sets if review debt is zero and delayed retrieval is stable. Increase scope cautiously only if both conditions hold.

This turns the plan into a feedback loop rather than a promise.

A 20-minute weekly review template

Twenty minutes is a practical starting point, not an evidence-based optimum.

Minutes 0-4: collect

Open the syllabus map, question history, error notes and calendar. Record only the minimum data set.

Minutes 4-9: interpret

Identify:

• one improvement;
• one repeated error cause;
• one item of review debt; and
• one mismatch between planned and real capacity.

Minutes 9-13: choose

Select the main constraint and decide what to preserve, stop or change.

Minutes 13-18: schedule

Place a few bounded Repair, Coverage and Maintenance tasks into realistic slots. Add fallback versions.

Minutes 18-20: close

Write the process experiment, evidence threshold and next review appointment.

Stop when the decisions are recorded. A longer review is justified when a mock, rota change or major plan failure creates genuinely new evidence; otherwise, extensive formatting can become avoidance.

Questions to ask during the review

Use prompts that demand evidence:

• Which corrected principle was still retrievable after a delay?
• Which error cause appeared more than once?
• Which topic received time but produced little independent retrieval?
• Which strong area can move to maintenance?
• Where did question volume exceed feedback capacity?
• Which planned session was never realistically available?
• What is the smallest change likely to remove the main bottleneck?
• What evidence next week would show that the change worked?

Avoid prompts such as "Did I work hard enough?" They invite moral judgment but rarely specify a better learning action.

What not to do in a weekly review

Do not carry every missed task forward

Reassess it. The task may still be important, may need a smaller boundary or may have been superseded by better evidence. Copying the entire backlog makes the next plan impossible before it begins.

Do not react to one score

Inspect question novelty, set composition, confidence, error causes and recent trend. The MRCPCH score-plateau guide shows how to diagnose a pattern rather than chase a single percentage.

Do not replace the study plan with tracking

The review should cost less time than the confusion it prevents. Track only variables that determine an action.

Do not redesign all resources weekly

Resource novelty can hide discontinuity. Keep a primary source and question process unless evidence identifies a specific limitation. The resource-selection guide provides a switching test.

Do not treat the review as a pass prediction

A weekly dashboard is an internal planning tool. It cannot reproduce RCPCH standard setting or establish a guaranteed pass mark.

Worked weekly example

A candidate planned four evening sessions and one longer weekend block. Two evening sessions were completed, one was shortened after a shift, and one was missed. The weekend block produced 40 questions, but explanations for 15 were left unresolved.

The initial emotional conclusion might be "I need to catch up with more questions". The evidence suggests a different constraint: set size exceeded review capacity.

The next-week change is:

1. cap ordinary sets at twelve first-seen questions;
2. reserve equal time for selective feedback;
3. use a five-question fallback after demanding shifts;
4. retrieve three corrected principles on the weekend; and
5. keep the change if important review debt falls to zero.

This preserves the long-term plan while testing one process change.

How to use PaedVault evidence without over-tracking

Use PaedVault activity to answer planning questions:

• Which exam and topics did I actually practise?
• Which answers were incorrect, guessed or uncertain?
• Which notes or flagged questions reveal repeated causes?
• Is completion volume rising while review quality falls?
• Which corrected material needs a delayed reattempt?

Do not interpret platform percentages as an official RCPCH pass prediction. Use them alongside syllabus coverage, question novelty, reasoning quality and delayed retrieval.

The question-bank learning-system guide explains how attempts, feedback, diagnosis and reattempts fit together.

Final answer

A useful weekly MRCPCH revision review is brief, evidence-led and decisive. Record what happened, evaluate learning rather than exposure, select one main constraint, engineer a realistic next week and trigger the next review.

Use RESET to protect continuity while adapting the plan. Keep successful methods, shrink impossible tasks, repair repeated errors and schedule delayed retrieval. The output should be a smaller set of better next actions, not a more elaborate timetable.

Frequently asked questions

How often should I review my MRCPCH revision plan?

A weekly review is a practical starting point because it provides several study observations while allowing regular correction. It is not an RCPCH rule or a research-defined optimum. Add a shorter review after a mock, major rota change or repeated plan failure, but avoid rebuilding the timetable after every difficult session.

How long should an MRCPCH weekly review take?

Start with about 20 minutes, but treat this as an editorial suggestion rather than an evidence-based threshold. The review is complete when you have recorded the minimum evidence, identified the main constraint, scheduled a few bounded actions and set the next review. Stop before formatting and tracking replace revision.

What should I track in an MRCPCH revision review?

Track only information that changes a decision: syllabus coverage, first-seen questions with completed review, delayed retrieval, repeated error causes, timing observations, review debt and realistic available capacity. Raw hours or question counts are insufficient without evidence about reasoning and feedback.

Should I carry unfinished MRCPCH tasks into the next week?

Not automatically. Reassess whether the task is still important, whether its boundary was too large and whether newer evidence changes its priority. Keep, reduce, reschedule or remove it deliberately. Copying every missed task forward creates a backlog that can make the next week unrealistic before it starts.

Can PaedVault scores tell me whether my weekly plan is working?

They can contribute evidence, but they are not official pass predictions. Interpret scores with question novelty, topic mix, confidence, error causes, syllabus coverage and delayed retrieval. A useful weekly review looks for repeated patterns and completed learning loops rather than reacting to one percentage.

Sources

1. RCPCH - Theory examinations
2. RCPCH - Theory exams: structure and syllabi
3. Self-regulated learning and academic success in health professions students: a systematic review
4. Self-regulated learning and learning outcomes in undergraduate and graduate medical education: a meta-analysis
5. Self-regulated learning training programmes enhance university students' academic performance, self-regulated learning strategies, and motivation: a meta-analysis
6. Self-regulated learning in the clinical context: a systematic review
7. Goal setting in higher education: how, why, and when are students prompted to set goals? A systematic review