An application is a set of answers to questions nobody writes down. A note on the ones that decide the file, and on the order they get asked in.
Most of what decides an authorisation happens before anything is filed. By the time a supervisor opens the file, the questions they will ask have already been settled by how the business is built, and the document either answers them or invites them.
That is not a criticism of applicants. It is a difference of reading. A founder reads a business plan as a description of what the company will do. A supervisor reads it as a set of claims about risk, each of which has to be evidenced somewhere else in the pack.
The four questions underneath every file
Whatever the permission, the same four things are being established. They are rarely asked in these words, and they are always being asked.
- Who controls the business, and what happens to that control if the shareholding changes.
- Where client money sits, who can move it, and how that is reconciled.
- What happens when something fails, and who notices first.
- Who is personally answerable, and whether they have the time to be.
A file that answers these in its own documents is short. A file that leaves them to correspondence is long, and gets longer. For the practical consequences of the second and third, see our note on safeguarding reconciliation.
A supervisor is not looking for a promise that nothing will go wrong. They are looking for evidence that you already know what will.
Governance is a description, not a diagram
An organisational chart shows reporting lines. It does not show whether the person at the top of one has the standing to stop the person at the bottom of another. The description is what carries that, and it is the part most often written last.
What a control framework has to survive
The test is not whether a policy exists. It is whether someone outside the firm could pick it up, follow it, and find the evidence it says should be there.
- A named owner for each control, who is not also its only reviewer.
- A record that the control ran, not an assertion that it would.
- An escalation route that has been used at least once.
Sequence matters more than completeness
A complete file assembled in the wrong order still reads as a set of separate documents. The stages below are the order that tends to hold together, because each one gives the next its context.
| Stage | What it settles | Written before |
|---|---|---|
| Structure | Who owns and controls what | Everything else |
| Activities | Which permission is needed | The business plan |
| Governance | Who is answerable | The control framework |
| Controls | How risk is evidenced | The financial model |
None of this makes an application quick. It makes it legible, which is the only part within anyone's control.
Placeholder article. The text above is written to size the template and is not published legal writing.