Standardising processes across a client base

Ask a practice why work cannot move between staff and the answer is always the same: you need to know the client.

That is true, and it is a description of a problem. If knowing the client is a prerequisite for doing the work, then holiday cover is difficult, a resignation is a crisis, and the practice cannot grow faster than it can transfer knowledge.

Standardisation is the fix. It is resisted because it sounds like treating clients identically, and that is not what it means.

What to standardise, and what to leave alone

Standardise the process. Vary the content.

The chart of accounts differs by industry — that is content, and forcing uniformity there produces useless reporting. But how documents arrive, when work is done, what the review consists of, where things are stored, how exceptions are handled — that is process, and there is no good reason for it to differ between clients.

The distinction is worth being strict about, because "this client is different" is usually true about content and almost never true about process.

The five worth standardising first

Document intake. One channel, same for every client. This single change does more than the rest combined, because it turns forty arrangements into one and makes the outstanding position visible without asking anyone.

The monthly cycle. The same sequence of steps in the same order for every client. Not the same dates — clients have different period ends — but the same steps, so anyone can pick up any client and know what stage it is at.

Naming and structure. Same account naming conventions, same folder structure, same file naming. Trivial individually and enormously expensive when it varies, because every transfer of work starts with orientation.

The review checklist. What gets checked before a set of accounts goes out. If this varies by whoever does it, quality varies by whoever does it.

Exception handling. Same categories, same routing, same escalation. Without this, every client's queue is its own dialect.

What must stay bespoke

Being honest about this is what makes standardisation acceptable to a practice.

• Chart of accounts detail
• Genuinely industry-specific treatments
• The client relationship, and who holds it
• Judgement on unusual transactions
• Reporting content the client specifically asked for

The pitch to a sceptical colleague: we are standardising how we work, not what we produce. The client's accounts remain theirs; only our internal process becomes uniform.

Doing it without losing clients

The reason practices do not standardise is that it means changing arrangements clients are comfortable with, and the fear is losing them.

The approach that works:

Start with new clients. Every client onboarded before you standardise is a permanent tax you have chosen to pay. New clients have no expectations to disappoint, so onboard them the standard way from day one — see onboarding a client onto automated books.

Convert existing clients at a natural moment. A year end, a fee review, a change of contact, a system change on their side. Attaching the change to something else makes it a detail rather than a demand.

Lead with what they get. Faster accounts, visibility of their own position, fewer requests from you. Those are real benefits and they are the reason a client accepts a change in habit.

Accept a small tail. A few clients will not change. Decide deliberately whether each is worth carrying as an exception — some are, on relationship or fee grounds. What matters is that it is a decision rather than a default.

What standardisation makes possible

Work becomes transferable. Anyone can pick up any client. Holiday cover stops being a problem and a resignation stops being a crisis.

Quality becomes consistent. Same checklist, same standard, regardless of who did it.

Training becomes shorter. One process to learn, not forty.

Automation becomes worth configuring. This is the compounding effect. Configuring automation for one process used across a whole book is economic; configuring it forty times is not, which is why practices that have not standardised get far less from the same software.

Problems become visible. When every client follows the same process, the one that does not fit stands out — and it usually stands out for a reason worth knowing.

The uncomfortable measure

One question tells a partner how standardised the practice really is:

If your most experienced delivery person left tomorrow, how many clients would be difficult to service next month?

If the answer is more than a handful, the practice is carrying knowledge in people rather than in process — and that is a risk that exists whether or not anything is ever automated.

A standard written down once tends to age quietly out of date the same way any other document does — see the SOP that nobody has opened in a year for what that looks like and why annual reviews rarely catch it.

Common questions

What should a practice standardise across clients?

The process rather than the content: how documents arrive, the sequence of the monthly cycle, naming and folder conventions, the review checklist, and how exceptions are categorised and routed. Chart of accounts detail, industry-specific treatments, judgement on unusual transactions and client-requested reporting should remain bespoke — the useful line is that you standardise how you work, not what you produce.

How do you standardise without upsetting existing clients?

Start with new clients, who have no expectations to change, then convert existing ones at a natural moment such as a year end, fee review or change of contact so the change is a detail rather than a demand. Lead with what the client gains — faster accounts, visibility of their own position, fewer requests — and accept that a small number will not change, deciding deliberately which of those are worth carrying.

Why does standardisation matter for automation?

Because configuring automation for one process used across a whole client book is economic, whereas configuring it separately for forty clients is not. This is why two practices running identical software can get very different results, and why standardisation is worth doing before rather than after an implementation.

How do I tell whether my practice is standardised?

Ask how many clients would be difficult to service next month if your most experienced delivery person left tomorrow. More than a handful means knowledge is held in people rather than in process, which is a risk regardless of whether anything is automated, and it caps how fast the practice can grow.

Related: taking on more clients without more staff · onboarding a client onto automated books · quality review in an automated practice