Communication Categories Classification

FINRA Rule 2210(a) requires you to classify every written or electronic communication as correspondence, retail communication, or institutional communication based on who receives it and how broadly it’s distributed. Operationally, you need a repeatable intake-and-tagging process, supervisory rules by category, and evidence that classification drives review, approval, and retention. (FINRA Rule 2210)

Key takeaways:

• Classification is audience-based: retail vs institutional, plus a volume test for correspondence vs retail. (FINRA Rule 2210)
• Your procedures must make classification the trigger for the right review/approval and supervision workflow. (FINRA Rule 2210)
• Examiners expect proof: inventories, decision rules, samples, and supervisory records tied to the category. (FINRA Rule 2210)

“Communication categories classification” is the first control gate for FINRA communications compliance. If you misclassify a communication, every downstream control can fail: the wrong approver signs off, required supervision doesn’t happen, filing decisions become inconsistent, and books-and-records retention can fragment across tools and teams. FINRA Rule 2210(a) solves this by forcing broker-dealers to sort communications into three categories with distinct obligations. (FINRA Rule 2210)

For a CCO or GRC lead, the fastest path is to treat classification as a standardized decision that happens at message creation or distribution, not after the fact. That means you need (1) clear definitions translated into operational decision rules, (2) a way to tag communications by category in the systems your business actually uses, and (3) supervision procedures that key off that tag. (FINRA Rule 2210)

This page gives requirement-level guidance you can put into a WSP update, a supervisory workflow design, and an exam-ready evidence package without overengineering.

Regulatory text

FINRA Rule 2210(a) states that communications are classified into three categories: correspondence, retail communications, and institutional communications, each with distinct regulatory requirements. (FINRA Rule 2210)

What you must do as an operator: implement policies, procedures, and supervision that (a) classify communications into the right category based on intended audience and distribution, and (b) apply the appropriate controls for that category. Classification is not a label for reporting; it is the routing mechanism for approvals and oversight. (FINRA Rule 2210)

Plain-English interpretation

You need to decide, for every written or electronic message your firm sends that is in-scope for communications rules, whether it is:

• Correspondence: distributed to 25 or fewer retail investors within 30 days. (FINRA Rule 2210)
• Retail communication: distributed to more than 25 retail investors within 30 days. (FINRA Rule 2210)
• Institutional communication: distributed only to institutional investors. (FINRA Rule 2210)

That classification then determines the supervisory treatment you apply (for example, what gets pre-approved versus what can be reviewed after distribution, and what gets escalated). FINRA Rule 2210(a) is the classification foundation; your WSPs and workflows should make it hard to “get cute” with categories. (FINRA Rule 2210)

Who it applies to

Entity scope

• Broker-dealers and their supervised persons responsible for communications with the public. (FINRA Rule 2210)
• Registered representatives and other staff who draft, approve, or distribute communications (sales, marketing, research distribution, client service). (FINRA Rule 2210)

Operational context (where this shows up in real life)

Classification must cover communications across the channels your firm uses, including:

• Email and message campaigns
• One-to-one prospecting emails and follow-ups
• Market commentary blasts, newsletters, seminar invites
• Website content and downloadable PDFs (where distribution targets retail or institutional audiences)
• Slide decks and scripts used in meetings when distributed electronically

Your exact channel list will vary; the control requirement is that you have a consistent way to categorize what the firm distributes. (FINRA Rule 2210)

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

Step 1: Define your firm’s classification decision rules (in WSP-ready language)

Create a one-page decision matrix that business users can follow and supervisors can test. Minimum content:

• Audience type test: retail vs institutional recipient population. (FINRA Rule 2210)
• Distribution count test: whether distribution to retail investors crosses the threshold that separates correspondence from retail communication. (FINRA Rule 2210)
• “Only institutional” rule: institutional communication is limited to institutional recipients; mixed lists are not institutional. (FINRA Rule 2210)

Practical control: require the sender to declare the intended audience and distribution method before sending, then treat that declaration as a supervisory attestation.

Step 2: Build an intake-and-tagging mechanism at the point of creation

Classification fails most often because it is “somebody’s job later.” Make it a required field or step in the workflow:

• In your marketing/content request process: include “Communication category (correspondence / retail / institutional)” as a required intake field. (FINRA Rule 2210)
• In email distribution tools: require list type selection (retail / institutional) and store the selection with the campaign record. (FINRA Rule 2210)
• In CRM/email for one-to-one: require a category tag for outbound templates and mass sends, and enforce supervisory review rules based on that tag. (FINRA Rule 2210)

If your tooling can’t enforce tagging, implement a compensating control: periodic sampling of outbound communications with documented classification and reviewer sign-off.

Step 3: Map each category to the right supervisory workflow

FINRA Rule 2210(a) tells you to classify; the operational requirement is to ensure the category drives the handling. Create a simple control map that your teams can execute:

Category	Operational trigger	Required handling (high-level)
Correspondence	Retail recipients, limited distribution threshold. (FINRA Rule 2210)	Supervision and review model defined in WSPs; sampling and escalation rules tied to risk.
Retail communication	Retail recipients, broader distribution threshold. (FINRA Rule 2210)	Tighter controls and consistent approvals; standard templates and pre-use review expectations in WSPs.
Institutional communication	Only institutional recipients. (FINRA Rule 2210)	Controls aligned to institutional-only distribution; prevent bleed-over into retail lists.

Keep this table free of wishful thinking. Only include steps you can evidence during an exam (tickets, approvals, logs).

Step 4: Control list hygiene and audience eligibility

Institutional classification depends on recipient status. Put ownership on a function (often Compliance with Operations support) to maintain:

• Institutional recipient criteria and validation approach for institutional-only lists. (FINRA Rule 2210)
• Procedures that prevent mixing retail and institutional recipients in the same distribution. (FINRA Rule 2210)

Practical control: lock institutional distribution lists so only list owners can add recipients, and require a documented basis for classifying each list as institutional-only.

Step 5: Train and test, then tune

Train the people who press “send” and the supervisors who approve:

• Quick training on the three categories, the distribution threshold, and the “institutional-only” restriction. (FINRA Rule 2210)
• A short quiz or acknowledgement tied to the WSP section that defines your decision rules.

Then run a calibration review: pull a sample of communications across channels, classify them independently in Compliance, compare results, and fix decision rules where your teams disagree.

Step 6: Operationalize monitoring and escalation

Put ongoing monitoring in place that specifically targets misclassification risk:

• Exceptions where an institutional tag is used but recipients include retail.
• High-volume sends tagged as correspondence.
• New templates or new distribution channels without a defined category.

If you use Daydream, treat it as the workflow system of record for communications intake, category tagging, approvals, and evidence packaging. The goal is a clean line from “category selected” to “supervisory action taken” with exportable artifacts for exams.

Required evidence and artifacts to retain

Examiners typically ask you to show that your written procedures match what actually happens. Build an evidence binder that includes:

1. WSP section on communication categories classification with definitions and your decision matrix. (FINRA Rule 2210)
2. Communication inventory (by channel/tool) showing where classification occurs and who owns the control.
3. System screenshots or configuration exports showing required category fields, routing rules, and access controls for institutional lists.
4. Sample sets of communications from each category with:
   • the classification tag,
   • the distribution list or recipient type,
   • approval/review records tied to the category.
5. Training materials and completion records for relevant roles.
6. Testing and QA results (for example, periodic sampling outcomes, issues found, remediation tickets).

Common exam/audit questions and hangups

Expect questions that test whether classification is real or cosmetic:

• “Show me how you determine whether a message is correspondence vs retail communication based on distribution volume.” (FINRA Rule 2210)
• “How do you ensure institutional communications only go to institutional investors?” (FINRA Rule 2210)
• “Where in the workflow does classification occur, and can a rep bypass it?”
• “Give examples of communications misclassified in the last review period and what you changed.”

Hangups that slow teams down:

• No single inventory of communication channels.
• Institutional lists maintained informally by the business.
• Classification performed after sending, with no reliable audit trail.

Frequent implementation mistakes (and how to avoid them)

1. Mistake: Treating “institutional” as a content style rather than a recipient restriction.
   Fix: institutional classification depends on distribution to institutional investors only. Lock down list management and document the basis for institutional-only status. (FINRA Rule 2210)

2. Mistake: Counting recipients inconsistently across tools.
   Fix: define how you count recipients for distribution-based classification inside your procedures, and align the tooling to capture that count where possible. (FINRA Rule 2210)

3. Mistake: One-off emails escape classification controls.
   Fix: require template tagging and implement supervisory sampling for correspondence; document how you select samples and how exceptions are remediated. (FINRA Rule 2210)

4. Mistake: WSPs define categories, but workflow doesn’t enforce them.
   Fix: add required fields, routing rules, and “stop-ship” controls for unclassified or mismatched distributions.

Risk implications (why regulators care)

Misclassification is a root cause problem: it can result in the wrong review cadence and inconsistent supervision across channels. Retail communications generally carry higher investor-protection sensitivity because they reach retail recipients at scale. Institutional-only communications assume a narrower audience and different expectations about the recipient’s sophistication, but that assumption collapses if your distribution control is weak. FINRA Rule 2210(a) forces firms to make that decision explicit and auditable. (FINRA Rule 2210)

Practical 30/60/90-day execution plan

Because this requirement is operational, focus on fast control establishment and evidence quality.

First 30 days: Stabilize and document

• Build a channel inventory of where communications are created and distributed.
• Publish a one-page classification decision matrix and update WSP language to match FINRA Rule 2210(a). (FINRA Rule 2210)
• Stand up an interim manual tagging and approval intake (ticket-based if needed) so classification is captured before send.

Days 31–60: Enforce in workflow

• Implement required classification fields in your intake and distribution processes.
• Lock institutional distribution lists and assign list owners.
• Train key populations (marketing, sales, client service, supervisors) and collect attestations.

Days 61–90: Prove it works and close gaps

• Run a quality review across a representative sample from each channel; document misclassifications and remediation actions.
• Add monitoring for institutional-list exceptions and high-volume retail sends.
• Package your exam-ready evidence set: WSPs, workflow records, samples, training, and testing results.

Frequently Asked Questions

If a communication goes to both retail and institutional recipients, can it be “institutional”?

No. Institutional communication is distributed only to institutional investors. Mixed distribution should be treated as retail-facing for classification and supervision purposes. (FINRA Rule 2210)

How do we handle a rep sending the same email to multiple retail clients over time?

Track distribution volume over the applicable period so you can determine whether it stays within correspondence or becomes retail communication based on the retail recipient count threshold. Your WSPs should define how you aggregate sends across tools. (FINRA Rule 2210)

Do we need a separate policy, or can this live inside WSPs?

WSPs are the right home for the decision rules, workflow triggers, and supervisory steps, as long as they are specific and testable against actual records. The key is that the category drives the process. (FINRA Rule 2210)

What evidence best proves we classify communications consistently?

A tagged communication inventory plus samples showing the classification field, recipient type/list, and the matching approval/review record tied to that category. Screenshots or exports from systems help because they show enforcement, not just intent.

Our tools can’t force a category tag before sending. What’s an acceptable workaround?

Use a compensating control: documented procedures requiring pre-send submission through a central intake for certain channels, plus periodic sampling with reviewer sign-off and tracked remediation for any misclassifications.

Where does Daydream fit if we already have email, CRM, and archiving tools?

Daydream can sit above those systems as the workflow and evidence layer: it captures the classification decision, routes the item for the right supervisory action, and packages artifacts for exams without relying on manual screenshot chasing.