How to Standardise Advice Processes | Advizo

How to Standardise Advice Processes Without Removing Adviser Judgement

To standardise advice processes, define the repeatable stages, information requirements, ownership, handovers and checks that should happen consistently across each client journey. Keep professional judgement separate from operational standardisation: advisers should still decide what is appropriate for an individual client, while the firm makes routine administration and case progression predictable.

A case should not progress differently simply because one adviser is busy, a case handler is on annual leave or a client sends documents through an unexpected route.

For mortgage brokers, protection advisers and financial planning firms, process standardisation is about reducing that dependency on individual memory and working habits.

The strongest process should make it easier for another appropriately authorised colleague to understand what has happened, what is missing, who owns the next action and what must happen before the case can move forward.

What does it mean to standardise advice processes?

Standardising advice processes means defining a reliable operating method for recurring client work while allowing controlled variation where the client's circumstances or professional judgement require it.

Depending on the firm's services, a standard advice process may cover:

• lead capture and initial contact;

• client onboarding;

• factfind completion;

• document collection;

• research and preparation;

• adviser review and recommendation;

• application or implementation activity;

• client communication;

• completion; and

• ongoing review or follow-up.

The objective is not to force every client through an identical sequence.

A straightforward remortgage, complex buy-to-let case, protection recommendation and financial planning review may require different work. What should be consistent is the firm's method for defining those different routes.

Each route should answer:

1. What stage is the case at?

2. What information or evidence is required?

3. Who owns the next action?

4. What must happen before the case moves forward?

5. How are exceptions recorded?

Why do advice processes become inconsistent?

Inconsistent processes rarely begin with a deliberate decision to work differently.

They normally develop gradually.

One adviser creates a useful email template and keeps it in their personal inbox. Another stores client documents in a particular folder. A case handler tracks follow-ups in a spreadsheet. A senior adviser remembers every key date without creating tasks.

Each method may work for the individual using it.

The problem appears when the firm grows, workloads increase or responsibility passes between people.

Common signs of process inconsistency include:

• different advisers asking clients for different information at the same stage;

• unclear meanings for pipeline stages such as "in progress";

• documents stored differently between cases;

• important updates remaining in personal inboxes;

• case handlers having to ask advisers for status updates;

• tasks being maintained in separate diaries or spreadsheets;

• duplicate information being entered into several systems; and

• new starters learning individual habits rather than one agreed operating process.

Operational inconsistency also makes management harder because the same status may mean different things to different members of staff.

7 steps to standardise advice processes

1. Map the process clients actually experience

Do not begin with the workflow the firm believes it follows.

Begin with several real cases.

Choose examples that include:

• a straightforward new client;

• a case with missing documents;

• a complex or unusual case;

• a case involving a staff handover; and

• a returning client.

Follow each journey from first contact through to completion or implementation and record every significant action.

Look specifically for:

• manual data entry;

• email requests;

• document handovers;

• staff-to-staff updates;

• tasks created manually;

• client delays;

• system changes;

• duplicate records; and

• points where somebody has to decide what happens next.

This reveals the difference between the documented process and the operating process.

Advizo's guide to mortgage broker workflows explores this type of journey mapping and stage-based workflow design in more detail.

2. Define clear case stages and exit criteria

A workflow stage is only useful when everybody understands what it means.

Labels such as "open", "active" or "in progress" often provide too little information to drive action.

A better stage describes a meaningful operational state.

For example:

• new enquiry;

• onboarding in progress;

• factfind outstanding;

• documents outstanding;

• ready for adviser review;

• application preparation;

• submitted;

• awaiting provider or lender;

• offer or recommendation issued; and

• completion or implementation.

The exact stages will vary by advice type.

More important is the exit criterion for each stage.

An exit criterion defines what must be true before the case can move forward.

For example:

Criteria should be observable.

"Client engaged" is subjective.

"Factfind submitted and outstanding document requests issued" is clearer.

For more detail on how clearer stages improve throughput, see Advizo's guide on how to improve case progression.

3. Give every next action a clear owner

A standard process can still fail if everybody can see the task but nobody owns it.

Every active case should have one clear owner for the next meaningful action.

That does not mean one person owns the entire case.

A mortgage journey might involve:

• an adviser owning the recommendation;

• a case handler owning document follow-up;

• an administrator owning data completion;

• a paraplanner owning preparation work; and

• a manager owning an escalation.

The key requirement is that ownership changes explicitly rather than through assumption.

A useful task should contain:

• the action;

• the owner;

• the relevant client or case;

• a due date where appropriate;

• priority; and

• an understandable status.

This also improves holiday and sickness cover because actionable work can be reassigned without losing context.

4. Standardise core client information without overbuilding the factfind

A factfind is the structured collection of information about a client's circumstances, needs and objectives used during the advice process.

Standardising factfinds can improve consistency because advisers and support staff know what core information should be available before particular stages.

However, there is an important balance.

A form that attempts to collect every possible field at the beginning of every journey can create unnecessary friction and encourage poor-quality placeholder responses.

A better approach is to distinguish between:

• core information required for the standard journey;

• conditional information required because of the client's circumstances; and

• adviser-led information that depends on professional judgement or the developing advice discussion.

This is where structured fact find software can support process consistency without turning every client interaction into one oversized form.

The objective should be to make information reusable throughout the process rather than collect it once and then repeatedly ask for it again.

5. Standardise document requests and review statuses

Document collection is one of the easiest places for otherwise good processes to become inconsistent.

One adviser asks for "income evidence". Another asks for three payslips. A third explains exactly which statement period is required.

The client experience and administrative outcome can be very different.

Standardise recurring document requests by defining:

• what document is required;

• the wording used to request it;

• any date-range or format requirements;

• where the client should upload it;

• who reviews it;

• what review states are available; and

• what happens when the document is unsuitable.

A simple status model might be:

Requested → Received → In Review → Accepted / Further Information Required

This is more informative than treating a document request as complete the moment a file arrives.

Advizo's guide to document collection software for brokers examines how structured requests and visible review states can fit into the wider advice workflow.

6. Standardise routine communication, not every conversation

Some client communication benefits from consistency.

Examples include:

• new-enquiry acknowledgements;

• appointment confirmations;

• factfind reminders;

• document requests;

• receipt confirmations;

• defined process updates; and

• routine follow-up messages.

Templates can reduce repeated writing and help clients receive clearer instructions.

However, standardisation should not make advisers sound robotic or prevent them from responding appropriately to individual circumstances.

A template should provide the consistent core message while allowing relevant context to be added.

A secure client portal can also standardise where clients complete recurring actions such as uploading documents, completing factfinds and responding to requests.

Advizo's current portal provides personalised to-do lists, document uploads, factfind access, messaging and case-progress visibility.

7. Automate predictable process steps carefully

Once stages, ownership and standard actions are clear, selected parts of the process can be automated.

Good candidates include:

• creating a task when a case changes stage;

• sending a defined reminder when information remains outstanding;

• notifying an appropriate team member when a document arrives;

• creating a follow-up after a known event;

• issuing a routine acknowledgement; and

• creating a future review task.

Advizo's automation and task functionality supports event-driven triggers, task creation, conditional logic and automated communications.

The important sequence is:

standardise first, automate second.

Automating an unclear process simply allows inconsistent work to happen faster.

For a deeper guide to appropriate automation, see workflow automation for mortgage brokers.

What should never be standardised too rigidly?

Advice firms need consistency, but some areas require professional judgement or individual treatment.

The aim is to standardise the infrastructure around judgement rather than the judgement itself.

When routine administration is predictable, advisers have more space to focus on areas where professional assessment and client context genuinely matter.

How should firms handle process exceptions?

Exceptions should be visible rather than hidden.

If a case needs to leave the normal route, allow an appropriately authorised person to do that and record why.

For example, a client may:

• require a different communication approach;

• have unusual income evidence;

• need additional review;

• be unable to use the standard digital journey; or

• have circumstances that make a routine automated sequence inappropriate.

A mature process recognises those situations.

What it avoids is allowing exceptions to become invisible workarounds in email or spreadsheets.

Review recurring exceptions periodically.

If the same "exception" appears every week, it may need to become a defined alternative route within the standard process.

How do you make standard processes stick?

The agreed process should be easier than the workaround.

If staff need six systems, repeated data entry and several manual searches to follow the official process, experienced employees will naturally create shortcuts.

Implementation should therefore focus on practical user journeys rather than policy documents alone.

Test the process with real roles:

• Ask an adviser to create and progress a new client.

• Ask a case handler to request and review documents.

• Ask an administrator to update client information.

• Ask another colleague to take over the case mid-journey.

Every point where somebody asks "Where do I find that?" or "Who does this?" is useful feedback.

The process is not fully standardised until those questions have consistent answers.

How should firms measure process consistency?

Do not measure standardisation by whether staff say they are following the workflow.

Measure operational signals.

Useful indicators include:

• cases with no visible next action;

• overdue tasks;

• factfinds reaching review with missing information;

• documents awaiting review;

• duplicate client requests;

• time spent at each case stage;

• number of manual handover queries;

• cases requiring repeated rework; and

• frequency of workflow exceptions.

Patterns matter more than individual cases.

If several advisers experience the same delay at the same stage, the problem may be the process rather than the person.

Can software help standardise advice processes?

Yes, but only after the firm has decided what good process looks like.

The software should then make the agreed way of working easier to follow by bringing the relevant elements together.

A useful operating environment may connect:

• clients;

• cases;

• factfinds;

• document requests;

• tasks;

• client communications;

• workflow automations; and

• case-stage visibility.

This is particularly relevant for firms that already use a network CRM.

The existing CRM may remain important for defined records, oversight or principal requirements while a separate operating platform helps the team manage everyday client work.

Advizo's guide to network CRM versus an operating layer explains this model in more detail.

The key is to define the role of each system clearly so process standardisation does not simply create duplicate entry.

How Advizo can support standardised advice processes

Advizo is designed as a day-to-day operating platform for UK mortgage brokers and financial advice firms, including firms that continue to use an existing network or compliance CRM.

Its current platform brings together client records, case management, factfinds, document requests, client portal activity, tasks and workflow automation.

Advizo's case-management functionality provides individual case workspaces with stages, tasks, notes, factfinds, documents and adviser assignment, making it possible to build a more consistent operating structure around each type of client journey.

The useful test is not whether software contains all of these features individually.

It is whether your firm can use them to make the agreed process easier to follow than the old workaround.

Frequently asked questions about standardising advice processes

What does standardising an advice process mean?

It means defining consistent stages, ownership, information requirements, handovers and routine actions for recurring client journeys. Professional judgement remains with the appropriate adviser while operational work follows a clearer structure.

Does process standardisation reduce adviser discretion?

No. Good standardisation separates repeatable administration from professional judgement. Tasks, document requests and handovers can be standardised without prescribing the advice conclusion for an individual client.

Should every advice case follow exactly the same workflow?

No. Firms often need several defined routes for different services or client circumstances. What matters is that each route has understandable stages, ownership and rules for handling exceptions.

Which advice process should a firm standardise first?

Start with the area creating the most repeated administration or uncertainty. Client onboarding, factfind completion, document collection and case handovers are often useful starting points because they recur frequently.

How many workflow stages should an advice firm use?

There is no universal number. Use enough stages to make the operational state and next action clear without creating unnecessary status management. Each stage should have a meaningful purpose and exit criterion.

Can standardised processes improve staff handovers?

Yes. Clear stages, task ownership, case notes and document status make it easier for another authorised colleague to understand and progress a case during holidays, sickness or workload reallocation.

Should standard processes be automated?

Only where the trigger and appropriate administrative response are predictable. Standardise the process first, then automate routine task creation, reminders or notifications while retaining human review for exceptions and judgement-based decisions.

How often should advice processes be reviewed?

Review them when recurring delays, errors or workarounds appear and include process review in the firm's normal operational governance. Growing firms may need more frequent refinement than mature, stable processes.

Can an operating platform work alongside a network CRM?

Yes. A firm can retain a network or principal CRM for required records while using a separate operating layer for day-to-day client work. The responsibilities and any required hand-offs between the two systems should be clearly defined.

Standardise the process around the advice, not the advice itself

The most effective way to standardise advice processes is to create consistency around the parts of client work that should not need to be reinvented every time.

Define the stages. Set observable exit criteria. Give every next action an owner. Standardise recurring requests and communications. Keep exceptions visible. Then automate only the predictable administration.

The result should not feel restrictive.

A well-designed process should make the working day calmer because advisers, case handlers and administrators spend less time asking where something stands or deciding how an ordinary task should be handled.

Professional judgement remains where it belongs: with the people responsible for understanding the client and determining the appropriate advice.

If your firm's processes currently depend on individual inboxes, spreadsheets and informal handovers, start with Advizo's mortgage broker workflow guide or explore Advizo to see how a purpose-built operating layer can support more consistent day-to-day advice operations.

Important: This article provides general operational information and does not constitute legal, regulatory, data-protection or compliance advice. Firms should consider their FCA obligations, network or principal requirements, data-protection responsibilities and internal compliance procedures when designing, changing or automating advice processes.