How to Build a Workflow That Scales

Many financial advice firms do not experience workflow problems when they are small.

An adviser can lean across a desk and ask an administrator for an update. A paraplanner knows which cases are urgent because they discussed them that morning. The operations manager remembers which client is waiting for a provider response.

The process works because people know one another, communicate frequently and carry a large amount of operational information in their heads.

Then the firm grows.

More advisers submit work. More case types are introduced. Staff work remotely or across different offices. New employees join without years of accumulated knowledge. The number of active cases increases and the informal process begins to struggle.

Questions become more frequent:

• Has this case been allocated?
• Who is waiting for the client?
• Was the provider chased?
• Is the report ready for review?
• Why has this case not progressed?
• Which version of the document is correct?

The usual response is to work harder. Teams hold more meetings, send more messages and maintain more spreadsheets.

That can keep the service functioning temporarily, but it does not create a workflow that scales.

A scalable workflow allows the firm to handle more work without increasing confusion at the same rate. It makes the correct next step easier to identify, reduces reliance on individual memory and allows managers to see problems before clients experience them.

What does a scalable workflow mean?

Scalability is sometimes treated as a technology question.

Firms assume that replacing a spreadsheet with a larger system will solve their workflow problems. Technology can certainly help, but it does not make an unclear process clear.

A scalable workflow has several characteristics:

• each case enters through a consistent route;
• required information is defined before work begins;
• the current stage is visible;
• responsibility for the next action is clear;
• expected timescales are understood;
• exceptions can be identified and managed;
• important decisions are recorded;
• managers can understand demand, capacity and risk; and
• clients receive a consistent level of communication.

This does not mean every case must follow an identical path.

Financial advice involves judgement. Clients have different circumstances, cases vary in complexity and unexpected issues arise. A workflow should not attempt to remove professional discretion.

It should create consistency around the parts of the service that should be consistent, while making genuine exceptions easier to recognise.

Why informal workflows eventually fail

Informal processes often work well until the volume of work exceeds the team’s ability to remember and communicate everything.

The problem is not necessarily that staff are performing poorly. In many firms, employees compensate for weak systems through effort and experience.

They create personal methods:

• flagged emails;
• private task lists;
• colour-coded spreadsheets;
• handwritten notes;
• calendar reminders;
• folders named “urgent”; and
• regular messages asking colleagues for updates.

These methods can be effective for the individual using them. They are less effective as a shared operating model.

When information is held privately, the firm cannot easily see the overall position. Work may be duplicated, forgotten or delayed. A manager may believe that a case is progressing because it has an owner, while the owner is waiting for information that nobody else knows is missing.

Growth exposes these weaknesses. It does not create them.

1. Define where the workflow begins and ends

Before designing stages, agree what the workflow is intended to cover.

Does the case begin when:

• a client makes an enquiry;
• an adviser holds the first meeting;
• the fact-find is completed;
• the client agrees to proceed;
• the case is submitted to support staff; or
• all required information has been received?

Does it end when:

• the suitability report is completed;
• the adviser presents the recommendation;
• the client signs the paperwork;
• the application is submitted;
• the recommendation is fully implemented; or
• the client receives a final confirmation?

Different firms may choose different boundaries. The important point is that the definitions are explicit.

Without agreed start and finish points, turnaround times become unreliable and cases can disappear between teams. One department may consider its work complete while another does not yet recognise that responsibility has transferred.

Clear boundaries also make it easier to decide which activities belong in the main workflow and which should be managed separately.

2. Map the current process before redesigning it

Firms often document the process they believe staff follow.

The more useful exercise is to document what actually happens.

Select several recent cases and trace them from beginning to end. Include a mixture of straightforward, complex, delayed and withdrawn cases.

For each one, record:

• who performed each action;
• where information was recorded;
• which decisions were required;
• how responsibility transferred;
• where the case waited;
• what caused rework;
• when the client was contacted; and
• which steps depended on personal knowledge.

This commonly reveals that the real workflow contains more handovers and workarounds than the official process suggests.

A case may move from the adviser to an administrator, back to the adviser, across to a paraplanner, back for clarification, forward for checking and then return again for implementation.

Mapping those movements helps the firm distinguish necessary professional review from avoidable repetition.

3. Create meaningful workflow stages

Workflow stages should explain where a case is and what is happening to it.

Broad labels such as Open, Pending or In progress provide very little operational value.

More meaningful stages might include:

1. Draft submission
2. Awaiting required information
3. Ready for allocation
4. Allocated to paraplanner
5. Research and analysis
6. Suitability report in progress
7. Awaiting adviser review
8. Amendments required
9. Ready for client meeting
10. Awaiting client decision
11. Implementation in progress
12. Completed

The firm does not need dozens of stages. Too many can make the workflow difficult to maintain and encourage staff to choose whichever status seems closest.

Each stage should answer three questions:

1. What is happening?
2. Who normally owns the next action?
3. What must happen before the case moves forward?

If two stages have the same owner, same actions and same exit criteria, they may not need to be separate.

4. Define entry and exit criteria

A workflow becomes unreliable when people interpret stages differently.

Consider a status called Ready for paraplanning.

For one adviser, that may mean the fact-find has been completed. For another, it may mean provider information is present, objectives are clear and all supporting documents have been uploaded.

The same status then describes cases at very different levels of readiness.

Entry criteria define what must be true before a case enters a stage. Exit criteria define what must be true before it leaves.

A case entering Ready for paraplanning might require:

• a completed and current fact-find;
• clear client objectives;
• documented adviser instructions;
• relevant provider information;
• risk and capacity-for-loss information;
• fee details;
• supporting documents; and
• confirmation of the target completion date.

The exact requirements will depend on the service and the firm’s procedures.

Clear entry criteria reduce the likelihood that work begins and then stops because essential information is missing.

5. Standardise submissions

A scalable workflow starts with a consistent intake process.

When cases arrive through emails, messages, conversations and separate spreadsheets, support teams must reconstruct the adviser’s request before they can begin the work.

A standard submission should capture the information needed for the specific case type.

This could include:

• client details;
• the advice being requested;
• objectives and priorities;
• relevant timescales;
• products or arrangements to be reviewed;
• provider information;
• known vulnerabilities or communication needs;
• documents required;
• adviser considerations or proposed direction; and
• any unusual features of the case.

Standardisation does not mean asking every possible question on every case.

A pension switch should not require the same information as protection, an ISA contribution or an annual review. The submission process should adapt to the work being requested while maintaining consistent minimum standards.

6. Make ownership visible

A case can involve several people without being jointly owned by everyone.

At any point, the team should be able to identify:

• the person accountable for the case overall;
• the person responsible for the current action;
• the person expected to act afterwards; and
• the person who should intervene if progress stops.

These may not always be the same person.

For example, an administrator may own the current action of obtaining provider information while the adviser remains accountable for the overall client relationship.

Clear ownership prevents tasks from becoming stranded between teams.

It also reduces unnecessary messages. People no longer need to ask the entire team who is dealing with something because the current responsibility is already visible.

7. Record the next action and expected date

A status describes the current position. A next action explains how the case will move forward.

Compare these two records:

“Waiting for provider.”

and:

“Administrator requested transfer information from the provider on 14 July. Chase on 21 July if it has not been received.”

The second record gives the team a plan. It identifies the owner, action and review date.

Every active case should ideally have:

• a clear next action;
• a named owner;
• an expected or review date; and
• an explanation where no action can currently be taken.

This does not mean inventing deadlines for events outside the firm’s control. When waiting for a provider or client, the expected date may be the point at which the firm will review, chase or communicate again.

8. Separate active work from waiting time

A case may be open for 60 days without requiring 60 days of work.

Much of that time may be spent waiting for:

• the client;
• the provider;
• an adviser decision;
• a third-party professional;
• a compliance review; or
• an implementation event.

A scalable workflow distinguishes between work being actively completed and work waiting for something else.

This helps managers understand whether a delay is caused by internal capacity, incomplete information or an external dependency.

It also supports better client communication. Instead of saying that a case is merely “in progress”, the firm can explain precisely what is outstanding and what it is doing next.

9. Build escalation into the process

Escalation should not depend entirely on somebody noticing that a case feels old.

The workflow should define when additional attention is required.

Possible triggers include:

• no meaningful activity for an agreed number of working days;
• a case remaining at one stage beyond the expected period;
• missing information not supplied after repeated requests;
• a target completion date approaching with significant work outstanding;
• a vulnerable client experiencing delay;
• a complaint or expression of dissatisfaction;
• a repeated quality issue; or
• an external dependency placing the intended outcome at risk.

Escalation does not always mean involving senior management.

It may mean reallocating a task, contacting the adviser, agreeing a revised date, sending a proactive client update or deciding that a different approach is required.

The purpose is to make delay visible while there is still time to respond.

10. Design for exceptions

No workflow can predict every situation.

A rigid process may work for standard cases but become difficult when:

• a client’s circumstances change;
• the recommendation changes during research;
• new information creates a compliance concern;
• a provider cannot supply the expected evidence;
• the client requires additional support;
• an urgent deadline emerges; or
• the case must be paused or withdrawn.

Scalable workflows do not pretend exceptions will disappear. They provide a clear way to manage them.

That may include:

• a documented exception status;
• a reason for departing from the normal process;
• approval where appropriate;
• a revised owner or timescale;
• a record of communication with the client; and
• a route back into the standard workflow.

When exceptions are handled invisibly through private messages, the organisation loses the opportunity to understand how often they happen and why.

11. Reduce unnecessary handovers

Every handover creates an opportunity for delay or information loss.

The receiving person needs enough context to understand:

• what has already happened;
• what decision has been made;
• what they are expected to do;
• when it is needed; and
• where the supporting information can be found.

Some handovers are necessary because the work requires different skills, responsibilities or controls.

Others exist because the process evolved gradually.

When mapping the workflow, ask of every handover:

1. Why does responsibility need to move here?
2. What information must accompany the transfer?
3. How does the receiving person know the case is ready?
4. Could the work be completed with fewer transitions?

Removing one unnecessary handover from every case can produce a significant benefit when repeated across the year.

12. Create one reliable operational record

A scalable workflow needs a recognised source of truth.

That does not necessarily mean every document and communication must live in one system. It means the firm has one reliable place to understand the operational position of the case.

Staff should not need to search an inbox, spreadsheet, client file and messaging platform to discover:

• the current status;
• the current owner;
• the next action;
• the target date;
• what is outstanding; and
• when the client was last updated.

Where systems contain conflicting information, teams begin to rely on whichever source they personally trust. That recreates the informal workflow the firm was trying to replace.

Agree where each type of information should be recorded and make that expectation part of the normal process.

13. Automate carefully

Automation can remove repetitive administration, but automating a poor process can make its weaknesses more difficult to see.

Useful automation might:

• assign standard checklist items based on case type;
• notify somebody when responsibility transfers;
• highlight cases with no recent activity;
• identify approaching target dates;
• prompt the team when a client update is due;
• create routine follow-up tasks;
• prevent submission where essential information is missing; or
• produce management information without manual collation.

Automation should not make important decisions without appropriate oversight.

It should support judgement by removing predictable administrative work and making relevant information easier to see.

Before automating a step, ask:

1. Is this step necessary?
2. Is the rule clear?
3. Are there legitimate exceptions?
4. What happens if the automation fails?
5. Will somebody understand why the action occurred?

14. Build client communication into the workflow

Client updates should not depend solely on somebody remembering to send them.

The workflow should identify communication points such as:

• confirmation that the case has been received;
• notification that further information is required;
• an update during an extended provider delay;
• confirmation that analysis or report preparation has begun;
• an explanation where the expected timescale changes;
• confirmation of submission or implementation; and
• confirmation that the work is complete.

Not every message should be automated or identical. Communication should reflect the client, the service and the circumstances.

The workflow’s role is to make sure the need for communication is visible and owned.

A client should not need to chase simply because the case is waiting for an external party.

15. Measure whether the workflow works

A documented process is not necessarily an effective process.

Firms should review evidence such as:

• end-to-end turnaround time;
• time spent at each stage;
• the age of open cases;
• cases with no clear next action;
• incomplete submission rates;
• rework and amendment rates;
• missed target dates;
• client progress enquiries;
• complaints relating to delay or communication;
• caseload by team member; and
• common reasons for exceptions.

These measures should be used to improve the process rather than rank individuals without context.

If cases consistently wait for adviser approval, the answer may be clearer review expectations or better capacity planning. If submissions are regularly incomplete, the intake process may need changing. If clients chase at the same stage, the firm may need a proactive update.

The workflow should evolve in response to evidence.

16. Prepare for disruption

A process that works only when every system and employee is available is not particularly resilient.

Firms should consider what happens when:

• a key employee is unexpectedly absent;
• the primary system is unavailable;
• an important supplier or provider experiences disruption;
• documents cannot be accessed;
• communications fail;
• case volumes rise suddenly; or
• a serious incident affects normal operations.

For firms within scope of the FCA’s operational-resilience rules, the regulatory requirements include identifying important business services, setting impact tolerances, mapping dependencies and testing the ability to remain within those tolerances.

Not every advice firm falls within the scope of those specific rules. However, understanding important services, dependencies, vulnerabilities and recovery arrangements is sensible operational practice for firms of any size.

The workflow should not rely on one person being the only individual who knows where work stands or what must happen next.

A practical implementation plan

Building a scalable workflow does not require the firm to redesign everything at once.

A practical approach is:

1. Select one high-volume case type. Choose work the firm completes regularly and understands well.
2. Review recent examples. Include successful cases and cases that experienced delays or rework.
3. Map the real process. Identify stages, owners, systems, handovers, waiting time and exceptions.
4. Remove unnecessary steps. Challenge duplication, repeated data entry and handovers that add no value.
5. Define submission requirements. Agree what must be present before work can begin.
6. Define stages and ownership. Give each stage a purpose, owner and exit criteria.
7. Add expected timescales and escalation. Decide when a case should be reviewed or raised for attention.
8. Pilot the workflow. Test it with a small number of live cases and gather feedback.
9. Measure the results. Compare turnaround time, rework, chasing and staff experience.
10. Refine before expanding. Apply what was learned before introducing the approach to other services.

This reduces the risk of creating an elaborate process that looks sensible on paper but does not support the way staff actually work.

Ask yourself

Review one of your firm’s common case types and consider:

• Is there one recognised way to submit the case?
• Is it clear what information must be supplied?
• Can the team see the current stage without asking somebody?
• Does every active case have a next action and owner?
• Can you distinguish active work from waiting time?
• Are handovers explicit and properly documented?
• Are delayed cases identified before target dates are missed?
• Are clients updated proactively?
• Can somebody cover the work when the usual owner is absent?
• Do you know which stages create the most delay or rework?

If several answers are no, the firm may be relying on its people to compensate for the process.

Growth should not require more confusion

A growing advice firm will inevitably become more complex.

There will be more clients, employees, services, systems, providers and decisions. The objective is not to prevent that complexity from existing. It is to prevent it from becoming disorder.

A scalable workflow creates enough structure for people to understand what is happening without removing the judgement required to provide good advice.

It allows new employees to learn how work moves through the business. It gives managers evidence about capacity and delay. It helps advisers submit clearer instructions, gives paraplanners better starting information and enables administrators to progress cases without constantly searching for context.

Most importantly, it gives clients a more predictable experience.

They may still encounter provider delays or complex decisions, but the firm knows where the case stands, who owns the next action and when communication is required.

That is the difference between a business that grows by adding more people to manage the confusion and one that grows by improving the way work is done.