NON-COMPETE & TRADE SECRETS | 2026-11-12
Employee Invention Assignment and California Labor Code 2870 (2026)
When a side project belongs to you and when your employer can claim it under California invention-assignment law.
By Anatolii Trembach, Esq. (California State Bar No. 349304; LL.M., USC Gould School of Law; admitted to the U.S. Court of International Trade), Trembach Law Firm, APC · Published
Nearly every California offer letter contains an invention-assignment clause that claims ownership of what you create. California Labor Code 2870 limits how far that clause can reach, protecting inventions you build entirely on your own time with your own resources. This guide explains the statutory
Who Owns What You Invent in California
Almost every California offer letter arrives with an invention-assignment agreement tucked inside the onboarding packet. The language is usually broad: everything you conceive, develop, or reduce to practice during employment belongs to the company. Many workers sign without reading it, assuming it is routine. It is not. California limits how far these agreements can reach, and the limit is written into the Labor Code itself. Under Labor Code § 2870, an employer cannot own an invention you build entirely on your own time, with your own resources, that has nothing to do with the employer business. Engineers, software developers, designers, and scientists who moonlight on side projects need to understand exactly where the statutory line falls, because a single overbroad clause can be read down to its lawful scope and no further.
This guide walks through what Labor Code § 2870 protects, the two statutory exceptions that pull an invention back inside the employer ownership, the notice employers must give under § 2872, the ban on coercive assignment clauses in § 2871, and how all of this interacts with California trade-secret law and the states strong public policy against noncompete agreements.
What Labor Code Section 2870 Actually Says
Labor Code § 2870(a) provides that any provision in an employment agreement requiring an employee to assign rights in an invention to the employer does not apply to an invention the employee developed entirely on their own time without using the employer equipment, supplies, facilities, or trade-secret information. That is the core protection. If you built it on your own time and your own dime, it is yours.
The statute then carves out two categories that remain the employer property even if developed on personal time. The assignment can still reach an invention that, at the time of conception or reduction to practice, either relates to the employer business or to the employer actual or demonstrably anticipated research or development, or results from work the employee performed for the employer. Those two exceptions do a great deal of work, and most real disputes turn on whether one of them applies.
The Four-Part Test for a Free Invention
Read together, § 2870 asks four questions. First, did you develop the invention entirely on your own time, not during work hours or while on call for work tasks? Second, did you avoid using the employer equipment, supplies, or facilities, meaning no company laptop, no company lab, no company cloud account? Third, did you avoid using the employer trade-secret information? Fourth, does the invention fall outside both statutory exceptions, meaning it does not relate to the employer business or anticipated research and did not result from your assigned work? Only if all four are satisfied does the invention escape the assignment clause. Fail any one and the clause may validly capture the invention.
The practical lesson is to keep hard separation. A developer who writes a mobile game at night on a personal computer, on a topic unrelated to the employer enterprise software product, has a strong claim to ownership. The same developer who sketches the game architecture on a company whiteboard during lunch, or who borrows a snippet of proprietary code, has handed the employer an argument under the equipment or trade-secret prongs.
Exception One: Relating to the Employer Business
The first exception is the broadest and the most litigated. If, at the moment of conception or reduction to practice, the invention relates to the employer business or to its actual or demonstrably anticipated research or development, the assignment still bites. Courts look at timing. The relationship is measured when the idea is conceived or first reduced to a working form, not years later when the market shifts. A battery chemist who invents a new electrode on a weekend will have a hard time arguing the invention is unrelated to an employer that makes batteries. An employer that wants to invoke anticipated research must show the anticipation was demonstrable, not a vague aspiration, which usually means documented roadmaps, funded programs, or board-level plans.
Exception Two: Resulting From Work Performed
The second exception captures inventions that result from work the employee performed for the employer. This is a causation test. Even on personal time and personal equipment, if the invention grew out of the specific problem you were paid to solve, the employer keeps it. A researcher assigned to fix a sensor defect who solves it in the shower on a Saturday has produced an invention resulting from assigned work. The statute does not reward relabeling company problems as personal hobbies.
Section 2871: Employers Cannot Demand an Unlawful Assignment
Labor Code § 2871 makes the protection real. It bars an employer from requiring, as a condition of employment, that an employee assign rights contrary to § 2870. A clause that purports to grab everything, including free inventions, is not simply enforced as written. California reads it down. The overbroad language cannot be used to coerce an assignment the statute forbids, and courts treat a provision that tries to override § 2870 as unenforceable to that extent. Employees sometimes see a contract that says the assignment does not apply to any invention that qualifies under Labor Code § 2870, which is precisely the savings language the statute pushes employers to include.
Section 2872: The Written Notice Requirement
Labor Code § 2872 requires that when an employment agreement contains an assignment provision, the employer must also give the employee written notice that the agreement does not apply to inventions protected by § 2870. Many California assignment agreements therefore include an express carve-out and a signed acknowledgment. The notice protects employees who might otherwise assume the broad language means what it says, and it protects employers by demonstrating good-faith compliance. If you signed an assignment agreement that contained no such notice, that is a red flag worth raising with counsel before any ownership fight, because the missing notice undercuts the employer position.
Disclosure Obligations Are Not Ownership
Employers frequently require employees to disclose inventions so the company can decide whether a statutory exception applies. A duty to disclose is lawful and is different from a duty to assign. You can be contractually required to tell the company what you built so it can evaluate ownership, while still owning the invention if it clears the § 2870 test. Blanket presumptions that every disclosed invention belongs to the employer run into trouble, because the statute, not the employer unilateral judgment, decides ownership. Keep dated records, lab notebooks, commit histories, and receipts showing when and how you built a side project; contemporaneous evidence of personal time and personal resources is what wins these disputes.
Trade Secrets Are a Separate Lane
Ownership of an invention is distinct from protection of a trade secret. California adopted the Uniform Trade Secrets Act, codified at Civil Code § 3426 through § 3426.11, which protects information that derives independent economic value from not being generally known and is the subject of reasonable efforts to keep it secret. Even if you own a side invention under § 2870, you may not use or disclose the employer trade secrets to build or commercialize it. The equipment-and-trade-secret prong of § 2870 and CUTSA reinforce each other: lift proprietary code or a confidential process into your personal project and you risk both losing the ownership argument and facing a misappropriation claim.
The Noncompete Backdrop: Section 16600
California voids most restraints on a person engaging in a lawful profession, trade, or business under Business and Professions Code § 16600. Employers sometimes try to use invention-assignment and confidentiality clauses as de facto noncompetes, sweeping in future work so broadly that an employee cannot leave and build anything new. Recent legislation strengthened the ban: reforms effective in 2024 reaffirmed that noncompete clauses are void regardless of where they were signed and required employers to notify certain current and former employees that such clauses are unenforceable. An assignment clause drafted to function as a lifetime restraint on inventing is vulnerable both under § 2871 and under the public policy that animates § 16600. California courts have repeatedly refused to let employers smuggle noncompetition into ancillary agreements.
How Assignment Disputes Play Out
When a former employer claims it owns a departing engineer side venture, litigation usually blends several theories: breach of the assignment agreement, trade-secret misappropriation under Civil Code § 3426.1, and sometimes unfair competition under Business and Professions Code § 17200. The employee defends by invoking § 2870 ownership, the § 2871 limit on coercive clauses, and the § 16600 public policy against restraints. Assignment fights of the Cadence and Whitewater variety illustrate how fact-intensive these cases become, turning on when the idea was conceived, whose equipment touched it, and whether any confidential information bled across. The party with clean, dated documentation usually prevails.
Practical Steps for Employees and Employers
Employees should read the assignment clause before signing, request the § 2872 notice if it is missing, list any pre-existing inventions on the prior-inventions schedule so they are excluded, and keep side projects physically and digitally separate from work systems. Employers should include the statutory carve-out and notice, define the business and anticipated-research scope honestly rather than limitlessly, require disclosure without presuming ownership, and avoid dressing up assignment clauses as noncompetes that § 16600 will not tolerate. Both sides benefit from clarity at the outset, because the cost of untangling ownership after a product launches dwarfs the cost of a careful agreement.
Remedies and Related Protections
If an employer tries to enforce an assignment barred by § 2870 or conditions employment on an unlawful assignment contrary to § 2871, a court can declare the clause unenforceable to that extent and refuse to transfer ownership. Where the overreach is paired with other conduct, employees may also look to broader Labor Code protections, including the principle that statutory rights cannot be bargained away by private agreement. For a fuller treatment of why California workplace rights resist contractual waiver, see our discussion of non-waivable Labor Code rights under section 2804, and track developments in the field through our California employment law news hub.
Negotiating the Agreement Before You Sign
The best time to resolve ownership questions is before employment begins, when the worker has the most leverage. A prospective employee can ask that the assignment clause expressly track Labor Code § 2870, that the written notice required by § 2872 be included and acknowledged, and that any ongoing side projects be listed on the prior-inventions schedule as excluded. A worker with an active consulting practice, an open-source portfolio, or a startup concept should negotiate a carve-out that allows continued outside work, subject to confidentiality and to the real limits of § 2870 and § 2871. Employers generally prefer to resolve these issues at the outset rather than litigate them after a product succeeds, so a measured request for clarity is often welcomed. Securing written approval for identified outside activities converts a future dispute into a settled expectation, and it avoids the trap of an overbroad clause that a court would read down under § 2871 but only after costly litigation.
Why Overbroad Clauses Backfire on Employers
Employers sometimes believe that the broadest possible assignment language maximizes protection. In California the opposite is often true. A clause that purports to assign everything, including free inventions, is unenforceable to the extent it violates Labor Code § 2870 and § 2871, and an employer that tries to enforce it against a genuinely free invention can face not only defeat but an argument that it conditioned employment on an unlawful assignment. A narrowly tailored clause that tracks the statute, pairs with the § 2872 notice, and respects the public policy behind Business and Professions Code § 16600 is more durable than a grasping one. The durable approach protects what the employer legitimately owns, inventions that relate to its business or result from the work it paid for, without overreaching into the personal creativity the statute reserves to the worker.
Equipment, Supplies, and Facilities in the Remote-Work Era
The equipment prong of Labor Code § 2870 has grown more complicated as work has moved into homes and onto personal devices. The statute denies the free-invention protection where the employee used the employer equipment, supplies, facilities, or trade-secret information. In a remote-work world, the lines blur: a company-issued laptop used for a weekend side project, a corporate cloud subscription, a software license the employer pays for, or a company virtual private network can all count as employer equipment or facilities. Workers who want to preserve ownership of personal projects should use a genuinely separate personal device and personal accounts, avoid company software licenses, and never route side-project work through employer systems. The convenience of using the laptop already on the desk can quietly forfeit the statutory protection, because the moment employer equipment touches the invention, the first requirement of § 2870 is no longer met.
Burden of Proof and Presumptions
Allocating the burden of proof matters in assignment disputes. Some agreements, consistent with the statutory scheme, require the employee to disclose inventions so the employer can assess whether an exception applies, and they may create a rebuttable presumption that inventions made during employment are subject to assignment unless the employee shows they qualify under Labor Code § 2870. California courts read such presumptions in light of § 2870 and § 2871, which means an employer cannot use a contractual presumption to capture a genuinely free invention. The worker who has kept clean records of personal time and personal resources can rebut the presumption; the worker who has not may struggle. This is why contemporaneous documentation is not a mere formality but the practical core of the entire analysis.
The Prior-Inventions Schedule
A well-drafted assignment agreement includes a schedule, often labeled a list of prior inventions, where the new hire can identify inventions conceived or reduced to practice before employment. Anything listed there is excluded from the assignment. Workers who skip this step hand the employer an argument that an idea they brought with them was actually developed on the job. If you have a side project, patent application, open-source contribution, or unfinished concept when you start a new role, list it. An attached schedule with dates and descriptions is the cleanest proof that the invention predates the employment and therefore falls outside both the assignment and the two exceptions in Labor Code § 2870. Where a worker has nothing to list, writing none on the schedule is better than leaving it blank, which can later be read against them.
Conception Versus Reduction to Practice
Patent and assignment law distinguish two moments: conception, when the complete idea is formed in the inventor mind, and reduction to practice, when the invention is actually built or described in a filing. Labor Code § 2870 measures the business-relationship exception at the time of conception or reduction to practice, so the timing of both matters. A concept conceived before employment but reduced to practice afterward can become contested terrain. This is one reason the prior-inventions schedule and dated records are so valuable: they fix the conception date and separate what the worker brought to the job from what they developed on the employer time. Disputes frequently turn on whether the key inventive step happened on a personal weekend or during a funded company project.
Open-Source and Moonlighting Considerations
Software developers face special pitfalls. Contributing to an open-source project on personal time can trigger an assignment clause if the contribution relates to the employer business, implicating the first exception in § 2870. Many California employers maintain open-source contribution policies precisely to manage this tension, often granting advance written approval that functions as a waiver of any assignment claim. A developer who wants to moonlight should seek written permission that addresses both ownership and any noncompete-style concerns, keeping in mind that an overbroad restriction on outside development can collide with Business and Professions Code § 16600. Clear, written approval protects the worker side venture far better than an unspoken assumption that the company will not care.
Remedies When an Agreement Overreaches
If an assignment clause purports to capture a free invention, the worker is not without recourse. A court can declare the clause unenforceable to the extent it conflicts with Labor Code § 2870 and § 2871, and can refuse to compel assignment of an invention that satisfies the statutory test. Where the employer conditioned employment on an unlawful assignment, that conduct may itself be challenged. And because the Labor Code reflects a strong public policy against contracting away statutory protections, an employer cannot cure an overbroad clause simply by having the worker sign it; the statute, not the signature, controls what can be assigned. The practical remedy in most disputes is a declaration of ownership and, where appropriate, recovery of the economic value the worker lost while the employer wrongly asserted control.
Protect what you invent. If a current or former employer is claiming ownership of your side project, or if you are an employer trying to draft an assignment agreement that holds up under California law, the attorneys at Trembach Law Firm can evaluate your agreement against Labor Code § 2870, § 2871, and § 2872 and chart a path forward. Call (213) 645-2246 for a confidential consultation with a California employment lawyer.
Frequently Asked Questions
Does my employer automatically own an app I build at home?
No. Under Labor Code § 2870, an app you develop entirely on your own time, without company equipment, supplies, facilities, or trade secrets, belongs to you, unless it relates to your employer business or anticipated research or results from the work you were paid to perform. The key is clean separation of time and resources.
What if my assignment agreement has no section 2870 notice?
Labor Code § 2872 requires employers to notify employees in writing that the assignment does not apply to protected inventions. A missing notice does not automatically void the agreement, but it weakens the employer position and is worth raising with counsel before any ownership dispute.
Can my employer make me sign over everything I ever invent?
No. Labor Code § 2871 bars requiring an assignment that is contrary to § 2870 as a condition of employment. California reads overbroad clauses down to their lawful scope, and clauses that function as lifetime restraints also run into Business and Professions Code § 16600.
How is invention ownership different from trade-secret duties?
They are separate. You may own a side invention under § 2870 yet still be barred from using your employer trade secrets, which are protected by Civil Code § 3426 through § 3426.11. Using proprietary information can cost you both the ownership argument and expose you to a misappropriation claim.
What evidence protects my side-project ownership?
Contemporaneous, dated records: personal-device logs, commit histories on personal accounts, receipts for your own equipment, and a prior-inventions schedule listing pre-existing work. This documentation shows the invention was built on your own time and resources, which is exactly what § 2870 requires.
Contact Trembach Law Firm at (818) 514-7680 for a confidential consultation.
Trembach Law Firm | 27001 Agoura Road, Suite 350, Calabasas, CA 91301