Protocol for Broker Recruiting Explained

Ask most brokers what the Protocol for Broker Recruiting does and the answer tends to run a few degrees broader than reality: "it lets me take my clients when I leave." That is roughly true, and also dangerously incomplete. The Protocol resolves one narrow legal question, whether the departing broker and the receiving firm can be sued by the departing firm for the act of taking a defined slice of client contact data. It says nothing about non-solicitation clauses, nothing about deferred compensation forfeiture, and nothing about the broader legal exposure that exists the moment either firm involved is not a current signatory.

This guide walks through what the Protocol actually authorizes, who is currently bound by it, what happens when a move falls outside it, and how it interacts with restrictive covenants and with the kind of structured team transitions and RIA M&A deals that look superficially similar to an ordinary broker departure but are governed by an entirely different set of legal documents.

History and Purpose of the Protocol

The Protocol for Broker Recruiting was adopted in 2004 by Merrill Lynch, UBS, and Smith Barney to reduce the volume of litigation generated by broker departures. Before the Protocol existed, a broker who left one wirehouse for another routinely faced a temporary restraining order within days, based on claims that the broker had misappropriated trade secrets or breached a duty of loyalty by contacting former clients using information obtained during employment. The firms recognized that this litigation cycle was expensive for everyone and did not meaningfully protect client relationships, since clients generally have the right to choose their own advisor regardless of which firm employs that advisor.

The Protocol's solution was to carve out a narrow category of information, defined client contact data, and agree in advance that member firms would not sue departing brokers or the receiving firm over that specific category, provided the broker followed the Protocol's procedures for the departure. The Protocol has since expanded well beyond its three founding firms to include hundreds of broker-dealers and registered investment advisers, but it remains a private contract among the firms that choose to sign it. No broker, and no client, is a party to the Protocol itself.

It is worth being precise about what kind of document this is. The Protocol is not a FINRA rule, not an SEC regulation, and not a statute. It creates no independent cause of action and confers no rights on brokers directly. Its only legal effect is that signatory firms have contractually agreed among themselves not to bring certain claims against each other and against departing brokers who comply with its terms. That is a meaningful protection, but it is a narrower one than the popular shorthand ("the Protocol lets me take my book") suggests.

Who Is a Member: Verifying Signatory Status Before a Move

Protocol membership is not static. Firms join by signing on, and firms withdraw, sometimes with little public notice, when they conclude the Protocol no longer serves their recruiting or retention interests. Large firms have withdrawn and, in some cases, later rejoined. Because of this movement, a broker planning a transition cannot rely on a list of member firms compiled months earlier, on industry reputation, or on what was true the last time a colleague made a similar move.

The Protocol's protections apply only when both the departing firm and the destination firm are current signatories on the date of the broker's resignation. If either firm has withdrawn, even if it was a member a year ago, the departure falls outside the Protocol entirely and the broker is exposed to the full range of ordinary claims a non-member firm can bring. Confirming current status, close to the actual transition date rather than during early planning, is one of the first steps in any Protocol-based departure analysis.

It is also worth noting that some firms are Protocol members only with respect to certain business lines or have adopted internal policies that layer additional restrictions on top of Protocol compliance. A firm's Protocol membership does not automatically mean every internal policy, compensation plan, or employment agreement at that firm defers to the Protocol's terms. Those documents have to be reviewed independently.

What a Departing Broker Can Take: The Five Permitted Data Fields

The Protocol's permitted data is limited to five fields for clients the broker actually serviced at the departing firm: client name, address, phone number, email address, and account title. That is the full scope of what the Protocol authorizes a departing broker to take without exposure to a claim from the departing firm for that specific act.

The Protocol does not authorize taking account numbers, account balances, positions or holdings, performance history, social security numbers, dates of birth, beneficiary designations, or any other information appearing on a client's account statement. It also does not authorize taking firm proprietary materials unrelated to client contact information, such as internal research, marketing templates, pricing models, or compliance manuals. A broker who copies a client statement, exports a holdings report, or forwards internal firm documents to a personal email account has stepped outside the Protocol's protection regardless of how compliant the rest of the departure was.

The Protocol also specifies procedure, not just substance. A departing broker must resign in writing and, at the time of resignation, provide the departing firm with a copy of the client list the broker is taking, limited to the permitted five fields. The list must be for clients the broker actually serviced, not a broader book the broker had access to but did not personally manage. Taking the list before resigning, or soliciting clients before the resignation is delivered, falls outside the procedure the Protocol requires and can independently support a claim, even where the underlying data would otherwise have been permitted.

What the Protocol Does Not Override

The single most consequential misunderstanding about the Protocol is the assumption that it clears the path for a departure generally. It does not. The Protocol addresses only whether the departing firm can sue over the taking of the permitted client contact data. It says nothing about, and does not override, non-solicitation agreements, non-compete agreements, non-disclosure agreements, deferred compensation forfeiture-for-competition provisions, or garden leave requirements the broker may have separately signed.

A broker can be fully Protocol-compliant, take only the five permitted data fields through the correct resignation procedure, and still be sued successfully for breaching an enforceable non-solicitation clause if that clause independently prohibits contacting former clients for a defined period. Enforceability of non-solicit and non-compete provisions varies significantly by state, and some states place meaningful restrictions on enforcing these covenants against employees, but the existence of that separate body of contract law is not addressed by the Protocol at all. Deferred compensation plans present a related but distinct risk: many wirehouse compensation plans include forfeiture provisions that claw back unvested deferred pay if the advisor joins a competitor, and these provisions have been litigated extensively and enforced in many jurisdictions independent of Protocol status.

Reviewing the employment agreement, the compensation plan documents, and any separate confidentiality or non-solicitation agreement is a distinct exercise from confirming Protocol compliance, and it needs to happen before a resignation letter is drafted, not after a demand letter arrives.

Leaving a Non-Protocol Firm or Joining a Non-Member

When either the departing firm or the destination firm is not a current Protocol signatory, none of the Protocol's protections apply to that move. The departing firm retains the full range of claims that existed before the Protocol was adopted in 2004: trade secret misappropriation, breach of the duty of loyalty, unfair competition, and tortious interference with business relationships, among others. These claims are frequently paired with an emergency motion for a temporary restraining order or preliminary injunction, filed within days of the resignation, seeking to bar the broker from soliciting former clients while the underlying dispute is litigated.

Regulation S-P, the SEC's rule governing the privacy of consumer financial information, adds a separate layer of exposure in non-Protocol moves. The Protocol's carve-out is understood industry-wide as providing a basis for transferring the permitted client contact fields without running afoul of Reg S-P's restrictions on disclosing nonpublic personal information without client consent. Outside the Protocol, that carve-out does not exist, and a firm or broker transferring client information without a valid basis for doing so faces a distinct regulatory exposure on top of the civil claims from the departing firm.

Non-Protocol departures are materially higher risk and require a different playbook: careful documentation of what information the broker genuinely retains independent recollection of, avoidance of any physical or electronic copying of firm records, and, in many cases, advance coordination with counsel on both the timing of the resignation and the firm's likely response before the broker gives notice.

Joining, Withdrawing, and the Practical Reality of a Moving Target

Firms evaluate Protocol membership as a recruiting and retention decision, not a fixed legal posture. A firm with a strong recruiting pipeline may see membership as advantageous because it makes the firm a more attractive destination for brokers at other member firms. A firm concerned about attrition of its own advisors may withdraw to raise the cost of departure for its own brokers, accepting the tradeoff that it becomes a less attractive destination for recruits from elsewhere.

This dynamic means the Protocol landscape shifts over time, sometimes significantly, as firms reassess their competitive position. A broker who has not actively confirmed both firms' current status close to the transition date is operating on outdated information, and outdated information about Protocol status is one of the more common and avoidable causes of departures going wrong.

Protocol vs. RIA M&A and Team Lift-Outs

The Protocol was designed around a specific fact pattern: an individual broker resigning and moving to a new firm, taking only the clients that broker personally serviced. It was not designed for, and does not adequately govern, situations that look similar on the surface but are legally different: a firm acquiring an advisor's entire book of business as a purchased asset, a multi-advisor team negotiating a coordinated lift-out with retention bonuses and transition financing, or a broker-dealer representative moving to form or join a registered investment adviser as part of a broader business transition (a subject covered in our breakaway advisor legal guide).

In each of those scenarios, the parties typically need a negotiated transition agreement that goes well beyond the Protocol's five permitted data fields: representations about the book being transferred, purchase price or retention terms, non-competition and non-solicitation provisions specific to the transaction, and a defined process for client notice and consent. Whether the receiving structure will be a broker-dealer or a registered investment adviser also changes which regulatory regime applies to the advisor's ongoing business, a distinction covered in our RIA versus broker-dealer comparison. Firms and advisors that treat Protocol compliance as sufficient for a transaction of this kind, rather than negotiating the additional terms the deal actually requires, routinely discover the gap only after a dispute has already started.

Alex's take: the Protocol gets treated as a blanket permission slip far more often than it should. The rule itself is narrow by design, five data fields, a specific procedure, and nothing else. The mistake I see most often is a broker or a receiving firm assuming that because the move is Protocol-compliant, the rest of the transition is automatically clean, when in fact the restrictive covenants, the deferred comp exposure, and, in team or book-of-business situations, the entire commercial structure of the deal still need to be negotiated and documented on their own terms. Precision about what the Protocol actually covers, and discipline about staying inside that scope, is what keeps a departure from turning into litigation.

Practical Steps for a Compliant Protocol Departure

A broker planning a Protocol-based move benefits from a disciplined sequence rather than an improvised one. Confirm the current signatory status of both the departing firm and the destination firm close to the actual transition date. Review the employment agreement, compensation plan, and any separate non-solicitation or confidentiality agreement independently of the Protocol analysis, since those documents govern risks the Protocol does not touch. Prepare the client list limited strictly to the five permitted fields, for clients actually serviced by the broker, and hold it until the moment of resignation.

Do not solicit clients, and do not take or copy any other firm records, before delivering the written resignation and the accompanying client list to the branch manager or designated recipient at the departing firm. Coordinate the timing with the destination firm so the transition happens promptly after resignation, minimizing the window in which the departing firm can characterize any delay as evidence of pre-resignation solicitation. Where the move is really a book-of-business acquisition, a team lift-out, or a shift from broker-dealer to RIA registration, treat the Protocol analysis as one input among several, not the entire legal review.

Frequently Asked Questions