IFoA CB2 common mistakes
IFoA CB2 · Understand the traps and how to avoid them.
Writing long prose paragraphs explaining economic intuition in the long-answer questions instead of answering the precise command word (e.g., 'state', 'describe', 'explain', 'discuss') with the number of distinct points the mark allocation implies.
Candidates carry over habits from essay-based subjects and believe volume earns marks; CB2 marks are allocated per discrete point, so buried points inside a paragraph are hard to credit and time is wasted that is needed for the data-response and calculation parts.
What to do instead
Before writing, convert the mark allocation into a point budget (roughly one creditable point per mark) and answer in short numbered or bulleted sentences, each making exactly one point. Practise by marking your own past answers against the mark scheme and counting how many distinct points you actually made versus the maximum available.
Treating CB2 as a pure mathematics paper: deriving formulae from first principles or grinding through algebra by hand in the modelling questions rather than setting up the model, stating assumptions, and interpreting output.
Candidates with strong quantitative backgrounds over-invest in derivation because it feels safe and verifiable, but CB2 rewards understanding of model structure, assumptions and limitations, and the time lost leaves later interpretation marks unattempted.
What to do instead
For each modelling topic, memorise the standard model statement (variables, parameters, functional form, key assumptions) and rehearse interpreting coefficients and outputs in plain language. In practice, cap time on any single derivation and force yourself to write at least two sentences of interpretation for every calculation you perform.
Quoting a numerical result or model output without stating units, time period, or the assumptions under which it holds, and without a concluding sentence saying what it means for the decision-maker.
Under exam pressure candidates treat the number as the answer, but CB2 marks typically split between method, accurate computation, and interpretation; omitting units or context loses the interpretation marks even when the arithmetic is perfect.
What to do instead
Adopt a fixed three-line template for every quantitative answer: (1) the result with units and period, (2) the key assumption or caveat, (3) a one-sentence implication ('this suggests the project is viable because...'). Apply the template in every practice question until it is automatic.
Confusing the distinct roles of the three financial statements and failing to link them: producing a cash flow or balance sheet that does not articulate with the income statement and retained earnings.
Candidates learn each statement in isolation and do not internalise the articulation (profit to retained earnings, depreciation add-back, working capital movements, financing and investing flows), so a single sign or classification error cascades through the whole answer.
What to do instead
Build a one-page articulation map linking the income statement, balance sheet and cash flow statement, then practise constructing all three from a single set of transactions. Always perform a reconciliation check (closing cash equals opening cash plus net cash flow; balance sheet balances) before moving on.
Ignoring the data-response scenario's specific facts and writing a generic textbook answer that could apply to any company, or importing assumptions not given in the scenario.
Time pressure pushes candidates to pattern-match to a memorised answer, but CB2 data-response questions are marked on application to the stated figures and context; generic points earn little and invented assumptions can be penalised.
What to do instead
Read the scenario twice and underline every quantitative fact, constraint and stakeholder. Before writing, list which facts you will use and where. Structure answers as 'principle + evidence from the scenario + consequence', explicitly citing the scenario's numbers or constraints in each point.
Misreading the command word and the scope of the question, for example 'discuss' answered as a one-sided list, or 'compare' answered by describing only one option.
Candidates skim the question stem after a long scenario and default to listing everything they know about the topic; command words carry mark-bearing structure (balance, evaluation, recommendation) that a list does not satisfy.
What to do instead
Build a command-word glossary (state, describe, explain, compare, discuss, evaluate, recommend) with the structure each demands, and practise rewriting the same content in each format. In the exam, circle the command word and the scope words (e.g., 'for the next five years', 'from the perspective of the lender') before planning.
Failing to state and justify model assumptions explicitly, or stating assumptions that contradict the scenario (e.g., assuming constant interest rates when the scenario specifies a rate change).
Assumptions feel like obvious background rather than examinable content, so candidates omit them; alternatively they copy a standard assumption list without checking it against the scenario, producing internally inconsistent answers.
What to do instead
Keep a per-topic assumptions checklist (distributions, independence, linearity, constant parameters, no arbitrage, rational agents) and write the relevant ones as a short numbered list before modelling. Cross-check each assumption against the scenario facts and flag any that must be relaxed, explaining the direction of the resulting bias.
Presenting a single deterministic projection or point estimate as the answer, with no sensitivity analysis, scenario analysis, or acknowledgement of uncertainty.
Candidates equate a completed calculation with a complete answer and run out of time before adding robustness checks, but CB2 explicitly rewards awareness that outputs are conditional and that decision-makers need ranges and drivers.
What to do instead
Reserve the final few minutes of any modelling question for a standard robustness paragraph: identify the two or three most influential inputs, state how the output moves if they vary, and name the technique (sensitivity, scenario, break-even, Monte Carlo). Practise producing this paragraph in under five minutes.
Poor time allocation: spending too long on the first long-answer question and leaving later questions, especially the data-response section, with rushed or blank answers.
Candidates are reluctant to leave a question incomplete and keep polishing, but marks per minute are roughly equal across questions, so over-investment early guarantees lost marks later; unfamiliar data-response formats also slow candidates who have not rehearsed them.
What to do instead
Set a per-question time budget from the marks (proportional to total exam time) and enforce it with a watch, moving on when the budget expires and returning only if time remains. In mocks, practise the data-response section first or second deliberately to break the habit of over-running on question one.
Using imprecise or misused technical vocabulary, for example conflating risk with uncertainty, return with yield, or capital with cash, and using terms like 'correlation' and 'causation' interchangeably.
CB2 spans economics, finance and modelling, and candidates often learn terms from context rather than definition, so near-miss usage slips through; markers award precision and penalise contradictory or undefined terminology.
What to do instead
Maintain a personal glossary with one-line definitions and a contrasting term for each entry (risk vs uncertainty, real vs nominal, systematic vs idiosyncratic, stock vs flow). Before the exam, self-test by writing definitions from memory and checking them against a reliable text, then use the precise term in every practice answer.