Proven Duty

Proving value for money on ongoing charges: what to log per client

The price and value outcome (PRIN 2A.4) asks whether the ongoing fee is justified by the ongoing value. The proof is per-client logging — the same fields, every year.

What the FCA says about ongoing charges

The price and value outcome (PRIN 2A.4) applies to the whole ongoing relationship, including what the client keeps paying after the initial advice. The FCA's Consumer Duty pages set out how the price and value outcome covers ongoing charges.

The FCA's Enforcement Watch newsletters describe firms that could not demonstrate what clients received for their charges. The per-client log is the record that answers that question.

The four log fields

Four fields turn an ongoing charge into an evidence trail. Each is logged against the client, the same way, every year.

The annual review that slipped, the value justification that lives in the adviser's head instead of the file — each is a fee-for-no-service or fair-value flag waiting to be found. Log it, and the record is the evidence.

Worked example: the year the charge went silent

The charge kept being taken. The record went quiet. Compare the two versions (anonymised, illustrative).

Before

“Ongoing fee £2,400. One call with the client. No record of what happened.”

After

“April: review meeting; portfolio checked against objectives. June: call on the tax impact of the top-up. Value note tied to this year's circumstances. Next review booked.” — four fields, one year, a continuous trail.

Common mistakes in the ongoing log

The log at a glance

FieldExample entryWhat it proves
Service deliveredApril: annual review meeting; portfolio checkThe charge was earned by real activity
When it happened12 April 2026; 3 June 2026The service is ongoing, not a one-off
Value against the feeReview re-ran the risk profile after the house purchaseThe justification fits this client, not a template
Next review date10 April 2027The trail is continuous and the cycle visible

Related reads

The ongoing log is how fair value stays evidenced between recommendations — start at the fair value hub for the whole silo, see the rule behind this check for the PRIN 2A.4 basis, and the value paragraph at file level for the version that appears inside the recommendation itself.

Frequently asked questions

How detailed does the log have to be?

Detailed enough that a reviewer can see what happened for the client, when, and why it justified the charge. It does not need to be long — one specific line beats pages of generic ‘ongoing support’.

What if the client declined the review?

Record that it was offered, what was said, and the outcome. A missed review becomes visible only when there is no record of what happened and why.

Is one entry per year enough?

The record should reflect the service the client was promised. Log every meaningful interaction, and at minimum the annual review — the fields work the same way every year.

Your next step

Take one ongoing client and rebuild the log: service delivered, dates, value against the fee, and the next review date. Fill the gaps before the yearly review, not after. Proven Duty tracks the service record and flags the clients whose logs go silent. see pricing or talk to us.