Building a file quality standard for your advice firm

Ask two experienced reviewers whether a file is "good" and you may get two answers. Both may agree it meets the rules. One dislikes the way documents are named, the other wants a file note after every phone call, and neither has written their expectations down. The adviser hears mixed messages, and the firm cannot show what it means by quality.

A written file quality standard fixes that. It sets out what your firm expects of every file over and above the regulatory minimum, so files can be scored against it the same way each time. This guide explains what to put in one, how to keep it separate from the rules, and how to score against it fairly.

Why a file quality standard is separate from compliance

The FCA rules set the floor. SYSC 9.1.1R requires "orderly records" that are "sufficient to enable the FCA to monitor the firm's compliance" (SYSC 9.1), and COBS 9, COBS 9A and COBS 6.1A set out what the file must show about suitability and charges. Those requirements are not optional, and your standard cannot lower them.

A file quality standard sits on top. It answers a different question: does this file meet the way our firm wants to work? A file can meet every requirement and still be hard to follow, inconsistent with your templates or slow to review. Equally, a beautifully organised file can contain an unsuitable recommendation. Scoring the two separately stops one hiding the other.

What to include in a file quality standard

Your standard should reflect your own processes. The areas below are a starting point. Where a point overlaps with a rule, we say so; everything else is good practice of the firm's choosing.

Structure and order

• A fixed folder structure, the same for every client.
• Documents named consistently, with dates in a single format.
• Superseded versions marked or removed, with a note.
• Scans legible, complete and the right way up.

Completeness and traceability

• Every recommendation traceable back to the fact find and meeting notes it relies on.
• Every figure in a report traceable to its source document.
• File notes for calls and emails that affected the advice, dated and signed off.
• Research and product comparisons saved at the date of advice.

Clarity of client communications

This area overlaps with the Consumer Duty. PRIN 2A.5.3R requires communications that are "likely to be understood by retail customers", and PRIN 2A.5.7G points to "plain and intelligible language" and avoiding "unnecessary disclaimers" (PRIN 2A.5). Your standard can go further, for example a maximum length for the summary page, or a rule that the recommendation appears before the background.

Timeliness

• Suitability report issued within a set number of working days of the meeting.
• Annual review letters issued within a set time of the review meeting.
• Actions from previous file reviews closed by their due dates.

The timescales are yours to choose. Write them down so they can be measured.

Writing and scoring each standard

Make every item observable

A standard only works if two reviewers would score it the same way. For each item, write:

1. The expectation, in one sentence: "Every file note is dated and names who wrote it."
2. What meets it: what a reviewer should expect to see.
3. What partly meets it, if you allow partial credit.
4. What fails it, with an example.
5. The weight: how much it counts towards the overall score.

Avoid items that depend on taste, such as "well written". Replace them with something observable: "the summary states the recommendation in the first paragraph".

Weighting and scoring

Not every item matters equally. A missing file note for a call that changed the advice matters more than an inconsistent file name. A simple approach:

• Group items into sections (structure, traceability, clarity, timeliness).
• Give each section a weight that reflects its importance to your firm.
• Score each item as met, partly met or not met.
• Express the result as a percentage, so files and periods can be compared.

Keep the arithmetic simple enough that an adviser can see how their score was reached. A score nobody can explain will not change behaviour.

Calibrating reviewers and benchmarking files

Even a well-written standard is applied differently by different people. Calibration narrows the gap:

1. Pick a small set of benchmark files that show strong, average and weak quality.
2. Have each reviewer score them independently against the standard.
3. Compare scores item by item and discuss where they differ.
4. Rewrite any item that produced disagreement, then rescore.
5. Repeat when a new reviewer joins or the standard changes.

Keep the agreed benchmark scores. They become the reference point for every later review, and the evidence that your standard is applied consistently.

Versioning, dating and reviewing the standard

Your standard will change as your processes change. Each time it does, give it a new version number and an effective date, and keep the old versions. A file reviewed in March should be judged against the standard in force in March. If a reviewer, network or the FCA later asks how a score was reached, you can show exactly which version applied.

Review the standard at least once a year, and whenever a pattern in your file reviews suggests an item is unclear or missing. Our compliance file review checklist covers the regulatory side, which your standard should sit alongside rather than replace.

Using the scores

File quality scores are most useful in aggregate. Tracked by adviser and over time, they show who needs support and whether changes to templates or training have worked. They can also feed your outcomes monitoring, alongside the compliance results, as part of the evidence described in Consumer Duty evidence for advice firms.

Scrutineer gives every file two headline scores: a compliance percentage against FCA suitability and disclosure standards, and a file-quality percentage against your firm's own standard. It learns from your own benchmark scores, so its standard matches your firm's judgement rather than a generic one. It also compares review periods, so you can see a file improve or slip year on year. By our estimate, a review that takes half a day by hand takes minutes. The standard, and the final judgement, remain yours.

Frequently asked questions

Does the FCA require a file quality standard?

The FCA requires orderly records and files that show compliance with its rules. A separate written quality standard is good practice that a firm chooses to adopt, and it can never lower the regulatory requirements.

How many items should a file quality standard have?

Enough to describe how your firm wants files kept, and few enough that each one can be scored consistently. Start small, calibrate, and add items only where reviews show a real need.

Should advisers see their file quality scores?

Yes. A score explained item by item tells an adviser exactly what to change, and tracking it over time shows whether coaching and template changes are working.

See how Scrutineer scores files against your own standard, or book a twenty-minute demo with Adam Booth on Microsoft Teams, run live on a demo firm with nothing to prepare.