Tick a box processes, how we as an industry built our own scoping problem

We built a scoping problem

Somewhere along the way, our industry stopped starting with the client in front of us and started with the compliance file we needed to build.

I say this as someone who has worked in compliance for over 20 years. I understand better than most that there are genuine obligations to be met and real risks to be mitigated when providing advice. This isn't an argument against compliance. It's an observation that, somewhere along the way, we lost sight of the difference between compliance and risk and started treating the two as the same thing.

We took a genuinely sound concept of scoped advice and turned it into something the profession now treats as a lesser cousin of "comprehensive" advice. As if advice that is scoped to a client's actual circumstances is somehow less rigorous than advice that tries to cover everything.

Here's the uncomfortable truth: all advice is scoped. Every single piece of advice, no matter how "comprehensive" we label it, is bounded by what the client told us, what they wanted addressed, and what we uncovered along the way. There is no such thing as unscoped advice. So why have we let "scoped advice" become industry shorthand for "not proper advice"?

Scoping isn't the problem. What we've turned scoping into is.

When scoping becomes a checklist

Too many advice processes and Statements of Advice today read like a shopping list of solutions: income protection, debt consolidation, insurance restructures, investment switches served up not because the client's circumstances called for them, but because a template said these are the boxes a "thorough" adviser ticks.

We've built processes that answer questions before they've been asked. A client walks in and says, "I have a job," and somewhere in the background it is concluded, "Therefore, they need income protection" before anyone has actually explored whether they have a protection need, what their existing cover looks like, or whether it even matters to them right now.

A client approaching retirement mentions a mortgage, and the process assumes "surely they want it paid off" instead of asking what role that mortgage actually plays in the cash flow picture they've described and whether paying it off is even something they care about.

That's not advice. That's a template or checklist wearing advice as a costume.

What a builder can teach us about scoping

Let me strip this back to something that has nothing to do with financial advice at all, because that's where everyone gets tangled up.

Imagine a builder sitting with a client who says, "I want to renovate my kitchen."

The builder doesn't start asking about the bathroom. Or the master bedroom. Or the patio. Their reasonable enquiries are entirely focused on what the client wants to achieve with the kitchen: the layout, the budget, the finishes, and how they use the space.

If the builder only renovates the kitchen and touches nothing else in the house, does the client not have a better home at the end of it? Of course they do. Nobody would seriously argue that leaving the bathroom untouched means the renovation "wasn't thorough."

Where it gets interesting is when something in the course of that kitchen work creates a genuine, connected implication elsewhere - say, removing a benchtop wall is going to punch straight through into the spare room. That's not scope creep for the sake of it. That's a real, explicit consequence the builder would be negligent not to raise.

And even then, the client might say, "Not a priority, don't have the budget, no one uses that room anyway, I'll live with it." That's their call. The builder still delivers a great kitchen. The advice wasn't incomplete because the spare room stayed as it was.

That's what good scoping looks like in advice, too.

You ask reasonable questions focused on what the client actually came to you for. You listen for the things that genuinely connect to their goal - the equivalent of the hole in the wall - and you raise those, because not raising them would be a disservice. But you don't walk in assuming every room in the house needs renovating just because you're capable of renovating rooms.

Understanding isn't the same as advising

There's a second confusion sitting underneath all of this: the idea that knowing something about a client automatically pulls it into scope.

Taking a client's relevant circumstances into account - e.g., their rental income, their Centrelink pension, whatever else feeds into their cash flow - so you can properly understand the picture you're advising on does not automatically mean property advice or Centrelink advice is now part of your scope. Understanding is not the same as advising.

Back to the builder. Knowing the client has a spare room down the hall doesn't mean the renovation now includes the spare room. It's simply part of the house the builder is working on. It only becomes relevant the moment the kitchen work actually touches it, the moment removing that benchtop punches a hole straight through the wall.

At that point, ignoring it isn't an option. That's the explicit or implicit need conversation that has to happen, and then it's a matter of working out, together with the client, whether what you're doing still leaves them better off even if the spare room stays exactly as it is.

That's the distinction we keep losing. Taking information into account so the advice is properly grounded is not the same as expanding the scope to cover everything you now happen to know about.

The two only intersect where what you're actually doing genuinely creates a consequence elsewhere. When that happens, you raise it, you have the conversation, and you let the client decide. You don't ignore it, and you don't treat every piece of client information as an open invitation to advise on it.

Where scoping can go wrong

None of this is to dismiss that inappropriate scoping happens.

It does. There are times when obvious needs go unaddressed when they genuinely shouldn't have been left on the table. I'm not suggesting otherwise.

But I do wonder how much of that comes down to a genuine misunderstanding of what scoping actually is, made worse by processes the industry itself has built; processes that make good scoping feel far more difficult and fraught than it needs to be.

We've built for the expectation of negligent behaviour rather than the reality of it.

When compliance becomes the process

And that's the part worth sitting with.

We should not be building our expectations and processes on the assumption that advice won't be done correctly. We should build our processes assuming most advice is done correctly, using monitoring and supervision to catch the small percentage that isn't.

Instead, we've done the opposite - built everything around the exception, as if most advice will fail. In the process, we've made it harder for advisers to do the one thing these processes are meant to protect: genuinely understanding the client sitting in front of them.

What we've built instead is a compliance-led checklist dressed up as a risk-based process.

Templates that trigger the same list of "considerations" regardless of the client sitting in front of us. Processes that exist to protect the file, not to genuinely explore the client's circumstances. Conversations that feel like a script or filling gaps in a document rather than understanding a person's actual picture.

What risk-based scoping actually looks like

Real risk-based scoping means asking what this client actually came to me for, what their circumstances tell me is genuinely relevant to that goal, and what, if anything, has emerged that they'd reasonably want to know about, even if it sits just outside what they first asked for.

It doesn't mean assuming everyone needs everything. It doesn't mean opinion dressed up as enquiry. And it certainly doesn't mean a shopping list of solutions in search of a problem.

For advice businesses looking at whether their existing policies, processes, and governance genuinely support good advice, a broader review of the way the business operates can help identify where the real gaps sit. This is the thinking behind Tangelo's Gap Assessment.

We need to rethink what ‘good scoping’ means

We don't need less scoped advice. We need to stop treating good scoping as second-rate and start calling out the compliance theatre that's been passed off as thoroughness for far too long.

The client in front of you didn't come in for a checklist. They came in with a kitchen they wanted renovated.