Broker Protocol eligibility checklist: how to confirm both firms are members before you resign
What is the Broker Protocol and why does dual membership determine everything
The Protocol for Broker Recruiting is a voluntary agreement, originally signed in 2004 by Merrill Lynch, Smith Barney, and UBS, that allows advisors to move between member firms without triggering litigation over client solicitation. The protection is conditional: both the departing firm and the receiving firm must be signatories on the date you resign. If either firm is not a member at that moment, the Protocol does not apply to your move.
According to XY Planning Network's Managing Director of Compliance, Travis Johnson, just under 2,500 registered investment advisors and broker-dealers are currently members of the Protocol. That number changes weekly. According to Integrated Financial Group citing FINRA data, 193 firms left the Protocol in 2023 alone, following 132 departures in 2022. The member list you checked six months ago is not the member list that governs your resignation today.
The Protocol is not administered by FINRA or the SEC. It is a private contractual arrangement. The current administrator is J.S. Held. Before that, Bressler Amery Ross held the role, and before that, SIFMA managed it. The administrator distributes the official member list every Monday, no later than 1 pm CT. That weekly cadence is the only authoritative source.
The stakes are concrete. An advisor who resigns without confirming dual membership faces the departing firm seeking a temporary restraining order before the week is out. A TRO freezes client contact, stops account transfers, and can collapse a transition that took months to plan. Protocol compliance is not a formality. It is the gate that determines whether your resignation is a clean break or litigation.
How to verify Broker Protocol membership for both firms before your resignation date
Verify membership through J.S. Held directly, or by reviewing the current Monday member list distribution. Do not rely on your firm's internal materials, your recruiter's assurances, or any list older than the most recent Monday. Confirm both the departing firm and the receiving firm appear on the same current list. Do this check from a personal device, never from a company computer.
The verification process has two parts.
Confirming your departing firm is still a member. Major wirehouses have a history of exiting without much warning to their advisors. Morgan Stanley exited in October 2017. UBS followed in December 2017. Citigroup and Smith Barney, despite being founding signatories, have also since exited. According to WealthManagement.com, firms are only required to submit a withdrawal letter at least 10 days before the withdrawal takes effect. Ten days. An advisor who planned a resignation for a date three weeks out could find the ground shifted underneath them inside that window. According to Comply.com, notable 2024 withdrawals included Cresset and multiple Focus Financial Partners affiliates.
Confirming your receiving firm is a member at resignation date. If you are joining an existing Protocol member, this is a lookup. If you are launching a new RIA, the timing is more complicated. The new entity must execute a Joinder Agreement with J.S. Held before you resign. The Joinder Agreement is zero-cost and straightforward to submit, but the timing creates a real trap.
The RIA joinder timing trap: when to register your new firm with the Protocol
Register the new RIA entity with the Protocol as late as operationally possible before your resignation date. Registering too early creates a discoverable record that tips off your departing firm. Registering too late means you resign without Protocol coverage and lose the protection entirely.
The Joinder Agreement must be executed and confirmed before you walk into the branch manager's office with your resignation letter. Not the same day, because confirmation is not instantaneous. Not weeks in advance, because the filing is searchable. Work with your transition attorney to set the exact sequence. This is a workflow sequencing problem, and it has a specific answer: the Joinder Agreement should be submitted and confirmed within the final days before your planned resignation date, in a window your attorney specifies based on your firm's monitoring practices.
For hybrid advisors with dual registration, both the RIA entity and the broker-dealer entity must be Protocol members. A new RIA that is Protocol-registered but whose affiliated BD is not does not have full coverage. Confirm both registrations before you move.
What client information you can legally take under the Broker Protocol
Under the Protocol, a departing advisor may take exactly five categories of client information: client name, address, phone number, email address, and account title. Nothing else.
The following are prohibited: account numbers, account statements, Social Security numbers, account balances, and transaction histories. Taking any prohibited data converts a Protocol move into a potential Reg S-P violation, a books-and-records issue under Rule 17a-4, and grounds for the departing firm to argue the move was not Protocol-compliant regardless of membership status.
For a deeper look at exactly where the Protocol's data permissions end and your repapering problem begins, The Broker Protocol: exactly what it covers, what it does not, and what that means for your repapering workflow walks through that gap and what it costs in practice.
The five permitted fields are what seeds the repapering workflow at the new firm. That data set, when structured correctly, becomes the input for new account form pre-population. It is not a complete record. It is a contact list. The account numbers, balances, and transfer details come later, through ACATS, after the client has signed new account documentation at the receiving firm.
At the moment of resignation, the advisor delivers two documents to the local branch manager: the resignation letter and a client list that includes account numbers. The client list with account numbers goes to the departing firm, not to the new firm. The advisor retains only the five permitted fields for use at the new firm.
How Protocol status gates your ACATS timeline and repapering workflow
Protocol status is not just a legal determination. It is the input that determines what data you carry on Day 1, which in turn determines how fast the receiving firm can begin repapering, which in turn determines when ACATS transfers can be initiated. The eligibility check is Step 0 of the entire operational sequence.
Here is how the chain works in practice.
A clean Protocol check means the advisor arrives at the new firm with a structured contact list covering the five permitted fields. That data can be loaded into the new firm's account opening system before the U4 is even filed. Pre-population of new account forms from Protocol-compliant data reduces the NIGO rate on submission. NIGO forms, meaning forms that are Not In Good Order, are the primary cause of ACATS rejection and transfer delay. Every NIGO is a re-submission cycle. Every re-submission cycle extends the dark period, the window after resignation when the advisor cannot service transferred accounts because the paperwork has not cleared.
According to Docupace, transitioning a book of business can take 3 to 6 months and involve thousands of forms. The dark period compounds client attrition risk. Clients who cannot reach their advisor for weeks are clients who reconsider whether to transfer at all.
A failed Protocol check, or a check that was never done, produces the opposite sequence. The advisor resigns into litigation risk. Client contact is constrained by TRO threat. The new firm cannot begin repapering because the legal status of the transfer is contested. ACATS initiation is delayed until the legal situation resolves. The 3 to 6 month window stretches further.
Protocol compliance is machine-readable input. Confirmed dual membership, combined with a structured five-field contact list, is the data state that allows an AI-powered repapering engine to begin work before the U4 drop date. FastTrackr AI's document intelligence platform ingests that contact data, cross-references it against new account form requirements, and flags missing fields before submission, cutting NIGO rates and compressing the dark period. The eligibility checklist is not a legal formality that precedes the transition. It is the first step in the transition workflow.
If you are running a breakaway and want to see how Protocol-confirmed data maps into an automated repapering sequence, FastTrackr AI's advisor transition platform is built specifically for that workflow.
Protocol vs. non-Protocol transition: what actually changes operationally
In a Protocol transition, the advisor carries five fields of client data, delivers a compliant resignation, and the departing firm is contractually limited in what it can do to block client contact. The receiving firm can begin outreach to clients immediately. ACATS can be initiated as soon as new account documents are signed.
In a non-Protocol transition, the advisor's employment agreement governs everything. Non-solicitation clauses, non-compete provisions, and garden leave requirements vary by firm and by state. Garden leave, where the firm keeps the advisor on payroll but prohibits client contact for a defined period, can extend the dark period by 30 to 90 days depending on the contract. Restrictive covenants in non-Protocol moves are enforceable in most jurisdictions, and the departing firm can seek a TRO within hours of resignation.
The operational difference is this: a Protocol move has a defined, predictable compliance path. A non-Protocol move has a contract-specific, attorney-dependent path. The repapering timeline in a non-Protocol move cannot be planned with the same precision because the legal situation may not be resolved before the advisor needs to begin client outreach.
According to InvestmentNews data, after Morgan Stanley withdrew from the Protocol in October 2017, advisor attrition was cut nearly in half: 70 teams left in the 12 months through September 2016, compared to 38 in the same period a year after exit. The Protocol's absence is a deterrent. But it does not stop all moves. It changes the legal and operational calculus for every one of them.
According to Financial Planning, citing FINRA BrokerCheck hiring announcements, approximately 60 registered reps overseeing more than $9 billion left for rival firms in the week immediately following Morgan Stanley's announcement of its Protocol exit. Those advisors moved quickly, before the withdrawal took effect. That is the correct response to a pending withdrawal: if you are planning to leave, the 10-day notice window is your operational deadline.
Broker Protocol eligibility checklist: the pre-resignation gate
Run this checklist before setting a resignation date.
Step 1: Confirm your departing firm is a current Protocol member. Check the most recent J.S. Held Monday distribution. Do this from a personal device. Merrill Lynch, Wells Fargo Advisors, and Raymond James are current members as of the research date for this article. Morgan Stanley, UBS, Citigroup/Smith Barney, Cresset, and multiple Focus Financial Partners affiliates are not. Do not assume. Verify.
Step 2: Confirm your receiving firm is a current Protocol member. If joining an existing firm, look them up on the current member list. If launching a new RIA, execute the Joinder Agreement with J.S. Held before you resign. The Joinder Agreement is zero-cost. The timing is everything. Work with your transition attorney to set the filing date.
Step 3: For hybrid advisors, confirm both the RIA entity and the BD entity are Protocol members. Dual registration requires dual membership. One entity registered without the other does not provide full Protocol coverage.
Step 4: Prepare exactly the five permitted data fields. Name, address, phone, email, account title. Nothing else leaves with you. No account numbers, no balances, no statements, no Social Security numbers, no transaction histories.
Step 5: Prepare your resignation letter and the client list with account numbers. The resignation letter goes to your local branch manager. The client list with account numbers goes to the departing firm at the same time. These two documents, delivered together, are the mechanics of a Protocol-compliant resignation.
Step 6: Do not pre-solicit. Before you resign, you cannot contact clients to tell them you are leaving or to ask them to follow you. Reg BI and FINRA Rule 2273 govern what new firms can say to clients in the period immediately following a transition. Pre-solicitation voids Protocol protections and creates independent regulatory exposure.
Step 7: File U4 at the new firm promptly. The U4 filing at the receiving firm and the U5 termination filing at the departing firm begin the FINRA registration clock. ACATS transfers cannot be initiated until the advisor is registered at the new firm. The faster the U4 is filed, the faster ACATS can begin.
Step 8: Initiate repapering from Protocol-compliant data. The five-field contact list is the seed for new account form pre-population. Load it into your repapering system before Day 1 client outreach. Every form that goes out pre-populated with accurate data is a form less likely to come back as a NIGO. For a detailed operations checklist covering what needs to happen once you have resigned and repapering begins, The First 72 Hours of an Advisor Transition: An Operations Checklist covers the sequencing that keeps NIGO rates low and the timeline on track.
FastTrackr AI's document intelligence platform ingests Protocol-compliant contact data and cross-references it against custodial new account form requirements, flagging gaps before submission. That pre-submission validation step is where NIGO rates drop. It is also where the dark period compresses. The advisor transition workflow is designed to begin at Step 8 of this checklist, the moment Protocol status is confirmed and compliant data is in hand.
Additional compliance rules that govern the transition period
The Protocol does not operate in isolation. Several other rules govern what happens during and immediately after a breakaway.
Reg S-P limits the new firm's use of Protocol-transferred client data to solicitation only. The new firm cannot use client data obtained through the Protocol for any purpose other than contacting those clients to ask them to open accounts. It cannot share that data with third parties or use it for other business purposes.
FINRA Rule 2273 requires that the new firm deliver a specific educational communication to clients of the departing advisor within a defined period after the move. This communication discloses that the advisor has changed firms and explains clients' rights regarding their accounts. Non-compliance with Rule 2273 is an independent regulatory violation, separate from Protocol compliance.
FINRA Rule 3210 governs accounts that registered persons hold at firms other than their employer. Advisors with outside accounts need to manage those disclosures carefully during a transition.
Books-and-records Rule 17a-4 means that the departing firm retains records of everything the advisor did on firm systems. Any data the advisor accessed, downloaded, or transmitted from firm systems before resignation is part of that record. This is why checking the Protocol member list from a work computer is a documented event, and why the instruction to use a personal device is not paranoia.
Reg BI requires that any recommendations made in the context of a transition, including recommendations to transfer accounts, be in the client's best interest. The receiving firm's transition process must be documented with that standard in mind.
If you are working through a team move, the four-year rule on client ownership in partnership agreements at the departing firm may affect which clients are legally yours to solicit, even under Protocol. That is a contract-law question, not a Protocol question, and it requires attorney review before you finalize your client list.
Transition consultants who manage these moves at scale face the same compliance sequencing requirements across every engagement. FastTrackr AI's platform for transition consultants is built to handle that volume without sacrificing the per-move precision that Protocol compliance demands.
FAQ: Broker Protocol eligibility and the breakaway transition
How do I check if my current firm is a member of the Broker Protocol?
Contact J.S. Held, the current Protocol administrator, directly, or obtain the most recent Monday member list distribution. J.S. Held distributes the full member list each Monday, no later than 1 pm CT. Do not rely on internal firm materials or any list that is more than one week old. Use a personal device for this check, not a company computer.
What happens if my new RIA is not yet a member of the Broker Protocol when I resign?
If the receiving firm is not a Protocol member at the moment you resign, the Protocol does not protect your move, even if the departing firm is a member. Your transition becomes a non-Protocol move governed by your employment contract's non-solicitation and non-compete provisions. The departing firm can seek a TRO against you. Execute the Joinder Agreement with J.S. Held before you resign.
Can I join the Broker Protocol before my new RIA is SEC-registered?
The Joinder Agreement process and SEC registration are separate. As a practical matter, you need a legal entity to execute the Joinder Agreement. Work with your transition attorney on the sequencing. The RIA registration timeline and the Joinder Agreement timing must be coordinated carefully, because registering the new entity too early creates a discoverable record before you are ready to resign.
Which major wirehouses have left the Broker Protocol and when?
Morgan Stanley exited in October 2017. UBS exited in December 2017. Citigroup/Smith Barney, despite being a founding signatory in 2004, has also exited. According to Comply.com, 2024 withdrawals included Cresset and multiple Focus Financial Partners affiliates. Merrill Lynch, Wells Fargo Advisors, and Raymond James remain members as of the research date for this article.
What are the five pieces of client information I can legally take under the Broker Protocol?
Client name, client address, phone number, email address, and account title. Those five fields only. Account numbers, account statements, Social Security numbers, account balances, and transaction histories are prohibited. Taking prohibited data voids Protocol protection and creates independent regulatory exposure under Reg S-P and Rule 17a-4.
What is the difference between a Protocol and a non-Protocol transition?
In a Protocol transition, both firms are signatories, the advisor carries five defined data fields, and the departing firm is contractually limited in seeking injunctive relief. In a non-Protocol transition, the advisor's employment agreement governs, non-solicitation and non-compete clauses apply, and the departing firm can seek a TRO within hours of resignation. Garden leave provisions, which keep the advisor on payroll but block client contact for 30 to 90 days, are a non-Protocol risk with no Protocol equivalent.
How quickly can a firm withdraw from the Broker Protocol and what notice is required?
Firms must submit a withdrawal letter at least 10 days before the withdrawal takes effect. That 10-day window is the only mandatory notice. An advisor who plans to resign in three weeks could find their departing firm exits the Protocol before the resignation date. Check membership status as close to your resignation date as operationally possible.
Does the Broker Protocol protect me if I am fired rather than resign?
No. The Protocol protects advisors who resign voluntarily. If you are terminated, the Protocol's protections do not apply. A termination converts your situation to a non-Protocol departure governed by your employment agreement, regardless of whether both firms are Protocol members.
Can I check the Broker Protocol member list from my work computer?
Do not. Under Rule 17a-4, departing firms retain records of advisor activity on firm systems. Accessing the Protocol member list from a company computer or company network creates a documented record of your pre-resignation research. Use a personal device and a personal network.
What is the J.S. Held joinder agreement and how do I submit it?
The Joinder Agreement is the document a firm executes to become a Protocol member. It is submitted to J.S. Held, the current Protocol administrator. Membership is zero-cost. For a new RIA launching as part of a breakaway, the Joinder Agreement must be submitted and confirmed before the advisor resigns. Timing the submission is a workflow sequencing decision that requires attorney coordination.
How does Broker Protocol status affect my ACATS transfer timeline?
Protocol status determines what data the advisor carries on Day 1, which determines how quickly new account forms can be pre-populated and submitted, which determines when ACATS transfers can be initiated. A clean Protocol transition allows repapering to begin before the U4 is filed. NIGO forms delay ACATS initiation. Pre-populated, Protocol-compliant data reduces NIGO rates and compresses the dark period between resignation and first completed account transfer. To see how that plays out in a real transition, the FastTrackr AI advisor transition case study shows the operational outcomes when Protocol-compliant data feeds directly into an automated repapering workflow.
What client data can I share with my new firm before I resign?
None. Pre-solicitation is prohibited under the Protocol and under FINRA Rule 2273. Before you resign, you cannot contact clients to inform them of your move or share any client data with the new firm. The five permitted fields travel with you at the moment of resignation, not before.
Does joining the Broker Protocol commit my new RIA to the same rules when its own advisors leave?
Yes. A firm that executes the Joinder Agreement and becomes a Protocol member is bound by the Protocol's rules in both directions. When advisors leave that firm for another Protocol member, the firm cannot seek injunctive relief for the five permitted data fields. Membership is reciprocal. That is a governance decision for the new RIA's principals to make with legal counsel before executing the Joinder Agreement.
How does a team move affect Broker Protocol client ownership rules?
The Protocol governs data portability, not client ownership. If your team operates under a partnership agreement at the departing firm, that agreement may include a four-year rule or similar provision allocating client ownership between partners. That is a separate contractual question from Protocol compliance. Both need to be resolved before you finalize your client list and resignation date.
What is garden leave and how does it interact with Broker Protocol protections?
Garden leave is a contractual provision in non-Protocol employment agreements that keeps the advisor on payroll while prohibiting client contact for a defined period, typically 30 to 90 days. Garden leave has no Protocol equivalent. Protocol-compliant transitions do not trigger garden leave because the Protocol's terms supersede the non-solicitation provisions that garden leave enforces. If your employment agreement includes garden leave and your move is Protocol-compliant, whether the Protocol supersedes the garden leave clause is a state-law question that requires attorney review.
Related Resources
- The Broker Protocol: exactly what it covers, what it does not, and what that means for your repapering workflow
- The First 72 Hours of an Advisor Transition: An Operations Checklist
- FastTrackr AI advisor transition platform
- Document intelligence for advisor transitions
- Advisor transition case study
- FastTrackr AI for transition consultants
