Client information can change long before the next annual review. This guide explains how advice firms can capture relevant updates, understand where information came from, assess what matters and keep professional records current without creating unnecessary administration.
06 May 2026
09 October 2026
Financial advisers do not need every piece of client information to update continuously.
They do need a reliable way to identify when relevant circumstances have changed, understand where that information came from and decide whether it requires action before the next formal review.
That distinction matters.
An annual review remains an important advice and service event. But if the client record only changes once a year, the adviser may spend the start of every review reconstructing the previous 12 months rather than discussing what those changes actually mean.
A better model is to maintain client information according to its freshness, provenance and materiality — then move relevant updates into the firm's professional processes at the right point.
Keeping client information current means having proportionate processes for capturing relevant changes in a client's circumstances, understanding how reliable those updates are and updating the firm's professional records where necessary.
It does not mean:
Different information changes at different speeds and for different reasons.
The objective is therefore not to make every field “live”. It is to create a better flow of relevant information between the client and the firm.
For relevant MiFID business, FCA rules are explicit that firms with an ongoing client relationship, such as ongoing advice or portfolio management, must have appropriate policies and procedures to maintain adequate and up-to-date client information to the extent necessary for suitability requirements.
The FCA also allows firms to rely on information supplied by clients unless the firm is aware, or ought to be aware, that it is manifestly out of date, inaccurate or incomplete.
Separately, where a firm provides a periodic suitability assessment, the applicable FCA rules set requirements around how frequently that assessment takes place.
These obligations should not be collapsed into one idea.
Keeping relevant client information current and conducting a formal periodic suitability assessment are related, but they are not the same process.
An update received in June does not necessarily mean a full review must happen in June.
Equally, the existence of an annual review does not mean information received in June should sit untouched until January.
The operating question for the firm is:
What has changed, how reliable is the information and does it matter enough to require action now?
A useful ongoing client-information process should distinguish three characteristics.
When was the information last updated or confirmed?
Some information becomes stale quickly. Cash balances, investments and borrowing can change frequently.
Other information may remain unchanged for years but still needs occasional confirmation.
Knowing the value is useful. Knowing when that value was last current is better. A pension value entered four years ago should not look identical to a pension value refreshed yesterday.
Where did the information come from?
Consider these two records:
Pension value: £420,000 — client supplied — updated 8 September 2026
and:
Pension value: £417,842 — connected/provider source — refreshed 16 September 2026
Both may be useful. They do not have the same provenance.
Client-entered information may be approximate. A document may be authoritative for a particular date but already several months old. Connected financial data may be current but cover only institutions supported by the relevant connection.
A good information architecture should preserve that distinction rather than reducing everything to a single number in a CRM field.
Does the change actually matter?
This is where more information does not automatically mean better advice.
The aim should therefore be better signal, not simply more data.
There is no universal “refresh client record” button.
Different types of information come from different sources and require different levels of confirmation.
The practical consequence is simple:
Firms need several ways to receive updates, not one giant fact-find repeated more frequently.
Clients are normally the first people to know that their circumstances have changed.
Giving them an ongoing place to maintain relevant information can therefore reduce the delay between a life event happening and the firm becoming aware of it.
This might include:
But there is a crucial distinction:
Allowing a client to update information does not mean allowing them to overwrite the firm's professional record automatically.
The client can provide the change.
The firm still determines what needs verification, professional consideration or entry into its authoritative systems.
Open Banking, Open Finance and provider integrations can reduce reliance on manually entered information for supported accounts and products.
Instead of a client estimating the balance of an account once a year, supported connections may provide a more current view.
That can be valuable.
But connected does not mean complete.
Connected data may not include every provider, property, private asset, business interest or manually held investment.
It also cannot explain why something changed.
A new £100,000 cash balance might reflect an inheritance, property sale, business distribution or temporary movement between accounts. The transaction is visible. The context still has to come from the client.
Connected financial information is therefore one input into the client picture rather than the entire picture.
Documents can reveal that a client's circumstances have changed even before somebody updates an individual field.
A new:
may indicate that the information previously held is now outdated.
The useful question is not just:
“Has the client uploaded a document?”
It is:
“Does this document change what we currently understand about the client?”
That can turn document collection from passive storage into a useful information process.
Some of the most important information will never arrive through an API.
A client mentions during a phone call that they are thinking of retiring earlier.
An email refers to a parent moving into care.
A meeting reveals that a child has returned home and become financially dependent again.
The information already exists within the relationship.
The operational problem is whether it stays buried in an email or meeting note, or enters a process where somebody can assess its relevance.
Firms therefore need a clear route for material information surfaced during ordinary interactions to reach the appropriate client record.
Not every update needs a 20-page questionnaire.
Where information has become old or needs confirmation, a focused question may be enough.
For example:
“We currently have your planned retirement age as 63. Is that still correct?”
“We last recorded your employment status as full-time. Has anything changed?”
“We currently have one property in addition to your main residence. Is that still accurate?”
This is easier for the client and more useful for the firm than asking somebody to reconstruct their entire financial life simply because 12 months have passed.
The most important design decision is what happens after new information enters the firm.
A sensible process can be broken into seven stages.
The firm receives a new piece of information.
That could come directly from the client, from connected financial data, a document, a provider or an adviser interaction.
The system should preserve where the information came from.
“£420,000 pension” is less useful than:
£420,000 pension — client supplied — updated 8 September 2026.
Provenance helps the next person understand what they are looking at.
The firm needs to determine whether the information is simply useful context or potentially relevant to advice, service or support.
Not every update needs intervention.
Some information may be accepted from the client.
Other information may need evidence, clarification, provider confirmation or adviser discussion before it is relied upon professionally.
Once information has been confirmed to the appropriate standard, it may need to enter the firm's CRM, financial-planning software, fact-find or another professional system.
The client-information layer and the firm's authoritative record do not have to be the same thing.
The result might be:
The process should route information, not make regulated decisions in place of the firm.
Where appropriate, firms should be able to understand:
That creates a much more useful record than simply replacing an old CRM value with a new one.
One obvious objection to ongoing client updates is volume.
If every account movement, document upload and personal change sends an alert to an adviser, a system designed to improve information quality simply creates another inbox.
A better model distinguishes between different levels of significance.
These are useful to keep current but do not normally require immediate adviser involvement.
Examples might include a changed mobile number or an updated document that does not affect the advice relationship.
These may be useful at the next scheduled client interaction.
A client recording another relatively modest held-away investment might fall into this category depending on the circumstances.
Some events may justify earlier consideration.
Examples could include:
These examples should not become rigid automated rules.
The same event may matter differently for two clients.
Technology can help organise and route information. The firm's professional processes and judgement determine its significance.
A common mistake is to treat “newest” as synonymous with “correct”.
Imagine a client enters a pension value of £420,000 today.
That may be more current than a provider statement from nine months ago.
But the client's figure may also be approximate.
The useful record is therefore not simply:
Pension: £420,000
It is closer to:
Pension: £420,000
Source: Client supplied
Updated: 17 September 2026
Evidence status: Not yet confirmed
This makes it possible to use the information appropriately without giving it a level of authority it has not earned.
The same principle applies in reverse.
A provider statement may be reliable evidence of the value on its statement date but no longer reflect the current balance.
Good client information management therefore separates:
freshness — how recent is it?
from:
provenance — where did it come from?
and:
verification — what checks have been completed?
Those distinctions become particularly important as firms use more automation and artificial intelligence across their advice processes.
Automation can process information faster.
It cannot make weak underlying information stronger simply by moving it between systems.
A client's financial position is not the only thing that can change between annual reviews.
Health, bereavement, caring responsibilities, financial resilience and other life events can also affect the way a client needs to be supported.
The FCA expects firms to be able to identify customers in vulnerable circumstances, understand their needs and act to meet those needs where necessary. It also expects firms to create processes that enable customers to disclose relevant needs.
That does not mean software should attempt to diagnose whether a client is “vulnerable”.
Nor does every difficult life event automatically mean that a client should be categorised in a particular way.
Instead, firms need sensible routes for clients to share relevant circumstances and for staff to record and respond to support needs appropriately.
This information may also be particularly sensitive.
In March 2026, the FCA and ICO published a joint statement on firms' use of vulnerability-related data, reinforcing the need to combine good consumer outcomes with lawful, fair and responsible treatment of personal information.
For an advice firm, the practical point is straightforward:
Support needs can change between annual reviews just as financial circumstances can.
A process designed to keep the client picture current should be capable of recognising both.
Consider two annual-review models.
In the first:
The review starts.
The adviser asks what changed.
The client tries to remember the previous 12 months.
New accounts emerge.
A pension statement has to be found.
The client mentions an inheritance from eight months ago.
A property has been sold.
Retirement plans have changed.
Only once all of this has been reconstructed can the substantive planning conversation begin.
In the second:
Relevant information has been maintained throughout the year.
The review starts with a clearer view of what changed and when.
The adviser confirms what is still current, verifies information where required and focuses more of the conversation on implications, decisions and planning.
The annual review still matters.
It simply does not need to be the first time the firm learns what happened during the previous twelve months.
Consider a client whose annual review takes place each January.
January
The review establishes that the client:
April
The client connects another savings account.
The firm's picture of their cash position improves. No immediate adviser action is necessarily required.
June
The client records a significant inheritance.
This may be material enough to require further information or an earlier conversation.
August
The client changes their intended retirement age from 63 to 60.
That may affect planning assumptions and future advice.
October
The client says that their mother has moved into care and they expect to provide ongoing financial support.
The event may affect anticipated expenditure and objectives. It may also be relevant to understanding the client's wider circumstances and support needs.
The following January
The annual review begins with these changes already visible.
The adviser still confirms the client's circumstances, considers the evidence and follows the firm's suitability and review processes.
But the meeting no longer has to begin with:
“So, what has changed since we last spoke?”
Keeping information current does not require one system to become the master database for every part of the client relationship.
Different systems have different jobs.
The objective is not one enormous database.
It is a controlled information flow in which each system performs the role it is designed for.
Lyfeguard is designed to provide a client-controlled information layer around an advice firm's existing systems.
Clients can organise information across areas including finances, property, family, estate planning and important documents, then choose what they share with their adviser.
Supported financial accounts can be connected read-only, allowing relevant balances and financial information to refresh without requiring the client to re-enter everything manually.
Other information remains client-led because that is where the context comes from.
A pension balance might update through a connection.
A new grandchild will not.
A property can be recorded.
A change in retirement intentions still needs the client to communicate it.
That combination matters because a financial life is wider than the accounts available through a data feed.
For the adviser, Lyfeguard can provide a more current, permissioned view of information the client has chosen to share.
It does not replace the firm's CRM, financial-planning software, suitability process or professional judgement.
Nor should every change made by the client automatically become verified firm data.
Instead, Lyfeguard sits earlier in the information flow: helping the client maintain a useful record, making relevant changes more visible and giving the firm better information to confirm and act upon through its own processes.
The result is a shift from repeatedly reconstructing a client's circumstances towards maintaining a more useful information relationship over time.
A fact-find is valuable because it establishes a picture of the client.
Its weakness is time. The moment it is completed, the client's life continues.
Accounts open and close. Families change. Careers move. Assets are acquired and sold. Plans change. Health changes. Documents are replaced. Priorities shift.
The answer is not to repeat the entire fact-find every few months. It is to build a better information flow between reviews.
That means knowing:
When those distinctions are clear, the annual review becomes less about reconstructing the client's past year and more about advising the person in front of you today.
