Confidential Information Invention Assignment Agreement: What Employers Should Review Before Rolling It Out

When hiring employees or contractors, US startups and small businesses often want to protect their confidential information and secure rights to inventions or intellectual property created during the engagement. A confidential information invention assignment agreement (sometimes called a CIIAA or CIIA agreement) is a common tool for this. But rolling out these agreements without careful review can lead to legal headaches, disputes, or even unenforceable terms.

Many founders and operators make mistakes such as using a generic agreement found online, ignoring state-specific rules, or failing to properly classify workers. Others assume that simply having a signed agreement guarantees protection, only to find out later that their IP or trade secrets are at risk. This guide explains what US employers should check before using a confidential information invention assignment agreement, including federal and state law issues, worker classification, and practical steps for rollout. We also cover common mistakes, practical examples, and a checklist to help you protect your business effectively.

What Is a Confidential Information Invention Assignment Agreement?

A confidential information invention assignment agreement is a contract between a business and a worker (employee or contractor). It typically covers two main areas:

• Confidentiality: The worker agrees not to disclose or misuse the company's confidential information, such as trade secrets, business plans, customer lists, or proprietary data.
• Invention Assignment: The worker agrees that any inventions, works of authorship, or intellectual property created in connection with their work for the company belong to the company, not the individual.

These agreements are commonly used in technology, software, creative, and life sciences businesses, but they are relevant to any company that values its intellectual property or business secrets. They are often required at the start of employment or engagement, and sometimes as a condition of continued work.

However, the enforceability and scope of these agreements can depend on several factors, including federal law, state law, the worker's classification, and the specific wording of the contract. Employers should not assume that a one-size-fits-all approach will work. For example, a SaaS startup in California may need a very different agreement from a marketing agency in Texas, especially regarding invention assignment and confidentiality carve-outs.

Example: A New York fintech company hires a remote developer based in Illinois. The company uses its standard CIIAA template, but fails to include the Illinois-required notice about the right to consult an attorney. Later, the developer challenges the enforceability of the agreement, and the company risks losing rights to key software code.

Key Federal and State Law Issues

There is no single federal law that governs confidential information invention assignment agreements. Instead, several federal and state laws interact to determine what is enforceable and what is not. Here are the main legal issues to consider:

• Trade Secret Protection: The federal Defend Trade Secrets Act (DTSA) allows companies to protect trade secrets, but state law (usually based on the Uniform Trade Secrets Act) also applies. Agreements must be tailored to protect information that actually qualifies as a trade secret. Not all confidential information meets the legal definition of a trade secret.
• Invention Assignment Limits: Many states limit the scope of invention assignment clauses. For example, California Labor Code Section 2870 says employers cannot require employees to assign inventions developed entirely on their own time without using the employer's resources, unless the invention relates to the employer's business or research. Washington, Delaware, and Illinois have similar carve-outs. Failing to include required carve-out language can render the assignment clause unenforceable.
• Non-Compete and Non-Solicit Clauses: Some employers include these in CIIAAs, but many states (including California, Oklahoma, and North Dakota) ban or restrict non-compete clauses. Non-solicitation clauses are also under scrutiny in some states, such as Washington and Massachusetts, which have specific requirements or bans.
• Notice Requirements: Some states require employers to give workers notice of their rights. For example, Illinois requires a notice to employees about their right to consult an attorney before signing certain restrictive covenants. Massachusetts requires written notice of non-compete terms at least 10 business days before the start of employment.
• National Labor Relations Act (NLRA): Confidentiality clauses that restrict employees from discussing wages or working conditions may violate federal labor law. The National Labor Relations Board has found that overbroad confidentiality language can chill protected concerted activity.

Because state law can override or supplement federal law, it is important to check the rules in every state where your workers are located. This is especially critical for remote teams or businesses with workers in multiple states. For example, a Delaware corporation with employees in California, Texas, and New York may need to use different CIIAA language or add state-specific addenda for each jurisdiction.

Example: A biotech startup in Massachusetts includes a non-compete in its CIIAA for a new scientist. Massachusetts law requires non-compete agreements to be supported by "garden leave" pay or other consideration, and to be provided in advance. The company fails to meet these requirements, and the non-compete is unenforceable.

Employee vs. Contractor: Classification and Agreement Risks

One of the most common mistakes is using the same agreement for both employees and independent contractors. The legal risks and enforceability can differ significantly depending on worker classification. The US Department of Labor (DOL) and IRS have specific tests for determining whether a worker is an employee or independent contractor. Misclassification can lead to penalties, back taxes, and loss of IP rights.

• Employees: Employers generally have more control over employees and can require assignment of inventions created within the scope of employment. However, state laws may still limit the scope of assignment and confidentiality clauses. For example, in California, employees cannot be required to assign inventions developed entirely on their own time and without company resources, unless the invention relates to the company's business.
• Independent Contractors: Contractors own the intellectual property they create unless the contract clearly assigns it to the company. However, overly restrictive agreements can be used as evidence that a contractor is misclassified and is actually an employee. For example, requiring a contractor to follow employee-style policies, work set hours, and assign all inventions may be used as evidence of an employment relationship.

Example: A SaaS company hires a freelance designer as a contractor and uses its employee CIIAA template, requiring the designer to assign all inventions, follow set work hours, and comply with company policies. The IRS later audits the company and finds the designer was misclassified as a contractor, resulting in back taxes and penalties. The company also risks losing IP rights if the assignment clause is found unenforceable.

Employers should:

• Use separate templates for employees and contractors.
• Review state law for assignment and confidentiality rules.
• Ensure the agreement language matches the actual working relationship.
• Consult with legal counsel if unsure about classification or agreement terms.

Checklist for Worker Classification:

• Review DOL and IRS guidance on classification.
• Assess degree of control, financial arrangements, and permanency of relationship.
• Document the basis for classification.
• Use appropriate agreement templates and language for each worker type.

What Should Be Included in a CIIAA?

While every agreement should be tailored to the business and the worker's role, most confidential information invention assignment agreements include the following elements:

• Definitions: Clear definitions of what counts as confidential information and what types of inventions or works are covered. For example, "Confidential Information" may include business plans, source code, algorithms, and customer data.
• Obligations of Confidentiality: The worker's duty to keep information secret, both during and after the engagement. Spell out the duration and any exceptions, such as information that becomes public through no fault of the worker.
• Assignment of Inventions: A clause assigning ownership of inventions, works of authorship, discoveries, and improvements made during the engagement, subject to state law limits. Include carve-out language required by states like California, Washington, and Illinois.
• Disclosure Requirements: A requirement that the worker promptly discloses any inventions or works created during the engagement. This helps the company track and secure IP rights.
• Exclusions: Specific carve-outs for inventions developed entirely on the worker's own time without company resources, as required by some state laws. For example, California requires a written notice of these exclusions.
• Return of Materials: An obligation to return or destroy company property and confidential information at the end of the engagement. This includes laptops, files, and access credentials.
• Notice of Rights: Any required state or federal notices about employee rights or limits on assignment. For example, Illinois requires a notice about the right to consult an attorney.
• Remedies: The company's rights if the agreement is breached, such as injunctive relief or damages. Specify the forum for disputes and whether attorneys' fees can be recovered.

Optional clauses may include non-solicitation (subject to state law), non-disparagement, or cooperation with IP filings. Avoid including non-compete clauses unless you have confirmed they are enforceable in the relevant state.

Example: A Texas robotics company includes a broad definition of "inventions" in its CIIAA, but fails to specify that only inventions related to the company's business are covered. An employee later claims ownership of a personal invention developed at home, leading to a dispute. Clear definitions and exclusions could have prevented the issue.

Employers should also keep signed copies of all agreements and maintain a process for updating agreements if the law or business needs change. Having a clear contracts process can help ensure compliance and protect your business interests.

Common Mistakes and How to Avoid Them

Even well-intentioned employers can make mistakes when rolling out confidential information invention assignment agreements. Here are some of the most frequent errors and practical steps to avoid them:

• Using Outdated or Generic Templates: Agreements found online may not reflect current law or the company's actual needs. For example, a template may lack the required California carve-out language or Illinois notice. Always review and update templates before use.
• Ignoring State Law: Failing to check state-specific rules can result in unenforceable clauses or even legal penalties. For example, California, Illinois, and Washington have unique requirements for invention assignment and confidentiality.
• Overreaching Clauses: Clauses that are too broad or vague may be struck down by courts. For example, claiming ownership of inventions unrelated to the business or restricting lawful employee activities, such as discussing wages or working conditions.
• Poor Worker Classification: Using employee-style agreements for contractors, or vice versa, can create classification risks and jeopardize IP rights. This is especially risky for startups using a mix of employees and freelancers.
• Missing Required Notices: Some states require specific notices or disclosures in these agreements. Failing to include them can make the agreement unenforceable. For example, Illinois requires a notice about the right to consult an attorney for non-compete and non-solicit clauses.
• Lack of Training or Communication: Workers may not understand what they are signing or what is expected of them. Provide clear explanations and opportunities for questions. Consider a brief onboarding session or FAQ handout.
• Not Updating Agreements: Laws and business needs change. Review your agreements regularly and update them as needed. For example, recent changes in non-compete law in several states may require updates to your templates.

Example: A Colorado startup uses an old CIIAA template that includes a broad non-compete clause. Colorado law now bans most non-competes for employees earning below a certain salary threshold. The agreement is challenged and found unenforceable, exposing the company to risk.

To avoid these mistakes, employers should:

• Work with legal counsel to draft or review agreements.
• Keep up to date with federal and state law changes.
• Train HR and managers on how to explain and implement agreements.
• Document all agreements and communications with workers.

Practical Rollout Checklist for Employers

Before rolling out a confidential information invention assignment agreement, employers should follow a practical checklist:

1. Identify Worker Type: Confirm whether the worker is an employee or independent contractor. Use IRS and DOL guidance for classification. Document your reasoning and keep records.
2. Check State Law: Review the rules in every state where your workers are located, especially for invention assignment, confidentiality, and required notices. Consult state labor agency resources and recent case law if needed.
3. Tailor the Agreement: Use separate templates for employees and contractors. Customize definitions and clauses for your business and industry. For example, a biotech company may need specific language for patentable inventions.
4. Include Required Notices: Add any state-mandated disclosures or notices about employee rights. For example, include the Illinois attorney consultation notice for restrictive covenants, or California's carve-out language for invention assignment.
5. Explain the Agreement: Provide workers with a plain-language summary and allow time for questions. In some states, you may need to advise workers of their right to consult an attorney. Consider a brief onboarding session or written FAQ.
6. Collect Signed Copies: Obtain signed agreements before work begins, and store them securely. Use e-signature tools with audit trails for remote teams.
7. Update as Needed: Review and update agreements regularly to reflect changes in law or business operations. Set a calendar reminder to review templates annually or after major legal changes.
8. Document the Process: Keep records of all steps taken, including training, communications, and signed agreements. This can be valuable if a dispute arises.

Example: A Florida e-commerce company expands to hire remote workers in California and Illinois. The HR manager reviews state law, updates the CIIAA templates with required carve-outs and notices, and provides each worker with a summary and time to review. The company collects signed agreements before onboarding, reducing legal risk and protecting its IP.

FAQs

Are confidential information invention assignment agreements enforceable in every state?

No, enforceability depends on state law and the specific terms of the agreement. Some states, such as California, place strict limits on invention assignment and confidentiality clauses. Always review the law in each state where your workers are located.

Can I require contractors to sign a CIIAA?

Yes, but the agreement must be carefully drafted. Overly broad or restrictive terms can create classification risks or be unenforceable. Contractors generally own the IP they create unless the agreement clearly assigns it to the company. Avoid using employee-style language for contractors.

What happens if I use the same agreement for employees and contractors?

This can create legal risks, including misclassification and unenforceable terms. Always use separate templates and tailor the agreement language to the worker's role and classification. Misclassification can lead to IRS or DOL penalties and loss of IP rights.

Do I need to include a non-compete clause in a CIIAA?

Non-compete clauses are not required and are unenforceable in many states. Focus on confidentiality and invention assignment, and only include non-compete or non-solicit clauses if you have confirmed they are allowed in the relevant state. Always check current state law before including restrictive covenants.

What should I do if a worker refuses to sign the agreement?

Discuss their concerns and explain the purpose of the agreement. In some cases, you may need to negotiate certain terms or consult legal counsel. For employees, you may be able to make signing the agreement a condition of employment, subject to state law. For contractors, consider whether the assignment is essential for your business.

Key Takeaways

• Confidential information invention assignment agreements are vital for protecting business secrets and intellectual property, but must be tailored to federal and state law.
• Worker classification (employee vs. contractor) affects agreement terms and enforceability. Use the correct template for each type.
• State law can override or supplement federal law, especially for invention assignment and confidentiality. Always check local requirements and required notices.
• Common mistakes include using generic templates, ignoring state law, failing to update agreements, and misclassifying workers.
• Employers should use a practical rollout checklist, train staff, and consult legal counsel as needed to reduce risk and protect their business.

If you have questions about confidential information invention assignment agreements or want help reviewing your documents, contact our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they are delivered by licensed lawyers at trusted law firm partners through the Sprintlaw platform.