Records and Documentation
This Firm Function is about the question that comes before keeping anything: what makes a document a record in the first place, and what the obligation to produce it actually demands. Review and Keep Records owns the practice — which records the earlier steps produce, keeping them, and the cadence for checking. What that step assumes, and what belongs here, is that the firm already knows which of the things it is generating are records at all. With AI in the workflow, that assumption is the weak point.
Key ideas
The obligation
The books and records rule requires an adviser to make and keep specified records, and to produce them on request in a form the firm can furnish. Records are kept for a set period, easily accessible throughout, with an initial stretch of that period kept in an appropriate office of the firm; both are figures rather than something to print here — see this year’s figures. The books and records rule is a Commission rule; a state-registered firm is under its state’s requirements.
A record is what it is, not what you decided to call it
This is the center of the page. Nothing arrives labelled. AI produces artifacts continuously — prompts, drafts, summaries, transcripts, chat logs — and none of them announce their status. The firm does not get to choose what counts; it only chooses whether it knows. A document that memorializes advice given to a client is that document whether it sits in the client file, in a shared drive, or in a chat history nobody has ever inventoried. The classification happened when the thing was created. The only variable is whether the firm found out before somebody asked for it.
This is the same artifact Data Privacy and Security describes from the other side: prompt history is a store of client information there, and a possible store of records here. One object, two obligations, and a firm that has inventoried it for neither.
Producibility is stricter than retention
Keeping something and being able to produce it are different capabilities, and the obligation runs to the second. Records spread across a vendor’s chat history, an assistant’s personal account, a laptop folder, and an email thread may all still exist in the sense that nothing was deleted — and be unproducible in any reasonable time, which is the sense that matters. The characteristic small-firm failure here is not deletion. It is dispersal: no single decision to lose anything, just an accumulation of places where things ended up because that was where the work happened.
Custody is not control
If the only copy of a record sits in a vendor’s system, under an account the firm does not administer, then the firm’s ability to produce that record depends on the vendor’s continued cooperation, pricing, and existence. An account termination, a downgrade to a plan with a shorter history, or a vendor shutting down can each put a retained record out of reach without anyone deleting it. “We have it” and “we can get it” are different claims, and only the second is worth anything on request. Vendor Oversight covers the relationship that determines which one is true.
Drafts, and an edge the guide will not pretend is settled
Not every intermediate artifact is a record. A firm that decides every prompt is one will build a retention scheme it cannot operate, and then not follow it — which, per Compliance and Supervision, is its own failure and a worse one than the gap it was meant to close. What the rule plainly reaches is reasonably clear: the records it specifies, including things that document advice and communications with clients. Where AI artifacts sit relative to those categories is genuinely unsettled at the edges, and this guide is not going to invent a test or a threshold to resolve it. What can be said without inventing anything: deciding in advance which categories of artifact the firm treats as records is better than deciding case by case after someone has asked for one. A decision made in advance is a policy. The same decision made afterward is an explanation.
Documenting the AI decisions themselves
Separate from any of the above, and worth keeping distinct from it: the firm’s reasoning about which tools were approved, what use was permitted, and why. No rule names that artifact. It is worth writing down anyway, because it is the only evidence that the firm’s position was arrived at deliberately rather than drifted into — and the difference between a decision and a drift is invisible in hindsight unless someone wrote it down at the time. That is sound practice rather than obligation, and the distinction matters: a firm should know which of its habits are required and which it keeps because they are sensible.
Where it shows up in the process
- Map the Rules That Apply: That step is where the recordkeeping duty attaches to specific named uses, rather than sitting in the background as a general fact about running a firm.
- Build the Workflows: A workflow is where the firm settles in advance which artifacts a use will generate and which of those it treats as records — the deciding-beforehand this page argues for, at the point it is cheapest.
- Review and Keep Records: That step keeps and checks what the firm has. It can only do that for artifacts the firm has recognized as records, which is the question this page covers.
Common misconceptions
- “It’s only a record if we filed it as one.” Filing is how a firm tracks a record. It is not what makes something one.
- “The vendor stores everything, so we’re covered.” Storage under someone else’s account is custody, not control, and the obligation runs to producing the record rather than to its continued existence somewhere.
- “We keep everything, so we can produce anything.” Keeping everything and finding one thing are close to opposite problems. A firm that retains without organizing has usually made production harder, not easier.
- “A prompt is just a question, not a document.” What a thing is called has no bearing on what it is. A prompt containing a client’s situation, and the output it produced, may be exactly the kind of artifact the rule reaches.
At a larger firm, retention is handled by systems rather than by anyone remembering: archiving that captures communications automatically, journaling nobody thinks about, and a records function whose job includes knowing where things are and producing them when asked. The individual adviser mostly cannot put a record somewhere the firm will not find it, because the capture happens beneath them. A small firm has to do by decision what a larger firm does by infrastructure — and the gap between those shows up as dispersal rather than as loss. Nothing goes missing; it just ends up in eleven places, none of them chosen.
Go deeper
- Books and records to be maintained by investment advisers, 17 CFR 275.204-2 , eCFR — the current text of the rule: what must be made and kept, and in what form it has to be available.
- AI Risk Management Framework (AI RMF 1.0) , National Institute of Standards and Technology (2023) — a general framework whose governance and documentation material bears on the last idea above, keeping a record of decisions about AI systems rather than only of their outputs.