A suitability report compliance check tends to flag the same failings again and again. These include generic objectives that could describe any client, a report that doesn’t match the fact find, capacity for loss missing or merged with attitude to risk, missing or boilerplate disadvantages, unclear costs, gaps in the file, and reports too long for the client to follow. Most of these aren’t advice failures. They’re documentation failures, and they’re almost all easier to fix before sign-off than after. The most effective fix is to check every report against a short, fixed list before it reaches compliance, and to feed what compliance keeps finding back into your templates so the same problem doesn’t happen next month.

This guide works through each failing, what the checker is actually looking for and how to fix it at the drafting stage.

Why the same failings keep coming up

The short answer: Most suitability report failings come from 3 sources: templates that encourage generic wording, information that’s collected but never used in the reasoning, and time pressure that pushes the report out before it has been checked against the file. Fix those and most compliance comments disappear.

The FCA’s own data shows how persistent this is. Its Assessing Suitability Review looked at 1,142 pieces of pension and investment advice from 656 firms. It found the advice suitable in 93.1% of cases, unsuitable in 4.3% and unclear in 2.5%. The disclosure picture was weaker. Disclosure was acceptable in 52.9% of cases and unacceptable in 41.7%. The FCA also noted that some suitability reports were too long or too complex.

More recent work tells the same story. In its 2024 thematic review of retirement income advice, the FCA reviewed 67 files in detail and couldn’t fully assess 15 of them because of material gaps in information. In other words, a large share of files couldn’t show the reasoning behind the advice, whether or not the advice itself was sound.

That’s the gap a compliance check is trying to close. In our experience writing suitability reports, the same handful of comments come back from compliance again and again. Very few of them are about the recommendation itself.

The 10 failings compliance checkers flag most often

FailingWhat the checker seesFix before sign-off
Generic objectives“You want growth” or “You want to retire comfortably”State the specific goal, amount, timescale and why it matters to the client
Report doesn’t match the fileDifferent risk profile, figures or dates from the fact findCross-check every key figure against its source
Capacity for loss missingAttitude to risk score with no capacity for loss reasoningAssess and explain capacity for loss separately
Weak disadvantages1 standard paragraph, or nothing at allList disadvantages specific to this recommendation
Alternatives not consideredNo mention of other options, including doing nothingExplain the options you considered and why you rejected them
Unclear costsCharges spread across sections, no total, no comparisonShow initial and ongoing costs together, with the effect over time
Information gapsExisting plan details or guarantees not confirmedChase the gap or explain why it doesn’t affect the advice
Too long or complex30 pages of product detail for a simple top-upCut to what the client needs and move detail to appendices
Vulnerability not addressedVulnerability noted on the fact find but missing from the reportShow what was considered and how it shaped the advice
Template residueWrong product names, irrelevant paragraphs, outdated tax figuresProofread for leftover wording and check current allowances

1. Objectives that could belong to anyone

The short answer: Generic objectives are the most common comment because they undermine everything that follows. If the objective is just “growth”, nobody can tell whether the recommendation actually meets it. A strong objective names the goal, the amount, the timescale and the reason behind it, so the recommendation can be tested against something specific.

“You’d like to grow your pension” can’t be checked. “You’d like your pension to support £30,000 a year of income from age 63, because you plan to cut your working week to 3 days” can be. The second version gives the rest of the report something to measure against. It also gives the compliance checker a reason to sign the report off rather than send it back.

2. A report that contradicts its own file

This is the failing that does the most damage in a complaint. If the fact find records a balanced risk profile, the report describes the client as cautious and the recommended portfolio sits at a higher risk band, any reviewer will spot it immediately. So will an ombudsman.

It usually happens through copying and editing an earlier report, or when information has been updated in 1 place but not another. The fix is mechanical but worth doing every time: check the client’s name, dates, values, risk profile and capacity for loss in the report against the source documents before it leaves the desk.

3. Capacity for loss missing or merged with attitude to risk

Attitude to risk is how the client feels about losses. Capacity for loss is what would actually happen to their life if the losses occurred. They’re not the same, and checkers flag reports that treat them as interchangeable, or that leave capacity for loss out entirely.

A good report explains capacity for loss in terms of the client’s real circumstances. Do they have an emergency fund? Is their essential spending covered by guaranteed income? What happens if the investment falls 20% in the first year? If the answer to the last question is “they’d have to cut their spending”, that needs to be in the report.

4. Disadvantages that read like boilerplate

COBS 9.4.7R requires the report to explain any possible disadvantages of the recommendation. Checkers often find a single standard paragraph about investment risk that appears in every report regardless of the advice.

Disadvantages should be specific to the recommendation. For a pension consolidation, that might include losing a guarantee, a higher charge on 1 arrangement or moving funds out of the market while the transfer goes through. A good test is to ask whether the paragraph would still make sense in a report for a completely different recommendation. If it would, it’s probably too generic.

5. No sign that alternatives were considered

Checkers want to see that the recommendation was a choice between options, not the only thing considered. That includes the option of doing nothing. A report that goes straight from the client’s objectives to the product leaves the reviewer guessing whether anything else was looked at.

1 or 2 sentences per alternative is usually enough. “We considered leaving your pensions where they are, but this wouldn’t meet your objective of simplifying your arrangements before you retire” does the job.

6. Costs that are hard to follow

Costs and charges disclosure was where the FCA found the most problems in its Assessing Suitability Review. Common faults include charges spread across several sections, adviser charges kept separate from product and fund charges, and no picture of the total cost or how it compares with the client’s current arrangement.

Put all the costs together in 1 place: initial and ongoing, adviser, platform and fund charges, in pounds as well as percentages where you can. If the recommendation costs more than the existing arrangement, say so plainly and explain why the client is still better off.

7. Gaps in the file

A report can only be as good as the information behind it. If an existing plan’s guarantees, charges or exit penalties weren’t confirmed, the checker can’t tell whether the advice took them into account. These are the files the FCA tends to class as “unclear”.

You have 2 options. Chase the missing information before the report is finalised, or explain in the file why it doesn’t affect the recommendation. Leaving the gap unmentioned isn’t an option.

8. Reports that are too long for the client

The Consumer Duty’s consumer understanding outcome has changed what compliance looks for. A report that’s technically complete but buries the recommendation under pages of product literature can be marked down on clarity even if every required element is present.

The FCA is pushing in the same direction. Its CP26/10 proposals on simplifying the advice rules encourage clearer, more concise reports. A practical approach is to lead with a short summary of the recommendation and the key points, keep the main body focused on this client’s reasoning and move product detail to appendices.

9. Vulnerability noted but not followed through

If the fact find records a bereavement, a health condition or low financial confidence, and the report says nothing about it, the checker will ask why. The report should show what was considered and how it shaped the advice or the way it was delivered. If you decided it wasn’t relevant to this recommendation, say so and explain why.

10. Template residue

This is the most avoidable failing and also one of the most embarrassing: a paragraph about ISAs in a pension report, the wrong product name, last year’s tax figures, or a section that refers to a spouse the client doesn’t have. It almost always comes from editing an earlier report rather than starting from a clean template.

A 5 minute pre-sign-off check

Before a report goes to compliance, run it against these questions:

  • Objectives Specific And Measurable
  • Every Figure Matches Its Source
  • Capacity For Loss Explained Separately
  • Disadvantages Specific To This Advice
  • Alternatives Including Doing Nothing
  • All Costs In 1 Place
  • File Gaps Chased Or Explained
  • Vulnerability Considered And Recorded
  • Tax Figures Current
  • Summary Readable In 2 Minutes

None of these takes long on its own. Together, they catch most of the comments that would otherwise send a report back for a second round.

Compliance checks vs file reviews

A pre-sign-off compliance check and a post-advice file review do different jobs, and firms sometimes rely on 1 to do the work of both.

The compliance check happens before the report reaches the client. Its job is to catch problems while they can still be fixed easily. The file review usually happens afterwards, on a sample of cases, and its job is to test whether the advice process is working. The key point is that file review findings should feed back into templates and training. If file reviews keep finding the same problem with capacity for loss, the fix belongs in the template, not in yet another reminder email.

Ongoing reviews need the same discipline. When the FCA looked at 22 of the largest advice firms, it found that suitability reviews were delivered in about 83% of cases where they had been promised. Clients declined or didn’t respond in 15% of cases, and in fewer than 2% the firm didn’t attempt the review at all. Review letters should go through the same compliance check as initial reports, because they make the same claims about suitability.

Building the checks into the template

The most reliable way to stop these failings is to make them hard to commit in the first place. A template with dedicated sections for capacity for loss, specific disadvantages, alternatives and vulnerability means the paraplanner has to fill them in or consciously decide they don’t apply. Approved wording for each section cuts down on boilerplate without forcing every report into the same mould.

That’s where suitability report software built around your own templates can help. Planbot includes a compliance checker among its ready-made templates, and Planbot lets your super users update template wording centrally. When a tax allowance changes or compliance asks for a new disclosure, you change it once and every new report picks it up. That deals with template residue at the source.

An AI suitability report generator can also help with the consistency failings by pulling figures directly from source documents, so the report and the file are less likely to disagree. It won’t decide whether the disadvantages are the right ones or whether the reasoning holds up. That’s why AI for paraplanners works best as a drafting and checking aid, with the paraplanner and compliance still responsible for the judgement. It’s also why it’s worth reading the FCA expectations on AI in financial advice before you rely on any automated check.

If you’re reviewing tools more widely, our guide to paraplanning software and our overview of AI software for financial advisers are a good starting point. If you need to make the case internally, our guide to the business case for AI in your advice firm shows how to measure the cost of reports being sent back.

Get fewer reports back from compliance

If your team keeps getting the same compliance comments, the fix is usually in the template rather than the people. Planbot turns your firm’s suitability report and compliance checker templates into AI-powered documents, so every report covers the sections compliance looks for. Your paraplanners still review and edit each one before sign-off. No client data is stored or used to train AI models.

Book a demo and see how your own templates could work in Planbot.