File review remediation: turning findings into closed actions

The file review is done and the findings are written up. Then the hard part starts. Actions land in an adviser's inbox alongside everything else, a few get done, some are quietly forgotten, and three months later the next review finds the same gap in a different file. Nobody can say for certain which findings were fixed, or whether the fix made any difference.

File review remediation is the step that turns a review into an improvement. This guide sets out a simple process: grade each finding, set a clear action, follow up with the adviser, re-check the result and record the whole trail so it can be shown to a reviewer or your board.

Why file review remediation matters as much as the review

A review that finds problems but does not fix them can leave the firm worse placed than before, because it now knows about the issue. The FCA's outcomes monitoring review says firms should show "What action they take in response" and "How they consider whether those actions have improved outcomes". Among its areas for improvement it lists no audit trail from MI to decisions and fixes that are not tested (FCA outcomes monitoring review).

Remediation also feeds the annual Consumer Duty board report. Under PRIN 2A.8, when the governing body approves the report it must agree any actions needed (PRIN 2A.8). A clear remediation log makes that discussion concrete.

A six-step file review remediation process

Step 1: grade every finding

Not every finding deserves the same response. Grade each one before setting actions. A four-level scale is a simple starting point:

Grades 1 and 2 relate to FCA requirements such as COBS 9.4.7R (COBS 9.4) and COBS 6.1A (COBS 6.1A). Grade 4 relates to your own standard. Keeping them apart stops a long list of naming issues drowning out one serious concern. Where a grade 1 finding may mean the client has lost out, take advice from your compliance support on what the firm needs to do next; that decision sits above an ordinary file action.

Step 2: write actions that can be closed

A vague action ("improve the suitability report") cannot be checked. A good action has five parts:

1. The finding, with the rule or standard it relates to and the evidence quoted.
2. The action: one specific thing to do, such as "file the signed client agreement" or "add a dated note recording why capacity for loss was not reassessed".
3. The owner: one named person.
4. The due date, set by grade.
5. The evidence of closure: what the reviewer will look for to mark it done.

The one rule that never bends: never backdate, rewrite or replace a historic document. If something was missing at the time of the advice, the honest fix is a dated file note setting out what was missing, what has been done now and why. A file that suddenly looks perfect invites more questions than one with a clear, dated remediation trail.

Step 3: follow up with the adviser

Remediation often runs through advisers, so how findings are shared matters. Some practical points:

• Share findings in writing first, with the evidence quoted, so the adviser can read before discussing.
• Discuss grade 1 and 2 findings in person or on a call. The adviser may know context that is not in the file.
• Let advisers challenge. A finding that turns out to be wrong should be withdrawn and recorded as such. That also tells you something about your checklist.
• Agree dates rather than impose them where possible, but hold to them.

File review findings are also evidence for training and competence. TC 2.1.12R requires firms to "review on a regular and frequent basis employees' competence" (TC 2.1). A pattern of findings for one adviser belongs in their competence review and development plan, though the FCA reminds firms that "We do not expect supervision to only involve file checking" (FCA training and competence). Our guide to coaching financial advisers covers how to turn patterns into coaching.

Step 4: look for the root cause

When the same finding appears across several files, the cause may well be more than one adviser's oversight. Ask:

• Does the template prompt for this point, or leave it to memory?
• Does the process give the adviser the information at the right time?
• Is the expectation written down anywhere, or only in the reviewer's head?
• Has anything changed recently, such as a new template, platform or adviser?

Fix the cause, then add a firm-level action to the log alongside the file-level ones. One template change can prevent many future findings.

Step 5: re-check, and test that the fix worked

Closing an action is not the same as solving the problem. Two kinds of re-check help:

1. Closure checks. A reviewer confirms each action was completed, using the evidence of closure set in Step 2.
2. Effectiveness checks. After a root-cause fix, review a batch of later files to see whether the finding has stopped appearing. This is the testing of fixes that the FCA lists as an area for improvement.

Comparing the same client's file across review periods is a direct way to see whether remediation stuck.

Step 6: record it so it can be shown

Keep one remediation log for the firm. For each finding it should show the grade, the action, the owner, the dates set and met, the evidence of closure and any root-cause action. Summarise it periodically:

• findings raised and closed, by grade;
• actions overdue, and why;
• themes and the root-cause fixes made;
• what effectiveness checks showed.

That summary is the audit trail from MI to decisions that the FCA looks for, and it is ready-made material for your board report. Our article on preparing for a file review covers how to present it when an external reviewer arrives.

Where Scrutineer helps

Scrutineer gives every reviewed file a list of outstanding file actions and a missing-document checklist, with each finding tied to a named FCA rule and the supporting passage quoted. It compares review periods, so you can see whether a file improved after remediation, and it flags any review that could only read part of a folder. A dashboard shows every check with what needs attention. By our estimate it saves about three and a half hours per file review. Grading, agreeing actions and signing off remain your compliance team's work and responsibility.

Frequently asked questions

How quickly should file review findings be remediated?

Set timescales by grade in your compliance procedures. Suitability concerns need immediate senior attention; file quality points can follow a longer timetable. What matters is that dates are set, tracked and met.

Should we fix old documents after a file review?

No. Never alter or backdate historic documents. File any original that was misplaced, and add a dated file note explaining what was missing and what has been done since.

How do we show remediation worked?

Re-check later files for the same finding after a root-cause fix, compare file scores across review periods, and record the results. That evidence of improvement is what turns remediation into outcomes monitoring.

See how Scrutineer lists outstanding actions for every file, or book a twenty-minute demo with Adam Booth on Microsoft Teams, run live on a demo firm with nothing to prepare.