skip to main content
iatroX JournalClinical insight

How to Turn PACES Mock Feedback into Better Bedside Practice

Featured image for How to Turn PACES Mock Feedback into Better Bedside Practice

Turn PACES mock feedback into bedside improvement by identifying the behaviour or knowledge gap behind the comment, choosing the setting that can test it and arranging a new observed attempt. A score tells you that something needs attention; it rarely tells you exactly what to do tomorrow. The useful output of a mock is a changed practice plan, not another percentage to compare.

The Federation's PACES preparation advice, checked on 3 October 2026, provides an official starting point for interpreting difficulties and seeking appropriate observation. Commercial and locally organised mocks vary in cases, observers and conditions, so their scores should not be treated as interchangeable official assessments.

Reconstruct the event before interpreting the label

Begin with what happened. Which task was set? What did you do or say? What did the observer identify? A comment such as poor presentation can describe several different problems, including inaccurate findings, missing prioritisation or a summary that obscured otherwise sound reasoning.

Ask for clarification while the encounter is still fresh when possible. If the observer cannot recall a specific example, record the uncertainty rather than inventing a detailed explanation for the mark. A broad comment may still guide discussion, but it is weaker evidence for a precise corrective action.

Separate the emotional impact of the mock from the learning question. A disappointing result deserves attention without requiring an immediate decision to change every resource or double the number of cases.

Classify the problem by the evidence it needs

An examination-technique problem requires observation of the physical action. A sign-recognition problem requires comparing what you found with an appropriate assessment of the patient. A reasoning problem needs explanation of the link between findings, alternatives and next steps. A communication problem needs review of the interaction.

These categories can overlap. A candidate may give a poor differential because a relevant finding was missed, not because they lack a long enough list of diagnoses. Correcting only the presentation would leave the original problem untouched.

Use the current PACES format and skills description, checked on 3 October 2026, to keep the assessment domains distinct. The categories in your personal log should help select the next activity, not create an alternative unofficial scoring system.

A fictional mock debrief

Sophie is a fictional trainee whose mock report identifies weak clinical judgement in a respiratory encounter. She initially plans a broad review of management topics. A discussion with the observer reveals that she reported an uncertain finding as definite and built the subsequent interpretation around it.

Her next action is therefore not simply reading more management. She arranges a suitable observed examination, asks for feedback on the relevant technique and compares the findings before discussing the differential. She then rehearses how to express uncertainty when the evidence is incomplete.

A later teaching case presents a different pattern. The observer checks whether Sophie distinguishes the observed information from her inference. This scenario illustrates a learning process; it does not report an actual examination result or demonstrate the effectiveness of a particular product.

Choose one change that can be observed

A useful next action is specific enough that another person can tell whether it happened. Improve neurology is not a complete action. Arrange observation of a defined part of the examination, explain the findings and ask the observer where technique or interpretation remains uncertain is more useful.

Do not select so many changes that the next encounter becomes an attempt to remember the entire feedback sheet. Prioritise a recurrent, consequential or foundational issue. Retain the other observations for later review rather than pretending they have been resolved.

This does not mean ignoring important safety concerns. Where feedback identifies a significant clinical or professional issue, seek appropriate supervision and address it directly instead of treating it as another routine revision target.

Match the next session to the gap

For a technical difficulty, request demonstration and a supervised repeat. For a knowledge gap, define the question before opening a reference. For an unclear presentation, practise selecting and organising the information, then test the approach on a different case.

For a communication difficulty, recreate the type of challenge rather than the exact words. A role-player might ask for clarification or express a different priority. Ask the observer whether you responded to it and whether the clinical explanation remained accurate.

The setting matters. A transcript cannot verify a physical manoeuvre, and a textbook cannot show whether you addressed the patient's concern. Choosing the correct medium is part of interpreting the feedback, not an afterthought.

Use guided learning after identifying the misconception

In iatroX's October 2026 product information, the Socratic Tutor starts from an attempted question and uses targeted follow-ups to explore the learner's reasoning. It can support clarification when a mock exposes a specific knowledge or interpretation gap.

The September 2026 simulation offering also includes PACES conversation practice with transcript-linked feedback. A relevant role is rehearsing an explanation after the underlying distinction has been clarified. These are educational design features, not evidence that a subscription corrects every weakness or predicts an official result.

For Sophie, the software-based activity follows the observed examination rather than replacing it. She can practise explaining how an uncertain finding affects her differential, but the physical observation remains the evidence for what she can actually elicit.

Retest with changed circumstances

An immediate repeat of the same case can help you understand the correction, but it may also reward memory of the observer's explanation. Add a later unfamiliar task that tests the same principle under different circumstances.

Change one meaningful feature initially. The candidate may need to apply the same examination technique, recognise a different pattern or answer a related concern. Explain why the variation tests the original weakness rather than simply making the case harder.

Record the result cautiously. One successful attempt is evidence of that performance, not proof that the skill will always be reliable. Look for a consistent pattern across appropriate observations without manufacturing a universal number of cases required for readiness.

Keep a small record of demonstrated change

A practical log needs the observed issue, the corrective action, the next test and what happened. Avoid copying every line of the mock report into a larger document that you never use.

Include uncertainties and disagreement. An observer's comment may require discussion if it appears inconsistent with the task or another defensible approach. The purpose is neither automatic acceptance nor automatic rejection, but a clearer account of the evidence.

Before the next mock, review which changes have actually been tested. Use the mock to examine integration or a remaining question, not as a substitute for the corrective work. Better bedside practice comes from connecting feedback to the next observed action, while recognising the limits of both the mock and your interpretation of it.

Frequently asked questions

Should I change resources after a poor PACES mock?

Not automatically: identify the problem before deciding whether a new resource can address it. Technique, knowledge, reasoning and communication gaps may require different support.

Can a high mock score prove that my weak areas are resolved?

No: scores depend on the cases and conditions, and may conceal unresolved individual skills. Review the observations and seek appropriate retesting on unfamiliar tasks.

What makes a useful PACES feedback log?

A short record linking an observed issue to a corrective action and a later test is usually more actionable than a collection of comments. Include what was demonstrated and what remains uncertain.

Turn a mock error into a focused reasoning exercise →

More from the Journal