Why more current data improves timing across engagement, support, and risk decisions

Most organisations invest heavily in customer data, so decisions across engagement, support, and risk are built on what looks like a solid foundation. And on the surface, it works. Teams act quickly, processes are in place, and activity happens where you’d expect it to. Yet while decisions may be happening in real time, they depend on how current the data behind them actually is.

Income changes, employment changes, spending adjusts, often gradually and without anything obvious showing up straight away. Meanwhile, the data feeding those decisions updates on its own schedule. It follows reporting cycles, refresh intervals, and internal processes that don’t always line up with what’s happening in the customer’s world.

And that’s where things start to slip. Decisions are being made in the moment, but they’re grounded in a version of the customer that may already be out of date. As Sheldon Mills, FCA Executive Director of Consumers and Competition, put it: “Firms also need to get serious about their data and not assume they can just re-package existing information.”

 

Key takeaways from this article: Most decisions are built on the last available data rather than the customer’s current situation Customer circumstances change between data updates, often without visible triggers Decisions can appear appropriate while being based on conditions that no longer hold Outdated data affects prioritisation, segmentation, and support across the lifecycle More current customer data improves decision accuracy by aligning actions to what is actually happening in the customer’s world

 

Customer change of circumstance happens between data points

The key issue here is that customer circumstances change in the moment, but data updates catch up later. For instance, income fluctuates, employment changes, and spending behaviour adjusts, often gradually, with nothing immediate appearing in the systems teams rely on. From an operational perspective, the customer may appear stable, while the underlying position is already in motion.

And that’s where it becomes harder to rely on what you see.

Decisions continue to be made based on the last recorded position, even as the customer’s situation moves beyond that point. Across engagement, support, and risk, there is an assumption that the data reflects the current state, when in reality it reflects the most recent update.

That difference starts to show up in how decisions are applied. You might see:

• income is becoming less consistent without affecting payments straight away
• employment changing between reporting cycles
• borrowing moving towards essential costs, while overall exposure appears stable

 

The UK unemployment rate stood at 4.9% in early 2026, with 1.78 million people out of work, and several million more moved in and out of employment, contract work, and self-employment across any given year.

Each of these can sit below the threshold on its own. Look at them together, and the picture is different. So decisions continue to follow the same logic, applied to a customer who is no longer in the same position.

That’s where accuracy starts to erode:

• cases are prioritised based on a previous state
• segmentation reflects earlier behaviour
• support is aligned with what was true at the last update

 

And because the data still looks complete, the decision itself can look right. It no longer fits the customer it is being applied to.

↪️Further reading: What FCA-aligned vulnerability identification looks like in operational teams

What outdated customer data does to decision accuracy

Once you start examining decisions against the customer’s actual position, the impact becomes easier to see.

Decisions don’t suddenly stop working. In most cases, they continue to follow the same logic, the same rules, and the same thresholds. What changes is the context they’re applied to. As customer circumstances move on, the data behind those decisions does not always keep pace. The logic stays consistent. The conditions underneath it begin to erode.

You see it in small ways at first:

• engagement assumes a customer is still reachable in the same way
• support reflects a view of affordability that no longer matches current income and expenditure insight
• risk decisions continue to follow past behaviour, even as that behaviour begins to change

 

None of these triggers an alert. Each follows the correct process and uses the data available. 

When two identical profiles produce different outcomes

Take two customers with similar account profiles. Both are up to date on payments, both sit in the same risk band, and both are managed under the same decisioning rules. One has recently moved to less stable employment and is relying on short-term credit for day-to-day spend. The FCA’s 2024 Financial Lives survey found that around 1.6 million UK adults with personal loans were already using them to cover everyday expenses like food, travel, or rent. The other customer has not changed.

That position does not show up in the data. So both continue to be treated in the same way.

What this looks like over time

One continues to perform as expected. The other shows signs of strain, despite both being managed in exactly the same way. The decisioning logic hasn’t changed. The process hasn’t changed. But the customer has. Decisions are being applied consistently, though not to the same version of the customer. But, at scale, that variation becomes harder to explain.

↪️Further reading: Open Banking hits 15 million users, but vulnerability needs a broader lens

Speed isn’t the constraint. Data recency is Most operations teams are already moving quickly. Processes are in place. Decisions are made where expected. Speed is rarely the problem. Decisions are only as accurate as the data behind them. When that data reflects a previous state, acting faster changes nothing. The logic runs correctly. The information is already out of date. The FCA’s review of Consumer Duty board reports found that some firms lacked sufficient data quality to justify their conclusions or give governing bodies adequate assurance they were meeting their obligations.

How more current customer data improves decision quality

Once the data behind a decision becomes more current, the quality of that decision starts to change as well. The assumptions behind those decisions are closer to the customer’s actual position. And that changes the basis on which the operation is working.

For example:

• engagement reflects current reachability rather than historic contact data
• support decisions align more closely to current affordability, using more recent income and expenditure insight
• risk assessment reflects current employment data and more recent changes in customer circumstances, alongside historic behaviour

 

And once those inputs become more current, consistency improves as well. Teams are no longer working from different versions of the customer, depending on when systems were last refreshed or which data source updated first. Decisions are applied against a view that is more closely aligned to the customer’s current situation.

That carries through the lifecycle:

• prioritisation becomes more accurate because it reflects current conditions
• support aligns more closely with present circumstances
• engagement becomes more relevant because contact strategies reflect how customers can actually be reached and supported

 

The FCA’s 2025/26 Consumer Duty priorities include a specific focus on poor identification of customers with characteristics of vulnerability (an area where current affordability and circumstance data matters most).

The decisioning framework itself may not change at all. The quality of the information feeding into it does. And that has a direct effect on how accurately decisions reflect the customer the organisation is actually dealing with at that point in time.

The commercial case sits alongside the regulatory one. The 2025 IBM Institute for Business Value report found that over a quarter of organisations estimate annual losses of more than $5 million from poor data quality alone.

↪️ Further reading: Why vulnerability detection must move earlier in the lifecycle

Maintaining a current view using real-time customer data

More current data only improves decision quality if that view stays consistent across the lifecycle. And consistency is harder to maintain once customer circumstances move faster than the core systems update. When that happens, teams across engagement, support, and risk start working from different versions of the same customer, depending on which data source updated first and when the last refresh was captured.

This is where FinTrace and KYVC are typically used.

FinTrace: visibility of customer change of circumstance

FinTrace improves visibility of customer movement as circumstances change, including:

• more current contact and reachability data
• current employment data and change of circumstance insight
• income and expenditure signals linked to affordability
• FCA-aligned vulnerability indicators beyond standard CRA refresh cycles

 

That reduces the delays between what is happening and what you can actually see.

YouGov research found that 6 in 10 UK adults display at least one characteristic that makes them potentially vulnerable under FCA criteria. Identifying those customers depends on having data that reflects their current circumstances, not their position at the last update.

KYVC: connecting signals to operational decisions

KYVC then brings those signals together within one single place, linking:

• identity and contactability
• behavioural and affordability insight
• vulnerability indicators aligned to Consumer Duty expectations

 

This helps engagement, support, and risk teams work from a more consistent customer position, rather than separate snapshots captured at different points in time.

And once that view becomes more consistent, decision quality improves with it.

What teams should review in their customer data strategy

Most teams find the answer once they start testing the assumptions sitting underneath day-to-day decision-making. And the questions themselves are often more revealing than another data refresh would be: 

• how current is the data behind engagement, support, and risk decisions?
• how often do customer circumstances change between data refresh points?
• where are decisions still relying on historic affordability or employment data?
• which systems update first, and which continue working from older customer positions?
• do different teams make decisions using different versions of the same customer?

 

This is where the operational impact of data recency tends to become visible. Customer circumstances move independently of the update cycles supporting those processes. And once that happens, decision quality starts to vary across the lifecycle, even where the underlying framework remains consistent. That’s usually the point where organisations begin reassessing how current customer data is maintained operationally, and how quickly changes in employment, affordability, or contactability become visible across the operation.

Why decision quality depends on current customer data Most organisations are not short of customer data. The problem is that much of it reflects a previous position. The FCA’s March 2025 review of firms’ treatment of vulnerable customers found that only four in ten consumers with characteristics of vulnerability had disclosed their circumstances to their provider. Firms cannot rely on disclosure alone. They need data that reflects the customer’s current position. The same review found that firms with good quality data were better placed to make evidence-based assessments of customer outcomes. Those that struggled were monitoring process outputs rather than actual customer circumstances. The framework is the same. The data is what changes things.

Test how current your customer view really is

Most organisations already have the decisioning frameworks in place.

But what’s less clear is how current the customer data behind those decisions actually is, and how often customer circumstances change between updates.

And that’s where we come in. We provide a Proof of Value to help teams assess:

• where decisions rely on historic customer positions
• how current employment, affordability, and contactability data change decision quality
• where more current customer insight improves consistency across engagement, support, and risk

From there, it becomes easier to see where data recency is affecting operational accuracy across the lifecycle. Book a Proof of Value Concept today.