IP Assignment Agreements: What Employees and Founders Actually Sign Away

When you start a new job or bring on your first employee, an IP assignment agreement is often buried in the onboarding paperwork — easy to overlook, hard to undo. These clauses do not just govern work you do at the office on company time. Depending on how they are written, they can reach into evenings, weekends, and side projects you thought had nothing to do with your employer. Understanding what you are actually agreeing to matters whether you are the person signing or the company drafting.

What an IP Assignment Clause Actually Does

An IP assignment clause transfers ownership of intellectual property from the creator — the employee or contractor — to the company, automatically and as a condition of employment. Unlike a license, which lets the company use your invention while you retain ownership, an assignment moves title entirely. If the clause is valid and covers your invention, the company owns it from the moment it is created. You do not.

Most assignment clauses cover:

• Inventions conceived or reduced to practice during the term of employment
• Inventions that relate to the company's current or reasonably anticipated business
• Inventions made using company resources, equipment, or confidential information
• Works of authorship — including code — that qualify as works made for hire under copyright law

The phrase "reasonably anticipated business" does real work here. A company does not have to be actively doing something for the clause to attach to it. If the company could plausibly enter that market, some courts will find the invention covered.

The Moonlighting Problem

Broad assignment clauses often try to capture inventions made entirely on the employee's own time, without company resources, and in areas unrelated to the employer's business. Whether those clauses are enforceable depends heavily on state law.

Several states — California, Delaware, Illinois, Minnesota, North Carolina, and Washington among them — have statutes that limit how far an employer can reach. In California, for example, an assignment clause cannot capture inventions the employee develops entirely on their own time without using company equipment or trade secrets, unless the invention relates to the employer's business or results from the employee's work for the company. Employers in those states are often required to notify employees of the statutory limits, sometimes in writing.

If you are in a state without a protective statute, a broad clause may be enforceable as written. The absence of a statutory floor does not mean courts will always enforce overreaching language, but it gives you less to stand on.

What to Do Before You Sign

If you have pre-existing inventions, side projects, or ongoing work you want to protect, the time to address them is before you sign — not after. Most employment agreements include a schedule or exhibit where you can list prior inventions you are carving out from the assignment. Courts generally respect these schedules when they are specific.

• List the project or invention by name and general subject matter, not just a vague category
• If you have a pending patent application, note the application number
• Do not over-disclose confidential details about a side business — the schedule is a carveout, not a confession
• Get confirmation from the employer in writing that the carveout is accepted

If you forget to fill out the schedule and sign a blank or generic form, you may be starting from a much weaker position later.

What Founders Need to Watch on the Other Side

If you are building a company and bringing on employees or contractors, your IP assignment language is a core piece of your ownership chain. Investors, acquirers, and licensees will look at whether every contributor has a signed, enforceable assignment on file. Gaps are expensive to fix retroactively.

Common Drafting Mistakes

• Relying on verbal agreements or offer letters that do not include assignment language
• Using contractor agreements that treat the work as a license rather than an assignment
• Forgetting that copyright's "work made for hire" doctrine has specific requirements for independent contractors — certain categories of works qualify, and everything else needs an explicit written assignment
• Failing to get agreements signed before work begins, which can complicate the chain of title

For software specifically, the code written by your first five contributors is often the core of your patent-eligible invention. If those assignment agreements are missing or ambiguous, you may not cleanly own the invention you are trying to protect.

Practical Takeaways

• An IP assignment clause transfers ownership entirely — it is not a license, and it is not reversible without the employer's cooperation
• State law varies significantly on how far an employer can reach into off-hours inventions; know which state governs your agreement
• Fill out the prior inventions schedule carefully and specifically before signing any employment agreement
• Founders should have signed IP assignment agreements from every employee and contractor before work begins, not after
• For contractors, a work-made-for-hire clause alone may not be enough — pair it with an explicit assignment to close copyright gaps
• Review your employment agreement before starting a side project, not after you have built something worth protecting

This guide is general education, not legal advice, and does not create an attorney–client relationship. For your specific situation, talk to a registered patent attorney.