Skip to Content

Records and Documentation

Records and Documentation is the standing job of keeping the paper trail that everything else in the firm produces: agreements, correspondence, filings, calculations, and the notes behind each decision. A firm starts generating records on its first day and never stops, which means the real work here is not any one filing cabinet or piece of software. It is a running discipline — deciding what counts as a record, where it lives, how long it stays, and whether you could actually put your hands on it if someone asked. This page is about keeping that discipline working for as long as the firm operates, not about the specific documents any single step produces along the way.

Where this starts in the process

If you are working through the guide in order, this area picks up two earlier artifacts. Form the Business produces the firm’s very first permanent records — the entity’s formation document, its federal tax identification number, and its separate business bank account — before any registration filing exists. Write the Policies later produces the recordkeeping scheme itself: a written decision about where every category of record lives, in what format, who can reach it, and how it is backed up. This area takes both forward: applying that scheme to records that did not exist when it was written, and making sure the records Form the Business started are still there, in a form you can actually produce, years later.

Key ideas

A record is broader than the filing cabinet

A record is not only the signed client agreement or the form you submitted to a regulator. It is any correspondence with a client, any piece of marketing the firm sent out, the calculation behind a specific recommendation, and the note explaining why the firm made the choice it made. Treat anything a client, a colleague, or an examiner could reasonably ask you to reproduce as a record, whether or not it looked like paperwork at the moment it was created. A text message about a trade, a spreadsheet used to size a recommendation, and a voicemail confirming a client’s instruction all count, even though none of them arrived through the system built to hold formal documents.

Retention length is a floor, not a target

How long each category of record must be kept is set by rule, differs by category, and belongs on This year’s figures rather than here. Treat that number as the minimum, not the plan. A record tied to a dispute, a departed client, or an unusual transaction is often worth keeping well past the required date, because the cost of deleting something you turn out to need later is almost always higher than the cost of storing one more file.

If you are on the SEC path: your retention obligations run under the federal books-and-records rule rather than your state’s version, and the two name overlapping but not identical categories, with retention periods that do not always match. Confirm which list actually governs a given record rather than assuming your state’s rule and the federal rule line up.

Keep every version, never overwrite the last one

Documents change: a fee schedule is updated, a policy is revised, a brochure gets a new disciplinary disclosure added. The standing habit that makes any of that defensible later is keeping every version as its own dated file, rather than editing the existing one and losing what it used to say. The question an examiner or a former client asks is rarely what the document says today — it is what it said on the date a specific person read it. A recordkeeping system that only ever shows the current version cannot answer that question, no matter how current it is.

Retrieval matters more than accumulation

Keeping a record and being able to produce it are not the same skill, and a firm that has only practiced the first one finds that out at the worst possible time. Storage that is organized around when something arrived, rather than around what a person might later need to find, tends to accumulate a great deal of material that nobody can locate quickly. Periodically pulling a record at random — an old client agreement, a specific month’s correspondence — and timing how long it takes to find it is a more honest test of a recordkeeping system than asking whether everything is technically saved somewhere.

Records of judgment, not just of transactions

Most of what a recordkeeping scheme captures documents things that happened: a trade, a delivery, a payment. A smaller and easily neglected category documents why something happened — why a recommendation was made, why an exception to a stated procedure was allowed, why a conflict was handled the way it was. Compliance and Supervision covers the review that checks this kind of judgment against the firm’s policies; the record this area is responsible for is what gives that review something to check. A firm that keeps transaction records but never writes down its reasoning has plenty of records and very little evidence of judgment.

A record survives a change in the system that holds it

Software gets replaced, a storage provider changes its terms, a firm moves from paper to something electronic or the other way around. None of that is supposed to be visible in the record itself — a client agreement from years ago should be just as retrievable and just as complete after a system change as before it. Plan a system change around the records that already exist, not only the ones you are about to create: confirm that a migration actually carries every category forward, in a readable format, before the old system is retired.

Common misconceptions

  • That recordkeeping means keeping everything forever in one place. An unorganized archive satisfies neither the retrieval test nor, in practice, the retention rule, since a record nobody can find is not meaningfully different from a record that was never kept.
  • That electronic records are automatically compliant because they are backed up. A backup that nobody has tried to restore, or a format nobody can open in five years, is not the same thing as a usable record.
  • That the recordkeeping scheme, once built in Write the Policies, runs itself. It describes where records are supposed to live; whether they actually land there is a fact you have to keep checking.
  • That retention obligations only reach formal filings and client agreements. Correspondence, marketing material, and the notes behind a recommendation are all covered too, and are the categories most often missing when an examiner asks for them.

For practitioners

In a solo firm, you are the only person who knows where anything is, which is exactly the risk a good recordkeeping system exists to remove. Write down, somewhere outside your own memory, where each category of record lives and how someone else could find it — a business continuity plan is only useful if the person invoking it can actually locate the records it describes. Review that map on the same schedule you use for everything else, since a system that made sense when you built it drifts quietly as the firm adds new kinds of records it never anticipated.

Go deeper