What reviewers look for in a sampled case

Describe the questions a reviewer asks when reading a case file.

When a file is reviewed, the person reading it was not in the meeting. Imagine you are that reviewer. You are holding a case file for a client you have never met, sold by a representative you may not know. You cannot ask anyone what they meant. You have the paper in front of you and a short list of questions. Once you can ask those questions of your own files, you start writing files that answer them.

Reviewers work from their firm's checklist and apply the measures their firm uses, so the exact wording differs from firm to firm. The underlying questions are much the same everywhere, because they come from the same rules you met in modules 2 to 4. There are four of them, and a reviewer takes them in order: the fact-find, the recommendation, disclosure, and whether the file matches the client's own account.

Checking that the fact-find is complete enough

The reviewer starts with the fact-find, because everything else in the file depends on it. A form with every box filled in can still fail. A fact-find is complete enough when it holds what the recommendation needed.

For life cover, that means dependants, debts, income and existing cover, including group cover. For an investment, it means objectives, time horizon, risk profile, other assets, and how much the client could afford to lose. In both cases the cash flow has to be there to support what the file says about affordability. If the client declined to give some information, the file should record that they declined and what effect it had on the advice.

Length does not decide the result. A long fact-find fails if the parts the recommendation rests on are missing, and a short one passes if everything relevant is there.

Checking that the recommendation follows from the needs

Next the reviewer reads the recommendation against the needs analysis. They want to see a product that answers a need the client actually has, needs ranked in a sensible order, and an amount the figures can justify. The reasoning has to be written down for this client. A generic sentence that could sit in any file tells the reviewer nothing about why this client got this product.

The reviewer also looks for alternatives. If only one product appears and nothing in the file suggests anything else was considered, the reviewer cannot tell whether you compared options. Lesson 4.1, "What a reasonable basis looks like on paper", set out the five elements a rationale needs: the need, the product, the reason, the alternatives, and affordability. Under this second question the reviewer checks each of the five.

Checking disclosure and the client's understanding

The third question asks whether the features, costs and risks were disclosed and understood. The reviewer checks whether the client received the required documents, and when. They check whether the material features, costs and risks were explained, including exclusions, charges and what happens if the client exits early.

Then they look for evidence that the client understood, beyond a signature. A file that records the client's own explanation of what they bought is far stronger than one that relies on a signed declaration. The habits from lesson 4.2, "Disclosure the client actually understands", pay off here. The reviewer also checks for anything that should have been disclosed and was left out, for example a conflict or a disadvantage of replacing an existing policy.

Checking the file against the client's own records

The fourth question asks whether the file is consistent with what the client experienced. Reviewers look at dates, signatures and sequence. They check whether the fact-find was signed before the recommendation or on the same page at the same moment, whether the document dates make sense together, and whether the signatures match.

Firms may also contact the client directly, for example by phone, and ask what happened in the meeting. They may listen to recorded calls where these exist. A file that says the client understood the surrender terms is undermined if the client says nobody mentioned them. So is a fact-find dated before a meeting that the client says happened a week later. This question catches files written to look right rather than to record what happened. Lesson 5.3, "Common file faults and how to avoid them", explains why writing your notes on the day matters for this.

Turning the four questions into your own checklist

The four questions are a starting point, but a checklist needs items you can tick or cross for one specific file. Break each question into the things a reviewer would look for, and borrow wording from your own firm's forms and requirements where you can.

Wei Ling (an invented example) built a checklist of twelve items under the four questions. Under the fact-find question they wrote five checks:

dependants recorded debts recorded existing cover listed, including group cover cash flow complete declined information recorded, with its effect on the advice

Under the fourth question they had three checks: dates, signatures, and when the notes were written.

Wei Ling then tested one recent file against the checklist. It passed ten of the twelve items. The two misses were a rationale with no alternatives and a disclosure record with only a signature. Both were among the three faults their supervisor had named as the most common.

In the activity below you build your own checklist from the four questions and test one of your recent or practice files against it. Note which items fail.

Write the reviewer's questions out as a checklist and test one of your recent or practice files against it.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).