Reg BI Care Obligation

Reg BI’s Care Obligation requires your broker-dealer to use reasonable diligence, care, and skill for every recommendation by understanding the product, the customer’s investment profile, and the recommendation’s risks and costs, then forming a reasonable belief it is in the customer’s best interest at that moment. You operationalize it by standardizing product due diligence, customer-profile capture, alternative consideration, and supervisory review with auditable records. (17 CFR § 240.15l-1)

Key takeaways:

• Build a repeatable recommendation file: customer profile, product/risk/cost analysis, and why the recommendation is in the customer’s best interest. (17 CFR § 240.15l-1)
• Require consideration of reasonably available alternatives and document why they were not selected. (17 CFR § 240.15l-1)
• Supervision must detect patterns across a series of transactions and flag potential excessiveness. (17 CFR § 240.15l-1)

The Care Obligation is where Reg BI becomes operational. It is not satisfied by a generic “suitable” determination or a disclosure-only approach. Your exam risk is highest when recommendations are made without consistent documentation of: (1) what you knew about the customer, (2) what you knew about the product (including risks and costs), (3) what alternatives you considered, and (4) why your recommendation was in the customer’s best interest at the time it was made. (17 CFR § 240.15l-1)

For a CCO or GRC lead, the fastest path to compliance is to treat “care” as a controlled workflow: defined inputs, required decision points, supervisory checks, and retained evidence. You want the same outcome every time, regardless of rep, channel, or product complexity. That means aligning front-office behaviors (how recommendations are formed and explained) with back-office governance (product due diligence, surveillance, and QA). (17 CFR § 240.15l-1)

This page breaks the Care Obligation into requirement-level steps you can assign, test, and evidence. It also highlights the exam “hangups” that tend to fail: weak alternative analysis, cost blindness, and missing aggregation logic for a series of transactions. (17 CFR § 240.15l-1)

Regulatory text

Text (excerpt): “The broker-dealer must exercise reasonable diligence, care, and skill in making the recommendation…” and must consider the customer’s investment profile and potential risks and costs. (17 CFR § 240.15l-1)

Operator interpretation (what you must be able to prove):

1. You understood the recommendation. Your firm can show it evaluated the product’s risks, rewards, and costs before allowing recommendations. (17 CFR § 240.15l-1)
2. You understood the customer. Your customer profile collection is complete enough to support a best-interest belief at the time of recommendation. (17 CFR § 240.15l-1)
3. You considered alternatives. You considered reasonably available alternatives and can explain why the selected option best served the customer’s interest. (17 CFR § 240.15l-1)
4. You assessed “series of transactions.” For patterns of trading or repeated recommendations, your supervision evaluates whether the combined activity becomes excessive or inconsistent with best interest. (17 CFR § 240.15l-1)

Plain-English requirement (what “Care” means day to day)

A rep cannot recommend a security, account type, or strategy unless they (and your firm) have done the homework to understand the product and the customer, and can articulate a defensible, customer-specific reason the recommendation is in the customer’s best interest right then. If costs are higher, risks are higher, or complexity is higher, your diligence and documentation should increase proportionally. (17 CFR § 240.15l-1)

A practical test: if you removed the rep’s narrative and left only objective artifacts (profile, product facts, alternatives, and approvals), a supervisor should still be able to reconstruct why the recommendation was reasonable. (17 CFR § 240.15l-1)

Who it applies to (entity and operational context)

Entities: The rule text you provided is in Reg BI for broker-dealers; apply this requirement to broker-dealer recommendations. (17 CFR § 240.15l-1)

Operational contexts where Care Obligation must be embedded:

• New account recommendations (including account type and services model where your firm treats it as a recommendation).
• Security transactions (buy, sell, roll, exchange).
• Strategy recommendations (e.g., reallocations, concentrated positions, systematic selling).
• Ongoing patterns that function as a “series of transactions,” especially where turnover, switching, or repeated trades can harm the customer through costs or risk. (17 CFR § 240.15l-1)

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

1) Define “recommendation” triggers and route them into a controlled workflow

• Create a clear internal list of events treated as recommendations (trade, switch, roll, strategy shift, account type suggestion).
• Build a workflow that forces required inputs before submission (profile + product + alternatives + cost view).
• Ensure the workflow is used consistently across channels (branch, call center, digital, hybrid). (17 CFR § 240.15l-1)

Control design tip: If your firm uses Daydream for GRC workflows, map the Care Obligation into a single “Recommendation File” checklist with conditional fields (e.g., higher scrutiny for complex products), then assign supervisory approvals and evidence retention tasks.

2) Standardize customer investment profile capture (minimum viable completeness)

Collect and maintain the customer’s investment profile elements relevant to your business model, then enforce updates when:

• the customer’s circumstances change,
• the recommendation materially changes risk exposure, or
• profile data is stale for your risk tolerance. (17 CFR § 240.15l-1)

Operational requirement: The rep cannot finalize a recommendation until required profile fields are completed, and missing fields trigger a documented follow-up or an explicit “cannot recommend” decision.

3) Perform product due diligence that is recommendation-ready

Before allowing recommendations, your firm should maintain product-level information that a rep and supervisor can rely on:

• key risks and scenarios where losses are likely,
• expected benefits and limitations,
• direct and indirect costs and how they are incurred,
• constraints (liquidity limits, surrender charges, lockups, complexity drivers). (17 CFR § 240.15l-1)

Practical approach: Build a product shelf dossier per product/security type that is easy to cite in a recommendation file. The rep should not be writing the product’s risk summary from scratch each time; they should be applying a vetted summary to a specific customer context.

4) Require a “reasonably available alternatives” step

For each recommendation, require the rep to identify alternatives considered and why the recommended choice was better for that customer at that time. (17 CFR § 240.15l-1)

Make it executable:

• Provide an alternatives menu tied to the product category (e.g., lower-cost share class, different duration/risk level, hold/do-nothing, staged implementation).
• Require one sentence per alternative: why it was not selected, tied to the customer profile and objectives.
• For higher-cost recommendations, require explicit cost/benefit rationale. (17 CFR § 240.15l-1)

5) Build a customer-specific best-interest rationale (short, structured, auditable)

Require a structured narrative that answers:

• Customer goal and constraint being addressed (from profile).
• Principal risks and costs acknowledged, in plain language.
• Why these risks/costs are acceptable given the customer’s profile.
• Why the recommendation is in the customer’s best interest now. (17 CFR § 240.15l-1)

Quality standard: If the rationale can be copy-pasted between customers without edits, it is probably deficient.

6) Supervise both single recommendations and “series of transactions”

Your supervisory system should:

• review recommendation files for completeness and logic,
• spot-check calls/notes against the documented rationale,
• run surveillance for patterns that indicate excessiveness when viewed together (e.g., repeated switching, frequent trading in a short window, escalating costs without clear benefit). (17 CFR § 240.15l-1)

Escalation design: Define what requires pre-trade approval vs post-trade review. High-risk/high-cost/complex recommendations should trigger tighter review.

7) Train to the workflow, not to slogans

Training must teach reps how to:

• document alternatives without turning it into boilerplate,
• discuss costs in customer language,
• handle incomplete profiles (pause, obtain info, or decline to recommend),
• recognize when repeated activity creates a “series of transactions” concern. (17 CFR § 240.15l-1)

Required evidence and artifacts to retain

Retain artifacts that let you reconstruct the decision at the time of recommendation:

• Customer investment profile record (captured fields + timestamps + update history).
• Recommendation file showing product, objective, risks, costs, and best-interest rationale. (17 CFR § 240.15l-1)
• Alternatives considered (options + reasons not selected). (17 CFR § 240.15l-1)
• Product due diligence dossier used by the rep (risk/cost summary source).
• Supervisory review evidence (approvals, exceptions, escalation notes, QA results).
• Surveillance outputs tied to “series of transactions” reviews and any investigations/remediations. (17 CFR § 240.15l-1)
• Training completion and role-based attestations that align to the workflow.

Common exam/audit questions and hangups

Expect examiners/auditors to probe:

• “Show me how you determined the recommendation was in the customer’s best interest at the time it was made.” (17 CFR § 240.15l-1)
• “Where do you document consideration of reasonably available alternatives?” (17 CFR § 240.15l-1)
• “How do you ensure risks and costs were understood and explained?” (17 CFR § 240.15l-1)
• “What controls detect excessive activity across a series of transactions?” (17 CFR § 240.15l-1)
• “How does supervision verify the recommendation file matches what happened in practice (notes, calls, emails)?”

Hangups that cause friction:

• Inconsistent documentation quality by rep/team.
• Alternatives step exists but is boilerplate.
• Costs are referenced vaguely rather than concretely described in the firm’s own terms.
• Surveillance is trade-by-trade only, with limited aggregation logic. (17 CFR § 240.15l-1)

Frequent implementation mistakes (and how to avoid them)

1. Treating Care as “suitability-plus.” Avoid: a suitability form with a new label. Fix: enforce alternatives + cost/risk reasoning + supervisory check. (17 CFR § 240.15l-1)
2. No product-level diligence library. Avoid: reps inventing product descriptions. Fix: maintain vetted product dossiers and require linkage in the recommendation file. (17 CFR § 240.15l-1)
3. One-size-fits-all rationale text. Avoid: templated narratives with no customer specificity. Fix: required fields that tie directly to profile attributes and the customer’s stated goal.
4. Ignoring “series of transactions.” Avoid: no roll-up review. Fix: surveillance that flags patterns and requires documented supervisory conclusions. (17 CFR § 240.15l-1)
5. Letting incomplete profiles proceed. Avoid: “best guess” recommendations. Fix: hard stops or documented exceptions with heightened review.

Execution plan (30/60/90-day)

First 30 days (stabilize the minimum viable workflow)

• Inventory recommendation triggers and where they occur.
• Define the minimum required profile fields and the “cannot recommend until complete” rule.
• Draft the recommendation file template (profile link, product link, risks, costs, alternatives, rationale).
• Identify supervisory checkpoints and exception categories. (17 CFR § 240.15l-1)

By 60 days (make it repeatable and supervised)

• Build or refine product due diligence dossiers for products commonly recommended.
• Implement alternatives menus by product category.
• Train reps and supervisors on the exact documentation standard.
• Start QA sampling and track recurring defects by rep/team/product. (17 CFR § 240.15l-1)

By 90 days (make it auditable and resilient)

• Add “series of transactions” surveillance with clear escalation playbooks.
• Implement management reporting that shows documentation completeness, exceptions, and remediation outcomes.
• Run a mock exam: select a sample of recommendations, reconstruct the decision, and test whether evidence supports best interest at the time made. (17 CFR § 240.15l-1)

Frequently Asked Questions

Do we have to document “reasonably available alternatives” for every recommendation?

Reg BI’s Care Obligation includes considering reasonably available alternatives as part of forming a reasonable best-interest belief. Build this into your standard recommendation file so it is consistently captured. (17 CFR § 240.15l-1)

What counts as sufficient cost consideration under the Care Obligation?

The requirement is to understand and consider potential risks and costs as part of the recommendation analysis and best-interest belief. Your documentation should show the rep recognized meaningful costs and weighed them against expected benefits for that customer. (17 CFR § 240.15l-1)

How do we operationalize “series of transactions” review without overhauling surveillance?

Start by defining patterns that trigger review (frequent switching, repeated trades, escalating costs) and require a documented supervisory conclusion when triggered. The goal is to evaluate whether the combined activity is excessive or not in the customer’s best interest when taken together. (17 CFR § 240.15l-1)

Can we meet the Care Obligation with a rep attestation alone?

A rep attestation may support your record, but it rarely proves diligence by itself. You need artifacts that show the inputs reviewed (profile, product risks/costs, alternatives) and supervisory oversight where required. (17 CFR § 240.15l-1)

What if the customer refuses to provide key investment profile information?

Treat missing profile elements as a decision constraint. Document the refusal and your resulting limitation: obtain the information, recommend a more conservative path, or decline to recommend if you cannot form a reasonable best-interest belief. (17 CFR § 240.15l-1)

How should we handle complex products under the Care Obligation?

Increase the diligence and documentation depth in proportion to complexity, risk, and cost. Make complex products conditional in your workflow with stricter supervision and a clearer articulation of risks, costs, and alternatives. (17 CFR § 240.15l-1)