The Weakest Point in Your Trade Preclearance Control

Every firm with a supervised employee population has a trade preclearance process. Not every firm has one that executes consistently. The difference rarely comes down to policy. It comes down to where the control lives and whether employees can realistically complete it under the conditions they actually work in.

What Regulators Are Looking For

Regulators have been explicit about what personal trading controls require. FCA COBS 11.7.4R obliges firms to ensure that each relevant person is aware of restrictions on personal transactions, that the firm is informed promptly of any personal transaction entered into, and that a record is kept of every transaction notified — including any authorisation or prohibition connected to it. The standard applied is not whether a preclearance process exists on paper, but whether it can be demonstrated to have operated consistently, at the right moment, with sufficient documentation to evidence the control. FCA Market Watch 83, published in September 2025, reinforced this: the FCA observed staff trading before receiving approval and compliance teams not undertaking sufficient checks before granting it — the two failure modes that sit at either end of the preclearance workflow, and exactly where examiners look first.

For firms in scope of UK MAR and MiFID II, those obligations extend beyond the approval workflow itself. UK MAR requires firms to maintain insider lists, report suspicious transactions and orders, and ensure that controls preventing personal account dealing are integrated with the firm’s broader market abuse detection framework.

ESMA’s guidelines reflect this too: compliance must operate independently and is responsible for monitoring adherence to obligations that manage potential conflicts of interest that can harm client interests. What both regulators want to see is the same thing: a complete, sequential record showing that the control operated at the moment it was supposed to — before the trade, not after it. A policy document is evidence of intent. An approval workflow with timestamps, conflict checks, and documented rationale is evidence of control.

How Preclearance Is Designed to Work

The process is straightforward in design. A supervised employee decides to trade. They submit a preclearance request. The firm evaluates it against restricted lists, blackout windows, holding periods, and applicable rules. The request is approved, denied, or escalated. The outcome is documented. The employee proceeds accordingly.

When that sequence holds, firms have exactly what regulators want: a contemporaneous record of supervised employee trading activity and the controls applied to it. When it doesn’t, the gaps are visible and from an examiner’s perspective, a control that was not documented is indistinguishable from a control that did not exist.

Where the Process Fails in Practice

Technology is rarely the problem; most firms have a compliance platform that handles preclearance well. The breakdown happens at the initiation. The moment when an employee decides to trade and must choose between acting and stopping to complete a compliance workflow in a separate system.

That employee is in the middle of their day. They are on a call, watching a position move, or in back-to-back meetings. They know they need to preclear. They also know that means opening a browser, navigating to the compliance platform, logging in, finding the right form, filling it out, and waiting for an outcome before they can act.

Under time pressure, that is a significant ask. Requests are delayed. Some get submitted after the fact. Some do not get submitted at all. None of that is malicious. It is the predictable result of a control design that places maximum friction at the moment of maximum urgency.

What Examiners See When They Look at Your Records

From an examination standpoint, timing matters as much as the outcome. A trade that was eventually reviewed but executed before preclearance was obtained still represents a supervisory breakdown because the control failed the moment it was supposed to operate.

Examiners reviewing employee trading activity are looking for chronological integrity: was approval obtained before execution, was the decision documented contemporaneously, and is the audit trail complete? When that sequence has gaps, the control appears to be failing regardless of whether the underlying conduct was problematic.

Firms that rely on employees to self-initiate a friction-heavy process are asking the control to succeed despite its design, not because of it.

The Real Problem Is Design, Not Discipline

The preclearance infrastructure exists at most firms. What compliance teams are wrestling with now is something harder to solve: operational reliability. Whether the process initiates consistently, at the right moment, with enough documentation to hold up under scrutiny.

That is a design problem, not a discipline problem. And it has a design solution.

Embedding the control in the tools employees already use removes the moment of friction entirely. Completion rates go up not because behavior changed, but because the process stopped working against it. When the moment an employee decides to trade is the same moment they can submit a preclearance request, without switching systems or interrupting their workflow, the control executes consistently.

The Question Every CCO Should Be Asking

If your preclearance process depends on employees voluntarily interrupting their day to initiate a manual workflow under time pressure, the question is not whether gaps exist. It is how many, and whether your audit trail reflects them.

Firms that are closing that gap now — by embedding preclearance into the tools supervised employees already use — are building the kind of consistent, contemporaneous record that makes examination season significantly more straightforward.

If you want to understand what that looks like in practice, check out our ComplyAI MCP Trade Preclearance demonstration.