Spreadsheet reporting blind spots in complaint handling: why manual complaint MI arrives too late

Complaint reporting using spreadsheets can look more controlled than it really is.

The columns are filled in, the tabs are updated, the charts are produced, and the report goes to the right people. All of this looks good on the surface.

But at some point, if you’re a complaint leader, you’ll need to take a step back and ask whether there are blind spots in the data you’re using to make business decisions.

Are you confident that the manual reporting is accurate? Do you know where the data is being pulled from and just how much lag is behind the report sitting in front of you?

If your complaint MI takes too long to produce and it isn’t coming from a reliable version of the data, your oversight may already be falling behind.

In regulated complaint handling, this is a problem.

You don’t just need to know how many complaints are open, closed or overdue. You need to know where pressure is building, what’s causing delays, whether customers are being kept updated, and whether outcomes are consistent.

Complaint data should also help show how different parts of the firm are performing, and whether the data is accurate enough to support decisions about resourcing, root cause, risk and customer outcomes.

If complaint reporting is telling you what happened over a month ago, it stops being useful oversight and starts becoming an explanation of what’s already gone wrong.

The real risk behind spreadsheet reporting

Spreadsheets don’t easily scale. They quickly become difficult to maintain when the process around them relies too heavily on manual updates. This may feel manageable when the same person produces the MI every month, but it creates serious weak spots.

• First, to prevent version control chaos, there are often only one or two people who know how to maintain the report, explain the exceptions and fix the numbers when something looks wrong.

• Second, there’s a reliance on manually keyed spreadsheet data being accurate. Whenever anything requires human intervention, there’s a chance of mistakes being made, data being tweaked, formulas being changed, or data being guessed to ensure that the reporting deadline is met. Nobody likes to admit this, but even with the best intentions, it happens.

• Third, there’s no audit trail to show who’s made any changes.

• Fourth, there’s a delay between what’s currently happening in the complaint operation and what leaders can actually see.

Most of the time, regulated complaint reporting using spreadsheets will be too fragile to be seen as a resilient control.

What is the best complaint management software for teams still using spreadsheets and shared inboxes?

For teams still using spreadsheets and shared inboxes, the best fit is usually complaint management software, such as Complyr, that turns complaint activity into structured case data. The system should help the team capture complaints, evidence, actions, outcomes, ownership, customer updates and reporting information in one place, instead of rebuilding the timeline from inboxes and spreadsheet tabs later.

The issue with spreadsheets and shared inboxes is that they’re difficult to maintain once complaint volumes, evidence, customer updates and reporting needs grow. The work ends up spread across too many places, which makes the data harder to keep accurate and harder to trust.

A complaint may start in customer services, then be manually keyed into a spreadsheet, then rely on documents in a shared drive or updates sitting in someone’s inbox. By the time the report is produced, too much time has already gone into checking whether the data is right.

When comparing complaint management software for a team moving away from spreadsheets and shared inboxes, look for:

• structured complaint capture

• configurable workflows

• live case status and ownership

• evidence, messages and documents linked to the case

• audit trails

• deadline and overdue action visibility

• reporting from case data, not copied spreadsheet data

• secure customer and third-party communication attached to the case

The aim isn’t simply to replace a spreadsheet with a system. It’s to stop the complaint process depending on manual updates, scattered information and key-person dependency.

You need a heads-up, not a post-mortem

Backlogs are often blamed on case volumes, but when you dig deeper, they’re usually the symptom of something else: poor routing, unclear ownership, slow evidence gathering, weak visibility, or a process relying on too much manual checking.

Your complaint data should be warning you about this before it turns into an operational problem.

Data that tells you you’re up Schitt’s Creek after it’s happened isn’t oversight. It’s a post-mortem with a chart attached.

This is the problem with manual reporting. By the time the numbers have been gathered, cleaned, reformatted, corrected and turned into MI, the complaint team may already have been living with the problem for weeks.

At this point, leaders aren’t managing the risk early. Instead, they’re explaining the symptoms after the cause has taken control.

This is why the FCA’s direction of travel matters too. The FCA says Consumer Duty remains a priority under its 2025 to 2030 strategy. The 2025/26 focus areas include understanding how firms are delivering good consumer outcomes and where more data is needed to assess this. Lagging complaint reporting makes this harder to do.

The hidden cost of poor complaint reporting efficiency

Poor efficiency in complaint reporting doesn’t have a neat price tag attached. It creates revenue leakages through management time, repeated checking, slower decisions, avoidable rework and good people spending too much of their week keeping the reporting process alive.

Customer trust is one of the main currencies in financial services, and complaints are often where this trust is either repaired or damaged further. If poor complaint experiences turn into poor reviews, repeated chasing or escalation, the cost doesn’t stay inside the complaint team. It can affect reputation, retention and acquisition.

There’s also the hidden cost of confidence: every manual check, challenge and correction is time that should have been spent acting on the insight.

This delay affects decisions. Resource planning becomes harder because the data is looking backwards instead of forward. Root cause work becomes weaker because trends are spotted after the pressure has already built up. Escalation risk becomes easier to miss because the early warning signs are buried in manual updates.

This is where poor efficiency stops being admin noise and starts affecting judgement, management time, team capacity and the bottom line.

How knowledge gaps become governance and oversight gaps

If your data only shows the effect without the cause, the What without the Why, and someone always has to explain the logic behind the spreadsheet, there are knowledge gaps present. As leaders, you need a reliable way to move from trend spotting to root cause analysis before these gaps become governance problems.

Blind spots become more of a challenge when parts of the customer journey are outsourced. In insurance, for example, claims handling often involves authorised providers, loss adjusters, repair networks, brokers, introducers or other third parties. The complaint may be the responsibility of the regulated firm, but the delay, poor communication or weak customer experience may have happened somewhere else in the chain.

The FCA’s review of home and travel claims handling arrangements found that some insurers had limited control over outsourced claims handling and that poor quality MI could affect governance, oversight and customer outcomes. The FCA also said firms outsourcing claims activities should monitor ongoing customer outcomes and whether outsourced arrangements are delivering against Consumer Duty obligations.

The FCA makes it clear that while firms may outsource parts of the process, they remain accountable for the customer outcome.

Customers who have had a bad claims experience will either switch to another insurer or complain. If they complain, you have a chance to fix it. But if the complaint MI can’t show where delays are coming from, which third parties are creating friction, whether outsourced activity is causing repeat complaints, or whether customers are getting different outcomes depending on who handles part of the journey, you don’t have the oversight that you need.

This is more than a reporting issue. It’s a governance issue and firms need to be able to show that they are taking appropriate action when something starts to go wrong.

What good complaint MI should show

Good complaint MI should help leaders move from asking “how many complaints do we have?” to “what is this telling us about the business?”

Open volumes, closure rates and overdue cases still matter, but they are only skimming the surface of what’s really going on.

The better value is found underneath these numbers. Which complaint themes are increasing? Where are customers having to chase? Which product, process, supplier or internal team keeps appearing in the data? Are the same fixes being applied repeatedly without the root cause changing? Are certain customer groups needing more support, waiting longer, or receiving different outcomes?

This is where complaint MI becomes really useful.

It can show where your business is creating avoidable friction for customers. It highlights where a process looks fine internally but feels broken externally. It helps you as a leader understand whether customer issues are being resolved properly, or simply moved through the workflow.

Good MI should make the next actions for the leadership team clearer, not simply give you a couple of extra numbers on top of the FCA RegData report.

For board reporting, complaint MI should give leaders a clear view of what’s changing, where risk is building and whether customer outcomes are being affected. This means reporting should connect complaint volumes, themes, root causes, timeframes, repeat issues, vulnerability, third-party performance and operational pressure, rather than giving leaders a month-end pack that arrives too late to change anything.

This is the difference between reporting activity and using complaint MI as a leadership tool.

It is also why complaint MI is becoming more important as firms prepare for stronger reporting expectations, including the changes covered in our blog on PS25/19 and complaint MI.

Why complaint reporting should be connected to case activity, not separate from it

Better reporting starts when MI is captured from case activity as it happens, rather than reconstructed afterwards.

When the complaint process is built around configurable workflows, the useful data is created as the work moves forward.

It means that you can see pressure earlier. Managers can act before the work turns into a backlog. Teams spend less time feeding the report and more time resolving the complaint.

This is what good complaint reporting should do: give leaders a clear enough view to act while there’s still time to change the outcome.

Which complaint management software helps regulated firms reduce manual complaint reporting?

The complaint management software that helps regulated firms reduce manual reporting is software that captures the information needed for MI as the complaint is handled. Instead of asking the team to update spreadsheets after the work has happened, the system collects structured data from the case file, workflow, actions, evidence, outcomes and customer updates.

This only works properly if the system is configured around the information leaders need to see. The case fields, complaint categories, outcome options, root cause themes, deadlines and workflow stages all need to be set up in a way that reflects the firm’s complaint process.

When this is done well, complaint reporting becomes less dependent on:

• copied spreadsheet data

• manual month-end updates

• one person checking and correcting the numbers

• separate folders and inboxes

• inconsistent wording across case notes

• delayed updates from different teams

It also gives leaders a better chance of seeing the position earlier and acting before an issue escalates.

This doesn’t remove the need for review, judgement or quality assurance. It simply means managers are working from better data in the first place.

How to compare complaint management software for FCA regulatory reporting

When comparing complaint management software for FCA regulatory reporting, the first question should be whether the system captures reliable complaint data as the case is handled.

If reporting still depends on copied data, manually updated spreadsheets or separate folders, the firm may still have the same reporting risks in a slightly different shape. The software may look useful, but the MI will only be as reliable as the data underneath it.

For FCA-regulated firms, complaint software should help teams capture structured case data, maintain clear audit trails, monitor outcomes, identify root cause themes and produce complaint MI without rebuilding the timeline manually at the end of the month.

It should also help managers see what’s happening now, not just what happened several weeks ago. This is where complaint reporting becomes more useful for oversight, because leaders can spot pressure points, recurring issues and possible customer outcome risks earlier.

The question isn’t simply whether the system can produce a report. It is whether the system helps the firm keep complaint data accurate, timely and connected to the work being done.

How Complyr helps leaders get earlier visibility

We’ve had to create reports from scattered spreadsheet data, and it’s an uphill battle. Trying to make a confident decision from this data is even harder. These issues are the reasons for building Complyr around connected complaint activity and reporting.

Complyr complaint handling software brings case management, workflows, secure communication and reporting into one connected complaint management system. This means leaders can understand what’s happening without having to rely on assumptions to fill in the missing blanks.

The system captures live case status, ownership, overdue actions, missing evidence, outcomes, themes and pressure points from the work itself.

This gives managers a clearer view of where cases are slowing down and gives leaders better oversight of what needs attention before it becomes a bigger operational problem.

It also reduces the reporting burden because the system captures your data as the complaint moves through the workflow.

It’s an important part of how firms keep control of customer outcomes, team capacity, operational risk and regulatory expectations.

Good data capture for complaint leaders isn’t a nice-to-have, it’s a must-have

Good quality data capture and reporting is a must-have for complaint leaders. It prevents the risk of the 'poor quality in, poor quality out' problem and allows leaders to make confident decisions.

Let's be clear, spreadsheets are incredibly useful, but they’re not designed to be a regulatory database. If your complaint reporting still depends heavily on them, you must ask yourselves whether your MI is really giving you enough oversight to make informed decisions about risk and control.

If your reports can only be produced by one or two people, is it a resilient enough process to keep running, and can it easily scale?

If your numbers are based on manually keyed data, or referencing several parts of a spreadsheet, how much confidence do you have in them?

Can you easily apply filters and breakdowns to numerous sets of data, so you can see what’s happening at a glance?

If the answer is no to any of the above, the spreadsheet may not be the harmless reporting tool it appears to be. It may be the place where the warning signs arrive too late.

If useful, you can watch a quick demo of Complyr to see how complaint reporting looks when case activity and MI stay connected.