I Am Leaving My Company—How Do I Keep Them from Suing Me and My Next Employer?
Leaving a job can feel uncertain: you want a clean exit, but you also don’t want a surprise lawsuit showing up in your inbox the minute your LinkedIn updates or worse, the inbox of the CEO of your new employer.
The good news is that most “departure litigation” is avoidable. The thing to remember is that the easiest mistakes are the ones people make when they’re moving fast—downloading files “just in case,” forwarding customer lists to a personal email, or copy/pasting code into a new repo.
Here’s a practical playbook for founders and employees in the emerging companies/VC world. Please note this is not legal advice, as the right answer depends heavily on your state, your role, and your documents with your employer.
What Do Companies Usually Sue Over?
Before we discuss the best steps to take to avoid unwanted litigation, it’s worth looking at why litigation occurs in the first place. Most disputes fall into a few familiar buckets:
With this in mind, here are some simple steps to stay out of the litigative crosshairs.
Step 1: Do a “Paperwork Refresh” Before You Resign
Before you give notice, locate and read (without forwarding around) the documents that will govern your exit:
People often behave “reasonably” but accidentally violate a very specific clause (notice requirements, return-of-property obligations, or a non-solicit that covers employees and contractors) during and/or after employment for a period of time.
Step 2: Don’t Take Stuff With You
If you remember only one thing: do not take company data or property when you leave. Do this instead of “just in case” downloading:
Trade secret law is built around whether information is secret and whether it was misappropriated. The fastest way to create “misappropriation facts” is to possess materials you shouldn’t have. With today’s modern IT systems, the Company will have receipts.
Step 3: If Joining (or Starting) Something Competitive, Build a “Clean Room” Plan
People move to competitors all the time. The trick is leaving cleanly and building cleanly at your next employer.
In addition to the above proactive steps, there’s no lack of other considerations to keep in mind:
Bottom Line
Most companies don’t sue just because someone left. They sue because the exit created evidence of data taking, customer raiding, employee poaching or product cloning.
To dramatically reduce the odds that anyone lawyers up:
If you’re navigating a move and want to sanity-check the risk points (documents, data handling, clean-room process, equity), that’s exactly the kind of “small issue now vs. expensive issue later” matter we can help with.
The good news is that most “departure litigation” is avoidable. The thing to remember is that the easiest mistakes are the ones people make when they’re moving fast—downloading files “just in case,” forwarding customer lists to a personal email, or copy/pasting code into a new repo.
Here’s a practical playbook for founders and employees in the emerging companies/VC world. Please note this is not legal advice, as the right answer depends heavily on your state, your role, and your documents with your employer.
What Do Companies Usually Sue Over?
Before we discuss the best steps to take to avoid unwanted litigation, it’s worth looking at why litigation occurs in the first place. Most disputes fall into a few familiar buckets:
- Trade secrets/confidentiality. If you take (or are accused of taking) non-public information (product plans, pricing, source code, training data, customer lists, “how we do X,” etc.) that’s the fastest path to finding yourself in litigation. Many suits are brought under federal and state trade secret laws.
- Restrictive covenants (non-competes/non-solicits). These are intensely state-specific. Some states enforce reasonable restrictions; others (most famously California) generally void employee non-competes (with narrow exceptions).
As of the time of this writing, at the federal level, the Federal Trade Commission’s attempted noncompete rule is not in effect and not enforceable, and the FTC moved to dismiss its appeal.
- IP/invention ownership. Your offer letter and invention assignment agreement (CIIA, PIIA, etc.) likely makes clear that inventions created “in the scope of employment” belong to the company. Some states provide carve-outs (e.g., California limits assignment of inventions created entirely on an employee’s own time without using company resources, with important exceptions).
- Systems access/data handling. If someone accesses systems they weren’t entitled to access, or scrapes, exports, or deletes data on the way out, companies sometimes add unauthorized computer access claims. The Supreme Court has narrowed one key federal statute (CFAA), but it’s not a free pass for sloppy exits.
With this in mind, here are some simple steps to stay out of the litigative crosshairs.
Step 1: Do a “Paperwork Refresh” Before You Resign
Before you give notice, locate and read (without forwarding around) the documents that will govern your exit:
- Offer letter + confidentiality agreement;
- Invention assignment / IP agreement;
- Any noncompete / non-solicit / non-interference clauses (remember these can be buried in bonus, incentive comp, and equity agreements or plans);
- Equity docs (plan, grant, early exercise, 83(b), repurchase rights, post-termination exercise window);
- Employment handbooks that may contain policies and provisions limiting what you are able to do; and
- Any side letters (especially for founders, execs, key engineers).
People often behave “reasonably” but accidentally violate a very specific clause (notice requirements, return-of-property obligations, or a non-solicit that covers employees and contractors) during and/or after employment for a period of time.
If you remember only one thing: do not take company data or property when you leave. Do this instead of “just in case” downloading:
- Don’t email yourself decks, customer lists, code, templates, pipeline reports, term sheets, board materials, or any materials marked proprietary or confidential.
- Don’t “clone the repo for reference.”
- Don’t export Slack/Notion/Drive folders to a personal account.
- Don’t keep credentials or backdoor access after your last day.
- Don’t wipe devices or accounts in a way that looks like destruction of evidence (work with IT).
Trade secret law is built around whether information is secret and whether it was misappropriated. The fastest way to create “misappropriation facts” is to possess materials you shouldn’t have. With today’s modern IT systems, the Company will have receipts.
People move to competitors all the time. The trick is leaving cleanly and building cleanly at your next employer.
What reduces risk:
- Use your own equipment/accounts (new laptop, new email, new storage).
- No overlapping work: don’t build the new product while still employed; don’t recruit using company time/resources; don’t use company resources to research or plan.
- Document independent development: keep a dated log of what you built and the public sources you used.
- Avoid “look-alike” shortcuts: don’t mirror internal docs, architecture, naming conventions, pricing, or playbooks from memory.
- Be careful with customer outreach: outreach can look like you used confidential info even if you didn’t.
- Don’t poke your prior employer in the eye with blog posts, social media or advertising campaigns that compares your new venture with the products or services of your prior employer.
- And remember, trade secrets can include methods, processes and compilations, not just obvious secrets.
In addition to the above proactive steps, there’s no lack of other considerations to keep in mind:
Don’t Underestimate “People Issues” (Solicitation and Messaging).
A lot of disputes start with how the departure is handled socially.
A lot of disputes start with how the departure is handled socially.
- If you have a non-solicit, treat it seriously. Employee poaching is a fast way to trigger a claim.
- Keep the announcement clean: “grateful for the team” beats “we’re building the real version of this product.”
- Don’t fight in writing. Assume texts/Slack/Teams/email become exhibits to future litigation. If you don’t want communications to show up in a legal filing or court room, don’t put it in writing.
When it’s Sensitive, a Structured Exit Saves Real Money.
- If the relationship is tense or the move is high-risk, a short, lawyer-led process can prevent expensive drama:
- Request a separation agreement or transition memo (return of property, confidentiality confirmation, neutral reference language).
- Agreed messaging for internal/external communications.
- Clarity on equity treatment, vesting, repurchase/exercise timelines.
- If there’s a dispute, a narrowly tailored settlement that buys peace for both parties.
… and Don’t Forget
- State law drives outcomes here.
- “Noncompete enforceability” is not a minor consideration.
- Jurisdiction, role, timing and drafting play a major role in where the chips will fall.
Bottom Line
Most companies don’t sue just because someone left. They sue because the exit created evidence of data taking, customer raiding, employee poaching or product cloning.
To dramatically reduce the odds that anyone lawyers up:
- Understand your documents;
- Leave without company materials; and
- Build your next thing with a clean process and a plan.
If you’re navigating a move and want to sanity-check the risk points (documents, data handling, clean-room process, equity), that’s exactly the kind of “small issue now vs. expensive issue later” matter we can help with.