Skip to Content
Firm FunctionsCompliance

Compliance and Supervision

This Firm Function is about the obligation itself and who carries it — not about any of the documents the obligation produces. Those have their own pages. What belongs here is the question underneath all of them: who is responsible for the firm’s use of AI, what does being responsible actually consist of, and how does any of that work in a practice where one person does everything. The compliance rule described below is an SEC rule. A state-registered adviser is under that state’s own requirements instead.

Key ideas

What the obligation actually requires

In plain terms, the compliance rule requires three things: written policies and procedures reasonably designed to prevent violations, a review of them at a set frequency, and a named person responsible for administering them. How often that review has to happen is a figure rather than something to state here — see this year’s figures. In a solo practice, the named person is the adviser. That is the whole frame, and everything else on this page follows from it. None of the individual documents get re-explained here; each has its own page.

Supervision when there is no second person

Supervision normally means one person checking another’s work. A solo firm has no second person, and this is the structural oddity at the center of this Firm Function. The substitute is not vigilance. Vigilance is judgment in the moment, and judgment in the moment is precisely what supervision exists not to rely on — the whole design of a supervisory system is to make the right outcome happen even when the person is tired, rushed, or convinced this one is fine. A firm of one has nothing but judgment in the moment unless it deliberately builds the substitute: a decision made in advance, written down, and checked against on a schedule. That is what a solo firm’s supervision consists of. It is thinner than a second person, and it is not nothing.

AI use belongs inside the compliance program, not beside it

A standalone AI policy that never touches the firm’s existing policies and procedures produces a specific failure: the compliance program goes on describing a practice the firm no longer runs. The firm’s actual procedures changed when a tool entered a workflow; if only the new document knows that, the program as written is now a description of the past. The point is integration, not a second binder. The document itself is Write the AI Policy’s subject.

You supervise people and permissions, not software

It is tempting to think of this as supervising a tool, and you cannot supervise software. What is actually under supervision is a person’s use of a tool, and, before that, the firm’s decision to permit the tool at all. Both of those have humans attached, which is what makes them supervisable. This is why the assistant’s tooling is the recurring gap in a two-person firm — see Operations and Back Office, which covers that case directly.

“Reasonably designed” is tested by whether you follow it

The standard is not how strict the policy sounds. A policy copied from a much larger firm and not followed is worse than a thinner one that is followed, because the gap between written and actual practice is itself the finding — a firm that documented a control it does not operate has produced evidence against itself. The Advisers Act’s own safe harbor for failure to supervise is built the same way. It protects a firm that set up procedures, and a system for applying them, that could fairly be expected to prevent and detect violations “insofar as practicable,” and that reasonably discharged its part under them without “reasonable cause to believe” they were not being followed. Every element of that is about operating the procedures, not about how demanding they look on paper. Small firms can overreach here, adopting procedures built for staffed compliance departments on the theory that more is safer. It does not read as caution. It reads as a control failure, and it is one.

Cadence, and looking again between cadences

The periodic review is where AI use gets re-examined against what the firm actually does now. Tools move faster than any fixed rhythm, though: a new tool, a vendor’s terms changing, or a use case expanding past what was approved are all reasons to look again without waiting for the next scheduled review. That trigger habit is sound practice rather than something the rule itself demands, and it is worth keeping distinct from the required cadence for exactly that reason — a firm should know which of its own practices are obligations and which are good sense. The cadence itself belongs to Review and Keep Records.

Where it shows up in the process

  • Decide What AI Is For: The inventory sets the outer boundary of what there is to supervise, which means a use nobody wrote down is unsupervised by default rather than exempt.
  • Write the AI Policy: This is where the obligation stops being a principle and becomes specific enough to follow, and where integration into the existing program either happens or does not.
  • Review and Keep Records: The cadence is what converts a decision made once into a control that can fail visibly, on a schedule, rather than quietly and whenever.

Common misconceptions

  • “A solo firm has no supervision obligation, because there’s nobody to supervise.” The obligation attaches to the firm, and the firm is the adviser. Having no one else to check does not remove the requirement; it changes what satisfying it looks like.
  • “The AI policy is its own document, separate from the compliance program.” A policy that sits outside the program leaves the program describing a practice that has changed.
  • “The vendor is compliant, so our use of it is compliant.” A vendor’s own compliance posture is about the vendor. The firm’s obligation is about the firm’s use, which the vendor knows nothing about.
  • “A longer, stricter policy is the safer choice.” An unfollowed policy is its own problem — the distance between what the firm wrote and what the firm does is the thing that gets found.

At a larger firm, supervision is somebody’s actual job, with a name attached and time allocated to it. That shifts the adviser’s role from deciding what is permitted to surfacing what they are using, and the characteristic failure shifts with it: the risk is no longer unsupervised use but undisclosed use — a tool that works well, adopted quietly, never mentioned to the person whose job it is to know. The compliance function cannot supervise what it has not been told about, and an adviser who assumes a small personal tool is beneath notice has made that call on the supervisor’s behalf. The disclosure is the adviser’s part of the obligation, and it is usually the whole of it.

Go deeper