What SEC Reg BI Actually Requires in Your Client Meeting Records

Picture an advisor's desk after a Tuesday morning review meeting: a tablet propped against the keyboard with an AI-drafted client note on screen, a printed Form CRS in the in-tray, and a sticky labeled "Reg BI file - need rationale." That sticky is the one that costs hours. Reg BI does not ask for a transcript; it asks for a defensible record that an advisor considered the client's best interest before recommending a security or strategy. The two are not the same thing, and conflating them is what turns a 45-minute meeting into a 90-minute documentation tail.

The other artifact worth visualizing is the compliance officer's review queue: a dashboard with red, yellow, and green flags next to each advisor-meeting record, where yellow usually means "missing rationale field" and red usually means "recommendation logged without disclosure of conflicts." Most of the friction in Reg BI documentation is not regulatory ambiguity. It is that advisor-written notes were never structured around the four obligations the rule actually names.

What Reg BI is actually asking for

Reg BI applies to broker-dealers and their associated persons making recommendations to retail customers. RIAs operate under the Advisers Act fiduciary standard, but most independent practices we work with are dually registered or routinely interact with brokerage accounts, so Reg BI documentation expectations creep into wealth-management workflows whether or not the firm is BD-licensed.

The rule names four obligations: Disclosure, Care, Conflict of Interest, and Compliance. For meeting records, the Care Obligation is the one that drives most documentation work. Per SEC guidance, the firm must be able to show it had a reasonable basis to believe the recommendation was in the retail customer's best interest, considering risks, rewards, and costs in light of the customer's investment profile.

The five fields a Reg BI-aligned meeting record needs

Across our pilot cohort of independent RIA practices, the meeting records that survived examination scrutiny without follow-up shared a common shape. Five fields, in roughly this order:

• Investment profile snapshot. Time horizon, liquidity needs, risk tolerance, tax situation, other holdings. Not a re-keyed risk questionnaire - a sentence or two confirming what changed since last meeting.
• Recommendation made. Specific security, strategy, or account type. Not "discussed bond ladder" - "recommended replacing the 2027 corporate ladder rung with a Treasury rung of comparable duration."
• Reasonable basis rationale. Why this recommendation fits this profile right now. Two to four sentences, plain English.
• Costs and alternatives considered. What other reasonable options were weighed, and why this one. Reg BI does not require the cheapest option; it requires that cost was considered.
• Conflicts disclosed. Compensation arrangements, proprietary product flags, any material conflict the customer should know about.

Where advisor-written notes leak

The advisors in our early cohort averaged 52 minutes of post-meeting documentation per client meeting before we onboarded them, and we asked them to keep keeping their old notes for two weeks during the rollout so we could compare. The leaks were consistent. Recommendation language was vague ("talked about reallocating" instead of a specific instrument). Rationale was implicit ("client comfortable" without explaining why the recommendation matched the profile). Cost-comparison was the most-skipped field - present in roughly one in three notes when advisors were drafting unaided.

None of this is laziness. It is what happens when notes are organized chronologically ("first we discussed, then we discussed") rather than around the four Reg BI obligations. The fix is structural: a template that forces the five fields above, then prose that fills them.

Field-test rule. If a Reg BI examiner pulled this single record out of a stack of fifty, could a reviewer who never met the client tell what was recommended, why it fit, and what alternatives were weighed? If the answer requires inference, the record is not yet defensible.

Where agentic AI helps and where it should stay out

An agentic note assistant can draft the recommendation, rationale, and alternatives-considered fields straight from the meeting transcript, citing the moment in the conversation each claim was made. That is the productivity unlock - within our pilot, advisors spent eight minutes editing a draft instead of forty-five minutes composing one. What the assistant should not do is decide whether the recommendation fits the profile. The Care Obligation is a judgment the human advisor owns; the AI's job is to make that judgment legible on the record.

Practically, that means the suitability determination field stays human-edited even when the rest of the note is AI-drafted. A few of the firms in our cohort flag that field with a checkbox the advisor must tick before the record commits to the CRM. It is a small UX choice that keeps the fiduciary line bright.

Retention, retrieval, and the part nobody talks about

Per SEC Rule 17a-4 and analogous Advisers Act recordkeeping requirements, meeting records sit in scope for at least five years, with the first two in an easily accessible location. The part advisors learn the hard way is the retrieval test. Examination requests rarely arrive with a tidy date range; they arrive as "all meeting records related to the recommendation of [product] across [period]" and the firm has thirty days to produce them. A note structure that supports search by recommendation type, not just client name and date, is the difference between a clean exam and a scramble.

A workable next step

Adopt the five-field structure for the next quarter of meetings. Do not retrofit old notes - that work is rarely worth the hours. At the next compliance review, sample ten meeting records and run the field-test rule above. The gap between current notes and Reg BI-aligned notes is usually one template change away, and the documentation-time savings show up on the second or third meeting, not the first.

Source notes

• SEC Regulation Best Interest, Release No. 34-86031, and accompanying staff Q&A on the Care Obligation.
• SEC Rule 17a-4 recordkeeping requirements as applied to broker-dealer customer communications.
• FINRA Regulatory Notice 4530 on reportable events and supervisory record expectations.
• IAA 2026 Investment Adviser Industry Snapshot on RIA examination frequency and documentation findings.
• T3/Inside Information 2025 Advisor Software Survey on documentation tooling adoption among independent RIAs.