Intellectual property disputes between former employees and their companies are a recurring feature of employment litigation. The engineer who built a system at work and kept a copy on a personal drive. The product manager who wrote a strategy document now being used by a competitor. The designer who made a logo on the side and later sold it to a client. Each of these triggers a question with surprisingly complex answers: who owns this, under what law, and what evidence matters? The default rules vary by type of IP, by state, and by the specific language of the employment agreement.
The Four Main Types of Employment IP and Default Ownership Copyright attaches automatically to any original creative work fixed in a tangible medium: code, documents, designs, video. Under the work-for-hire doctrine, work created by an employee within the scope of employment belongs to the employer by default. Work by independent contractors belongs to the contractor unless the agreement transfers ownership in writing.
Patent rights follow different rules. Inventions made using employer resources during working hours typically trigger employer rights, but the specifics depend on state law and the written IP assignment. Trademarks belong to whoever uses the mark in commerce, which in employment usually means the employer. Trade secrets belong to whoever takes reasonable steps to protect them.
IP Assignment Agreements: What They Cover and What They Can't Most employers include an IP assignment clause in the offer letter or a separate Proprietary Information and Inventions Agreement (PIIA). A typical clause assigns all work product created during employment to the employer, along with all inventions, improvements, and discoveries related to the company's business.
State law limits how broadly employers can assign. California Labor Code 2870 prohibits assignment of inventions made entirely on the employee's own time, without company resources, and not related to the company's business or anticipated research. Similar statutes exist in Delaware, Illinois, Kansas, Minnesota, North Carolina, Utah, and Washington. An IP assignment that tries to grab these exempt inventions is unenforceable to that extent.
What About Pre-Existing IP the Employee Brings to the Job? IP the employee created before joining remains theirs unless they specifically assign it. Most PIIAs include a schedule or exhibit where the employee lists pre-existing inventions. That list matters: items not listed can later be presumed to belong to the employer under certain doctrines, so employees should populate it thoroughly.
How Most Employment IP Disputes Actually Unfold The common scenarios: a departing engineer has copies of proprietary code on personal devices. A product leader starts a competing venture using confidential market research. A designer freelances on the side and the outputs look similar to work they're doing for the employer. A researcher publishes results that implicate trade secrets.
These cases turn on three questions. Was the IP created within the scope of employment? Did the employee sign an enforceable assignment? Were reasonable steps taken to protect it as confidential? When any answer is "no" or "unclear," the dispute becomes expensive and uncertain, often settling through negotiation.
Building an Intellectual Property Program That Prevents Disputes Use a clear, state-specific IP assignment agreement signed at the start of employment, not midway through. Include the required state-law exceptions for jurisdictions that require them. Use NDA agreements that cover confidentiality obligations beyond the employment term. Document the pre-existing IP list carefully at onboarding.
For high-IP roles, run exit interviews that specifically cover return of company materials, delete-or-return obligations on personal devices, and reminders of post-employment obligations. Pair IP policies with non-compete agreement and non-solicit terms where state law permits. Reference USPTO guidance on employer-employee invention rights at uspto.gov/patents . Tie IP education into your employee handbook so that every employee understands the basics.
.svg)
.svg)
