Your compliance calendar is current, but your CRM provider has changed its data terms, a client complaint is still unresolved, and a supervisor can't locate the approval record for a marketing email. You have policies for each issue. What you don't have is a clear answer to which issue creates the greatest exposure and who needs to act.
A regulatory risk assessment should give you that answer. For an advisory practice or broker-dealer, it connects business activities, applicable obligations, control evidence, and management decisions. The useful version isn't a questionnaire filed away before an examination. It's a working record of what could go wrong, how you know your safeguards work, and what you'll do when they don't.
Map the Laws and Regulators That Apply to You
Regulators and rule sets by firm type
| Firm or professional | Primary regulator | Core rule sets to map | Typical exposure |
|---|---|---|---|
| Registered investment adviser | SEC | Investment Advisers Act of 1940, applicable SEC adviser rules | Fiduciary duty and disclosure failures |
| State-registered investment adviser | State securities regulator | State adviser rules, adopted NASAA model rules, applicable privacy rules, including Regulation S-P where applicable | Examination findings and registration issues |
| Broker-dealer | SEC | Securities Exchange Act of 1934, applicable financial responsibility and recordkeeping rules | Net capital shortfalls and conduct violations |
| FINRA member firm | SEC and FINRA | FINRA rules, supervision requirements, Form U4 and Form U5 filings | Sanctions, arbitration and U5 disputes |
| Dually registered advisor | SEC and FINRA | Adviser and broker-dealer rules together | Overlapping duties and conflicts of interest |
| CFP certificant | CFP Board | Code of Ethics and Standards of Conduct | Disciplinary sanctions |
Start with the question that determines the scope of every assessment: which laws and regulators reach this practice? The table is a starting map, not a conclusion that every listed rule applies to every firm. State adoption, registration status, activities, and exemptions need their own applicability check.
A solo investment adviser may answer to the SEC or a state securities regulator. A CFP designation adds professional standards rather than replacing securities-law duties. For a dual registrant, identify the capacity in which the advisor acts during each activity, not just the registrations printed on a business card.
Look beyond the operating entity
Holding-company relationships can add another layer. The SEC's Office of Broker-Dealer Finances explains that its Section 17(h) Risk Assessment Program generally reaches broker-dealers within holding-company structures that hold customer funds or have regulatory capital exceeding $20 million, while identifying an exemption for broker-dealers holding customer securities with regulatory capital below $250,000.
Say a broker-dealer belongs to a group with financing and investment affiliates. Its assessment needs to consider affiliate funding dependencies, not merely the brokerage entity's own expenses. Covered firms' records and filings include organizational charts, risk-management policies, financial statements, and material associated-person positions.
For the broader distinction between managing exposure and checking compliance, Vigil Security's guide to risk and compliance is a useful companion. Our discussion of compliance for RIAs provides an adviser-focused starting point.
Finish the mapping exercise with a reconciliation:
- Registrations: List every firm registration and individual credential.
- Correspondence: Review regulator communications from the last three years.
- Coverage: Confirm each authority appears in the map, with an owner responsible for tracking its requirements.
How to Build Your Risk Inventory Step by Step
Build the inventory around activities, not rule titles. An entry labeled supervision is too broad to test. An entry describing who reviews an advisor's proposed recommendation, in which system, before which action gives a reviewer something concrete to examine.
A controlled spreadsheet is enough to start. Use stable risk identifiers, dropdown fields for owners and status, and links to evidence stored in a restricted document repository. Don't attach sensitive client records to a broadly shared workbook.
Build rows that someone else can test
Inventory every business activity. Include account opening, recommendations, custody, trading, marketing, outside business activities, and vendors that touch client data. Walk through an actual client relationship from prospecting to account termination so handoffs don't disappear between departments.
List the applicable obligations. Record the specific rule or standard, its applicability, and the policy section that implements it, rather than paraphrasing everything as compliance required. Keep legal obligations separate from contractual commitments and internal preferences so reviewers understand the consequence of each failure.
Describe the risk event in plain language. Examples include recommending a product outside a client's risk profile or sending required account information late. Identify the action, the failure, and the affected person so the event can be matched to a test.
Assign the owner, process, and system. Name the accountable person rather than writing compliance department. Identify where the activity occurs, such as the CRM, order-management platform, email archive, or vendor portal, because evidence must come from the actual workflow.
Attach relevant history. As a practical starting window, pull the last three years of examination findings, complaints, near misses, and internal escalations. Match each item to its activity and distinguish an allegation from a substantiated failure so the inventory doesn't turn untested complaints into conclusions.
Keep the inventory in draft until peer review. Have someone other than the preparer challenge missing activities, unsupported applicability decisions, and vague ownership. In a small practice, use a qualified outside reviewer when an independent internal review isn't realistic.
ThreatExploit AI's explanation of how to conduct a security risk assessment can help structure the technology portion. Use that lens to identify systems, access, and threats, then connect those findings to the advisory activity and its legal obligation.
Resolve exceptions before sign-off
Missing information should create an open task, not an empty cell that looks complete. If nobody can identify who approves a workflow, record that ownership gap and assign someone to resolve it before final approval.
Practical rule: A reviewer should be able to follow a row from business activity to obligation to evidence without asking its author what it means.
Every row should carry this sign-off line: activity, obligation, risk event, owner, date reviewed. Preserve the reviewer's name and any unresolved qualification alongside it.
Scoring Risks and Ranking What to Fix First
Risk score bands and required responses
The following is a proposed internal scoring policy, not a regulator-prescribed matrix. Its response periods are management choices that must yield to applicable legal deadlines.
| Score (likelihood x impact) | Rating | Required response | Review interval |
|---|---|---|---|
| 1–4 | Low | Document the risk and review it during the annual cycle | 12 months |
| 5–9 | Moderate | Confirm existing controls operate and record the evidence | 3 months |
| 10–15 | High | Add or strengthen controls and assign a deadline within 30 days | 30 days |
| 16–25 | Critical | Escalate to management immediately and consider restricting the activity | Monitor until contained, then set a documented review date |
Use likelihood and impact scales from 1 to 5 for this illustrative framework. Define likelihood from unlikely to recurring or expected, and impact from limited, readily corrected harm to severe client, financial, licensing, or operational consequences. Write those definitions into the methodology so different reviewers aren't scoring different concepts.
Make the judgment visible
Consider a hypothetical recommendation process with no documented suitability review. A reviewer assigns likelihood 4 and impact 4, producing 16, a critical score under this framework. Management should receive the issue now, together with a recommendation on whether recommendations can continue under an interim approval process.
The multiplication isn't the difficult part. The reviewer must explain whether the score reflects missing records, actual unsuitable recommendations, repeated exceptions, or an untested assumption. Those facts could justify different corrective actions even when the total score is identical.
The U.S. Government Accountability Office's guidance distinguishes risk from uncertainty and identifies methods including statistical analysis, expert judgment, probability distributions, risk scoring, schedule-risk analysis, and Monte Carlo simulation, while emphasizing transparent assumptions, methods, data, and uncertainty in analysis.
For most advisory practices, documented expert judgment is more useful than an elaborate simulation built on weak inputs. Record the evidence behind the rating, the observation period, and what you don't know. If missing vendor information could materially change the score, flag that uncertainty instead of assuming the vendor's controls are effective.
Separate exposure from control performance
Maintain an inherent score before controls and a residual score after verified controls. Don't lower the residual score merely because a written procedure exists. Explain which tested safeguard reduces likelihood, impact, or both.
A score is a prioritization tool, not permission to miss a legal deadline.
Work the highest score first, but give a risk with a regulatory deadline priority regardless of its score. Client harm requiring immediate containment also warrants escalation outside the normal queue.
Assessing Vendors and Outsourced Providers
Buying a service doesn't buy relief from supervision. FINRA's 2025 Regulatory Oversight Report announcement introduced third-party risk as a dedicated topic after increased vendor-related cyberattacks and outages, emphasizing supervisory systems and written procedures for outsourced activities, including information technology, cybersecurity, and anti-money-laundering monitoring.
Your firm can delegate performance by contract. Its supervisory obligation remains with the firm. That makes vendor oversight a regulatory risk assessment issue, not merely a procurement checklist.
Vendor tiers and the evidence each requires
Use this as a proposed internal evidence standard, adjusting it to the service's consequences rather than treating the review cycles as legal mandates.
| Tier | Typical services | Evidence to require | Review cycle |
|---|---|---|---|
| Tier 1 critical | Clearing firm, custodian, core trading or back-office platform | Current SOC 1 or SOC 2 report, audit rights, tested business continuity plan | Quarterly review and annual incident drill |
| Tier 2 significant | CRM, compliance surveillance tool, cloud storage holding client data | SOC 2 report or security questionnaire, data-handling terms in the contract | Annual review |
| Tier 3 limited | Newsletter tool, scheduling software without client data | Basic due diligence and standard contract terms | Every two years or at contract renewal |
| AI tool or AI feature | Note-taking or drafting tools that process client information | Written data-use terms, notice of model changes, access logs | Semi-annual review or after any material change |
Tier by consequences, then test the evidence
Ask whether a failure would prevent trading, expose client information, interrupt required supervision, or leave records inaccessible. A cheap cloud service can be critical if it holds the only usable copy of required records. An AI feature is an overlay, not automatically a low-risk category.
Read the scope and exceptions in a SOC report. Confirm that the reviewed service matches the service you buy, and identify controls the report expects your firm to perform. A report's cover page alone doesn't establish that your configuration is safe.
Nutmeg Technologies' guide to understanding vendor risk assessments offers a supporting framework for organizing diligence. Connect the results to enforceable notice, access, termination, and transition provisions through disciplined contract management practices.
Handle refusals and changes explicitly
If a provider won't disclose controls, request a SOC report or detailed questionnaire, document what remains unknown, restrict the data it receives, and decide whether to accept the exposure or replace it. A signed confidentiality agreement isn't a substitute for control evidence.
Reassess after an outage, data incident, subcontractor change, or merger. The business owner should propose the tier, compliance should challenge the reasoning, and the designated principal or authorized senior manager should approve critical-vendor decisions and unresolved exceptions.
Finding Control Gaps and Writing Mitigation Plans
Ask two questions for every material risk: is there a designed control, and is there evidence that it operates? A policy requiring approval answers the design question. A dated approval record tied to the final communication answers the operating question.
Treat an unsupported control as a gap for assessment purposes. That doesn't prove nobody performed the review, but it means the firm can't rely on that review without further evidence.
Work a marketing gap through closure
Consider a hypothetical practice whose undocumented marketing approvals score 16 under the illustrative matrix. The problem isn't that the procedure needs better wording. Staff can release material without a reliably retrievable record showing who approved the final version.
A workable mitigation entry would include:
- Action: Require pre-release approval through a controlled log linking the submitted draft, reviewer comments, final version, and release authorization.
- Owner: Name the marketing supervisor responsible for implementation, with compliance responsible for independent testing.
- Deadline: Enter an actual completion date and identify the interim approval route.
- Target residual score: In this example, aim for 6, subject to successful testing rather than automatic reduction.
- Closure evidence: Retain the configured workflow, staff instructions, approval records, and results from quarterly sampling of 20 pieces as an illustrative testing plan.
Select samples across advisors and communication types rather than choosing only easy examples. If the population is smaller than the proposed sample, review the available population and explain the approach. Failures should lead to an expanded review or revised corrective action, not a passing conclusion based on a mostly complete log.
Test readiness, not just policy language
The SEC's cybersecurity risk-management proposal contemplated written policies, immediate notification after significant incidents, detailed reporting where applicable, public disclosures, and record preservation. That source describes a proposal, not a final obligation; confirm current applicable requirements separately.
Its mechanics still provide useful test questions. Can staff identify an incident, reach the escalation owner, assemble facts for counsel, evaluate notification and disclosure duties, and preserve records? A tabletop exercise can reveal missing contact information or inaccessible logs that a policy review won't catch.
Our explanation of written supervisory procedures helps distinguish an operational instruction from a statement of intent. Write the corrective procedure so a substitute supervisor can perform it without relying on the original author.
Closure standard: A plan without evidence doesn't close the item.
Require a reviewer to approve closure and the revised residual score. Keep the original finding, remediation history, and test results together so the decision remains traceable.
Monitoring Metrics and Reporting to Management
Management needs indicators that prompt decisions, not a dashboard that stays green because nobody defined failure. Choose measures tied to the practice's actual risks, assign owners, and specify the source system used to calculate each result.
The following are illustrative internal thresholds, not universal regulatory deadlines. Legal response and filing requirements must be tracked separately.
Set thresholds that trigger action
- Complaint handling: Track the percentage resolved within 30 days, using a proposed target of 100%. The complaint owner reports monthly and explains matters requiring a longer investigation rather than closing them prematurely.
- Vendor oversight: Target 100% completion of scheduled reviews. The vendor owner reports monthly, with overdue critical-provider reviews escalated immediately.
- Examination remediation: Flag any deficiency open beyond 90 days, or earlier if the regulator's deadline requires it. Compliance reports status monthly.
- Trade exceptions: Track whether exceptions clear within two business days under the proposed internal standard. The trading supervisor reviews the queue daily and reports unresolved exceptions.
- Regulatory filings: Use a target of zero late filings. The filing owner reports approaching deadlines and escalates a threatened miss before it occurs.
- Corrective actions: Flag every overdue critical mitigation. The assigned owner provides a status update and requests any deadline change before the due date.
A threshold breach should identify the action required: investigate, contain, add resources, or seek a management decision. Don't silently change the threshold because the firm keeps missing it.
Give management a decision document
Use a proposed one-page summary for the chief compliance officer or principal, supported by detailed schedules. Show the top ten risks, score changes since the last quarter, overdue mitigations, and decisions needed. If the practice has fewer material risks, don't pad the list.
Distinguish a score reduced after testing from a score reduced through revised judgment. Management should be able to see whether exposure changed or the assessor changed an assumption.
Keep the supporting record organized:
- Assessment file: Inventory, scoring definitions, and approved ratings.
- Third-party file: Vendor tiers, evidence, exceptions, and approvals.
- Remediation file: Mitigation log, test results, and closure decisions.
- Oversight file: Indicator results and minutes documenting review.
Align storage and disposal with applicable record retention requirements, including any preservation hold.
An assessment nobody reviews is documentation, not risk management.
Before management signs off, enter the actual date of the next annual review in the calendar and assessment record. Assign responsibility for initiating it, while allowing material events to trigger an earlier reassessment.
Review Your Assessment With Counsel Before Your Next Exam
Have counsel review material legal judgments and unresolved exposure before your next examination or policy renewal. Confirm that every registration is mapped, every critical risk has a dated mitigation, and vendor tiers reflect the contracts and services currently in use.
The legal review shouldn't become a request to rewrite the spreadsheet in more formal language. Ask focused questions about applicability, reporting obligations, preservation, potential disclosures, and whether an interim restriction is needed.
Know when outside review is warranted
Bring counsel into decisions involving:
- A regulatory inquiry: Confirm scope, response obligations, responsible custodians, and document preservation.
- An on-the-record interview: Prepare around the relevant records and issues without guessing at facts.
- A Form U5 issue: Examine the underlying record, proposed language, and consequences of disputed statements.
- A FINRA investigation: Coordinate responses and identify inconsistencies before producing explanations.
- A vendor incident involving client data: Evaluate contractual notice, regulatory duties, evidence preservation, and client communications together.
For CFP professionals, disciplinary exposure also deserves separate attention. The CFP Board's Sanction Guidelines require consideration of aggravating and mitigating factors, making the surrounding facts and supporting records relevant beyond whether a violation occurred.
At Kons Law, our Securities Regulatory practice guides financial advisors through regulatory inquiries, on-the-record interviews, and compliance issues, and defends advisors in investigations and disciplinary actions. We're a Hartford-based business law firm serving financial professionals nationwide.
Give counsel the working assessment, unresolved exceptions, relevant correspondence, and supporting evidence, not just the polished management summary. The useful outcome is a clear decision about what must change, who will act, and what records will support that decision.
Kons Law helps financial professionals address compliance issues and respond to regulatory inquiries, investigations, and disciplinary actions. Visit Kons Law to learn how we can help you evaluate the legal issues identified in your regulatory risk assessment. If you want to discuss your business law matter, contact Kons Law at (860) 920-5181.
