Pension fund administrators: six months to prove your complaints framework works

The FSCA’s Conduct Standard 2 of 2025 (RF) took effect on 6 August 2025. By 6 February 2026, administrators must evidence fair outcomes with plain-language communications, consistent escalation and board-grade MI, not spreadsheets.

Complaints handling has moved from policy statements to a practical test you can pass or fail. Under the FSCA’s new conduct standard, pension fund complaints are a governance outcome. Boards must see and question the evidence; members must receive clear, timely updates; and administrators must reproduce complete case histories on demand. Good intentions won’t be enough. You will be asked to show your workings.

Part IX in practice
Part IX stitches together the duties that define fair treatment. It requires timely, accurate, plain-language communications around administration agreements and throughout the complaints journey. It mandates an effective complaints framework that fits your business model, with clear objectives, responsibilities, performance standards, categorisation rules and escalation paths, including how outsourced complaints are handled.

Oversight is explicit. The governing body owns the framework and its effectiveness. Complaint handlers must be trained, experienced, impartial and empowered to make fair decisions. Where a complaint is upheld, actions follow promptly; where it is rejected, reasons are clear and escalation routes are set out. None of this works without accurate record-keeping and management information (MI) that tracks volumes, types, resolution times and outcomes, analysed and reported so you can prevent repeats, not just tidy them up.

The process must also be transparent, accessible and free. Members should know what information is required, how to submit, the expected timelines and how to track progress. That demands a front door that works (web, phone, e-mail, letters) and a single case view regardless of channel.

What “operational by month six” looks like
By 6 February 2026, an administrator should demonstrate four things without a scramble:

1. Every complaint becomes one case. However it arrives; call centre, e-mail, web form, letter, it lands in a single record with documents, messages and timestamps attached.
2. Definitions and categorisations are in place and implemented. A standard and consistent process the frontline can apply; a shared rule for when the clock starts and stops; and escalation paths the system enforces, not memory.
3. Board-grade MI is reproducible on demand. The same view, month after month: upheld/rejected, time to resolve by category, internal/external escalations, compensation/goodwill, and the top three root causes with named owners and due dates.
4. Decisions and communications stand up. A traceable rationale for outcomes; prompt implementation when upheld; and clear, dated, plain-language updates, especially for vulnerable members.

If you cannot reproduce the last three months’ packs in under an hour, you are running on heroics and spreadsheets, not on controls and systems.

Systems, not spreadsheets
Spreadsheets are excellent for analysis; they are poor systems of record. They don’t start the clock when a complaint lands, enforce escalation when timelines slip or keep an immutable trail of who did what, when. They cannot guarantee that the board sees the same measures with the same definitions every month.

Administrators need platforms and processes that quietly enforce what the framework promises: consistent intake, configurable workflow, templated plain-language communications, exportable reporting and integration with the administration core and document stores to remove double capture, the source of many timing and accuracy disputes. This isn’t a pitch for a tool; it’s a reminder that technology is the operating system of fairness.

Governance that drives change
Make complaints a standing board item. Use a small, stable set of measures and focus the discussion on what changed, why and what will be fixed by whom and by when. Publish service standards; it is uncomfortable, but it reduces escalation because members know what to expect. Treat root-cause trends as a prevention pipeline, not a dashboard decoration.

Three questions for the board now

- Can we see every complaint in one place?
- What starts and stops the clock, and is it applied consistently?
- Can we reproduce the last three months’ packs, using the same definitions, in under an hour?

If any answer is “not yet”, the six-month window is already tight.

The Standard is not asking for thicker files; it is asking for proof: communications people understand; frameworks teams use; decisions that are fair and explainable; records that tell the truth; MI that drives prevention. Get the plumbing right, and you will demonstrate fair outcomes without heroics, and members will feel the difference.