Reg BI Disclosure Obligation

Reg BI’s Disclosure Obligation requires your broker-dealer to give retail customers, in writing, full and fair disclosure of all material facts about the scope and terms of your relationship before or at the time you make a recommendation. Operationalize it by standardizing relationship/fee/conflict disclosures (including Form CRS delivery), controlling timing and versioning, and retaining evidence that each customer received the right disclosure at the right moment. (17 CFR § 240.15l-1)

Key takeaways:

• Your control objective is provable: the customer got written, material relationship disclosures before or at the recommendation. (17 CFR § 240.15l-1)
• “Material facts” must cover relationship scope/terms, fees and costs, services, conflicts, and limitations on products/strategies. (17 CFR § 240.15l-1)
• Build a workflow that ties disclosure delivery to recommendation events and preserves delivery evidence, versions, and supervisory review.

The Reg BI disclosure obligation fails in practice for one reason: firms can draft decent disclosures but cannot prove delivery timing and completeness at the point of recommendation. The requirement is simple to state and hard to operationalize at scale because recommendations can happen across channels (phone, email, in-person, digital), by different roles, and under different account types.

For a CCO or GRC lead, the fastest path is to treat this as a transaction-control problem, not a drafting project. You need a controlled disclosure inventory, mapped to recommendation scenarios; a delivery mechanism that triggers before or at the recommendation; and immutable evidence that the correct disclosure version was delivered to the specific retail customer. You also need governance that keeps disclosures current as services, compensation, and conflicts change.

This page translates the regulatory text into an implementation plan: who must comply, what “full and fair” and “material facts” mean operationally, the exact steps to deploy controls, the artifacts to retain for exams, and the common hangups that cause findings. Source reference: SEC Regulation Best Interest at 17 CFR § 240.15l-1. (17 CFR § 240.15l-1)

Regulatory text

Requirement (excerpt): “Before or at the time of the recommendation, the broker-dealer must provide the retail customer, in writing, full and fair disclosure of all material facts relating to the scope and terms of the relationship.” (17 CFR § 240.15l-1)

Operator meaning

Your obligation is not satisfied by having disclosures “available” or “posted.” You must:

1. Provide disclosures to the retail customer
2. In writing
3. Before or at the time you make a recommendation
4. Cover all material facts about the scope and terms of the relationship. (17 CFR § 240.15l-1)

A practical control objective: for any sampled recommendation, you can show the written disclosure package delivered to that customer, with a timestamp (or equivalent sequencing evidence) that places delivery before or at the recommendation, plus the disclosure version in effect on that date. (17 CFR § 240.15l-1)

Plain-English interpretation (what must be disclosed)

The disclosure obligation requires providing retail customers with information about:

• Nature and scope of the broker-dealer relationship
• All fees and costs
• Type and scope of services provided
• Material conflicts of interest
• Limitations on securities or strategies that may be recommended
  This includes delivery of Form CRS (Customer Relationship Summary) at or before the recommendation. (17 CFR § 240.15l-1)

Treat these as minimum content buckets. Your job is to make them specific enough that a retail customer can understand what you do, what it costs, where incentives exist, and what you will not do.

Who it applies to

Entity scope

• Broker-dealers making recommendations to retail customers are directly in scope for this Reg BI obligation. (17 CFR § 240.15l-1)

Operational contexts where this shows up

• New account onboarding where a rep recommends account type, rollovers, or an initial allocation
• Ongoing advice-like brokerage where reps recommend trades, strategies, or product types
• Digital recommendations (model-based suggestions, prompts, or guided portfolios) when they rise to “recommendation” in your program design
• Call center or branch interactions where “informal” suggestions occur and are later executed

If your firm is dually registered or has an affiliated adviser, you still need to ensure the brokerage recommendation path triggers the Reg BI disclosure workflow and that customers are not confused about capacity and services. Keep the disclosure package consistent with your actual operating model. (17 CFR § 240.15l-1)

What you actually need to do (step-by-step)

Step 1: Define “recommendation events” and map them to workflow triggers

Create a written inventory of the events that your firm treats as recommendations for Reg BI workflow purposes (for example: security-specific recommendations, account type recommendations, strategy recommendations). Then map each event to:

• the channel (rep, branch, call center, digital)
• the system of record (CRM, order entry, planning tool)
• the point you can force disclosure delivery or capture attestation
  Your goal is deterministic triggering: if a recommendation happens, the system prompts delivery and logs it. (17 CFR § 240.15l-1)

Step 2: Build a disclosure inventory and “package logic”

Maintain a controlled library of disclosures, versioned and approved, including:

• Relationship scope/terms disclosure
• Fees and costs disclosure
• Services description
• Conflicts disclosure
• Limitations disclosure
• Form CRS delivery artifact (as part of the package) (17 CFR § 240.15l-1)

Then define package logic (a simple decision table works) so the right disclosures go to the right customer scenario. Example decision factors:

• brokerage vs advisory capacity (if applicable)
• product set limitations (proprietary-only menus, platform restrictions)
• compensation types and conflicts tied to the recommendation context
• service model (transactional vs ongoing monitoring)

Step 3: Control timing (“before or at the time”) with enforceable gates

Pick at least one control gate you can enforce:

• Pre-trade gate: order entry cannot proceed until disclosure delivery is logged for that customer and scenario.
• Conversation gate: a scripted verbal lead-in plus immediate written delivery (email, portal, e-sign) before documenting the recommendation.
• Digital gate: the recommendation screen requires the customer to open/acknowledge the disclosure before showing the final recommendation or enabling acceptance.

Design for the hard cases: phone recommendations followed by later execution, recommendations made off-platform, and transfers between teams. The exam question you are preparing for is, “Show me three recommendations and prove the disclosure package was provided before or at the time.” (17 CFR § 240.15l-1)

Step 4: Implement review and change management

Disclosures drift when the business changes. Set governance that forces updates when:

• pricing schedules change
• new products, revenue sharing, or differential compensation is introduced
• service model changes (monitoring, account minimums, restrictions)
• conflicts are added, removed, or recharacterized
  Tie disclosure updates to your formal change processes (product approval, compensation committee decisions, platform onboarding). (17 CFR § 240.15l-1)

Step 5: Train to behavior, not just content

Training should answer:

• What counts as a recommendation in your channels?
• What must be delivered and when?
• How to complete the workflow in systems and how to handle exceptions
• What to do when the customer refuses e-delivery or cannot access the portal

Keep role-specific job aids. Reps need a checklist; supervisors need an exception playbook; operations needs a reconciliation report. (17 CFR § 240.15l-1)

Step 6: Monitor and test (control assurance)

Build recurring testing that samples recommendations across channels and verifies:

• correct disclosure package selected
• correct version in effect
• delivery evidence present
• sequencing supports “before or at the time”
• exceptions resolved with documented rationale and remediation
  Where possible, automate surveillance reports that flag recommendations without logged disclosure delivery. (17 CFR § 240.15l-1)

Where Daydream fits

Daydream is useful when you need a single place to manage your disclosure inventory, map it to onboarding and recommendation workflows, and produce audit-ready evidence packets by customer, date, and disclosure version. The win is speed during exams: you answer sampling requests with standardized artifacts instead of ad hoc screenshots and inbox searches.

Required evidence and artifacts to retain

Create an “exam packet” standard for each recommendation sample:

• Disclosure content (PDF/HTML) as delivered, with version ID and effective dates
• Delivery proof (portal log, e-sign certificate, email delivery log, mail record, or CRM activity with timestamp)
• Recommendation record (order ticket, CRM note, call log, digital acceptance) with timestamp
• Supervisory review evidence for exceptions or overrides
• Policies and procedures describing timing, packaging logic, and exception handling (17 CFR § 240.15l-1)

If you cannot produce delivery proof for the channel, you do not have a control; you have a hope.

Common exam/audit questions and hangups

Expect these:

• “Define ‘before or at the time’ in your workflow. Show me how systems enforce it.” (17 CFR § 240.15l-1)
• “How do you determine what’s ‘material’ and ensure disclosures cover all material facts?” (17 CFR § 240.15l-1)
• “How do you ensure Form CRS was delivered at or before the recommendation?” (17 CFR § 240.15l-1)
• “Show evidence for recommendations made by phone or email.”
• “How do you manage disclosure versions and prove which version a customer received?”

Hangups that trigger findings: inconsistent timestamps across systems, manual processes with no immutable log, and disclosures that describe a service model you do not actually deliver.

Frequent implementation mistakes (and fixes)

1. Posting disclosures on a website and calling it delivery.
   Fix: require customer-specific delivery evidence tied to the recommendation record. (17 CFR § 240.15l-1)

2. Generic conflict language that omits the conflicts that matter in your model.
   Fix: maintain a conflicts register and map conflicts to disclosure text and recommendation scenarios. (17 CFR § 240.15l-1)

3. No packaging logic, so staff guess what to send.
   Fix: decision table + system prompts + supervisor exception review.

4. Version control gaps.
   Fix: central repository, approval workflow, effective dates, and a hard rule that only current versions can be delivered.

5. “We delivered once at onboarding” without considering later recommendations.
   Fix: define when re-delivery is required based on your recommendation flow and material changes; document it in procedures. (17 CFR § 240.15l-1)

Enforcement context and risk implications

Even without citing specific public cases here, the risk pattern is consistent: if you cannot prove timely written delivery or your disclosures omit material facts about fees, conflicts, limitations, or service scope, you face exam findings, remediation demands, and potential enforcement escalation. The operational risk is also real: inconsistent disclosures create customer confusion, complaint exposure, and supervisory control failures.

Practical 30/60/90-day execution plan

First 30 days: Stabilize the control surface

• Inventory recommendation channels and systems; document recommendation event triggers.
• Centralize current disclosures and identify owners, versions, and approval status.
• Confirm Form CRS delivery method and where evidence is stored. (17 CFR § 240.15l-1)
• Draft the disclosure package decision table and exception types.

Next 60 days: Implement enforceable delivery and evidence

• Add workflow gates in key systems (CRM/order entry/portal) to log disclosure delivery.
• Stand up reporting for “recommendation without disclosure evidence” exceptions.
• Update written procedures: timing standard, packaging logic, version control, exceptions. (17 CFR § 240.15l-1)
• Train reps and supervisors with channel-specific job aids.

By 90 days: Prove it under sampling

• Run an internal mock exam: pull a sample of recommendations across channels and assemble full evidence packets.
• Fix gaps (timestamp mismatches, missing logs, staff workarounds).
• Implement ongoing QA testing cadence and management reporting.
• If your evidence is scattered, consider consolidating disclosure and evidence management in Daydream to reduce scramble time during exams.

Frequently Asked Questions

Does “in writing” mean the disclosure must be on paper?

No. “In writing” can be electronic, but you still need evidence the specific retail customer received it before or at the recommendation. Keep delivery logs and the exact disclosure version provided. (17 CFR § 240.15l-1)

If we delivered disclosures at account opening, do we have to deliver again for later recommendations?

Reg BI requires disclosure before or at the time of the recommendation; your procedures must define when prior delivery remains valid and when changes require re-delivery. If material facts change, update and re-deliver as part of your control design. (17 CFR § 240.15l-1)

What counts as “material facts” for scope and terms of the relationship?

At minimum, cover relationship nature/scope, fees and costs, services provided, material conflicts, and limitations on securities or strategies you may recommend. Make the disclosure match how the business actually operates. (17 CFR § 240.15l-1)

How do we handle phone recommendations where the customer trades later?

Treat the phone recommendation as the control moment. Deliver the written disclosures during or immediately after the call through a logged channel (portal, e-sign, or recorded email delivery) and tie that evidence to the documented recommendation. (17 CFR § 240.15l-1)

Our reps email disclosures manually. Is that acceptable?

It can be, but manual email processes often fail on proof and consistency. Require standardized templates, controlled attachments, and retained delivery logs, and implement supervisory review for missing evidence. (17 CFR § 240.15l-1)

What artifacts do examiners ask for most often?

They usually sample recommendations and ask for: the disclosure package (including Form CRS), proof of delivery timing, the recommendation record, and your written procedures and training materials that define how you meet “before or at the time.” (17 CFR § 240.15l-1)