Projections and Predictions Restrictions

FINRA’s projections and predictions restrictions require you to prevent retail communications and correspondence from forecasting performance, suggesting past results will repeat, or making exaggerated or unwarranted claims about investment outcomes. Operationalize this by hard-coding review standards, building “no-go” language rules, and retaining pre-use approvals and supporting back-up for every performance-related statement. (FINRA Rule 2210)

Key takeaways:

• Retail communications and correspondence cannot include performance projections/predictions or imply past performance will recur. (FINRA Rule 2210)
• You need supervisory controls that catch both explicit forecasts and “implied guarantee” language before distribution. (FINRA Rule 2210)
• Evidence matters: keep the final communication, approvals, version history, and support for any investment-results claim. (FINRA Rule 2210)

“Projections and predictions restrictions” is one of the fastest ways a well-intended marketing piece becomes a regulatory problem. The rule is simple on paper: retail communications and correspondence cannot predict or project performance, cannot imply past performance will recur, and cannot make exaggerated or unwarranted claims about investment results. (FINRA Rule 2210) The operational reality is harder: problematic language often appears as a casual phrase (“should deliver,” “on track to return,” “proven winner,” “expect a meaningful percentage”), a chart that implies a forward path, or a “case study” that reads like a promise.

As a Compliance Officer, CCO, or GRC lead, your job is to translate this restriction into repeatable controls: (1) clear drafting standards for marketing and reps, (2) surveillance and pre-use review that flags projections and implied guarantees, (3) a consistent approach to permissible performance discussions (facts with appropriate context, not forecasts), and (4) records that show supervision was real, not nominal.

This page gives you requirement-level guidance to implement FINRA Rule 2210(d)(1)(F) quickly, with steps, artifacts, audit questions, common failure modes, and an execution plan you can run with immediately. (FINRA Rule 2210)

Regulatory text

Requirement (excerpt): “Retail communications and correspondence may not predict or project performance, imply that past performance will recur, or make any exaggerated or unwarranted claim about investment results.” (FINRA Rule 2210)

What the operator must do:
You must supervise communications so that any message directed to retail (and covered correspondence) does not include (a) explicit forecasts (numbers, ranges, target returns), (b) implied recurrence of past results, or (c) inflated claims about investment outcomes that are not fair, balanced, and supportable. The control outcome you are driving is straightforward: no prohibited performance-forward statements reach retail audiences. (FINRA Rule 2210)

Plain-English interpretation (what the rule really forbids)

Treat this restriction as a “no promises, no forecasts” standard for retail-facing content.

What to block in retail communications and correspondence:

• Explicit projections/predictions: “We expect the fund to return a meaningful percentage,” “target yield,” “projected performance,” “your account could grow to…”
• Implied recurrence: “Last year was a meaningful percentage, so you can expect similar results,” “this strategy keeps winning,” “consistent returns”
• Exaggerated/unwarranted results claims: “Guaranteed,” “can’t lose,” “proven to outperform,” “best way to generate income,” or superlatives that imply a reliable outcome without a fair, balanced basis. (FINRA Rule 2210)

Borderline content that often fails in practice:

• Conditional promises that still read like a forecast (“if rates fall, this will deliver strong returns”)
• Back-tested or hypothetical scenarios presented like they are likely outcomes for the reader
• Testimonials or “success stories” that imply the reader will achieve similar results

Who it applies to (entity and operational context)

Covered entities and roles

• Broker-dealers and their associated persons/registered representatives preparing, approving, or distributing communications with the public. (FINRA Rule 2210)

Covered communication types (operationally)

• Retail communications: marketing materials, webpages, social posts, pitch decks, mass emails, seminar slides, video scripts, and any other communication distributed to retail investors.
• Correspondence: rep-to-customer emails, messages, and letters that are not “institutional communications,” including templates and mass-customized notes. (FINRA Rule 2210)

Key operational contexts where violations appear

• Marketing launches (new product, new strategy, new “model portfolio”)
• Sales enablement content used by reps (talk tracks, one-pagers, FAQs)
• Advisor “commentary” on markets that drifts into forecasts
• Third-party content you re-share (market letters, model performance narratives) that includes implied outcomes

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

1) Define “prohibited projection” rules your business can apply

Write a short, enforceable internal standard that maps directly to the rule text:

• Prohibit any forward-looking performance statement in retail communications/correspondence. (FINRA Rule 2210)
• Prohibit language that implies recurrence of past performance. (FINRA Rule 2210)
• Prohibit exaggerated/unwarranted investment result claims, including absolutes and “can’t miss” phrasing. (FINRA Rule 2210)

Create a “red flag lexicon” for reviewers and drafters (examples):

• “expect,” “project,” “target,” “will return,” “should generate,” “guarantee,” “proven,” “always,” “consistent,” “can’t lose” Add business-specific terms (strategy names, product nicknames) that commonly appear next to performance claims.

2) Embed controls into the content lifecycle (draft → review → publish)

Implement a workflow that forces a compliance checkpoint before retail distribution:

• Intake: Require submitters to tag whether content references performance or investment results.
• Pre-use review: Route all retail communications that mention performance, results, rankings, “outperformance,” or investor outcomes for heightened scrutiny against 2210(d)(1)(F). (FINRA Rule 2210)
• Edits and re-review: Treat revisions as new versions; re-approve when performance-related language changes.
• Final-lock publishing: Only approved versions can be posted/sent.

If you use Daydream, configure a review checklist specifically for “projections and predictions restrictions,” with structured fields for (a) whether any forward-looking statement exists, (b) whether any past-performance language implies recurrence, and (c) what support exists for any claim about results.

3) Train drafters and reps with “allowed vs. not allowed” patterns

Training should focus on substitutions people can actually use:

• Replace “This will outperform” with neutral, factual descriptions of objective features (strategy objective, risks, time horizon), without predicting results. (FINRA Rule 2210)
• Replace “You can expect…” with “The investment involves risk, including…” plus factual product characteristics.
• For past performance: allow factual presentation with appropriate context, but prohibit “therefore you will get similar results” messaging. (FINRA Rule 2210)

Give them a one-page cheat sheet. Most violations come from casual phrasing, not intentional misconduct.

4) Control third-party and rep-created content

Two recurring weak points:

• Third-party research/commentary re-distributed to retail: screen it for projections/predictions and implied recurrence before sharing under your name.
• Rep templates and “approved snippets”: lock down pre-approved language blocks so reps don’t improvise return expectations in emails.

Operational approach:

• Maintain an approved content library of performance-safe statements.
• Require reps to use templates for common topics (market volatility, income needs, diversification) that avoid forecasts.

5) Establish exception handling (and don’t let “exceptions” become the rule)

If the business pushes for “scenario analysis,” “targets,” or “what-if growth” tools for retail, treat it as a compliance design review. The default posture under 2210(d)(1)(F) for retail communications/correspondence is restriction on projecting/predicting performance. (FINRA Rule 2210) Route proposed exceptions through Legal/Compliance with documented rationale, disclosures, and supervisory sign-off.

6) Monitor and test the control

Add targeted surveillance:

• Sample rep correspondence where certain keywords appear (“expect,” “target,” “guarantee”).
• Review social posts and seminar materials for forward-looking language.
• Track rejects/edits as leading indicators and retrain teams that repeatedly submit noncompliant drafts.

Required evidence and artifacts to retain

Build an exam-ready file for each retail communication and any controlled correspondence templates:

• Final approved communication (PDF/screenshot/video script)
• Submission record (requestor, channel, intended audience)
• Compliance review record (comments, required edits, approval decision) (FINRA Rule 2210)
• Version history showing what changed and when
• Support file for any investment-results-related statement (basis and substantiation)
• Distribution record (where/when published or sent)
• Training attendance and materials on projections/predictions restrictions
• Supervisory procedures referencing the prohibition language (mapped to 2210(d)(1)(F)) (FINRA Rule 2210)

Daydream is often used here as the system of record: it centralizes approvals, version control, and audit trails so you can show exactly how performance-forward language was caught and corrected.

Common exam/audit questions and hangups

Expect reviewers to probe:

• “Show me how you prevent projections/predictions in retail communications and correspondence.” (FINRA Rule 2210)
• “How do you define and detect ‘implied past performance will recur’?”
• “How do you supervise rep emails and messages where promises are often made?”
• “Where is your substantiation for investment-result claims that could be read as exaggerated?”
• “How do you handle third-party content you re-share to retail?”
• “Do you re-approve modified materials, or can marketing ‘minor edit’ around compliance?”

Hangups that slow teams down:

• Arguing “it’s not a guarantee, it’s an expectation.” Expectations can still be a prediction.
• Treating charts as “just educational” when the visual implies a forward trajectory.
• Letting senior producers bypass controls for “quick market updates.”

Frequent implementation mistakes (and how to avoid them)

1. Keyword scanning without human review
   Fix: use keyword detection as triage, then require a reviewer to assess implied messages.

2. Banning numbers but allowing implied promises
   Fix: prohibit both explicit and implied forecasts; train on “reads like a promise” examples. (FINRA Rule 2210)

3. Approving a deck, then letting reps paraphrase it
   Fix: approve talk tracks and snippets; supervise seminar delivery where feasible; require use of approved scripts for performance-adjacent topics.

4. Failing to control correspondence templates
   Fix: treat templates as retail communications controls; review and lock versions; monitor rep modifications.

5. No substantiation file for “results” claims
   Fix: require a support attachment for any claim about investment results, even if it’s qualitative (“outperformed,” “strong returns”), and document why it is not exaggerated/unwarranted. (FINRA Rule 2210)

Enforcement context and risk implications

FINRA frames the restriction to prevent “unrealistic expectations about investment returns” in retail communications and correspondence. (FINRA Rule 2210) Your practical risk is not limited to a single offending sentence. A pattern of projected-results language can indicate weak supervision of communications, weak rep oversight, and poor governance over marketing and sales materials, all of which can expand the scope of an exam.

Practical execution plan (30/60/90)

First a defined days (stabilize and stop the bleed)

• Inventory retail communication channels and owners (web, email marketing, social, seminars, rep templates).
• Issue a drafting standard: no projections/predictions, no implied recurrence, no exaggerated results claims. (FINRA Rule 2210)
• Add an intake question: “Does this mention performance or investment results?” Route “yes” to heightened review.
• Pull samples from recent content and rep correspondence; document findings and immediate remediations.

Next a defined days (build repeatable controls)

• Update written supervisory procedures to reflect 2210(d)(1)(F) checks and escalation paths. (FINRA Rule 2210)
• Create a red-flag language list and reviewer checklist.
• Build an approved content library (snippets, FAQs, market-volatility language) that avoids predictions.
• Implement tooling/workflow (often Daydream) for version control, approvals, and evidence capture.

By a defined days (prove it works)

• Run a targeted test: re-review a sample of approved items and rep correspondence for “promise-like” language.
• Track rejects, rework, and repeat offenders; retrain specific teams.
• Formalize third-party content governance for retail redistribution.
• Prepare an exam binder view: ability to produce any retail item with its approval history and substantiation file on request. (FINRA Rule 2210)

Frequently Asked Questions

Does this mean we can never discuss performance with retail clients?

You can discuss performance factually, but retail communications and correspondence cannot predict or project future performance or imply past performance will recur. Keep statements descriptive and avoid promise-like language. (FINRA Rule 2210)

Are “target returns” or “expected yield” always prohibited in retail materials?

In retail communications and correspondence, targets and expectations can function as projections or predictions and create unrealistic expectations. Treat them as prohibited unless you have a vetted, documented exception approach reviewed through compliance. (FINRA Rule 2210)

What about a chart showing historical performance that visually trends upward?

Historical charts can become problematic if the surrounding narrative or design implies the trend will continue. Review the full presentation, including captions and commentary, for implied recurrence. (FINRA Rule 2210)

Can reps send “market outlook” emails to clients?

They can send educational commentary, but they must avoid forecasting a client’s investment results or suggesting a product “will” perform a certain way. Supervisory surveillance should focus on outlook messages because that’s where predictions appear. (FINRA Rule 2210)

How do we handle third-party research that includes forecasts if marketing wants to share it?

Screen it before distribution to retail, and do not redistribute material that predicts or projects performance in a way that would violate your retail communication standards. If you do share third-party content, retain evidence of your review and approval. (FINRA Rule 2210)

What evidence will an examiner expect for a rejected piece that was fixed?

Keep the initial submission, compliance comments, the revised version, and the final approval record. Version history is part of showing real supervision over projected-results language. (FINRA Rule 2210)