FINRA & Broker Protocol Expertise: How to Evaluate a Transition Vendor
FINRA & Broker Protocol Expertise: How to Evaluate a Transition Vendor
A transition vendor that does not deeply understand FINRA registration mechanics, the Broker Protocol, and the patchwork of non-protocol firm policies will create more risk than it removes. The compliance side of an advisor transition is where TROs are won or lost, where Form U5 amendments are triggered, and where state-by-state registration delays kill repapering momentum. This article gives you the 12-question framework for evaluating whether a vendor's compliance expertise matches the regulatory complexity of your transition.
The Three Compliance Lanes Every Vendor Must Cover
Transition compliance is not one discipline; it is three. A vendor weak in any one lane is a vendor who will hand the problem to your in-house compliance team during the highest-pressure moment of the transition.
The three lanes:
- FINRA registration mechanics. Form U4 and U5 handling, state registration sequencing, BrokerCheck monitoring, fingerprint and CRD updates, and dual-registration scenarios for advisors moving between BD-only and dual-registered structures.
- Broker Protocol classification and non-protocol playbook. Knowing the current protocol member list, advising on which client information is takeable, and running the tighter non-protocol resignation choreography when the prior firm is not a member.
- Custodian and account-type compliance. ERISA fiduciary handoffs for qualified plans, state insurance license re-registration for variable annuity books, Reg BI compliance for the post-transition relationship, and Form ADV updates for advisors moving into RIA channels.
When you evaluate a vendor, ask which of these three lanes they own, which they outsource, and which they pretend not to need.
The 12 Questions Your RFP Should Ask
This is the operational scorecard we recommend. Each question has a "good answer" benchmark you can hold the vendor to.
| # | Question | Good answer |
|---|---|---|
| 1 | Who on your team has lived inside an advisor transition resignation day, and which non-protocol firms have you exited from? | A named person who has personally handled 50+ exits including non-protocol firms |
| 2 | When did the Broker Protocol last add or remove a member firm, and how do you track changes? | They can name the most recent additions/removals from the past 60 days |
| 3 | Walk me through your non-protocol resignation playbook for a Merrill, UBS, or Morgan Stanley exit. | A concrete hour-by-hour playbook with specific tombstone language and garden-leave handling |
| 4 | How do you handle Form U5 monitoring for departing advisors? | Automated BrokerCheck polling with alerts within 24 hours of U5 posting |
| 5 | What is your process for state registration sequencing when an advisor is moving across 8+ states? | A state-sequencing matrix with priority states identified by deal economics |
| 6 | How do you support advisors moving from BD-only to dual-registered or RIA-only structures? | Specific Form ADV, ADV 2A, and 2B handling with template language |
| 7 | What is your TRO playbook if the prior firm sends a cease-and-desist letter? | A defined first-72-hours response protocol with sample affidavits |
| 8 | How do you handle ERISA fiduciary handoffs for qualified plan accounts? | Clear separation between rollover advice (Reg BI) and ongoing fiduciary handoff |
| 9 | Show me a compliance audit trail from a real transition (sanitized). | A document log, version-controlled, with timestamps and signer attestations |
| 10 | How do you stay current on FINRA rule changes and state-level adviser-act amendments? | Named regulatory counsel relationship; documented update cadence |
| 11 | What is your client-communication template library for non-protocol exits? | Multiple scripts: tombstone, follow-up call, no-solicitation language |
| 12 | When have you walked away from a deal because the compliance risk was unmanageable? | A specific example, with explanation |
Question 12 is the diagnostic. A vendor who has never walked away has never said no — and a vendor who has never said no will not say no on your transition.
Protocol vs Non-Protocol: What the Vendor Should Know Cold
The Broker Protocol for Recruiting governs what client information a departing advisor may take from a former employer. As of 2026, the protocol member list shifts continuously. Major non-members include Merrill Lynch (since 2017), Morgan Stanley (since 2017), UBS (since 2017), and several regional firms that have withdrawn in the years since.
Protocol exits allow the departing advisor to take name, address, phone, email, and account-title information for clients they personally serviced, with a notification to the prior firm at resignation. The TRO risk is materially lower if protocol procedures are followed exactly.
Non-protocol exits allow none of that pre-departure. The advisor must reconstruct contact data from public sources after resignation, send compliant tombstone announcements, and operate under the prior firm's contractual non-solicitation and garden-leave provisions.
A vendor who treats those two scenarios identically is a vendor whose platform was built for the easy case. Ask them to walk you through both. The contrast in their answers will tell you the depth of their compliance expertise.
The Compliance Audit Trail Your Vendor Must Produce
A defensible transition produces a complete audit trail. The vendor should be able to produce, on demand:
- Time-stamped resignation documents
- Form U4 and U5 filing confirmations
- Every client communication, with template version and approver
- State registration applications and approvals
- Custodian transfer paperwork and submission receipts
- Any cease-and-desist correspondence and the response
- Garden-leave compliance attestations
- Compliance officer sign-offs at each transition gate
If the vendor stores any of this in shared inboxes, free-form spreadsheets, or chat threads, the audit trail will not survive a FINRA enforcement matter or a private arbitration. Demand version-controlled, exportable, timestamped artifacts.
Red Flags in Vendor Demos
Three demo signals predict compliance weakness:
The "we handle compliance" hand-wave. When asked specifics — Form U5 monitoring, state registration sequencing, garden-leave handling — the vendor pivots to features. That is not compliance expertise. That is product marketing.
No named regulatory counsel. Every serious transition platform has either in-house regulatory counsel or a named outside firm they consult on rule changes. If the vendor cannot name them, they do not have them.
A protocol-only playbook. If the vendor's resignation playbook assumes the prior firm is a protocol member, ask what they do for Merrill, Morgan Stanley, or UBS exits. A blank stare here is disqualifying.
What Strong Compliance Expertise Looks Like in Practice
A vendor with deep FINRA and Broker Protocol expertise has three things you can verify: a named compliance lead with a real biography, a documented playbook updated within the last 90 days, and three customer references who used the vendor for non-protocol exits and can describe how the playbook held under pressure. Anything less is a marketing claim, not an operational capability.
The right question to close your evaluation: "Can I speak to your compliance lead, not your sales team, for 30 minutes?" A vendor who declines is not the right vendor for a transition with any compliance complexity.
Frequently Asked Questions
How current does a vendor's Broker Protocol membership list need to be? Within 30 days. Firms join and leave the protocol several times per year, and a stale list creates real risk for the advisor and the receiving firm.
Should the vendor or our compliance team own resignation-day choreography? The vendor should provide the playbook, scripts, and audit-trail tooling. Your compliance team should approve and execute. A vendor who promises to own the entire process is overpromising — final compliance liability sits with the registered entities.
What is the biggest hidden compliance cost in a transition? State registration delays. Multi-state books often hit registration approval delays in 2-4 states out of 12. A vendor with a state-sequencing matrix prevents those delays from blocking the full transition; without one, the advisor sits in limbo on partially registered status.
How important is the vendor's TRO response playbook? Essential for non-protocol exits. Even a well-executed Merrill, UBS, or Morgan Stanley breakaway will sometimes draw a cease-and-desist letter. The first 72 hours of the response determine whether the matter escalates to litigation.
Related: Meeting Assistant · Advisor Transitions Platform · For Transition Consultants · For Breakaway Advisors
