Options and Security Futures Filing Requirements

FINRA Rule 2210(c)(7) requires you to file any retail communication about options or security futures with FINRA at least 10 business days before first use so FINRA can review higher-risk product advertising. To operationalize it, you need a repeatable intake-and-classification process, a pre-use filing workflow, and evidence that no covered communication is distributed before the filing window clears. (FINRA Rule 2210)

Key takeaways:

• Treat “options/security futures + retail audience” as an automatic pre-use FINRA filing trigger at least 10 business days before first use. (FINRA Rule 2210)
• Build controls that stop distribution until filing is completed and the timeline requirement is met. (FINRA Rule 2210)
• Retain artifacts that prove classification, submission timing, approvals, and the exact content version that was filed and later used. (FINRA Rule 2210)

Options and security futures retail advertising is a classic exam hotspot because it combines product complexity, retail impact, and time-bound procedural requirements. FINRA Rule 2210(c)(7) creates a simple but unforgiving operational obligation: if the communication is a retail communication and it concerns options or security futures, you must file it with FINRA at least 10 business days before first use. (FINRA Rule 2210)

CCOs and GRC leads usually fail this requirement in predictable ways: the marketing calendar moves faster than compliance; communications are misclassified (e.g., treated as “correspondence” or “institutional” when they’re retail); or a last-minute edit creates a “new” version that was never filed. The fix is not more policy language. The fix is an operational system that (1) identifies covered communications early, (2) enforces a hard distribution gate tied to the filing clock, and (3) preserves evidence that aligns the filed version to the version actually used.

This page gives you requirement-level implementation guidance you can deploy quickly: scoping, workflow design, step-by-step tasks, evidence to retain, exam questions you should pre-answer, and a pragmatic execution plan.

Regulatory text

Requirement (excerpt): “Retail communications concerning options or security futures must be filed with FINRA at least 10 business days before first use.” (FINRA Rule 2210)

Operator interpretation (what you must do):

1. Identify whether a draft is a retail communication and whether it concerns options or security futures. If yes, it is in scope. (FINRA Rule 2210)
2. File the retail communication with FINRA before it is used publicly, with a lead time of at least 10 business days. (FINRA Rule 2210)
3. Prevent first use (posting, emailing, handing out, publishing, sponsoring, or otherwise distributing to retail) until the filing timing requirement is satisfied. (FINRA Rule 2210)

Plain-English requirement

If you market or educate retail investors about options or security futures, you cannot “finish it and ship it.” You must submit the retail communication to FINRA in advance and build enough runway so first use happens no earlier than the required pre-filing window. (FINRA Rule 2210)

Who it applies to (entity + operational context)

In-scope entities

• Broker-dealers preparing or distributing retail communications about options or security futures. (FINRA Rule 2210)
• Registered representatives and supervised persons who create, approve, or distribute such communications under the firm’s name or through firm channels. (FINRA Rule 2210)

In-scope operational contexts (common examples)

• Website pages, landing pages, banner ads, and app content promoting options or security futures.
• Retail email campaigns about options strategies, risks, benefits, or account features related to options/security futures.
• Social posts or paid social ads directing retail investors to options/security futures content.
• Retail seminar/webinar invitations or decks where the content concerns options or security futures.

Key scoping decision

• If the audience is retail (or could reasonably be retail due to open distribution) and the content concerns options/security futures, treat it as fileable and time-gated. (FINRA Rule 2210)

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

1) Build an intake trigger that catches covered drafts early

Create a single intake path for marketing, product, and rep-created retail content. Your intake form (ticket, request, or job jacket) should require:

• Product/topic checkboxes: options, security futures
• Audience selection: retail vs institutional vs 1:1
• Channel: web, email, social, print, seminar, third-party site
• Intended first-use date (required field)

Control objective: If “options/security futures” + “retail” is selected, the workflow auto-routes to “FINRA filing required” and blocks launch scheduling until compliance clears it. (FINRA Rule 2210)

2) Classify the communication and document the rationale

In your review checklist, include a short “classification” section:

• Is it a retail communication?
• Does it concern options or security futures?
• Conclusion: FINRA pre-use filing required or not required

Keep this rationale brief but explicit. Examiners look for consistent classification, not essays.

3) Lock the version that will be filed

Version control is where teams get burned. Before filing:

• Export a “frozen” copy (PDF/screenshot for web and social; final HTML/text for email; final deck for events).
• Assign a unique version ID.
• Require any later change to be treated as a new review event, with a re-check of filing needs. (FINRA Rule 2210)

4) Prepare the FINRA filing package

For each filed item, compile:

• Final creative/version ID
• Channel and distribution plan
• Intended first-use date
• Internal approvals (principal sign-off per your supervisory process)

Even if your internal process includes additional reviews (legal, risk, product), keep the filing package standardized so the compliance team can submit quickly.

5) Submit the filing with the required lead time and enforce a distribution gate

Operationalize the rule as a hard gating control:

• Your marketing operations calendar must treat the intended first-use date as a dependent date that cannot be earlier than the filing window. (FINRA Rule 2210)
• Disable publishing permissions (where possible) until compliance marks the job as “filed and timing satisfied.”
• For reps, require pre-approval of retail options/security futures content and monitor outbound channels for unapproved postings.

6) Post-filing: manage comments, changes, and launch readiness

Maintain a single “source of truth” record showing:

• What was filed (exact version)
• When it was filed
• The approved first-use date (aligned to the filing requirement)
• Any subsequent edits and whether a new filing/review was triggered

7) Put monitoring in place (so you catch out-of-process use)

Minimum monitoring set:

• Periodic sampling of live web pages and active campaigns tagged “options/security futures”
• Review of rep social activity where the firm has a supervision obligation
• Exception log for any content used without completing the filing workflow (with remediation and discipline where appropriate)

Required evidence and artifacts to retain

Store these items together per communication (one folder/record per filing):

• Classification record (retail + options/security futures determination) (FINRA Rule 2210)
• Final filed version (PDF, screenshots, deck file, or final copy) and version ID
• FINRA submission confirmation and timestamps (FINRA Rule 2210)
• Approval evidence from the firm’s review chain (who approved, date/time)
• Distribution gate evidence (ticket statuses, publication logs, email send logs, social ad launch logs)
• Change log documenting post-approval edits and re-review decisions

Retention should align to your firm’s communications recordkeeping program; the key is the ability to reconstruct the timeline and prove first use was not before the filing window. (FINRA Rule 2210)

Common exam/audit questions and hangups

Expect to answer these quickly, with artifacts:

1. How do you identify retail communications concerning options/security futures that require filing? Show the intake trigger and classification checklist. (FINRA Rule 2210)
2. How do you prove the filing happened at least 10 business days before first use? Provide submission timestamps and launch logs. (FINRA Rule 2210)
3. How do you control version changes after filing? Show version IDs and change logs tied to approvals.
4. How do you prevent business users from bypassing the workflow? Demonstrate system permissions, monitoring, and exception management.

Frequent implementation mistakes (and how to avoid them)

1. Mistake: Treating “educational” options content as exempt from filing.
   Fix: Base scope on “retail communication concerning options/security futures,” not on marketing intent. (FINRA Rule 2210)

2. Mistake: Filing the concept, then publishing a revised version.
   Fix: Freeze the filed version; any substantive change triggers re-review and a filing reassessment. Maintain strict version control.

3. Mistake: Relying on calendar reminders instead of a hard launch gate.
   Fix: Build a workflow status that blocks publication or campaign activation until compliance clears the timing condition. (FINRA Rule 2210)

4. Mistake: Reps post options content on social without going through marketing.
   Fix: Make rep channels part of your supervised communications program, require pre-approval for covered content, and conduct surveillance for off-workflow activity.

Enforcement context and risk implications

No public enforcement cases were provided in the source materials for this requirement, so this page does not summarize specific actions.

Practically, the risk is structural: options and security futures are higher-risk products, and FINRA requires pre-filing for retail communications so it can review these messages before they reach retail investors. Missing the filing window, losing proof of timing, or using a different version than what was filed can convert a marketing project into a reportable compliance issue. (FINRA Rule 2210)

Practical 30/60/90-day execution plan

First 30 days (stabilize and stop bleeding)

• Inventory current retail-facing options/security futures content across web, email, and social channels.
• Stand up a single intake ticket with required fields: product, audience, channel, intended first-use date.
• Add a “FINRA filing required” status and block launch unless compliance clears it. (FINRA Rule 2210)
• Define version control rules: what constitutes a new version and who can approve changes.

Next 60 days (systematize and evidence-proof)

• Train marketing, product, and supervised persons on the trigger: retail + options/security futures = file at least 10 business days before first use. (FINRA Rule 2210)
• Implement a standardized filing package checklist and evidence folder structure.
• Add monitoring: periodic sampling of live pages and campaigns tagged as options/security futures; log exceptions and remediation.

By 90 days (operational maturity)

• Run a tabletop test: pick several communications and reconstruct the full timeline (draft → approval → filing → first use) from your artifacts.
• Tighten controls for rep-created content (pre-approval workflow, surveillance checks).
• Automate reporting for aging drafts and upcoming launches that cannot meet the filing window, so the business adjusts timelines early. (FINRA Rule 2210)

Where Daydream fits

If you are coordinating multiple teams (marketing, trading/product, legal, supervision) and struggling with version control plus evidence, Daydream can act as the workflow system of record: intake, classification, approvals, filing-task tracking, and an audit-ready artifact package per communication. Keep the tool decision secondary to the control outcome: no covered retail communication goes live before the filing window is satisfied. (FINRA Rule 2210)

Frequently Asked Questions

What counts as “first use” for the filing clock?

Treat first use as the first time the retail communication is distributed or made available to retail investors in the channel you control (posting, sending, publishing, or launching). Your controls should prevent any retail availability until the filing timing requirement is met. (FINRA Rule 2210)

If a web page is accessible to the public, is it “retail” by default?

Open-access content is typically treated as retail-facing for operational purposes because retail investors can access it without restriction. Use your classification step to document how you reached the retail determination and route it to filing if it concerns options/security futures. (FINRA Rule 2210)

Do minor edits after filing require a new filing?

The rule excerpt provided here addresses the pre-filing requirement, not a materiality standard. Operationally, treat any change as a re-review trigger and document whether you filed the updated version to avoid version-mismatch findings. (FINRA Rule 2210)

How do we handle third-party marketing agencies creating options ads for us?

Make the third party follow your intake and version-control process, and contractually require they cannot publish on your behalf until your compliance team confirms filing and timing are satisfied. Keep the same evidence package as if the content were created in-house. (FINRA Rule 2210)

Can we schedule a campaign while the filing is pending?

You can plan internally, but your workflow should prevent launch activation and external distribution until the filing requirement is satisfied. The marketing calendar should treat launch dates as conditional on compliance clearance. (FINRA Rule 2210)

What evidence is most persuasive in an exam?

A complete record that ties together the exact filed version, the submission confirmation and timestamp, internal approval, and objective proof of the first-use date (publication logs or send records). Gaps usually appear where teams cannot prove the version used matched what was filed. (FINRA Rule 2210)