Talk to us

A complete file can still leave us with questions

By
Hannah Keane

When a case reaches our technical planning team, a lot of work has usually gone into getting it there. Provider information has been gathered, documents checked and everything organised so we can get started.

Nicola Porter recently wrote about the preparation involved in getting a case to that stage, so I thought I’d pick up from where she left off and look at what happens when the file reaches us.

It’s quite possible to open a case and find everything you’d expect to see. The fact-find is complete, the provider information is there, the risk assessments have been done and we’ve got the relevant research. But we might still need to go back to the adviser with a question, and it’s not necessarily because anything is missing.

 

Having the information isn’t quite the same as understanding the reasoning

There’s a difference between having all the information and understanding the thinking behind a recommendation.

Take a retirement planning case, for example. We might have the pension valuations, risk assessments, cashflow modelling and the client’s income requirements. The adviser is recommending flexible drawdown, but I still want to understand why that approach has been chosen.

Has the client considered securing some guaranteed income? How does the recommendation sit with their capacity for loss? And what happens to the plan if investment returns aren’t quite what everyone hoped?

There may be perfectly good reasons for the approach, and the adviser may already have discussed all of this with the client. We just need to make sure that reasoning comes through in the file.

The same applies to something like an investment switch. The research might clearly show the differences between two options, but if the recommended solution has higher charges, we’d want to understand what additional benefits justify those costs and why they matter to that particular client.

These aren’t necessarily complicated questions, but the answers can make quite a difference to how the advice is researched and explained.

 

Why those conversations matter

When a technical planner goes back with a query, it doesn’t automatically mean there’s something wrong with the advice.

Financial planning isn’t always straightforward, and two experienced advisers could look at the same circumstances and reasonably approach them differently.

We’re not there to make the decision for the adviser, but we do need to be comfortable that the options have been properly considered and that the reasoning behind the recommendation is clear.

Sometimes that means challenging an assumption or asking whether another option was considered. Other times, it’s simply a case of understanding something the adviser discussed with the client that hasn’t quite made its way into the paperwork.

I think that’s an important distinction. A question from the technical planning team isn’t necessarily a criticism of the recommendation. It’s part of working through the advice and making sure everything fits together.

And I’d much rather have those conversations while we’re working on the case than discover something needs clarifying when the report is almost ready to go.

 

What makes a good handover?

One thing you notice when working with different advice firms is that everybody has their own way of doing things.

Some advisers provide detailed notes explaining their recommendations, while others prefer to talk through a case with us. Both approaches can work well, provided the reasoning is clear and properly recorded afterwards.

And it doesn’t necessarily mean creating more paperwork. Sometimes a few lines explaining what mattered most to the client, what alternatives were considered and why a particular approach was chosen can save quite a few emails later.

I’ve also found that the cases with the most paperwork aren’t necessarily the ones that need the most technical discussion. A relatively straightforward recommendation can raise an important question, while a complicated case can be surprisingly clear if the adviser’s reasoning is well documented.

Having a good working relationship helps enormously. Advisers need to feel comfortable talking through their thinking, and technical planners need to be equally comfortable asking questions or challenging something when it’s appropriate.

Good preparation makes a huge difference, as Nicola explained in her article. The more organised a case is when it reaches us, the better. But even with a complete set of documents, there’s still the adviser’s knowledge of the client, the conversations they’ve had and the professional judgement that’s gone into arriving at their recommendation.

For me, that’s a big part of what makes technical planning interesting. It’s not simply about having the right documents or producing a well-written report. It’s understanding how everything fits together and making sure the advice is supported by the information, research and reasoning behind it.

ISO/IEC 27001:2022 certified
UKAS-accredited information security management system
You can verify the validity of our ISO certificate via the UKAS register.

ISO/IEC 27001:2022 certified

Affiliate of

Consumer Duty Alliance

Proud to work with

Paradigm ValidPath

Contact

Old Brewery Business Centre
Castle Eden
Co. Durham
TS27 4SU

Tel: +44 (0)1472 728 030
Email: hello@wecomplement.co.uk

© 2026 We Complement | Privacy Policy
We Complement Limited registered in England & Wales under company number 13689379, ICO number ZB427271. Registered address: Old Brewery Business Centre, Castle Eden, Co. Durham, TS27 4SU.