Suitability reports and incomplete client information: how to document gaps

Incomplete client information is one of the easiest suitability report problems to underestimate. It can look like a small admin gap: an old expenditure figure, an unconfirmed pension value, a missing vulnerability note, or a risk-profile output that has not been refreshed.

But under the FCA suitability rules, missing information can be more serious than a housekeeping issue. COBS 9 requires firms to obtain the information needed to understand the essential facts about the client and to have a reasonable basis for believing the recommendation is suitable. That day-to-day judgement is where COBS suitability reports become practical, because the issue is not just whether information exists somewhere on file. It is whether the information is current, relevant and strong enough to support the recommendation.

That is why incomplete information needs to be handled visibly in the suitability report and the underlying advice file. The point is not to make every file look perfect, or to treat suitability documentation as a tick-box exercise. The FCA suitability report requirements can help structure the review, but the real test is whether the file shows what the firm knew, what it checked, what it treated as uncertain, and why the adviser still had enough evidence to proceed. Where that evidence is not enough, the file should make the pause clear too.

Why this matters

COBS 9 is not asking for a neat narrative after the event. It is asking the firm to take reasonable steps before making the recommendation. That means obtaining necessary information about the client’s knowledge and experience, financial situation and investment objectives, so the adviser can judge whether the recommendation fits the client and the risks they can bear.

The rule on reliance matters here. Firms can rely on information provided by clients unless they are aware that it is manifestly out of date, inaccurate or incomplete. In practice, this is where advice files can become fragile. A fact find may contain a figure. A previous review may contain an objective. A risk profile may exist on file. But if the adviser knows something material has changed, the existence of an old data point is not enough.

A client may have retired, divorced, inherited money, lost employment, started taking withdrawals, changed their retirement date, developed health concerns, or disclosed support needs. Any of those changes can affect objectives, affordability, risk, time horizon, liquidity needs or the way information should be explained. The suitability report should not quietly carry forward old assumptions as if nothing has changed.

For report writers, the practical challenge is knowing when a gap is merely administrative and when it affects the basis of the advice. That judgement will depend on the service, the recommendation and the firm’s compliance framework, but the file should make the reasoning easy to follow.

Information that commonly goes stale

Some client details go stale quickly because they are tied to life events, employment, market values or health. Income and expenditure are obvious examples, especially around retirement, redundancy, business sale, reduced working hours, mortgage changes, care costs or support for adult children. Pension values, contribution levels, employer matching, investment holdings and withdrawals can also become unreliable if the file is using figures from an old review or provider statement.

Other information becomes stale because the client’s priorities have moved on. A retirement plan based on a target date from three years ago may no longer reflect what the client wants. A cautious risk profile may not sit comfortably with a new objective for higher withdrawals. A previous statement about no foreseeable need for capital may be undermined by a recent family commitment, health concern or planned house move.

Vulnerability and support needs deserve particular care. They may be temporary, fluctuating or disclosed only in conversation. If a client has mentioned illness, bereavement, cognitive difficulty, financial pressure, low confidence or reliance on a family member, the advice file should show how that information affected the process and how any support needs or adjustments were reflected before the recommendation was issued.

A report based on stale information may still read well. That is the risk. The writing can be polished while the evidence base is weak. Good suitability documentation is not just about fluency; it is about making the evidence, assumptions and unresolved points visible.

Minor gaps versus suitability gaps

Not every missing field means the advice process must stop. A missing middle name, formatting inconsistency or historic address detail may need tidying, but it will not usually affect whether the recommendation is suitable. A missing income need, unconfirmed capacity for loss, unclear service requirement or unsupported replacement rationale is different.

A suitability gap is information that could reasonably affect the recommendation. If a client wants income in retirement but sustainable expenditure has not been confirmed, the adviser may not have enough evidence to judge the withdrawal level. If a transfer or replacement product is being considered but existing guarantees, penalties or charges are not documented, the file may not support the comparison. If capacity for loss has been inferred from total assets rather than tested against objectives and essential expenditure, the recommendation may rest on a weak assumption.

This is especially important in retirement income advice files, where small assumptions can have a large effect over time. A recommendation may look suitable under one spending assumption and unsuitable under another. The file should show which assumptions were used, why they were reasonable, and what would change if the client confirmed different figures. Where the recommendation relies on projections, cashflow modelling assumptions should be treated as part of the suitability evidence, not as a separate planning exercise.

The useful test for a paraplanner or reviewer is simple: if this missing point changed, could it change the recommendation, the risk explanation, the affordability assessment, the product comparison, the charges disclosure or the client’s understanding? If yes, it should be treated as a suitability gap, not a minor admin task.

How to document assumptions

Assumptions can be appropriate, but they must not be dressed up as facts. The file should separate confirmed information from adviser judgement and provisional drafting. That distinction protects the client, the adviser and the reviewer because it shows where the advice rests on evidence and where it needs confirmation.

A weak version might say: “The client has sufficient emergency funds.” That reads as a fact, but it does not show the source, the amount, the timing or whether it has been tested against expenditure. A stronger version would be: “The client has stated that they hold approximately six months’ expenditure in cash. This should be confirmed before finalising the recommendation, as the advice assumes the client can meet short-term needs without accessing the investment.”

The stronger version does three useful things. It identifies the source of the information. It makes the assumption explicit. It explains why the point matters to the recommendation. That is far more helpful than leaving a reviewer to infer whether the writer knew the information was uncertain.

Where an assumption is material, the file should usually answer five questions in plain language: what is known, what has been assumed, why the assumption is reasonable, whether the recommendation depends on it, and what needs to be confirmed before the advice is issued. This does not need to become a long defensive paragraph every time. It needs to be clear enough that another adviser, paraplanner or compliance reviewer can follow the thread without reconstructing the whole case.

Contradictions should be surfaced, not smoothed over

Contradictory information is not always a reason to stop, but it is usually a reason to explain. A client may describe themselves as cautious while also wanting a withdrawal level that puts pressure on the portfolio. They may say they want flexibility while considering an option that limits access. They may want low charges while the recommendation increases total cost for a service or feature that needs to be justified.

These tensions are normal in advice. Clients do not always express objectives in a perfectly consistent way, and good advice often involves helping them weigh trade-offs. The documentation problem comes when the draft removes the tension instead of showing how it was dealt with.

A better file records the contradiction, explains the adviser discussion and shows why the final recommendation remains suitable. If the client accepts a higher cost, the file should explain what they are receiving for that cost and why it is appropriate. If the client accepts investment risk, the file should show how the adviser checked understanding and capacity for loss. If the client chooses not to follow the recommendation, the documentation may need to deal with insistent-client considerations as a separate advice-file issue.

The aim is not to make the file longer for the sake of it. It is to make the reasoning visible where a later reviewer would otherwise ask, “How did we get from this fact pattern to this recommendation?”

When the process should pause

A pause is not wasted time. It protects the quality of the advice and avoids creating a report that has to be unpicked later. It is usually better to stop early for one clarification than to produce a polished draft built on an assumption nobody has confirmed.

The process should be questioned where core objectives are unclear, income or expenditure figures are out of date, risk profile results conflict with the conversation, existing plan details are missing, charges or guarantees are unconfirmed, vulnerability or support needs have not been reflected, or a retirement income recommendation relies on untested assumptions.

The pause should also be documented in a practical way. The file should show what clarification is needed, who needs to provide it, and why the answer matters. In review cases, this links closely to the service being delivered. If the firm is charging for ongoing advice, the review file should evidence what has been checked and updated, not simply repeat last year’s position.

If the client cannot or will not provide the necessary information, the firm should be careful about the boundary between advised and non-advised services. COBS 9 notes that where a firm cannot make a personal recommendation because it lacks the necessary information, the client may still ask for another service, but the firm should obtain written confirmation of instructions and consider best interests and appropriateness obligations. That makes the line between execution-only and appropriateness important to document clearly.

What good documentation looks like

Good suitability report documentation does not need to be theatrical. It should read like a clear record of professional judgement. The adviser has gathered relevant facts, noticed what is missing, tested the material assumptions, explained uncertainty where it matters, and either proceeded on a reasonable basis or paused until the evidence is strong enough.

In a strong file, the suitability report and the underlying notes tell the same story. The fact find does not say one thing while the recommendation assumes another. The risk discussion is not isolated from the product recommendation. The client’s objectives are not repeated as generic statements; they are connected to the specific recommendation, time horizon, costs, risks and trade-offs.

Record keeping is part of that discipline. If a clarification was obtained by email, phone call, meeting note or provider document, the file should preserve it in a way the firm can retrieve later. If a client confirmed that an old figure was still accurate, the file should show when and how that confirmation happened. A clear audit trail for suitability reports is what turns a judgement call into something another reviewer can understand later.

Where Templi fits

Templi helps advice teams bring client context, fact-find data and firm-standard report structure into one drafting workflow. That can make gaps easier to spot because the source material, draft wording and review points sit closer together.

This matters because incomplete information is often hidden by process fragmentation. One detail sits in the fact find, another in the meeting record, another in a provider document, and another in the adviser’s head. Templi supports the drafting workflow by helping teams work inside their firm’s existing templates and make review points visible before the report is issued.

The adviser and paraplanner still decide whether the evidence is sufficient. Templi supports reviewable drafting; it does not decide that advice can proceed when information is missing. The human approval point remains central.

Sources

This article is general information for UK advice firms. It is not legal or compliance advice. Firms should check the current FCA Handbook and their own compliance framework before publication.

• FCA Handbook: COBS 9 Suitability
• FCA Handbook: COBS 2.1 Client’s best interests rule
• FCA Handbook: COBS 10 Appropriateness for non-advised services
• Templi reference article: FCA suitability report requirements

Disclaimer

This article is intended as general information for UK financial advice firms only. It should not be taken as legal, regulatory, compliance, tax or financial advice. Firms should refer to the current FCA Handbook, their own compliance framework and appropriate professional support before making decisions about suitability reports or advice processes.