Your engineers, designers, and developers create the code, the designs, and the processes that give your company its edge. The single document that decides who owns that work is the employment agreement. A precise one keeps your intellectual property where it belongs. A vague one can hand a departing employee, or their next employer, the value you paid to build.
Understanding these agreements starts with knowing what they cover, where California businesses commonly make mistakes, and the legal rules that govern their enforceability.
What Employment Agreements Actually Control
People assume patents and trademarks are where IP protection happens. Those registrations protect rights you already own. The employment agreement works alongside copyright and patent law to establish ownership by contract and to fill the gaps those default rules leave open.
A useful way to read the rest of this guide: a strong agreement does three jobs at once. It settles who owns what an employee creates, controls who can see confidential material, and sets the rules for what happens when someone leaves. Get all three right in writing, before the work starts, and you remove the ambiguity that drives most IP disputes.
The Key Clauses Explained
A strong agreement is built from a few specific provisions. Each one closes a different gap, and each one fails in a predictable way when it is missing or poorly written.
IP Assignment and Work Made for Hire
These two clauses settle ownership, and they are not interchangeable.
Work made for hire comes from the Copyright Act of 1976, 17 U.S.C. §101. When an employee creates copyrightable material within the scope of their employment , the employer is considered the author and generally owns the copyright, including work such as software code, marketing copy, and design files. The rule has limits:
- It applies only to work made within the scope of employment, not to projects an employee develops on their own time.
- It does not automatically cover independent contractors, and for contractors it applies only to 9 statutory categories and only with a signed written agreement stating it is a work made for hire under 17 U.S.C. §101(2) .
An IP assignment clause fills the gap. It should contain a present assignment (“hereby assigns”) and transfers ownership of inventions, improvements, and other creations to the company, including patents, which fall entirely outside copyright. Most companies secure these rights through an employee invention assignment agreement.
California limits how far that assignment can reach. Under Labor Code section 2870(a), you cannot require an employee to assign an invention they developed entirely on their own time, without using the employer’s equipment, supplies, facilities, or trade-secret information, unless it relates to your business or anticipated research/research and development, or results from work performed for you . A clause that tries to capture everything anyway is unenforceable as to those personal inventions, and section 2872 requires written notice of this carve-out in the agreement. So a California clause has to claim what you can lawfully claim, not simply “all inventions.”
Example: a developer builds an internal tool on the job. The Copyright Act generally gives you the code, but if the tool includes a patentable invention, only an assignment clause secures the patent rights. A clean assignment also ensures a clear chain of title for later licensing or sale of the asset, which matters when you transfer IP ownership or raise funding.
Confidentiality and Trade Secret Protection
A confidentiality clause for California employees defines what constitutes proprietary information and obligates the employee to keep it confidential during and after the employment .
Strong confidentiality language does three things:
- Names the specific categories of protected information, so no one can later claim they did not know a file was sensitive.
- Builds non-disclosure obligations into the contract itself, covering the employment period and surviving termination .
- Requires return of materials at exit, so data does not leave on a personal laptop or in a private cloud account.
This is the layer tied to your trade secrets, and it only works if you actually treat the information as secret and take reasonable measures to preserve secrecy. A clause that calls everything confidential protects nothing.
Contractors and IP Ownership Pitfalls
Contractors are the most common ownership trap, so it helps to handle them in one place. Because work made for hire does not automatically cover them without a signed writing in one of the nine categories, a contractor can own a deliverable you paid for unless they signed a separate written IP assignment. Misclassifying a worker compounds the problem: treat a contractor like an employee without an assignment clause, and you may not own their output.
Example: you hire a freelance designer to build your logo and brand system. Without a signed assignment the designer, not your company, may hold the copyright, and you may only have an implied non-exclusive license to use it.
The fix is procedural and worth building into your hiring process. Every contractor signs an IP assignment with a defined scope of work before starting, containing both a present assignment and work-made-for-hire language as a backup . A clear scope can also help prevent later claims to derivative IP.
The Risk Scenarios
The same agreement that protects you exposes you when it is silent or sloppy. A few situations cause the most damage.
Employee Departure
The exit is the highest-risk moment. If the agreement has no surviving confidentiality obligation that survives termination, you may have limited contractual recourse once information surfaces with a competitor. When that obligation is missing, you lose your contractual hook to demand the files back, and recovering them later becomes a practical fight rather than a clear breach.
Ambiguous ownership language turns a clean exit into a dispute that gets settled in court rather than in your favor. These are the exact failures that get tested when protecting trade secrets from employee theft becomes a live matter.
AI-Generated Work Ambiguity
Generative AI has outpaced most older templates. As a matter of policy, your agreement should address it directly:
- State who owns the AI-assisted output produced on company time, using company resources, within scope of employment .
- Set expectations for meaningful human involvement and documentation of prompts/human edits, since the U.S. Copyright Office guidance (March 2023, as updated) currently extends protection only to work with sufficient human authorship.
- Restrict unapproved third-party AI tools, which can pull in infringing material or expose confidential inputs via training data ingestion .
Treat these as company policy that the agreement supports, not as a settled legal formula. This area remains subject to evolving guidance and case law, and a clause written now can save you from arguing about it after the work exists.
Remote Work Leakage
Distributed teams widen the surface area for loss. Practical agreement and policy terms should define acceptable use of personal devices (BYOD) and set access controls and logging for the cloud and collaboration tools that hold proprietary material, and require use of company-approved storage, so company data is not scattered across accounts you cannot reach. Building these terms into the hiring process is one of the most direct ways to prevent IP theft before it happens.
The California Legal Landscape
Where you operate changes which tools work. California law is unusually protective of employee mobility, which reshapes how you guard your IP.
Trade Secret Law: DTSA and CUTSA
Two statutes do the heavy lifting for trade secret protection, and both reward employers who put real safeguards in place.
The California Uniform Trade Secrets Act (CUTSA), codified at Civil Code sections 3426-3426.11, and following, is the state framework. It protects information that derives independent economic value from not being generally known, and that is the subject of reasonable efforts to maintain its secrecy. Your confidentiality clauses and access controls are part of the reasonable efforts you demonstrate.
The Defend Trade Secrets Act (DTSA) is the federal counterpart, providing employers a path to federal court for misappropriation claims. The DTSA requires employers to include a whistleblower-immunity noticeunder 18 U.S.C. §1833(b) in any agreement governing trade secrets or confidential information entered into or updated after May 11, 2016. Failure to include the notice does not void trade-secret protection, but it forecloses exemplary damages and attorney’s fees under the DTSA in an action against the employee.
In a misappropriation case under either statute, courts look at concrete evidence: access logs, the timing of a departure relative to file activity, emails, and what the employee took. Well-drafted agreements and documented secrecy practices are what help that evidence add up in your favor.
Why Non-Competes and Non-Solicitation Rarely Help Here
This is where many out-of-state templates go wrong. California voids most employee non-compete clauses under Business and Professions Code section 16600, regardless of choice-of-law. Recent laws, AB 1076 and SB 699, effective Jan. 1, 2024, reinforced that ban, made it unlawful to include or attempt to enforce a void non-compete, created a private right of action, and added notice obligations (notice to current and certain former employees by Feb. 14, 2024 for pre-2024 agreements) .
Non-solicitation clauses sit in a narrower space than employers expect. Customer non-solicits are generally void under section 16600 as interpreted by the California Supreme Court in Edwards v. Arthur Andersen LLP (2008) 44 Cal.4th 937. Employee non-solicits may also be struck down depending on their scope and effect, an issue highlighted by the 2018 AMN Healthcare decision, in which a broad clause was found to restrain recruiters from practicing their profession. That holding turned on the specific fact that the employees were recruiters, so the clause directly restricted their core work. Later federal courts applying California law have extended the reasoning beyond recruiters, but the scope remains fact-intensive. A non-solicitation provision is most defensible when it is genuinely and narrowly tied to protecting actual trade secrets (e.g., barring use of trade-secret customer lists), and even then, the analysis is fact-intensive.
The practical takeaway for California businesses: build your protection on ownership clauses, confidentiality, and trade-secret safeguards. Restraints on where people can work afterward are unlikely to hold.
One related point on attribution. Federal moral rights are narrow, applying mainly to certain visual artworks under the Visual Artists Rights Act (17 U.S.C. §106A) . If your company commissions visual art, a moral-rights waiver can matter, though it is rarely central outside fine art or highly creative commissioned work. For most software, copy, and technical work, it does little.
Implementation Checklist
A strong agreement still fails if it is signed late, written generically, or never updated. Use this sequence:
- Separate the documents at onboarding. An offer letter sets employment terms (at-will status, compensation). A Confidential Information and Inventions Assignment Agreement (CIIAA) governs IP and confidentiality, clearly identifying the assignment of inventions and non-disclosure obligations. Avoid overloading the offer letter with IP terms.
- Sign before day one. Pre-employment execution prevents retroactive ownership disputes over work that starts immediately and gives the terms a firmer footing, ensures adequate consideration.
- Use a defined scope of work for every contractor, signed before work begins, with both work-made-for-hire and assignment language.
- Tailor the definitions to your field. List what actually matters: source code and algorithms, models, training data for software/AI firms, customer lists and pricing models for sales-driven businesses, formulations and processes for product companies.
- Review and re-sign as things change. Update for new laws (e.g., AB 1076/SB 699), AI use, and remote work, and have employees re-sign when a promotion gives them access to more sensitive IP. For existing employees, provide additional consideration when adding new restrictions.
- Add DTSA whistleblower immunity notice to all CIIAAs and maintain access logs, onboarding/offboarding checklists, and training to show reasonable measures.
Frequently Asked Questions
Do I need a separate IP agreement for contractors?
Yes. Work made for hire does not automatically transfer a contractor’s output to you and requires a signed writing in a statutory category, so a contractor can own what you paid for unless they signed a separate written IP assignment. Have every contractor sign one with a defined scope before the work starts.
Does the work-made-for-hire doctrine cover everything an employee creates?
No. It covers copyrightable work made within the scope of jobemployment. It does not reach patents, and it does not cover inventions an employee makes entirely on their own time without using employer resources that are unrelated to your business, which Labor Code §2870(a) protects . You close the remaining gaps with an invention-assignment clause written to respect those limits, using “hereby assigns” language .
Are non-competes enforceable in California?
Generally no. California voids most employee non-compete clauses under Business and Professions Code section 16600, and recent laws make attempting to enforce one unlawful and actionable. Build your protection on ownership, confidentiality, and trade-secret terms instead.
When should employees and contractors sign these agreements?
Before the work begins. Pre-employment signing prevents disputes over work that starts on day one and gives the terms a firmer footing. Re-sign when someone moves into a role with access to more sensitive IP.
Protect Your IP With Counsel Who Understands the Stakes
The strength of your IP often comes down to a few clauses signed before an employee writes a line of code. Heimlich Law, PC is a boutique intellectual property firm in San Jose with an emphasis on patents. The firm counsels startups and businesses and drafts confidentiality agreements as part of a broader trade-secret protection strategy, with extensive experience working with technical teams. To talk through the IP ownership issues that arise in your employment and contractor relationships, contact Heimlich Law for consultation.
