Regulation Best Interest

Regulation Best Interest (Reg BI) requires a broker-dealer to act in the retail customer’s best interest when making a recommendation of a securities transaction or investment strategy, at the time the recommendation is made. To operationalize it, you must implement and evidence four obligations across your recommendation lifecycle: Disclosure, Care, Conflict of Interest, and Compliance. (17 CFR § 240.15l-1)

Key takeaways:

  • Reg BI triggers on “recommendations” to “retail customers,” so you need a defensible way to identify both in your workflows. (17 CFR § 240.15l-1)
  • Your controls must cover four component obligations: Disclosure, Care, Conflicts, and Compliance, with records that show what happened at the time of the recommendation. (17 CFR § 240.15l-1)
  • Examiners will test whether your policies translate into rep behavior, product governance, and supervision, not whether the policy language sounds right. (17 CFR § 240.15l-1)

Reg BI is a requirement about how your firm behaves at the moment it influences a retail investor. The rule’s core test is simple to say and hard to prove: when your broker-dealer recommends a securities transaction or an investment strategy to a retail customer, the recommendation must be in that customer’s best interest at that time. (17 CFR § 240.15l-1)

For a CCO or GRC lead, the fastest path to compliance is to treat Reg BI as an end-to-end “recommendation control system,” not a disclosure exercise. You need clear triggering logic (what counts as a recommendation, who is a retail customer), a repeatable process for documenting the basis of the recommendation, a conflicts program that reduces incentives to put the firm first, and supervision that detects exceptions early.

This page translates the requirement into operational steps, evidence to retain, common exam questions, and a practical execution plan you can run with. It stays at requirement level: what you must be able to do consistently, and what artifacts should exist when regulators ask “show me.”

Regulatory text

Reg BI standard of conduct (excerpt): “A broker-dealer shall act in the best interest of the retail customer at the time the recommendation is made.” (17 CFR § 240.15l-1)

Operator meaning: you must design your recommendation process so that, for each retail recommendation, you can demonstrate (with contemporaneous records) that you:

  • gave required disclosures and material facts,
  • exercised reasonable diligence, care, and skill in forming the recommendation,
  • identified and addressed conflicts of interest through policies and controls, and
  • maintained written policies and procedures that reasonably achieve compliance.
    All of these are part of Reg BI’s component obligations: Disclosure, Care, Conflict of Interest, and Compliance. (17 CFR § 240.15l-1)

Plain-English interpretation (what Reg BI requires)

Reg BI raises the standard of conduct above suitability for recommendations to retail customers. It does not allow you to rely on “the product is suitable” if the recommendation is influenced by avoidable conflicts, incomplete disclosure, or weak diligence. Reg BI’s four obligations work together:

  • Disclosure obligation: your retail customer must receive Form CRS and material facts about the relationship and the recommendation. (17 CFR § 240.15l-1)
  • Care obligation: the rep and the firm must use reasonable diligence, care, and skill to understand the product/strategy and match it to the customer’s circumstances and objectives. (17 CFR § 240.15l-1)
  • Conflict of Interest obligation: you must identify conflicts and implement controls to at least mitigate (and in some cases eliminate) incentives that could push recommendations away from the customer’s best interest. (17 CFR § 240.15l-1)
  • Compliance obligation: you must maintain written policies and procedures designed to achieve compliance across the business. (17 CFR § 240.15l-1)

Practical translation: Reg BI is proven in the workflow. If your CRM, order entry, product shelf, comp grids, surveillance, and supervision do not align, you will struggle to evidence “best interest at the time.”

Who it applies to (entity and operational context)

Entities: Reg BI applies to broker-dealers making recommendations to retail customers. The provided summary also references investment advisers in applicability, but the regulatory text here is broker-dealer focused; treat adviser applicability carefully and map to your actual registration and business model. (17 CFR § 240.15l-1)

Operational contexts where Reg BI typically triggers:

  • A registered rep recommends a specific security (buy/sell/hold).
  • A rep recommends an investment strategy that includes securities transactions (for example, rolling a portfolio into a managed program, moving into higher-turnover strategies, or concentrating positions).
  • Digital or hybrid channels that present “recommended” portfolios, model changes, or nudges that function as a recommendation.

Core scoping decision you must make: define “recommendation” and “retail customer” in a way that is consistent across business lines, supervision, and recordkeeping. Reg BI’s compliance strength depends on consistent triggering and consistent evidence. (17 CFR § 240.15l-1)

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

1) Map the recommendation lifecycle and insert Reg BI gates

Build a simple swimlane map from lead intake → profile → product selection → recommendation presentation → acceptance → execution → post-trade monitoring. Mark where each component obligation is satisfied and what record is created. (17 CFR § 240.15l-1)

Minimum gates to implement:

  • Pre-recommendation gate (Care + Conflicts): validate customer profile completeness; validate product eligibility; flag conflicts and compensation incentives relevant to the product. (17 CFR § 240.15l-1)
  • Recommendation gate (Disclosure + Care): deliver required disclosures; document the rationale and alternatives considered; confirm the recommendation matches the profile. (17 CFR § 240.15l-1)
  • Supervisory gate (Compliance): supervisory review standards for higher-risk scenarios; exception handling and escalation path. (17 CFR § 240.15l-1)

2) Standardize “best interest” documentation at the rep desktop

Create a required “Reg BI recommendation note” template embedded in your CRM/order workflow. Make it short enough to be used and structured enough to be testable.

Include fields that support the four obligations:

  • Customer objective/time horizon/liquidity needs and risk tolerance (Care). (17 CFR § 240.15l-1)
  • Product/strategy purpose and key risks explained (Care). (17 CFR § 240.15l-1)
  • Why this recommendation versus reasonable alternatives on your shelf (Care). (17 CFR § 240.15l-1)
  • Material conflicts disclosed and how they were addressed (Conflicts + Disclosure). (17 CFR § 240.15l-1)
  • Confirmation of required disclosures delivered (Disclosure). (17 CFR § 240.15l-1)

3) Implement conflicts controls that change outcomes, not just disclosures

Reg BI requires policies to identify and mitigate conflicts. Translate that into controls that supervisors can test:

  • Compensation governance: document where comp varies by product class, share class, proprietary/non-proprietary, revenue bands, or other incentives; define mitigations (for example, neutralizing payouts in high-conflict areas, adding pre-approval, or enhanced surveillance). (17 CFR § 240.15l-1)
  • Product shelf governance: define approval criteria, ongoing review triggers, and constraints for products with complex features or higher costs. Tie shelf decisions to what reps can recommend. (17 CFR § 240.15l-1)
  • Sales contests and quotas: identify incentives that could bias advice; implement restrictions and sign-offs aligned to conflict mitigation. (17 CFR § 240.15l-1)

4) Build supervision and surveillance around Reg BI failure modes

Convert Reg BI into exception reports supervisors can action. Examples of practical surveillance prompts:

  • Recommendations inconsistent with stated risk tolerance or time horizon.
  • High-cost or complex products sold to first-time investors without documented rationale.
  • Concentration, turnover, or repeated switching into higher-compensation products.
  • Missing or late disclosures relative to the recommendation timestamp.

Your written supervisory procedures should state who reviews what, when, and what happens when an exception is found (coaching, reversal, customer remediation, discipline, or policy changes). (17 CFR § 240.15l-1)

5) Close the loop with training that matches your products and channels

Generic “Reg BI training” does not fix rep behavior. Train by scenario:

  • What counts as a recommendation in your channels.
  • How to document alternatives.
  • How to explain fees, risks, and conflicts in plain language.
  • When to escalate to supervision.

Tie training completion to role-based access (for example, ability to sell certain products after training and attestation). (17 CFR § 240.15l-1)

6) Operationalize with a control library and ownership

Assign each Reg BI obligation a control owner (front line, supervision, compliance, product, operations). Maintain a control inventory that ties:

  • obligation → control → evidence → testing method → issue management path. (17 CFR § 240.15l-1)

If you use a GRC platform like Daydream, this mapping becomes easier to maintain across policies, controls, testing, and evidence requests because you can link “recommendation note completeness” and “conflict mitigation review” directly to the Reg BI obligation and retain artifacts in one place.

Required evidence and artifacts to retain

Keep evidence that proves what happened at the time of the recommendation. Build an evidence checklist by obligation:

Disclosure

  • Form CRS delivery records (date/time, channel, version).
  • Product/relationship disclosures delivered (fees, scope, conflicts), with version control.
  • Customer acknowledgments where your process collects them. (17 CFR § 240.15l-1)

Care

  • Customer profile (KYC, objectives, risk tolerance, time horizon, liquidity needs).
  • Recommendation rationale note (including alternatives considered).
  • Product due diligence file used to support understanding of risks/costs/features. (17 CFR § 240.15l-1)

Conflict of Interest

  • Conflicts inventory and updates.
  • Compensation and incentive governance approvals.
  • Mitigation controls evidence (pre-approvals, neutralization rules, supervisory sign-offs).
  • Surveillance reports and disposition logs. (17 CFR § 240.15l-1)

Compliance

  • Written policies and procedures addressing the four obligations.
  • Supervisory reviews, exception handling logs, and corrective actions.
  • Training materials, attendance/completion, and attestations.
  • Internal testing/audit results and remediation tracking. (17 CFR § 240.15l-1)

Common exam/audit questions and hangups

Expect regulators and internal audit to pressure-test how your policy works in real recommendations:

  • “Show me how you determine whether an interaction is a recommendation and therefore under Reg BI.” (17 CFR § 240.15l-1)
  • “Produce evidence that Form CRS and other disclosures were delivered before or at the recommendation.” (17 CFR § 240.15l-1)
  • “How do you document why a recommendation was in the customer’s best interest versus alternatives?” (17 CFR § 240.15l-1)
  • “What conflicts exist in your comp grid and product shelf, and what mitigations actually change behavior?” (17 CFR § 240.15l-1)
  • “How do supervisors review Reg BI risk, and what happens when exceptions are identified?” (17 CFR § 240.15l-1)

Hangup to plan for: firms often have pieces scattered across systems (CRM, email archive, order system, learning platform). Exams get harder when evidence cannot be assembled quickly and consistently.

Frequent implementation mistakes (and how to avoid them)

  1. Treating Reg BI as a disclosure project.
    Fix: build Care and Conflicts controls into the recommendation workflow and supervision, then back into disclosures. (17 CFR § 240.15l-1)

  2. No clear “recommendation” trigger in digital/hybrid channels.
    Fix: inventory all customer-facing prompts and model outputs that could function as a recommendation; apply the same documentation and disclosure logic. (17 CFR § 240.15l-1)

  3. Conflicts inventory exists, but mitigations are vague.
    Fix: define specific mitigations tied to incentives (approval steps, payout neutralization, limits, surveillance), and test their effectiveness. (17 CFR § 240.15l-1)

  4. Rep documentation is free-form and inconsistent.
    Fix: structured fields with required minimum rationale elements; supervisors review for quality, not just presence. (17 CFR § 240.15l-1)

  5. Policies are written, but ownership is unclear.
    Fix: name accountable owners per obligation and per control; track issues through to closure. (17 CFR § 240.15l-1)

Enforcement context and risk implications

No public enforcement cases were provided in the source catalog for this page, so this guidance focuses on the regulatory requirement and how to evidence compliance. Your practical risk is that weaknesses in documentation, conflicts mitigation, and supervisory follow-through create an inability to prove “best interest at the time,” which can expand exposure during exams, customer complaints, and arbitration. (17 CFR § 240.15l-1)

Practical execution plan (30/60/90)

First 30 days (stabilize scope and evidence)

  • Define and publish your firm’s operational definitions for “recommendation” and “retail customer,” aligned to your channels and products. (17 CFR § 240.15l-1)
  • Map the recommendation lifecycle and identify where each obligation is met and recorded. (17 CFR § 240.15l-1)
  • Create the minimum “Reg BI recommendation note” template and make it required for retail recommendations. (17 CFR § 240.15l-1)
  • Inventory disclosures (including Form CRS delivery mechanism) and confirm version control. (17 CFR § 240.15l-1)

Next 60 days (implement controls and supervision)

  • Build/refresh conflicts inventory and define concrete mitigations for top conflicts (comp, product shelf, incentives). (17 CFR § 240.15l-1)
  • Implement supervisory exception reporting and a documented disposition process. (17 CFR § 240.15l-1)
  • Update written supervisory procedures to reflect actual workflows and escalation paths. (17 CFR § 240.15l-1)
  • Train reps and supervisors using scenarios tied to your offerings and channels. (17 CFR § 240.15l-1)

By 90 days (test and harden)

  • Run a targeted internal test: sample recommendations, check disclosure timing, rationale quality, conflicts flags, and supervisory review evidence. (17 CFR § 240.15l-1)
  • Fix the top workflow failures (missing fields, late disclosures, weak alternative analysis, inconsistent supervision). (17 CFR § 240.15l-1)
  • Put Reg BI into ongoing monitoring: periodic surveillance reviews, control testing, and issue remediation tracking (ideally in a single system of record such as Daydream). (17 CFR § 240.15l-1)

Frequently Asked Questions

Does Reg BI apply to every customer interaction?

Reg BI applies when a broker-dealer makes a recommendation of a securities transaction or investment strategy to a retail customer. You need a clear internal standard for what your firm treats as a “recommendation” so the right workflow and evidence triggers consistently. (17 CFR § 240.15l-1)

What is the minimum documentation you should require for each recommendation?

Require a structured record that captures the customer profile basis, why the product/strategy fits, what alternatives were considered, what disclosures were provided, and what conflicts were identified and addressed. The goal is to show best interest at the time of the recommendation. (17 CFR § 240.15l-1)

Is delivering Form CRS enough to satisfy the Disclosure obligation?

No. The Disclosure obligation includes Form CRS and material facts about the relationship and the recommendation. Your process should show what was delivered, when it was delivered, and which version. (17 CFR § 240.15l-1)

How do you show you “mitigated” conflicts rather than just disclosed them?

Maintain a conflicts inventory and pair key conflicts with measurable controls, such as pre-approval requirements, compensation governance decisions, product eligibility limits, and surveillance with documented disposition. Examiners will look for mitigations that affect behavior and outcomes. (17 CFR § 240.15l-1)

What should supervisors be reviewing for Reg BI?

Supervisors should review recommendations for alignment to customer profile, completeness and quality of rationale (including alternatives), conflicts indicators, and timely disclosure delivery. Keep evidence of the review and how exceptions were resolved. (17 CFR § 240.15l-1)

How do you operationalize Reg BI across multiple systems (CRM, order entry, email, learning)?

Define one “system of record” for each evidence type (recommendation note, disclosures, supervision, training) and standardize naming/versioning so you can assemble an exam response quickly. A GRC tool like Daydream can help connect controls, testing, and artifacts to each Reg BI obligation. (17 CFR § 240.15l-1)

Frequently Asked Questions

Does Reg BI apply to every customer interaction?

Reg BI applies when a broker-dealer makes a recommendation of a securities transaction or investment strategy to a retail customer. You need a clear internal standard for what your firm treats as a “recommendation” so the right workflow and evidence triggers consistently. (17 CFR § 240.15l-1)

What is the minimum documentation you should require for each recommendation?

Require a structured record that captures the customer profile basis, why the product/strategy fits, what alternatives were considered, what disclosures were provided, and what conflicts were identified and addressed. The goal is to show best interest at the time of the recommendation. (17 CFR § 240.15l-1)

Is delivering Form CRS enough to satisfy the Disclosure obligation?

No. The Disclosure obligation includes Form CRS and material facts about the relationship and the recommendation. Your process should show what was delivered, when it was delivered, and which version. (17 CFR § 240.15l-1)

How do you show you “mitigated” conflicts rather than just disclosed them?

Maintain a conflicts inventory and pair key conflicts with measurable controls, such as pre-approval requirements, compensation governance decisions, product eligibility limits, and surveillance with documented disposition. Examiners will look for mitigations that affect behavior and outcomes. (17 CFR § 240.15l-1)

What should supervisors be reviewing for Reg BI?

Supervisors should review recommendations for alignment to customer profile, completeness and quality of rationale (including alternatives), conflicts indicators, and timely disclosure delivery. Keep evidence of the review and how exceptions were resolved. (17 CFR § 240.15l-1)

How do you operationalize Reg BI across multiple systems (CRM, order entry, email, learning)?

Define one “system of record” for each evidence type (recommendation note, disclosures, supervision, training) and standardize naming/versioning so you can assemble an exam response quickly. A GRC tool like Daydream can help connect controls, testing, and artifacts to each Reg BI obligation. (17 CFR § 240.15l-1)

Authoritative Sources

Operationalize this requirement

Map requirement text to controls, owners, evidence, and review workflows inside Daydream.

See Daydream
Client Onboarding & Suitability: Regulation Best Interest | Daydream