Form CRS Delivery and Content

To meet the Form CRS delivery and content requirement, you must (1) maintain an accurate, properly structured Form CRS and (2) deliver it to retail investors at account opening and before or at the time of certain recommendations, with records that prove timely delivery. Your operating model should hard-stop onboarding and recommendation workflows until delivery is completed and logged. (17 CFR § 240.17a-14)

Key takeaways:

• Treat Form CRS as a workflow control: no account opening or covered recommendation completes without recorded delivery. (17 CFR § 240.17a-14)
• Content must stay within Form CRS’s required format and topics, including conversation starters and references to additional resources. (17 CFR § 240.17a-14)
• Evidence matters as much as delivery: keep version history, delivery logs, and supervision records that show consistent operation. (17 CFR § 240.17a-14)

Form CRS failures usually happen in plain sight: the document exists, but delivery is inconsistent, evidence is thin, or the content drifts outside the required boundaries. Examiners tend to focus on operational reality, not intent. If your teams cannot prove “who received which CRS version, when, and why,” you have a control gap even if your disclosure language is strong. (17 CFR § 240.17a-14)

This requirement also sits in the same client journey as suitability and recommendation activity. A common breakdown is separating disclosure obligations from recommendation workflows, especially in hybrid firms or where marketing, onboarding, and advisory teams each touch the retail relationship. Aligning Form CRS delivery points with recommendation and account-opening events is the simplest way to keep supervision coherent and reduce exceptions. (17 CFR § 240.17a-14; FINRA Rule 2111)

This page gives requirement-level implementation guidance for a CCO/GRC lead: what the rule expects, where it breaks in operations, what steps to implement, and what artifacts to retain so you can answer exams quickly and consistently.

Regulatory text

Operator meaning: You must deliver Form CRS to retail investors at account opening, and you must run your business so that delivery happens consistently and is provable. The minimum baseline in your source pack is: “Broker-dealers and investment advisers must deliver Form CRS to retail investors at account opening.” (17 CFR § 240.17a-14)

What the operator must do (in plain terms):

• Maintain a current Form CRS that covers the required topics (services, fees/costs, conflicts, standard of conduct, disciplinary history), includes the required conversation starters, and points investors to additional resources. (17 CFR § 240.17a-14)
• Deliver Form CRS to each retail investor at account opening, and also before or at the time of certain recommendations (your data set highlights rollover recommendations), and upon request. (17 CFR § 240.17a-14)
• Keep records that demonstrate timely delivery and which version was delivered. (17 CFR § 240.17a-14)

Plain-English interpretation (what “good” looks like)

A workable interpretation for operations is:

1. Content compliance: Your Form CRS stays in the required “relationship summary” lane. It is short, standardized, and covers the mandated categories with the required prompts and references. (17 CFR § 240.17a-14)

2. Event-based delivery: Delivery occurs at defined client events:

• Account opening for retail investors. (17 CFR § 240.17a-14)
• Before/at certain recommendations (your data set flags rollovers as a key trigger). (17 CFR § 240.17a-14)
• Upon request with a consistent fulfillment method and proof. (17 CFR § 240.17a-14)

3. Supervision and evidence: You can reconstruct the story for any retail relationship: who the investor was, whether they were “retail,” which CRS version applied, when it was delivered, by what channel, and who supervised exceptions. (17 CFR § 240.17a-14)

Who it applies to (entity and operational context)

Entities:

• Broker-dealers. (17 CFR § 240.17a-14)
• Investment advisers. (17 CFR § 240.17a-14)

Operational contexts where it shows up:

• Digital or paper new account opening workflows (direct, through an associated person, or through a third party platform where you still control the relationship). (17 CFR § 240.17a-14)
• Recommendation workflows that touch retail investors (including rollover recommendations highlighted in your source pack). (17 CFR § 240.17a-14)
• Service desks and branches handling ad hoc requests for Form CRS. (17 CFR § 240.17a-14)

Related control surface (why suitability teams care):

• Recommendations and suitability supervision are often handled under broker-dealer supervisory systems and FINRA expectations. If Form CRS triggers are tied to recommendations, align them with the same systems that document basis/suitability so you do not create an “unsupervised lane.” (FINRA Rule 2111; Regulatory Notice 12-25)

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

Step 1: Define retail investor scope and triggering events

• Document your definition of “retail investor” for Form CRS applicability and how your onboarding system flags it. (17 CFR § 240.17a-14)
• Create a trigger matrix that lists events and required action:
  • New retail account opening → deliver Form CRS. (17 CFR § 240.17a-14)
  • Rollover recommendation to retail investor → deliver Form CRS before/at recommendation. (17 CFR § 240.17a-14)
  • Investor request → deliver Form CRS promptly with proof of fulfillment. (17 CFR § 240.17a-14)

Practical control: Make triggers machine-readable in your CRM/onboarding tool (event type + client classification + channel).

Step 2: Build and govern Form CRS content

• Assign a document owner (Compliance) and required reviewers (Legal, business line). (17 CFR § 240.17a-14)
• Confirm the form includes, at minimum, the topics your data set enumerates: services, fees/costs, conflicts, standard of conduct, disciplinary history, conversation starters, and pointers to additional resources. (17 CFR § 240.17a-14)
• Implement version control:
  • Version ID on the document.
  • Effective date.
  • Archive old versions with withdrawal date and rationale. (17 CFR § 240.17a-14)

Common operator rule: Any change to fees, services, or conflicts should trigger a CRS review before the change goes live in client-facing materials. (17 CFR § 240.17a-14)

Step 3: Engineer delivery into onboarding and recommendation workflows

Account opening (retail):

• Add a required “Form CRS delivered” step before account creation can complete. (17 CFR § 240.17a-14)
• For e-delivery, capture an auditable event: timestamp, delivery method, version, recipient identity, and confirmation mechanism used by your platform. (17 CFR § 240.17a-14)
• For paper delivery, require a scanned acknowledgment or a documented mailing event tied to the account-opening case. (17 CFR § 240.17a-14)

Recommendation triggers (including rollovers):

• Embed CRS delivery into the same workflow that records recommendation rationale/suitability, so supervisors review it in one place. (17 CFR § 240.17a-14; FINRA Rule 2111)
• Put a hard stop: recommendation cannot be finalized until CRS delivery is logged, unless an exception is approved and documented. (17 CFR § 240.17a-14)

Upon request:

• Provide a consistent intake channel (service ticket, email alias, portal request).
• Require fulfillment logging (date/time, version delivered, channel). (17 CFR § 240.17a-14)

Step 4: Supervise, test, and remediate exceptions

• Create a daily/weekly exception report: retail accounts opened without delivery evidence; covered recommendations without delivery evidence; request tickets without fulfillment evidence. (17 CFR § 240.17a-14)
• Triage exceptions:
  • True miss (no delivery) → deliver immediately, document remediation, consider client communication script approved by Compliance. (17 CFR § 240.17a-14)
  • Evidence gap (delivery occurred but not logged) → fix logging defect, retrain, and update procedures. (17 CFR § 240.17a-14)
• Run periodic sampling tests and document results as part of your supervisory controls. (17 CFR § 240.17a-14)

Step 5: Train front line and ops with scripts that match the form

• Train registered reps, IARs, and onboarding staff on:
  • When delivery is required.
  • How to explain what Form CRS is (relationship summary) without adding promises or expanding beyond the form.
  • Where the conversation starters fit in the client discussion. (17 CFR § 240.17a-14)

Tie training to recommendation quality expectations so the CRS conversation does not compete with suitability conversations; it should complement them. (FINRA Rule 2111; Regulatory Notice 12-25)

Required evidence and artifacts to retain

Maintain an “exam-ready pack” that you can produce quickly:

Content and governance

• Current Form CRS (final).
• Prior versions with effective/retired dates and change log.
• Approval records (Compliance/Legal sign-off).
• Mapping of CRS sections to required topic areas (internal checklist). (17 CFR § 240.17a-14)

Delivery evidence (by channel)

• System logs showing delivery timestamp, recipient, channel, and version. (17 CFR § 240.17a-14)
• Paper delivery evidence (acknowledgment, mailing record, or equivalent workflow artifact). (17 CFR § 240.17a-14)
• “Upon request” ticket records: request intake + fulfillment details. (17 CFR § 240.17a-14)

Supervision and testing

• Written procedures describing triggers, workflows, and exception handling.
• Exception reports and remediation notes.
• Training materials and completion records for relevant roles. (17 CFR § 240.17a-14)

Daydream note (earned mention): If you already manage onboarding controls in Daydream, treat Form CRS as a control with explicit trigger conditions, required artifacts, and recurring evidence checks. That structure reduces “tribal knowledge” risk when teams change.

Common exam/audit questions and hangups (what to prepare for)

Prepare crisp answers with exhibits:

1. “Show me how Form CRS is delivered at account opening.” Provide process map + screenshots + sample logs. (17 CFR § 240.17a-14)
2. “How do you know the right CRS version was delivered?” Provide versioning scheme + delivery logs including version ID. (17 CFR § 240.17a-14)
3. “How do you handle electronic vs paper delivery?” Provide channel-specific procedures and evidence types. (17 CFR § 240.17a-14)
4. “What triggers delivery outside onboarding?” Provide trigger matrix, especially rollover recommendation handling per your stated model. (17 CFR § 240.17a-14)
5. “How is this supervised?” Provide exception reporting, sampling results, and escalation. (17 CFR § 240.17a-14)
6. “How does this tie to recommendation controls?” Show integration with suitability documentation workflows. (FINRA Rule 2111; Regulatory Notice 12-25)

Frequent implementation mistakes and how to avoid them

Mistake	Why it fails	Fix
Treating Form CRS as “posted on the website” instead of delivered	Posting does not prove delivery to a specific retail investor at a specific event	Put delivery in the onboarding workflow with logged evidence. (17 CFR § 240.17a-14)
No hard stop on account opening	Staff can bypass, creating silent misses	Configure system validation or require supervisor-approved exception. (17 CFR § 240.17a-14)
Weak version control	You cannot prove which CRS applied	Add version ID, effective date, and archive process tied to logs. (17 CFR § 240.17a-14)
Rollover/recommendation triggers not mapped	Delivery occurs at opening but not at covered recommendations	Build trigger matrix and embed in recommendation workflow. (17 CFR § 240.17a-14)
Evidence scattered across systems	Exams slow down; gaps appear	Centralize evidence index (GRC register) and standardize artifacts. (17 CFR § 240.17a-14)

Enforcement context and risk implications

No public enforcement cases were provided in your source catalog, so this page does not cite specific actions.

Practically, the risk profile is still clear:

• Disclosure risk: failing to deliver Form CRS at the required event can be treated as a regulatory delivery failure, even if your intent was compliant. (17 CFR § 240.17a-14)
• Supervisory risk: if Form CRS triggers align with recommendation events, gaps can also raise supervisory questions because the same client interaction is under suitability scrutiny. (FINRA Rule 2111; Regulatory Notice 12-25)
• Operational risk: weak evidence controls convert minor process misses into exam findings because you cannot prove what happened. (17 CFR § 240.17a-14)

Practical 30/60/90-day execution plan

Your instruction set prohibits unsourced numbered timelines, so use phase-based execution.

Immediate (stabilize delivery and evidence)

• Confirm your current Form CRS includes required topics, conversation starters, and pointers to additional resources. (17 CFR § 240.17a-14)
• Implement version control (version ID + archive).
• Identify all retail account-opening paths and ensure each has a required CRS delivery step with logging. (17 CFR § 240.17a-14)

Near-term (close trigger gaps and supervision gaps)

• Build a trigger matrix that includes rollover recommendations and “upon request” fulfillment. (17 CFR § 240.17a-14)
• Integrate delivery controls into recommendation workflows that are already supervised for suitability documentation. (FINRA Rule 2111; Regulatory Notice 12-25)
• Stand up exception reporting and a remediation playbook. (17 CFR § 240.17a-14)

Ongoing (prove it in exams)

• Run periodic sampling, document results, and track corrective actions to closure. (17 CFR § 240.17a-14)
• Refresh training for onboarding staff and supervised persons whenever you change workflows or update the form. (17 CFR § 240.17a-14)
• Maintain an “exam-ready” evidence folder keyed to retail investor, trigger event, and CRS version. (17 CFR § 240.17a-14)

Frequently Asked Questions

Do we have to deliver Form CRS to every client?

The requirement is scoped to retail investors and specific triggering events like account opening and certain recommendations. Build your workflow so retail classification drives whether delivery is required and logged. (17 CFR § 240.17a-14)

Is website posting enough to satisfy Form CRS delivery?

Website posting can support access, but you still need a process that delivers Form CRS at required events and creates evidence tied to the retail investor and the CRS version. Plan for examiners to ask for delivery logs. (17 CFR § 240.17a-14)

What evidence is strongest for electronic delivery?

System-of-record logs that capture recipient identity, timestamp, delivery channel, and CRS version are the easiest to defend. Pair that with written procedures that describe how the system produces the log. (17 CFR § 240.17a-14)

How should we handle rollover recommendations operationally?

Treat rollover recommendations as a defined trigger and embed CRS delivery into the same workflow where you document the recommendation basis and supervise suitability-related steps. This keeps the disclosure and recommendation record aligned. (17 CFR § 240.17a-14; FINRA Rule 2111)

What if an account was opened without recorded Form CRS delivery?

Treat it as an exception: deliver Form CRS promptly, document remediation, and fix the control that allowed the account to open without the delivery log. Keep the exception record for exams. (17 CFR § 240.17a-14)

How often should we update Form CRS?

Update when your services, fees/costs, conflicts, or other required disclosures change in a way that makes the current relationship summary inaccurate. Maintain version history so you can show what investors received at the time. (17 CFR § 240.17a-14)