What Not to Do While You Are Still There
Part seven of the 18-Month File. Everything else in this series is work you can do openly. This is the boundary: the ordinary, well-intentioned things advisors do in the year before a move that turn a clean departure into a contested one. Almost none of them are done in bad faith, which is exactly why they happen.
Filed by Tyler Noe

The short answer: Understanding your own agreement, knowing your own numbers and improving your own practice are ordinary. Taking client data, approaching colleagues, pre-positioning clients or running a search on firm systems are not, and each converts a clean position into a contested one. Almost nobody does these things in bad faith, which is why they keep happening.
This is part seven, the last, of the 18-Month File.
The six pieces before this one describe work you could do with your branch manager watching. That is not incidental; it is the test the series was built on.
This piece is the other side. And the reason it exists is that the advisors who get into trouble are rarely the ones acting cynically. They are usually the careful ones who did something sensible-seeming a few months early.
The bright line: client data
If there is one thing to take from this piece, it is this.
Client information generally belongs to the firm and to the client, not to the advisor who serves them. Where the Protocol for Broker Recruiting applies, it permits a narrow, specified set of contact details to travel at the point of resignation. Not before, and not more than the list allows. The Protocol's actual scope, and the things advisors wrongly believe it covers, are in the Protocol for Broker Recruiting explained.
What that means in practice is that exporting a client list, emailing files to a personal address, saving statements to a personal drive or photographing a screen are all the same act, and it is the most common single cause of an ordinary departure becoming litigation.
It also does not work, because the export is logged.
The evidence trail is longer than you think
Firm systems record a great deal: document downloads, printing volumes, CRM exports, email forwarded to external addresses, access to records outside your normal pattern.
Those logs are commonly pulled after a resignation as routine practice, not as an accusation. Advisors are regularly surprised by the granularity, and by how far back it reaches.
The practical rule is simple. Anything you would not want read back to you in a hearing should not happen on a firm system, a firm laptop or a firm phone. That includes the search itself: using firm email or a firm device to correspond about other firms is an unforced error that costs nothing to avoid.
What firms actually do when an advisor resigns, including how quickly, is in the exit litigated.
Colleagues, which is a separate exposure entirely
Employee non-solicitation provisions are common, generally enforceable, and completely separate from anything concerning clients. The Protocol does nothing about them.
So the conversation with the assistant of eleven years, the one you feel you owe them out of loyalty, is a legal timing question rather than a management one. Some securities attorneys advise saying nothing until after resignation and extending an offer afterwards, precisely so that no conversation can be characterized as recruiting the firm's employees.
Whether that fits your situation depends on your agreement and your state. The full picture, including the associate's own registration timeline, is in what happens to your team when you move firms.
Pre-positioning clients, the well-intentioned one
This is the mistake made by the most conscientious advisors, and it is worth naming precisely because it never feels like a violation.
It sounds like warming a client to change. Mentioning that the industry is shifting. Asking, hypothetically, how they would feel about a different platform. Saying nothing specific, but leaving the impression that something may be coming.
In substance that is solicitation, regardless of phrasing, and it is assessed on substance. It is also usually counterproductive: clients who have been half-warned for months are more unsettled when the move arrives, not less, because they have had time to construct their own explanation for it.
The conversation happens after you have resigned, not before.
What to do if you have already crossed a line
Tell your counsel, early.
Most of these situations are far more manageable when disclosed and addressed in advance than when discovered by the other side after the fact. The version that goes badly is the advisor who knows there is a problem, says nothing, and allows it to be found at the worst possible moment.
The end of the series, and the point of it
Seven pieces, and the through-line is that the advantage in this business goes to whoever prepared themselves rather than to whoever moved fastest.
Everything in parts two through six can be done openly, improves the practice whether or not you ever move, and takes long enough that starting early is the only way to get it. Everything in this last piece is avoidable by knowing where the line sits.
Contract provisions vary by firm, by state and by the year you signed. This series describes what to look for, not what yours says. Review the specifics with your own counsel, and nothing here advises breaching an agreement you are party to.
When you do reach the point of deciding something, going independent as a financial advisor compares the paths and the ultimate transition checklist covers execution.
We work with advisors for years before anything is decided, and a meaningful share of those conversations end with the advisor staying exactly where they are. If you want the long-timeline version of this conversation, request an introduction. Held in strict confidence, and the advisor never pays.
Frequently asked
What is the line between preparing yourself and preparing a move?
Can I take a list of my own clients?
Will my firm know what I accessed?
Can I talk to my long-time assistant about leaving?
What if I have already done some of these things?
Filed
September 15, 2026