IFoA SP1 common mistakes
IFoA SP1 · Understand the traps and how to avoid them.
Writing a long descriptive answer that explains what a reserving or pricing method is, without ever stating the assumptions it depends on or the circumstances under which it breaks down.
Candidates memorise method descriptions from the Core Reading and default to reproducing them, because description feels like safe, mark-earning content. SP1 marks are weighted towards application and evaluation, so description alone caps the score even when it is accurate.
What to do instead
Before writing, convert the verb in the question into a checklist: 'describe' needs one line per feature; 'explain' needs a mechanism; 'evaluate' needs strengths, weaknesses and a conclusion. For every method you mention, force yourself to add two sentences: the key assumption, and what happens to the result if that assumption fails. Practise by taking past-style method questions and rewriting each answer so that at least half the words are assumption or limitation content.
Ignoring the specific product, scheme or portfolio details given in the scenario and answering with generic textbook material that would apply equally to any insurer.
Under time pressure, pattern-matching to a familiar topic feels efficient, and candidates fear that engaging with unfamiliar scenario details will expose gaps. The result is an answer that never uses the numbers, guarantees, or member characteristics provided, which examiners reward heavily.
What to do instead
Read the scenario twice: first for the question, second to underline every quantified fact and product feature. Build the answer so each paragraph explicitly names one of those underlined facts and draws a consequence from it. A useful discipline is to ban yourself from writing any sentence that would still be true if the scenario company were replaced by a different one.
Producing a calculation with no audit trail: numbers appear without a stated formula, units, time period, or explanation of what the result represents.
Candidates treat the calculation as the answer rather than as evidence, and rushed working is often done in margins or skipped. Marking allocates credit to method, so unexplained arithmetic loses marks even when the final figure is right, and a single slip becomes impossible to trace.
What to do instead
Adopt a fixed layout for every calculation: state the formula or approach in words, list inputs with units and source, show one substituted line, give the result with units and time basis, then write a one-sentence interpretation ('this implies a capital requirement of X, which is Y% of available capital'). Practise under timed conditions so the layout becomes automatic rather than an extra step you drop when rushed.
Treating the capital or reserving question as purely technical, listing formula inputs and never discussing the commercial, regulatory or policyholder consequences of the answer.
The syllabus draws on both actuarial techniques and their business context, but revision tends to split them, and technique is easier to revise because it has right answers. Candidates therefore stop at the number and never reach the 'so what' that carries the higher-order marks.
What to do instead
After any technical answer, write a short 'implications' paragraph covering at least three of: effect on pricing and competitiveness, effect on reported profit and volatility, regulatory or capital adequacy impact, policyholder or member outcomes, and management actions available. Keep a standing list of these five lenses and apply them mechanically until it becomes habitual.
Listing risks or advantages as an unstructured stream with no grouping, ranking or conclusion, so the examiner cannot see whether the candidate has judged which points matter most.
Brainstorming under time pressure produces whatever comes to mind first, and candidates worry that organising will cost time and reduce the number of points. In practice, unranked lists read as undifferentiated and lose the evaluative marks that distinguish a pass from a strong pass.
What to do instead
Use a two-stage approach on the answer sheet: spend a minute jotting points, then group them under two to four headings (for example financial versus non-financial, or short-term versus long-term), and order headings by importance. Close with an explicit judgement sentence naming the two or three dominant factors and why they dominate. Practise this grouping on one question per revision session until the minute spent planning is clearly repaid.
Answering a question about a specific insurance context with life-insurance concepts, or vice versa, for example discussing mortality-based reserving when the scenario concerns claim frequency and large-loss volatility.
Many SP1 ideas (risk pooling, prudential capital, reinsurance, underwriting) appear in more than one domain, and revision notes often blend them. Candidates then reach for the most familiar version of the concept rather than the version the scenario demands.
What to do instead
Before answering, write the domain and sub-context at the top of your answer (for example 'general insurance, commercial property, short-tail'). Then for each concept you use, check it against that label: does the driver here behave like frequency and severity, or like longevity and interest? Build a comparison table during revision showing how the same concept (reserving, capital, reinsurance) differs across health and care, life, general insurance and pensions.
Spending disproportionate time on the first question, producing an over-long answer, and then leaving later questions or parts unattempted or answered in note form.
Early questions often feel tractable, and candidates chase completeness on them because partial answers feel unsatisfying. Marks are allocated per point across the whole paper, so time spent beyond the mark value of a question is time taken directly from easier marks elsewhere.
What to do instead
Before starting, compute a time budget per mark (total minutes divided by total marks) and write the target finish time for each question in the margin. Use the mark allocation to decide how many distinct points to produce, and stop when you reach that count even if you could write more. In mocks, record actual versus budgeted time per question and treat overruns as a specific error to correct next time.
Describing a model or method as if it were exact, without stating the data limitations, parameter uncertainty, model risk, or the need for judgement and sensitivity testing.
Textbook presentations of models are clean, and candidates reproduce the clean version because uncertainty feels like hedging rather than content. SP1 rewards awareness that actuarial results are estimates whose reliability must be assessed.
What to do instead
Attach a standard 'limitations' coda to any model discussion: data volume and quality, parameter stability, whether the model captures the real risk drivers, and how results would change under plausible alternative assumptions. Where the question permits, name a specific sensitivity (for example a shift in the discount rate or a change in claim trend) and state the direction of its effect rather than only saying 'results are uncertain'.
Writing about the actuarial technique in isolation and omitting the wider environment: regulation and solvency supervision, taxation, accounting treatment, competition, distribution channels, and policyholder or member expectations.
Candidates structure revision by technique, so the surrounding environment is studied as separate background reading and never integrated into answers. Questions that ask for advice to a client or board expect this context, and its absence leaves answers looking academic.
What to do instead
Keep a one-page environment checklist (regulation, tax, accounting, competition, distribution, customer expectations, capital markets) and run every 'advise the company' or 'discuss the implications' question through it, selecting the two or three items that genuinely bite in the scenario. Practise by taking a technical answer you have written and adding an environment paragraph that changes the recommendation, not just decorates it.
Misreading the command word and the scope of the question, for example giving a list when asked to 'discuss', or answering a question about the disadvantages by describing the advantages.
Command words look similar on a quick read, and candidates under time pressure latch onto the topic noun and start writing about the subject rather than the task. A well-written answer to the wrong task scores poorly.
What to do instead
Circle the command word and any scope limiters (a named stakeholder, a time horizon, 'for the regulator') before planning. Translate the command word into a required structure: 'discuss' means points for and against plus a view; 'criticise' means weaknesses with justification; 'calculate' means method plus result plus interpretation. Check your finished answer against the circled words to confirm you addressed the task, not merely the topic.