Confidentiality & IP Assignment Agreement | Word & PDF

A confidentiality and invention assignment agreement is a binding contract between an employer and a worker that does two jobs in one instrument. The confidentiality half obligates the employee to protect trade secrets and other proprietary information during and after employment. The invention assignment half transfers ownership of inventions, software, designs, and other work product the employee creates within the scope of the job. Most US employers fold both into a single agreement because the two protections reinforce each other: confidential information often becomes the raw material for inventions, and a court reviewing one will usually look at the other.

People sometimes confuse this document with a plain employee NDA, but the two are not interchangeable. An NDA mostly governs the flow of information and stops there. A full invention assignment agreement goes further, addressing who owns intellectual property the moment it is conceived, how prior inventions are carved out, and what the employee must do to perfect the employer's title later. The clean approach for a growing company is to use a US employee non-disclosure agreement when you only need a confidentiality promise, and reserve the CIIAA for any role that generates IP. Engineers, designers, marketers writing copy, and anyone producing original work fall into that second group. Treating the two documents as one mistake is how startups lose ownership of features they paid to build.

Three layers of law shape this agreement, and you have to satisfy all three. At the federal level, the Defend Trade Secrets Act of 2016 (18 U.S.C. § 1833) created a private right of action for trade secret misappropriation, but it also attached a string that surprises many employers. The DTSA requires you to include a whistleblower immunity notice in any contract that governs the use of trade secrets, and skipping it carries a real penalty. Under § 1833(b)(3), an employer who fails to give that notice cannot recover exemptions or attorney fees in a later trade secret suit against that employee. The notice tells workers they cannot be held liable for disclosing a trade secret in confidence to a government official or attorney solely to report a suspected violation of law. You can read the official statutory language and immunity conditions in the Cornell Legal Information Institute text of the Defend Trade Secrets Act whistleblower provision. A compliant template builds this notice in automatically, which is one less thing to forget.

The second layer is invention assignment law, governed mostly by state statute and contract principles. Several states limit how broadly you can claim an employee's inventions. California's Labor Code § 2870 is the model: it voids any assignment of an invention the employee developed entirely on their own time, without company equipment or trade secrets, and unrelated to the employer's business. Washington, Illinois, Minnesota, and others have parallel carve-outs. A well-drafted agreement quotes the applicable statute and includes a schedule for the employee to list prior inventions they want excluded. The third layer is general contract formation: the agreement needs consideration, and timing matters. Presenting it at the offer stage gives clean consideration through the job itself. Handing it to someone six months in can raise questions about what they received in exchange, which is why our at-will employment agreement template pairs naturally with this document at onboarding.

The most common trigger is a new hire who will create or access proprietary work. The moment a developer commits code, a designer files a mockup, or a marketer drafts campaign strategy, ownership questions go live, and you want them answered in writing before the first commit, not after a dispute. Onboarding is the natural moment to sign, alongside the offer letter and other first-day paperwork. A second frequent scenario is bringing on someone who will see customer lists, pricing models, or unreleased product plans. Even if their role does not generate inventions, the confidentiality obligations and clear return-of-property duties protect you when they eventually leave.

Fundraising and acquisitions create their own urgency. Venture investors and acquirers run IP due diligence, and a company that cannot produce signed assignment agreements from every engineer is a company with a hole in its title. Founders often discover during a term sheet that an early contractor never signed anything, and that gap can delay or shrink a deal. A third situation is the transition of a contractor into a full employee, or vice versa, since the IP rules differ and the paperwork should match reality. Our 1099 independent contractor agreement carries its own IP assignment language for that population.

One edge case worth flagging: employees who arrive with prior inventions of their own. A musician who codes on weekends, an engineer with a patent from a previous job, a writer with a published book all need a way to exclude pre-existing work from the assignment. If the agreement has no prior-inventions schedule, you risk either over-claiming work you never paid for or leaving the door open to a later ownership fight. A second edge case is the remote worker who uses personal hardware, where the line between company time and personal time blurs, and where a remote work agreement helps document equipment and boundaries.

• The confidentiality and trade secret clause defines proprietary information broadly enough to cover technical data, business plans, customer information, and source code, then imposes the duty to protect it during and after employment. It pairs the definition with a non-use obligation, so the employee cannot exploit the information even where they have not formally disclosed it.
• The present assignment of inventions uses operative language that transfers ownership the instant an invention is conceived, not at some future signing. Courts treat "I hereby assign" very differently from "I agree to assign," and the present-tense version avoids the trap of an unenforceable promise to assign later. This clause is the heart of the document.
• The prior inventions schedule gives the employee a structured place to list inventions they owned before joining, carving those out of the assignment. A blank or unsigned schedule is read as a representation that the employee had no prior inventions, which protects the employer from a surprise claim down the line.
• The DTSA whistleblower immunity notice reproduces the statutory protection required by 18 U.S.C. § 1833(b), preserving your right to recover exemplary damages and attorney fees in a future trade secret suit. Without this notice, those remedies are off the table.
• The return-of-property and post-termination clause obligates the employee to hand back all documents, devices, and copies of confidential information on the last day, and to certify they have done so. It also addresses the § 2870 statutory carve-out where state law requires it.
• The further assurances clause requires the employee to cooperate after they leave by signing patent applications or other documents needed to perfect the company's title, with a power-of-attorney backstop if they refuse or cannot be reached.

California sets the strictest limits on invention assignment in the country. Labor Code § 2870 voids any attempt to claim inventions an employee developed on their own time, without company resources, and outside the employer's field, and § 2872 requires you to give written notice of that limitation. California also bars most non-compete clauses outright under Business and Professions Code § 16600, so the confidentiality and assignment provisions carry the protective weight that non-competes do elsewhere. A California agreement that omits the § 2870 notice can expose the employer to a finding that the entire assignment was overbroad.

New York has no statutory equivalent to California's carve-out, which gives employers somewhat broader assignment rights, but New York courts still scrutinize confidentiality and restrictive terms for reasonableness. Trade secret claims here draw on both the common law and the federal DTSA, and recent legislative attention to non-competes means employers should keep restrictive covenants narrow and lean on confidentiality language instead. Clear definitions of what counts as proprietary matter more in New York than blanket prohibitions.

Texas enforces invention assignment and confidentiality agreements readily, treating them as ordinary contracts supported by consideration. Texas trade secret protection runs through the Texas Uniform Trade Secrets Act, and the state is generally friendlier to employer restrictive covenants than California, provided they protect a legitimate business interest and stay reasonable in scope. A Texas agreement still benefits from precise definitions, since vague confidentiality language is the most common reason these contracts fail.

Florida follows its own Uniform Trade Secrets Act and enforces reasonable restrictive covenants under § 542.335, which expressly recognizes legitimate business interests including trade secrets and substantial customer relationships. Florida employers often combine the assignment agreement with the non-compete and non-solicitation agreement because the state's statute gives those covenants more reliable footing than in many other jurisdictions. As everywhere, the DTSA notice should appear regardless of state.

You start by entering the company's legal name and the employee's name, then selecting the state where the employee primarily works, since that choice drives the statutory carve-outs and notice language the form inserts. From there, the template asks about the employee's role and whether they will create inventions, which determines how broadly the assignment clause reads. You then reach the prior inventions step, where the employee can list any pre-existing work they want excluded, or confirm there is none. The form fills the DTSA whistleblower notice automatically, so you do not have to track down the statutory wording yourself.

Next you set the effective date, which should match or precede the first day of work to keep the consideration clean. The system adjusts the California § 2870 notice and similar state provisions based on your earlier location choice, and flags whether your state requires extra language. Once you review the assembled document, you download it in Word and PDF, circulate it for signature alongside the rest of the onboarding packet, and store the signed copy. Keeping a complete set of signed agreements is exactly what investors will ask for later, so a tidy file structure pays off.

The single most damaging mistake is using "agree to assign" instead of "hereby assign." That difference sounds like lawyer hairsplitting, but the Federal Circuit has held that a promise to assign in the future does not automatically transfer title, while a present assignment does, and a startup that gets this wrong can find it never actually owned a key patent. The second frequent error is skipping the DTSA whistleblower notice, which quietly strips your ability to recover exemplary damages and attorney fees if you ever sue over a stolen trade secret. Employers also routinely forget the prior-inventions schedule, leaving no record of what the employee brought with them and inviting a later ownership dispute over work that predated the job.

Timing trips up many companies too. Presenting the agreement weeks or months after the start date weakens the consideration argument, especially in states that scrutinize restrictive terms, so the document belongs in the offer-stage packet. Another mistake is treating one template as universal across all fifty states without adjusting for California's § 2870 carve-out or similar statutes, which can render an overbroad assignment partly unenforceable. Finally, employers often draft confidentiality language so vague that a court cannot tell what was actually protected. Define proprietary information concretely, because a definition a judge can apply is worth more than a sweeping clause a judge will throw out. Pairing the agreement with a clear employee handbook covering confidentiality and conduct reinforces the obligations across your policies.