Most financial advice firms collect more data than they realise.

Their systems contain submission dates, client records, case statuses, provider information, meeting notes, task lists, file histories and completion dates. Teams also maintain spreadsheets, inbox folders and personal reminders to keep work moving.

Yet having data is not the same as having useful management information.

A dashboard containing dozens of numbers can still leave a managing director unable to answer basic questions:

• Where is work becoming delayed?
• Does the team have enough capacity?
• Which clients are waiting too long?
• How predictable is the firm’s service?
• Are operational changes producing better results?

The purpose of a key performance indicator is not to make reporting appear sophisticated. It is to help somebody recognise a problem, ask a better question or make a more informed decision.

The most useful measures for an advice firm therefore tend to be practical. They show how work enters the business, how efficiently it moves, where it stops and what clients experience as a result.

Start with the question, not the dashboard

Firms often begin reporting projects by asking what their software can display. A better starting point is to ask what the business needs to understand.

For example:

• If clients are regularly asking for updates, the firm needs information about waiting times and communication.
• If paraplanners feel overloaded, the firm needs information about incoming work, active caseload and allocation.
• If completion dates are unpredictable, the firm needs to understand how long cases spend at each stage.
• If management cannot see where cases are becoming stuck, the firm needs ageing and bottleneck information.

This approach prevents reporting from becoming a collection of figures that are technically available but operationally irrelevant.

A measure should have a clear purpose. Somebody should know why it is being monitored, what an acceptable result looks like and what action might follow when performance changes.

The difference between activity, performance and outcomes

Not all measures tell the same kind of story.

Advice firms commonly track activity:

• emails sent;
• tasks completed;
• provider requests submitted;
• meetings held; and
• reports produced.

These figures can be useful, but they mainly describe effort.

Performance measures go further. They might show how quickly work is completed, how many cases meet a target date or how much rework is required.

Outcome measures examine what the activity ultimately achieved. They may consider whether clients received timely support, understood the advice, experienced unreasonable delays or received a service consistent with the firm’s proposition.

A balanced set of management information should consider all three.

Counting completed tasks without examining waiting time can hide delays. Measuring speed without looking at quality can reward rushed work. Measuring revenue without considering capacity can encourage a firm to accept more work than it can deliver reliably.

Good reporting connects activity to performance and performance to client outcomes.

1. New cases received

Every firm should understand how much new work is entering the business.

This can be measured weekly or monthly and broken down by:

• adviser;
• case type;
• office or team;
• paraplanner;
• client segment; and
• source of business.

The number is valuable because demand affects almost every other operational measure.

A rising caseload may be positive commercially, but it can also increase waiting times, place pressure on quality checks and create an expanding backlog.

Looking at new submissions alongside available capacity helps management decide whether work should be redistributed, expectations adjusted or recruitment considered.

The figure should not be viewed in isolation. Ten straightforward annual review cases may require less work than two complex pension transfers. Volume therefore needs context.

2. Cases completed

The number of cases completed during a period provides a basic indication of output.

Comparing completed cases with new cases received can reveal whether the firm is keeping pace with demand.

If 40 cases enter the workflow and 30 are completed, the firm has added ten cases to its active workload. Repeating that pattern each month will eventually create pressure, even if everybody appears busy and completion volumes are rising.

Completion data is more useful when segmented by case type. Different services require different levels of research, documentation and implementation.

A single total can hide changes in the complexity of work being undertaken.

3. End-to-end turnaround time

Turnaround time measures how long a case takes from an agreed starting point to an agreed completion point.

The firm must define those points clearly.

Does the clock begin when the client first contacts the firm, when the adviser completes the fact-find, when the case is submitted to paraplanning or when all required information has been received?

Does completion mean the recommendation has been written, presented to the client, submitted to the provider or fully implemented?

Without consistent definitions, comparisons are unreliable.

Firms should also be careful with averages. A small number of exceptionally long or short cases can distort the result.

It can be helpful to monitor:

• the median turnaround time;
• the average turnaround time;
• the proportion completed within the target; and
• the oldest open cases.

Together, these provide a more complete picture than one headline number.

4. Time spent at each workflow stage

End-to-end turnaround time tells the firm that a case took too long. Stage-level data helps explain why.

A firm might track time spent:

• awaiting initial client information;
• awaiting provider information;
• waiting for allocation;
• in paraplanning;
• awaiting adviser review;
• awaiting client authority;
• with compliance or a case checker; and
• in implementation.

This distinction matters because different delays require different solutions.

Long provider waiting times may call for better chasing rules and proactive client communication. Long adviser review times may point to unclear expectations or capacity constraints. Long periods before paraplanning begins may indicate incomplete submissions or poor allocation.

Without stage-level information, management may respond to every delay in the same way, even though the causes are different.

5. Case ageing

Case ageing groups open work according to how long it has remained active.

A simple report might show cases open for:

• 0–14 days;
• 15–30 days;
• 31–60 days;
• 61–90 days; and
• more than 90 days.

The appropriate bands will depend on the firm’s services and expected timescales.

Ageing is valuable because a healthy average can conceal a small group of cases that have been unresolved for a long time.

Older cases should not automatically be treated as failures. Complex work, provider delays and client decisions can all extend the timeline legitimately.

The purpose of the measure is to make older cases visible so the firm can review whether the delay is understood, managed and communicated.

6. Cases at risk of missing their target date

A report showing missed deadlines is useful, but it arrives after the opportunity to prevent the problem.

Better management information identifies risk before the target date passes.

A case may be considered at risk when:

• it has spent too long at its current stage;
• required information remains outstanding;
• there has been no meaningful activity recently;
• the assigned person has more work than they can reasonably complete;
• an approval or quality check is still required; or
• the remaining work is unlikely to fit within the time available.

This turns reporting into an early-warning system.

Managers can intervene while there is still time to reallocate work, clarify an action, contact the client or revise expectations.

7. Work waiting by responsible party

It is useful to understand not only how many cases are delayed, but what they are waiting for.

Common categories include:

• waiting for the client;
• waiting for the adviser;
• waiting for the paraplanner;
• waiting for administration;
• waiting for the provider;
• waiting for compliance or checking; and
• waiting for a third party.

This prevents all unfinished work being treated as one undifferentiated backlog.

It can also reveal patterns. If a large proportion of cases repeatedly waits for adviser approval, the firm may need to review approval capacity or escalation arrangements. If many cases wait for clients immediately after submission, the initial fact-finding process may not be gathering enough information.

The aim is not to assign blame. It is to understand where the workflow loses momentum.

8. Active caseload by team member

Headcount alone does not show capacity.

Two paraplanners may each have 20 active cases, but their workloads may be very different if one is handling straightforward ISA work and the other is managing complex retirement planning.

Caseload should therefore be reviewed alongside:

• case complexity;
• current workflow stage;
• target dates;
• part-time or full-time working patterns;
• planned absence;
• quality-checking responsibilities; and
• other non-case duties.

The objective is not to make everybody’s numbers identical. It is to identify serious imbalances before they become delays.

Capacity reporting should support fair allocation, not become a simplistic league table.

9. Rework and resubmission

Completed cases do not always move through the process cleanly.

Work may be returned because:

• key information is missing;
• the recommendation changed;
• provider details were incomplete;
• the adviser’s instructions were unclear;
• documents were inconsistent;
• a quality issue was identified; or
• the client’s circumstances changed.

Some rework is unavoidable and may reflect effective quality control.

Repeated rework for the same reason, however, usually points to a process problem.

Firms should consider monitoring:

• the proportion of cases returned for amendment;
• the most common reasons for return;
• the workflow stage where problems are detected; and
• the additional time created by rework.

This information can support better training, clearer submission standards and more effective checklists.

10. Submission completeness

A case that enters the workflow without the required information often creates delay throughout the rest of the process.

The paraplanner may begin work and then stop. The adviser is asked for clarification. The client is contacted again. Documents are uploaded separately. The target date remains unchanged even though meaningful work could not begin.

A submission-completeness measure can show:

• the proportion of cases accepted first time;
• which required items are most often missing;
• how long incomplete cases remain unresolved;
• which case types generate the most clarification; and
• the effect of incomplete submissions on turnaround time.

This is one of the clearest opportunities to improve efficiency without asking people to work faster.

11. Client update performance

A case can be progressing internally while still feeling inactive to the client.

Firms should understand whether clients are being updated in line with the service they were promised.

Measures might include:

• the date of the last meaningful client update;
• the proportion of active clients updated within the agreed period;
• the number of inbound progress-chasing calls or emails;
• the number of complaints relating to communication or delay; and
• whether vulnerable clients received any additional support required.

The emphasis should be on meaningful communication rather than automated messages sent merely to satisfy a target.

A useful update explains the current position, any outstanding issue and when the client should expect to hear from the firm again.

12. Client outcomes and service quality

Operational reporting should ultimately help the firm understand the service its clients receive.

The FCA’s Consumer Duty requires firms to monitor the outcomes retail customers experience. The information used will vary according to the firm’s size, client base, products and role.

For an advice firm, relevant information could include:

• complaints and their root causes;
• cases where agreed service standards were not met;
• client feedback;
• communication and understanding checks;
• support provided to clients in vulnerable circumstances;
• cancellations or withdrawals;
• implementation failures;
• different outcomes experienced by different client groups; and
• actions taken when poor or potentially poor outcomes are identified.

The purpose is not merely to prove that the firm followed its process.

A completed checklist does not by itself demonstrate that a client understood the advice, received appropriate support or experienced a reasonable service.

Management information should help the firm move from:

“Did we complete the required steps?”

to:

“What happened to the client, and what does that tell us?”

13. Revenue and profitability by case type

Operational measures should not be separated entirely from commercial performance.

A case type that generates strong revenue may appear attractive until the firm considers the time, complexity and rework involved in delivering it.

Useful measures may include:

• revenue by adviser;
• revenue by case type;
• average revenue per completed case;
• internal or outsourced paraplanning cost;
• estimated staff time;
• rework cost;
• revenue delayed by incomplete cases; and
• gross contribution by service or case type.

These measures need careful interpretation.

An adviser working with complex or vulnerable clients should not be judged only against somebody handling higher-volume, simpler work. Some services may also be strategically important even when their immediate margin is lower.

Commercial data should inform decisions, not replace judgement.

How many KPIs does a firm need?

There is no universal number.

A smaller advice practice may need a concise weekly view containing eight or ten measures. A larger firm may require separate dashboards for advisers, operations, compliance and senior management.

The reporting should remain proportionate to the business.

A useful starting set might include:

1. New cases received
2. Cases completed
3. Active cases
4. Median turnaround time
5. Cases outside the target timescale
6. Cases at risk of missing their target
7. Cases with no recent activity
8. Work waiting by responsible party
9. Active caseload by team member
10. Rework or incomplete-submission rate
11. Clients due an update
12. Complaints, service failures or poor-outcome indicators

Additional measures can be introduced when there is a clear reason for doing so.

How often should KPIs be reviewed?

Different information supports different decisions.

Daily or live

Operational teams may need immediate visibility of:

• overdue actions;
• cases at risk;
• unassigned work;
• clients due an update; and
• cases with missing information.

Weekly

Team leaders may review:

• incoming and completed work;
• caseload and capacity;
• ageing cases;
• stage-level delays; and
• upcoming target dates.

Monthly or quarterly

Senior management may focus on:

• longer-term trends;
• service performance;
• client outcomes;
• complaints and root causes;
• revenue and profitability;
• recruitment or capacity requirements; and
• whether improvement actions produced the intended result.

The frequency should match the speed at which the information can change and the urgency of the decisions it supports.

Turn reports into action

Reporting is valuable only when it creates an appropriate response.

Each KPI should have:

• a clear definition;
• a named owner;
• an agreed review frequency;
• a target, threshold or expected range where appropriate;
• a method for investigating unexpected results; and
• a record of actions agreed.

Suppose the firm discovers that cases are spending an increasing amount of time awaiting adviser review.

The correct response is not simply to add the figure to next month’s report. Management should investigate:

• whether the increase affects the whole firm or particular teams;
• whether case volume or complexity has changed;
• whether advisers receive enough notice of upcoming reviews;
• whether responsibilities are clear;
• whether reports require avoidable amendments; and
• whether a change in allocation or workflow would help.

The action should then be reviewed to see whether it worked.

This creates a useful cycle:

1. Measure the position.
2. Identify an issue or risk.
3. Investigate the cause.
4. Take proportionate action.
5. Review the result.

Without the final step, firms can accumulate improvement actions without knowing whether they improved anything.

Ask yourself

Consider the management information currently used in your firm:

• Can you see where cases are becoming delayed?
• Can you identify risk before a target date is missed?
• Can you distinguish internal delays from external ones?
• Can you see whether work is distributed fairly?
• Can you identify repeated causes of rework?
• Can you tell which clients are waiting for an update?
• Can you connect operational performance with client outcomes?
• Does every report lead to a question, decision or action?
• Could somebody explain exactly how each KPI is calculated?

If not, the firm may have plenty of data but very little operational visibility.

Measure what helps the firm improve

The best advice firms do not necessarily have the most elaborate dashboards.

They have reliable information that helps them understand what is happening and act before small problems become larger ones.

They can see when demand is outpacing capacity. They know which cases are becoming old, which stages are slowing down and which clients may need an update. They can distinguish unavoidable external delays from problems within their own process.

Most importantly, they do not treat reporting as an administrative exercise.

They use it to ask better questions:

What is changing, why is it changing, who is affected and what should we do about it?

A KPI earns its place when it helps answer one of those questions.

Everything else is just data.