RIA Advisor AI Assistants: Recordkeeping Under Advisers Act Rule 204-2 and Fiduciary Supervision
Rule 204-2 requires registered advisers to make and keep true, accurate and current books and records, and Rule 206(4)-7 requires written policies and procedures that are implemented, reviewed annually and administered by a chief compliance officer. Neither rule is written for AI assistants, so firms must map each assistant interaction to a record category themselves, retain what was actually delivered or relied on, and be able to show what the assistant was permitted to do and what it did. Enforcing policy in the execution path, rather than reviewing interactions afterward, is the most direct way to produce that evidence.
Requirements to evaluate assistant evidence against
- Completeness: each interaction captures the prompt, output as delivered, tool calls, policy decision applied and any human approval.
- Retention: periods are configurable to at least the Rule 204-2 period and any longer internal policy, and the firm controls deletion.
- Retrievability: records can be found by client, date and record category and exported for an examination request.
- Tamper resistance: stored evidence cannot be altered without detection, and reviewer identity is retained with each approval.
- Supervisory review: consequential actions require human approval that is enforced in the workflow, with escalations and exceptions recorded.
- Residency and custody: storage location matches the firm's data residency and production requirements, and any third party holding records is subject to oversight.
What the two rules require
Rule 204-2(a) requires every investment adviser registered or required to be registered under section 203 of the Advisers Act to make and keep true, accurate and current the specified books and records relating to its advisory business. The rule sets out the types of records required and the manner, location and duration of retention. The SEC has described the retention requirement as keeping records in an easily accessible place for not less than five years from the end of the fiscal year of the last entry, with the first two years in an appropriate office of the adviser.
Rule 206(4)-7 makes it unlawful to provide advice unless the adviser adopts and implements written policies and procedures reasonably designed to prevent violations of the Act and its rules by the adviser and its supervised persons. The adviser must review them at least annually, covering both adequacy and the effectiveness of implementation, and designate a chief compliance officer to administer them. As of November 2026, both rules are current.
Neither rule contains AI-specific text. In 2023 the SEC proposed additional Rule 204-2 recordkeeping for advisers using covered technology in investor interactions, and in 2022 it stated that the rule does not prescribe requirements when an adviser outsources recordkeeping functions to a third party. Both are proposals, and this guide does not treat them as current obligations. The mapping below is analysis of how existing categories apply, not settled SEC guidance.
Mapping assistant interactions to record categories
The table sets out which Rule 204-2 categories each assistant artifact plausibly touches. Whether a specific output falls into a category is a firm determination, and the rationale for categories judged out of scope should be written down.
- AI-drafted client communications on performance or rate of return: Written communications category: copies of those sent and originals of those received. Retain the output as delivered.
- Assistant output that shapes content the firm disseminates as an advertisement: Advertisement copies. The marketing rule amendments require copies of all advertisements, with alternative methods for oral advertisements. The firm decides whether an output is an advertisement.
- Tool calls that pull data used in performance figures: Documentation supporting performance calculations. The tool-call record may form part of that support.
- Meeting summaries and outputs relied on to support recommendations: Assess against the full rule text on records supporting recommendations, and document the conclusion.
- Prompts and intermediate drafts: A firm policy decision about which artifacts are the retained record. State the decision in the written procedures.
- Approvals, escalations and reviewer actions: Supervisory evidence for the Rule 206(4)-7 compliance program and its annual review.
Where recordkeeping and supervision gaps arise
The "true, accurate and current" standard suggests a retained record should reflect what was actually sent or relied on. This is an inference for evidence design, not an SEC statement about AI. In practice, it means keeping the final output as delivered, not only the prompt. A prompt log without the delivered text cannot show what a client received. A final email without the prompt and tool calls cannot show what data the assistant used.
The second gap is distribution. Prompts, outputs, tool calls and approvals are generated across several models and tools, each with its own storage and retention behavior. A firm may hold fragments of an interaction in different places, with no common identifier tying them to a client communication. Retrieval during an examination then depends on manual reconstruction.
The third gap is supervision that exists only in policy. A procedure stating that consequential outputs require human approval satisfies the documentation half of Rule 206(4)-7. The rule also requires that procedures be implemented, and the annual review must assess whether they work. If the approval step can be bypassed in the workflow, the firm cannot show that it operated. Assistant logs, escalation records and approval evidence are natural inputs to that annual review, and they should be producible as they were generated, not rebuilt after the fact.
A fourth gap is third-party custody. If an AI vendor or logging service keeps or generates required records, the firm needs due diligence and monitoring around it, even though Rule 204-2 does not currently prescribe outsourcing requirements.
Enforcing policy in the execution path
Reviewing assistant interactions after the fact can sample outcomes, but it cannot show what the assistant was permitted to do at the moment it acted. Enforcement in the execution path decides, before an output or tool call takes effect, whether it is allowed, redacted, blocked or escalated for human approval, and records that decision. The decision record is the supervisory evidence.
Trussed enforces policy at runtime across models, agents, tools and MCP servers, with actions that include allow, redact, block, rate limit and escalate for human approval. The scope is individual interactions and tool calls. Audit-ready evidence is generated by that enforcement, so each interaction carries the policy decision applied and any approval. Deployment is self-managed in the customer cloud, with configurable retention and data residency, which lets a firm keep evidence in its own environment and set retention to its own schedule.
This addresses the execution-path evidence requirements above. It does not decide which Rule 204-2 category an output belongs to, whether content is an advertisement, or what the firm's retained record should be. Those determinations stay with the compliance function and belong in the written procedures. Trussed does not provide SEC-specific rule mapping, transaction-level governance or end-to-end tracing of agentic workflows.
From assistant interaction to examination evidence
Interaction
Prompt, output as delivered, and tool calls from an assistant workflow.
Record category
Mapped to written communications, advertisements, performance support or recommendation support.
Policy decision
Allowed, redacted, blocked or escalated, with the decision retained.
Retrievable evidence
Retained under the firm's schedule and producible by client, date and category.
Review your assistant workflows against these requirements
Talk to an expert about enforcing policy in the execution path and producing audit-ready evidence for assistant interactions and tool calls.
Talk to an Expert