The RIA Compliance Documentation Checklist for Every Client Meeting
If you laid out an independent RIA's compliance binder on a conference table - the spine cracked, tabs labeled by year - you would see the same shape repeated in every section: a meeting agenda, a hand-typed note, a follow-up email screenshot, and a yellow-flagged sticky reading "need rationale." The shape is the problem. A checklist that lives only in tribal memory is a checklist that drifts. This piece is the version we hand to advisors during onboarding and ask them to tape to the inside of their CRM.
The second image worth holding in mind is the screen most advisors actually look at after a client meeting: a CRM activity record open in one window, a partially-typed note in another, and a Form ADV brochure pinned to a third tab. The checklist below maps to those three surfaces. It does not assume any specific tool, but it does assume that whatever tool you use leaves a timestamped, retrievable record.
Reg BI and Advisers Act fiduciary documentation both start before the meeting. Two items belong in the file before the client walks in.
The advisors in our pilot cohort who consistently produced clean records did one specific thing during meetings: they verbally restated recommendations and the client's response. "So I'm hearing you'd like to move forward with the muni-ladder rebalance we just discussed - is that right?" That sentence, spoken aloud, becomes a defensible record the moment a transcript or note captures it. It is also the cleanest signal an agentic note assistant can latch onto when drafting the recommendation field.
Three things to capture in the moment, even if only as scribbled keywords:
Per FINRA Rule 4530 and Advisers Act recordkeeping practice, contemporaneous documentation is the standard - which examiners read as same-day or next-business-day. Within twenty-four hours, the meeting record should contain:
Eight items is more than the average advisor-typed note carries. Across our early advisor cohort, unaided notes averaged four to five of these eight fields. The missing fields were almost always rationale, alternatives, and conflict acknowledgment - the three that matter most to an examiner.
The 24-hour test. Open a meeting record from yesterday. Without re-reading the surrounding emails, can you tell what was recommended, why it fit, what else was considered, and what conflicts were disclosed? If you cannot, neither can a reviewer in three years.
Some documentation only makes sense once the action items have moved. Within seven days the file should also include:
A documentation checklist that is never audited becomes performative. Within our pilot, the firms that kept the discipline did one quarterly review: pull a random sample of ten meeting records, score them against the eight-field structure above, and feed the gaps back into the next quarter's training. It takes about ninety minutes per quarter and surfaces drift before an SEC examination does. RIA tech-stack budgets typically have room for this; a 2025 IAA snapshot put median annual RIA compliance technology spend in the low five figures across firms with under $1B AUM, and the marginal cost of a quarterly review is staff time, not software.
An agentic note assistant can draft the eight-field structure straight from the meeting recording, leaving the suitability rationale flagged for advisor edit. The advisors in our pilot moved from a 52-minute documentation tail to roughly 8 minutes of editing time per meeting. The checklist is the same; the labor inside each line item is what changes. The fiduciary judgment - whether the recommendation fits the client's interest - stays with the human, and the record stays defensible because it now includes the fields the unaided note tended to skip.