Feature Compliance Strategy
FINRA Just Let You Project Returns. The Hard Part Is Proving the Audience.
FINRA's Rule 2210 projections exception takes effect Feb. 1, 2027. Build the relevance file, disclosure spec, and source records now.
Table of Contents
Marketing review has had one reflexive answer for fifteen years: 2210 doesn’t allow projections, so cut the projected-return slide. On November 18, 2026, FINRA published Regulatory Notice 26-24, adopting amendments to Rule 2210(d)(1)(F) that create a real exception. It takes effect February 1, 2027.
The exception is narrow and it moves the work. Instead of arguing about whether a number is a projection, you will argue about whether the audience was eligible to see it, and then prove the disclosure and the source. That is a review file problem, and most firms do not have the file.
What the rule now says
The SEC approved the change in Release No. 106675 (Oct. 15, 2026; 91 FR 66371, Oct. 20, 2026), File No. SR-FINRA-2026-004. The operative text sits in Rule 2210 at new paragraph (d)(1)(F)(iv):
| Before Feb. 1, 2027 | From Feb. 1, 2027 |
|---|---|
| No projections, with three carve-outs at (d)(1)(F)(i)–(iii): hypothetical illustrations of math, Rule 2214 analysis tools, research price targets — plus separate projected-figure allowances for security futures and options communications | A fourth carve-out at (d)(1)(F)(iv) for projected performance or a targeted return on a security, portfolio, or strategy |
| No relevance test | Written policies and procedures reasonably designed to ensure the communication is relevant to the intended audience’s likely financial situation and investment objectives |
| No disclosure spec beyond general fair-and-balanced | Disclosure of criteria used, assumptions made, and the risks and limitations of relying on the number |
| Source record required for statistical tables, charts and graphs | Source record required for projections and targeted returns too — 2210(b)(4)(A)(iv) |
The general standards still apply. A projection has to be fair and balanced and rest on a sound basis under (d)(1)(A). The exception buys you the ability to put a forward number in front of the right person; it does not buy you a number that can’t be defended.
The relevance gate is the rule
Read the notice’s discussion of who can receive this and the design constraint lands fast: the exception is “generally prohibited” in communications to a mass audience or general circulation, including general retail investors, because there is no basis for an expectation of relevance.
That kills the obvious commercial play. Product wants the projected-return graphic on the public site and in the January campaign email. Neither qualifies without work.
FINRA does leave room. Firms may group investors into categories using reasonable judgment rather than assessing each recipient, and the notice offers two acceptable bases: policies grounded in past experience with particular investor types, or restricting distribution to people who expressed interest in those securities or already invested in similar ones. It also adds the trap most likely to get quoted back at you in a deficiency letter — mere interest in high returns does not, on its own, establish relevance.
So the eligibility taxonomy has to be about the investor, not the mood of the pitch. Something like:
| Audience | Defensible today? | What the file needs |
|---|---|---|
| Institutional accounts | Yes, with methodology disclosure | Account type confirmation, delivery record, standard disclosure block |
| Existing clients already in the same strategy | Yes, with a stated basis | Position or prior-investment evidence, category assignment memo, delivery list |
| Clients who requested the strategy by name | Yes, narrowly | Dated request, category assignment, disclosure |
| Prospects meeting a stated profile (horizon, liquidity, loss tolerance) | Conditional | Documented profile at the assumptions level, not a risk-tolerance score alone |
| Website, open access | Usually no | Either gate it, or label the graphic as a hypothetical illustration under (d)(1)(F)(i) |
| Broad campaign email to the whole list | Usually no | Segment the send, or keep projections to the gated follow-up |
Two internal arguments worth settling early: a suitability questionnaire that captures risk tolerance but nothing about horizon, liquidity, or existing allocation gives you a weak relevance record. The projection’s assumptions are the thing being matched.
The methodology side has a precedent to borrow from. SEC actions against crowdfunding platforms over revenue projections turned on missing assumption support, and the fix there was a methodology file that a reviewer could test.
Build the policy in four clauses
Firms that treat this as a one-line addition to the WSPs will produce a policy that says “we ensure relevance.” Here is the substance a reviewer can actually apply.
Clause 1 — scope and definition. Define projected performance and targeted return, list the permitted instruments (security, portfolio, allocation, strategy), and exclude anything still covered by another carve-out so reviewers don’t double-classify a hypothetical illustration.
Clause 2 — audience eligibility. State the approved categories, the evidence required to place an investor in each, who may approve a new category, and the default when evidence is missing. Write the web rule explicitly, including whether gating is permitted and what the gate must collect.
Clause 3 — methodology and disclosure. Require a methodology memo before first use: what the model does, the assumption set, the historical window, and whether the output is gross or net of anticipated fees and expenses. FINRA expects that net-of-fee status to be disclosed. Bind the approved disclosure block to the methodology version so a model change forces a disclosure change.
Clause 4 — approval, change, and exception. Name the principal approver, require re-approval on methodology or assumption changes, and define the escalation path when product disagrees. Add a documented exception process, because the first time a wholesaler wants to send a projection to an ineligible prospect, the answer will be “just this once.”
Example clause language: “Projected performance and targeted returns may be used in institutional communications and in retail communications distributed only to investors assigned to Categories 1 through 3 under Schedule B. Category assignment must be recorded in the communication file before distribution. A principal must approve the methodology memo and the disclosure block. Any use outside an approved category requires written exception approval by the CCO, recorded with the date and rationale.”
The disclosure is a spec, not a paragraph
FINRA doesn’t prescribe a methodology or a calculation, and firms don’t have to publish a proprietary model. It does expect the audience to be able to understand the basis and the failure modes. Five elements satisfy that:
- What the model is. A general description of approach — scenario-based projection, historical-return bootstrap, capital-market-assumption blend.
- The assumption set. Return inputs, volatility, horizon, rebalancing, and tax treatment, at the level of specificity that lets an investor check whether the assumptions resemble their situation.
- Net or gross. Whether the figure is net of anticipated fees and expenses. Say it plainly.
- Why actual results diverge. Sequence-of-returns risk, assumption drift, cost changes, and the fact that the horizon is a construct.
- Where the number is weakest. The assumption doing the most work gets named.
Keep the block version-controlled. A disclosure that references a methodology memo by version and date is auditable; a disclosure that lives in a marketing slide template is not.
Substantiation: the file behind the number
New (b)(4)(A)(iv) makes the source of the projection a required record. Combined with the sound-basis standard, the file for any approved communication should carry:
- the methodology memo and its version identifier
- the model, vendor, or data source, with version
- the data as-of date and the run date
- the person who produced the run and the principal who approved it
- the recipient list with category assignments and the send date
- the approved disclosure block, matching the methodology version
Two quick tests catch most weak files. Pull any projection approved in the last quarter and ask a reviewer to reconstruct the number from the file alone. Then change one assumption in the model and see whether anything in the file forces the disclosure to be re-approved. If the second test produces silence, the control is decorative.
The file structure is the same one used for private placement markup diligence: a dated record of what was reviewed, by whom, and on what basis. Communications review has been the last function still running on slide templates and tribal knowledge.
60 days to February 1
The effective date is ten weeks out. A sequence that fits:
- Weeks 1–2: inventory every projection currently circulating outside Rule 2214 tools and research price targets. Most of it dies; the rest tells you which product lines to build for.
- Weeks 3–4: draft the four clauses, publish the methodology memo template and disclosure block template, and designate principal approvers by product line.
- Weeks 5–6: assign the audience categories to the existing book, train reviewers and sales on the eligibility question, and update the web page plan (gate or relabel).
- Weeks 7–8: dry-run five live communications end to end, including one deliberate failure, and fix what breaks.
Log the dry run. It is the only contemporaneous evidence that the procedures were designed and implemented before the date they mattered, which is exactly the distinction between a policy and a control.
So What?
The amendment reads like permission. Operationally it is a relevance-documentation requirement with a disclosure rider, and the firms that treat February 1 as a switch to flip will produce a wave of projections aimed at audiences nobody profiled. Start with the audience taxonomy. It is the clause that decides which of your current communications survive, and it is the clause an examiner will read first.
If you’re building the policy set from scratch, the GRC Starter Kit has the register, KRI, and governance templates to hang a communications review program on.
FAQ
Does an existing Rule 2214 analysis tool still need this? No. Tools and reports that meet Rule 2214 keep their own carve-out at (d)(1)(F)(ii), and a written report from such a tool remains covered. The new exception matters for decks, fact sheets, and one-to-one emails.
What if the client asks for the projection? A request is one of the two bases FINRA names, but it has to be dated and tied to the specific security or strategy. “Client asked for something with yield” is not the same record as “client requested this strategy on this date.”
Do institutional communications need the full disclosure block? The disclosure obligation attaches to the communication, so yes — though the sophistication of the audience lets you drop the hand-holding and keep the substance. Methodology, assumptions, net-of-fee status, and divergence risk stay.
Does a principal have to approve every send? Not necessarily every send, but the methodology and the disclosure block should carry principal approval, and the category assignment should be reviewable. If nobody with supervisory authority signs the methodology, the policy is running on trust.
◆ Need the working template?
Start with the source guide.
These answer-first guides summarize the required fields, evidence, and implementation steps behind the templates practitioners search for.
◆ Related template
GRC Starter Kit
Everything a new compliance hire needs to build their first risk program — 6 products at 47% off.
◆ Immaterial Findings · Weekly
Sharp risk & compliance insights. No fluff.
◆ FAQ
Frequently asked questions.
What does FINRA Regulatory Notice 26-24 actually permit?
Can we put a projected return on the public website now?
Does a client's interest in high returns establish relevance?
What has to be in the disclosure?
What recordkeeping changes?
Author
Rebecca Leung
Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.
◆ Related framework
GRC Starter Kit
Everything a new compliance hire needs to build their first risk program — 6 products at 47% off.
◆ Keep reading
Related posts.
Compliance Strategy
OCC Published Its MRA Manual for the First Time. The Five Cs Are Now Your Issue-File Spec.
OCC PPM 5400-11 and Bulletin 2026-41 set the MRA evidence standard: Five Cs, legal citations, dates, dollar amounts. How to build the issue file that survives validation.
Nov 20, 2026
Compliance Strategy
Sixteen Consent Orders Were Terminated. Don't Archive the Obligation Map.
The CFPB terminated 16 pending orders in FY2026 and waived redress allegations at Navy Federal. Build the closeout file before leadership declares victory.
Nov 19, 2026
Compliance Strategy
Third-Party Risk Board Metrics That Survive a Follow-Up Question
Five third-party risk board reporting metrics with definitions, paired evidence, and gaming vectors — built for a board that asks who signed.
Nov 16, 2026