FCA Part 4A pre-application meetings that actually move the file

A useful FCA pre-application meeting is not a pitch. It is a structured conversation about perimeter, risks, controls, governance, and the evidence the regulator will expect in the file — and firms that treat it that way walk out with a shorter, cheaper authorisation than firms that treat it as marketing. This is a working guide to getting real value from pre-application engagement: what to bring, who should be in the room, how to read the signals, and how to convert the meeting into a file that completes inside the statutory clock.

What the meeting is for

The FCA offers pre-application engagement to prospective Part 4A applicants precisely because bad applications are expensive for both sides. A weak file consumes case-officer time in correspondence, stretches the applicant's runway, and frequently ends in withdrawal — the statistic the FCA quotes when it encourages firms to engage early. The pre-application conversation exists to surface, before submission, the issues that would otherwise surface in month seven of assessment.

The case officer's questions in these meetings preview the assessment itself: where the regulated activity boundary sits for this model, which permissions are actually needed, what the supervision team will worry about, and which parts of the file usually sink applicants of this type. For wholesale firms the FCA runs structured pre-application support with defined meeting formats; payments and e-money applicants have their own engagement track; novel or complex models can usually obtain at least one substantive conversation if they ask for it properly — with a concrete agenda and pre-reading, not a request for "an intro call."

The firm's job is symmetrical: surface the hardest questions early enough that the answers can be built into the application rather than retrofitted under assessment pressure.

The threshold conditions, translated

Everything the FCA asks traces back to the threshold conditions — the statutory minimums every authorised firm must meet at the gate and forever after. In practical language:

• Location of offices: the mind and management of the business in the UK, not a brass plate with decisions taken elsewhere.
• Effective supervision: a structure the FCA can actually supervise — group charts, outsourcing, and offshore dependencies that do not obscure who controls what.
• Appropriate resources: capital and liquidity adequate for the model, and non-financial resources — people, systems, controls — that match the plan.
• Suitability: fit and proper management, with the competence and probity questions answered by evidence, not adjectives.
• Business model: a model that is coherent, sustainable, and does not depend on consumer misunderstanding for its economics.

Reading your own draft application against these five headings, adversarially, is the single highest-value preparation exercise before any meeting.

What to bring

Come with a working draft of the regulatory business plan, not a deck. Specifically:

• A perimeter analysis: which activities in the model map to which permissions, with the marginal cases argued rather than hidden. If a flow might be a regulated activity, say so and show the analysis.
• The target operating model: customer journey, money flows, outsourcing map, and where decisions are made — one diagram per flow that a case officer can follow unaided.
• A capital and liquidity sketch against the applicable prudential regime, with the assumptions visible and a downside case included.
• The senior team as it will exist at authorisation — including the gaps, named as gaps, with a hiring plan and interim cover.
• The three weakest points of the application, identified by you first, each with its remediation plan.

That last item is the meeting's real currency. Raising your own hard questions converts the FCA from examiner to adviser for an hour; waiting for them to find the issues converts the application into correspondence. Case officers remember which firms did which.

Who should be in the room

The people who will own the answers: the CEO, the prospective SMF16 and SMF17 (compliance oversight and money laundering reporting), and whoever owns the financial model. If the chair or a senior independent director exists, their presence signals governance that is real rather than decorative.

External advisers belong in the preparation and can attend, but a meeting where consultants answer every question tells the FCA the firm has bought a file rather than built a business — and the assessment team will test for exactly that later, in interviews the consultants cannot attend. The working rule: advisers frame, principals answer.

Reading the signals

The FCA will rarely say "this will fail." It speaks in calibrated language, and the calibration is the information:

• "We would expect to see significant strengthening of the second line before authorisation" — a hiring requirement, stated as politely as it will ever be.
• "The perimeter analysis for that flow will need careful consideration" — the current analysis is wrong or missing.
• "Firms with this model have found safeguarding arrangements challenging" — your safeguarding section will be examined first and hardest.
• "You may wish to consider whether the projections are realistic" — the projections are not realistic.

Treat each hedge and qualifier as a work package. Firms that leave the meeting with a written list of every such sentence — and resolve each one before filing — are the ones whose applications complete inside the statutory window. Send a follow-up note recording your understanding of the points raised; it disciplines your own team and builds a record of responsiveness the cover letter can later cite.

After the meeting: sequencing the file

The statutory determination window is six months for a complete application and twelve for an incomplete one, and the difference between those two numbers is usually decided before submission. The sequence that works:

• Close the gaps the meeting surfaced — people, capital, perimeter — before drafting final documents, not in parallel with submission.
• Write the regulatory business plan around the risks the FCA named, in their order of concern. The reviewer should recognise their own agenda in your structure.
• Prepare the SMF applications to the same standard as the firm application; weak individual forms undermine a strong corporate file, and the interviews test the individuals.
• File once, completely. Drip-feeding documents after submission restarts internal queues and signals disorganisation.
• Assign one named owner for regulator correspondence with a 48-hour internal turnaround standard. Response latency is the variable the applicant controls, and it is visible.

Common failure patterns

• The pitch meeting: forty slides of market opportunity, no perimeter analysis. The FCA regulates activities, not ambition.
• The consultant ventriloquist: principals who cannot answer governance questions without looking left. Authorisation interviews are designed to catch this.
• The optimistic perimeter: regulated flows characterised as unregulated to shrink the permission set. Discovered perimeter problems convert assessment into investigation.
• The phantom team: key functions "to be hired post-authorisation." Some roles can follow; the second line cannot.
• The static file: meeting feedback acknowledged, file unchanged. Worse than not meeting at all, because it documents non-responsiveness.

The regulatory business plan: what good looks like

The RBP is the document the case officer actually reads first, and the one most applicants write last. The version that works is built for an adversarial reader:

• The model in one page, then the detail: what the firm does, for whom, earning what — before the market sizing, not after.
• Flows drawn, not described: one diagram per money or instruction flow, with the regulated activity labelled on the arrow where it occurs.
• The risk chapter written by the firm, not about it: the genuine top risks of this model, each with the control that answers it and the person who owns the control.
• Financials with visible assumptions: base and downside cases, capital and liquidity against the applicable regime in both, and the funding line for the gap.
• Governance as it will operate: meeting cadence, MI that reaches the board, escalation paths — the machinery, not the org chart.
• An honest dependencies section: outsourcing, group services, key vendors, with exit plans for the critical ones.

Length is not quality; reconciliation is. A forty-page RBP whose numbers match the SMF forms and the capital model beats a hundred-page one that contradicts itself once.

SMF interviews: how the individuals are assessed

For most applications the firm's fate travels through two or three individual interviews. What the assessors are testing:

• Competence in role: the SMF16 who can explain the monitoring plan, the SMF17 who can walk a suspicious-activity escalation end to end, the CEO who knows the numbers without the CFO in the room.
• Ownership: "the consultants drafted that policy" is an acceptable history; not knowing what the policy says is not.
• Candour: assessors ask about previous failures, regulatory history, and the model's weaknesses. Rehearsed perfection reads worse than honest scar tissue with lessons attached.
• Capacity: other directorships, other jobs, and the realistic hours this role gets. Part-time second lines at full-time firms are a standing concern.

Preparation that works is mock interviews against the firm's own file — not coaching to scripts, which assessors are trained to puncture, but fluency in the business the individual is about to be accountable for.

If things go wrong: minded-to-refuse, withdrawal, and refiling

Most weak applications do not end in refusal; they end in a conversation. When the assessment team concludes the threshold conditions are not met, the practical sequence is usually an invitation to withdraw before a formal minded-to-refuse process — because a refusal becomes public record and follows the principals onto every future form, while a withdrawal does not carry the same weight.

The decision calculus if that conversation arrives:

• Withdraw and refile when the gaps are real but fixable: hire the missing function, raise the capital, rebuild the perimeter analysis, and return in six months with the deficiencies closed and named in the cover letter. Refiles with genuine remediation succeed routinely.
• Contest only with substance: the formal process exists and is winnable where the assessment rests on a misunderstanding — but it is slow, adversarial, and rarely the right commercial answer for a startup burning runway.
• Never resubmit the same file: the second reading is done against the first file's findings, by a team with notes.

The cheapest version of this entire section is the pre-application meeting done properly — which is the argument the whole process makes for itself.

Fees and the clock

Two administrative facts worth internalising early: the application fee scales with the complexity category of the permissions sought and is payable at submission — non-refundable on withdrawal, which sharpens the file-once discipline. And the statutory clock pauses for nothing on the applicant's side: every week spent answering a question letter is a week inside the six- or twelve-month window, which is why the internal 48-hour response standard is not bureaucratic zeal but clock management.

Questions firms ask

Can we request a pre-application meeting for any Part 4A application?

Structured programmes exist for defined categories, and engagement is broadly encouraged elsewhere. The practical gate is preparation: a firm that submits a tight agenda, a perimeter summary, and specific questions usually gets a substantive conversation; a firm that asks for general guidance usually gets a referral to published materials.

Does the meeting commit the FCA to anything?

No. Pre-application views are informal and given on the information presented. They bind no one — but they predict the assessment with high accuracy, which is their entire value.

How early is too early?

Before there is an operating model to interrogate, the meeting wastes its one good use. The right moment is when the business plan exists in draft, the perimeter analysis has been attempted, and the team can answer operational questions — typically three to six months before intended submission.

What if we cannot fix everything the meeting surfaced?

File when the threshold conditions are genuinely met, not before. An application submitted with known, named gaps and credible remediation dates can survive; an application that hopes the gaps will not be noticed will not. Hope is not a regulatory strategy.

A Part 4A authorisation is a long conversation with a regulator that remembers. The pre-application meeting is the cheapest part of that conversation — used properly, it is where the application stops being a gamble and becomes a project plan.