Written Supervisory Procedures for Communications

FINRA Rule 3110(a) requires your firm to maintain written supervisory procedures (WSPs) that supervise associated persons’ communications through a system reasonably designed to meet securities laws and FINRA rules. To operationalize it, you need documented supervision ownership, channel coverage, review and escalation workflows, and durable records showing what was reviewed, by whom, when, and what actions were taken. (FINRA Rule 3110)

Key takeaways:

• Your WSPs must cover all communication types and channels your associated persons use for firm business, not just email. (FINRA Rule 3110)
• Examiners look for documented supervisory action, not just policy language: reviews, approvals, escalations, and remediation. (FINRA Rule 3110)
• The standard is “reasonably designed,” so you must align reviews and controls to your products, risks, and communication patterns, then evidence execution. (FINRA Rule 3110)

“Written supervisory procedures for communications” is less about producing a binder and more about proving that supervision happens in a controlled, repeatable way across the channels your business actually uses. FINRA Rule 3110(a) sets the baseline: each member must establish and maintain a supervisory system reasonably designed to achieve compliance with applicable securities laws and regulations and applicable FINRA rules. (FINRA Rule 3110)

For communications oversight, that means you need written procedures that (1) assign supervisory responsibility, (2) define which communications are in-scope, (3) specify what gets reviewed, when, and by whom, (4) spell out escalation and remediation, and (5) require documentation of supervisory actions. In practice, firms get into trouble when their WSPs describe a perfect process that does not match real communication behavior, or when they cannot show evidence that supervision occurred.

This page translates the requirement into an operator-grade checklist you can implement quickly: scoping, control design, workflows, training, and artifacts to retain so you can answer exam questions without rebuilding history.

Regulatory text

Rule excerpt: “Each member shall establish and maintain a system to supervise the activities of each associated person that is reasonably designed to achieve compliance with applicable securities laws and regulations, and with applicable FINRA rules.” (FINRA Rule 3110)

Operator meaning for communications supervision:
Your WSPs must describe a supervisory system that covers how associated persons communicate for business purposes, and your firm must be able to show that the system operates as written. “Reasonably designed” is not a promise of perfection; it is a requirement to build supervision that fits your products, risks, business model, and communication channels, then to maintain and follow it. (FINRA Rule 3110)

Plain-English interpretation (what the requirement is really asking)

You need written procedures that a competent supervisor can follow without improvising:

• Who supervises communications (named roles and backups).
• Which communications are captured and supervised (channels, devices, formats).
• How supervision happens (pre-use approvals, post-use reviews, sampling logic if used, documentation).
• What happens when issues are found (escalation, corrective action, retraining, discipline, communications to compliance, and evidence retention).
• How you prove it (logs, attestations, review queues, exception registers, case notes). (FINRA Rule 3110)

Who it applies to

Entities: FINRA member broker-dealers and their associated persons. (FINRA Rule 3110)

Operational contexts where this becomes urgent:

• Firms with multiple offices, OSJs, or supervisory layers where responsibility is easy to diffuse.
• Hybrid/remote work where business communication migrates to collaboration tools and mobile devices.
• Product lines that drive higher communications risk (complex products, higher-touch sales, retail-facing communications).
• Use of third parties that enable messaging, archiving, marketing content workflows, or call recording (your procedures still need to govern the firm’s supervision responsibilities). (FINRA Rule 3110)

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

Treat this as a build-and-run requirement. WSPs are the blueprint; supervision records are the proof.

1) Inventory and classify communication channels

Create a channel register that answers:

• Channel name (email, recorded lines, collaboration chat, SMS, social media, web meetings, etc.).
• Business use cases (client outreach, internal approvals, trade confirmations, marketing).
• Who uses it (teams/roles).
• Capture method (archived, recorded, retained via third party, or prohibited).
• Supervision method (pre-review, post-review, exception-based review).
• Owner (supervisor role) and compliance oversight contact. (FINRA Rule 3110)

Deliverable: “Communications Channel Inventory” with an explicit “Permitted / Prohibited / Conditional” status for each channel.

2) Assign supervisory responsibility with named roles

Your WSPs should identify:

• Primary supervisor role(s) for communications review.
• Backup coverage for absences.
• What compliance monitors vs. what business supervisors own.
• Escalation points (compliance, legal, HR) for potential violations. (FINRA Rule 3110)

Deliverable: RACI (Responsible, Accountable, Consulted, Informed) for communications supervision.

3) Define review workflows that match the channel

Write procedures at the level of “do this, then that,” not principles. For each permitted channel, specify:

• Trigger for review (pre-approval required; periodic review; event-driven review).
• Review population (all items, sampling rules, exception flags).
• Review criteria (what constitutes an issue in your context; how to document rationale).
• Time expectations (state as “promptly,” “on a scheduled basis,” or per your internal standard; keep it consistent and testable).
• Disposition outcomes (approved, rejected, escalated, corrected, retraining required).
• Documentation standard (minimum notes to record in the review log). (FINRA Rule 3110)

Practical tip: Make the workflow usable in a ticketing or surveillance queue. If the WSP cannot map to system statuses, execution evidence becomes messy.

4) Build an escalation and remediation playbook

Your WSPs should require:

• When to escalate (examples: potential rule breach, customer harm risk, repeat issues, off-channel communications).
• Who receives the escalation and what information must be included.
• Remediation actions (content correction, client follow-up, supervisory coaching, heightened supervision, restriction of channel, disciplinary path).
• How to close out issues with documented resolution. (FINRA Rule 3110)

Deliverable: “Communications Escalation Matrix” (issue type → severity → owner → required actions → closure evidence).

5) Implement controls that enforce channel rules

WSPs alone do not stop off-channel communication. Pair written procedures with operational controls, such as:

• Approved tools list and access controls (who can use what).
• Archiving/retention configurations for permitted channels.
• Restrictions on forwarding to personal email, use of personal devices, or consumer messaging apps for business purposes (state your firm’s rule clearly).
• Supervisory review queues and audit trails. (FINRA Rule 3110)

Where Daydream fits naturally: if you are struggling to keep channel inventory, approvals, WSP mapping, and evidence in one place, Daydream can function as the system of record for controls and testing, so your procedures link to real artifacts and review logs instead of static documents.

6) Train, attest, and enforce

Operationalize your WSPs by requiring:

• Targeted training for associated persons on permitted channels and recordkeeping expectations.
• Supervisor training on review criteria and documentation standards.
• Attestations that staff understand channel rules and will not conduct business on prohibited channels.
• Enforcement mechanics (what happens on first occurrence, repeat occurrences, and refusal to cooperate). (FINRA Rule 3110)

7) Test the supervision system and correct drift

Build a periodic WSP effectiveness check:

• Compare actual channel usage against your channel register (find “shadow” tools).
• Sample completed supervisory reviews for adequate documentation.
• Verify escalations were tracked to closure.
• Update WSPs when tools, products, or organizational structure changes. (FINRA Rule 3110)

Required evidence and artifacts to retain

Examiners typically want both the written design and proof of operation. Keep:

• Current WSPs for communications supervision, with version history and approvals. (FINRA Rule 3110)
• Communications channel inventory and permitted/prohibited determinations. (FINRA Rule 3110)
• Supervisor assignment documentation (org charts, RACI, delegation letters if used). (FINRA Rule 3110)
• Review evidence: queues, review logs, approvals/rejections, annotations, and timestamps. (FINRA Rule 3110)
• Escalation records: cases, investigation notes, remediation actions, closure approvals. (FINRA Rule 3110)
• Training records and attestations (by role, date, content). (FINRA Rule 3110)
• Exception register (repeat issues, heightened supervision decisions, channel bans). (FINRA Rule 3110)

Retention periods are governed by other recordkeeping requirements; don’t invent a timeline inside this requirement page. Keep a cross-reference in the WSPs to your firm’s record retention schedule.

Common exam/audit questions and hangups

Use these to pressure-test readiness:

• “Show me your WSP section that governs texting/chat and how you supervise it.” (FINRA Rule 3110)
• “Which channels are prohibited, and how do you enforce that prohibition?” (FINRA Rule 3110)
• “Who reviews communications for this desk, and how do you evidence the reviews occurred?” (FINRA Rule 3110)
• “Give examples of escalations from communications reviews and how they were resolved.” (FINRA Rule 3110)
• “How do you know associated persons are not using off-channel communications for firm business?” (FINRA Rule 3110)
• “What changed in your WSPs after you adopted [new tool]?” (FINRA Rule 3110)

Hangup to anticipate: supervisors often “review” but do not document rationale. Your process should force a disposition plus a short note for exceptions.

Frequent implementation mistakes (and how to avoid them)

1. WSPs describe coverage that your tools cannot support.
   Fix: Only permit channels you can capture and supervise; align WSP language to actual system capabilities. (FINRA Rule 3110)

2. Ambiguous ownership (“Compliance monitors communications”).
   Fix: Name accountable supervisory roles; define compliance’s oversight/testing role separately. (FINRA Rule 3110)

3. Sampling without a documented method.
   Fix: Write down the sampling logic, selection method, and how exceptions expand the sample or trigger heightened review. (FINRA Rule 3110)

4. No closed-loop remediation.
   Fix: Require documented corrective action and closure approvals for issues found in review. (FINRA Rule 3110)

5. Channel sprawl after tool adoption.
   Fix: Put a pre-adoption gate in place: no new communication tool becomes permitted until it is in the channel inventory with capture + supervision workflows. (FINRA Rule 3110)

Enforcement context and risk implications

FINRA Rule 3110(a) is a supervision baseline. If communications supervision fails, downstream risks follow quickly: unsuitable recommendations communicated informally, unapproved marketing language, inconsistent disclosures, and inability to evidence supervision. The practical risk for a CCO is compounded findings: an examiner rarely treats “weak WSPs” as isolated if they also see gaps in execution evidence. (FINRA Rule 3110)

A practical 30/60/90-day execution plan

Avoid calendar promises. Use staged outcomes you can meet regardless of firm size.

First 30 days (stabilize and scope)

• Stand up the communications channel inventory and mark permitted/prohibited/conditional. (FINRA Rule 3110)
• Assign supervisors and backups for each channel and business line. (FINRA Rule 3110)
• Identify the highest-risk channels (typically mobile and chat) and set interim controls if capture/review is unclear. (FINRA Rule 3110)

Days 31–60 (write procedures that map to workflows)

• Rewrite or refactor WSPs into channel-specific procedures with review steps, documentation requirements, and escalation paths. (FINRA Rule 3110)
• Implement review logs/queues and minimum documentation standards (fields supervisors must complete). (FINRA Rule 3110)
• Publish training and obtain attestations for permitted/prohibited channel rules. (FINRA Rule 3110)

Days 61–90 (evidence operation and tune)

• Run supervisory reviews under the new workflows and test for completeness of evidence. (FINRA Rule 3110)
• Perform a targeted effectiveness check: find off-channel usage signals, validate escalations closed, confirm supervisor coverage. (FINRA Rule 3110)
• Update WSPs based on findings and lock in ongoing governance for tool adoption and WSP updates. (FINRA Rule 3110)

Frequently Asked Questions

Does FINRA Rule 3110(a) require a separate WSP just for communications?

The rule requires a supervisory system and written procedures sufficient to supervise associated persons’ activities, including communications. Many firms implement communications as a dedicated WSP section or standalone procedure to make ownership and evidence clear. (FINRA Rule 3110)

What counts as “communications” that must be supervised?

Your supervision should cover all communication types and channels used by associated persons for firm business, based on your channel inventory and WSP scope. If a channel is used for business, treat it as in-scope or explicitly prohibit it with enforcement controls. (FINRA Rule 3110)

Can we rely on a third party archiving tool and call it done?

A third party tool can help capture and retain communications, but your firm still must define and execute supervisory reviews, escalations, and documentation. Examiners will ask for evidence of supervision, not just tool screenshots. (FINRA Rule 3110)

How detailed do supervisor review notes need to be?

Notes must be detailed enough to show what was reviewed, what decision was made, and why, especially for exceptions and escalations. If the record cannot support a reasonable reconstruction of the supervisory action, treat it as insufficient. (FINRA Rule 3110)

What if different desks use different channels?

That is normal. Your WSPs should still be consistent in structure while allowing desk-specific channel rules, review frequencies, and escalation paths, all anchored to a single firmwide channel inventory. (FINRA Rule 3110)

How do we keep WSPs from drifting out of date after new tools roll out?

Add a governance gate: no new communication channel becomes permitted until it is added to the inventory, has capture/retention confirmed, has a defined supervisory workflow, and supervisors are trained. Track this in a system of record such as Daydream so you can show approvals and change history. (FINRA Rule 3110)