FCPS Part-1 common mistakes
FCPS Part-1 · Understand the traps and how to avoid them.
Answering basic-science items from remembered clinical practice instead of from the underlying mechanism, e.g., choosing a treatment step for a pharmacology item that actually asks for the receptor or enzyme level explanation.
Candidates who have done clinical work or house jobs default to pattern-matching clinical scenarios, and FCPS Part-1 basic-science stems often dress a mechanism question in a clinical vignette, so the familiar clinical reflex overrides the asked mechanism.
What to do instead
Before answering, underline the interrogative in the stem and classify it as mechanism, structure, or clinical. If it is mechanism, force yourself to state the receptor, pathway, or enzyme first and only then select the option that matches that stated mechanism; practise this on 20 mixed stems per day for two weeks.
Treating physiology and pathology as separate silos, so a question requiring integration (e.g., how a change in Starling forces produces the observed edema, or how a channel defect produces an ECG change) is answered with only one half of the chain.
Most candidates revise subject by subject, and exam items that cross two disciplines expose the missing links; the brain retrieves the subject label rather than the causal chain.
What to do instead
Build one-page 'chain maps' linking normal physiology to the pathological consequence and its clinical sign, for each major system (cardiac, renal, respiratory, endocrine). Recite the chain aloud in three steps before moving on; test yourself with items that explicitly cross two subjects.
Misreading negatively phrased or 'except' stems, and single-best-answer stems where two options are both true but only one answers the question asked.
Under time pressure, candidates scan for a true statement and stop at the first familiar true option, missing 'least likely', 'except', or 'most appropriate initial step'.
What to do instead
Adopt a fixed reading routine: circle the negative word or the exact question word, then evaluate all options and mark each as true/false before choosing. If two options are true, re-read the stem's final clause and eliminate the one that is true but does not answer it.
Jumping to management in clinical-science items when the question asks for the most likely diagnosis, the next best investigation, or the underlying cause.
Clinical experience creates a strong 'treat first' bias, and many vignettes resemble familiar ward scenarios, so the candidate answers a question that was not asked.
What to do instead
Classify every clinical vignette into one of four buckets before looking at options: diagnosis, investigation, immediate management, or mechanism/complication. Write the bucket letter on your scratch paper and only consider options belonging to that bucket.
Ignoring the epidemiological or demographic clues in a vignette (age, sex, occupation, travel, drug history, family history) and answering from the headline symptom alone.
Candidates focus on the dramatic finding and skip the framing data, but in single-best-answer exams the discriminator between two plausible diagnoses is often a single demographic or exposure detail.
What to do instead
Train a checklist: age, sex, onset/duration, exposures (travel, occupation, drugs, animals), and family history. Apply it to every vignette for a week, writing the checklist findings down before reading the options, until it becomes automatic.
Over-investing time in a small number of difficult items early in the paper, leaving insufficient time for later items and forcing rushed guesses.
Perfectionism plus the high stakes of a postgraduate entry exam makes candidates reluctant to abandon an item, and they lose track of cumulative time.
What to do instead
Set a per-item time budget from the total item count and total time, and enforce a hard cutoff: if an item is not resolved within the budget, mark it, choose the best current option, and move on. Reserve the final block for marked items and practise this pacing in at least three full-length timed mocks.
Leaving answers blank or changing correct first answers to wrong ones during review without a concrete reason.
Fear of negative marking or uncertainty causes blanks, while anxiety-driven review causes answer changing based on a vague feeling rather than new evidence.
What to do instead
Confirm the paper's marking rule in advance and never leave a blank if there is no negative marking. During review, change an answer only if you can state a specific fact or stem detail that justifies the change; otherwise keep the first answer.
Rote-memorising lists (e.g., causes of a symptom, drug side effects) without anchoring them to a mechanism or a discriminating feature, so options that are all 'known' cannot be ranked.
Undergraduate revision rewards recall of lists, but Part-1 items typically require ranking or discriminating between options that are all individually true.
What to do instead
Convert each list into a discrimination table: for each entry, record the one feature that distinguishes it from the others (mechanism, time course, key lab finding). Self-test by covering the feature column and reconstructing it, not by re-reading the list.
Revising only from question banks and never from a structured curriculum, producing patchy coverage with whole systems or disciplines untouched.
Question-bank practice gives immediate feedback and a sense of progress, so it crowds out systematic coverage, and candidates then meet unfamiliar topics for the first time in the exam.
What to do instead
Audit coverage against the published syllabus at the start, mark each topic as confident, shaky, or unseen, and schedule unseen and shaky topics into fixed study blocks before starting question practice on them. Re-audit every four weeks.
Failing to review errors by cause, so the same type of mistake (misread stem, knowledge gap, wrong reasoning chain) recurs across mocks.
Candidates review only the correct answer and its explanation, which fixes the fact but not the behaviour that produced the error.
What to do instead
Keep an error log with three columns: the item, the cause category (knowledge, misread, reasoning, guessing), and the corrective rule. Re-read the log before each mock, and track whether the misread and reasoning categories fall over successive mocks.