Does Your New Employer Own Your Side Project? Reading an Intellectual Property Assignment Agreement

Your new employer does not automatically own your pre-existing side projects, but an overly broad intellectual property assignment agreement can claim anything you build during your employment if you fail to carve it out in writing before your start date. Whether a company owns your personal software, designs, or technical writing depends entirely on the specific language in your offer packet, the equipment you touch, and how precisely you document your retained inventions.

When you receive an offer packet containing an offer letter, an equity grant summary, and an intellectual property schedule, the intellectual property assignment agreement is often the most legally consequential document for your personal engineering work. Most candidates read their base salary, review their vesting schedule, and glance past the proprietary inventions paperwork. If you maintain an open-source library, a software-as-a-service application, or technical research outside your day job, signing without a line-by-line review of the assignment terms can inadvertently assign full legal title of your work to your new employer.

What an Intellectual Property Assignment Agreement Covers in a Standard Job Offer

An intellectual property assignment agreement—frequently titled a Proprietary Information and Inventions Agreement (PIIA), Invention Assignment Agreement (IAA), or Confidential Information and Invention Assignment Agreement (CIIAA)—is a binding contract designed to secure company ownership over all work product generated by employees. In United States employment paperwork, this document establishes that any intellectual property developed within the scope of your employment belongs exclusively to the hiring entity.

The standard purpose of this agreement is clear: companies must prove clear title to their assets to satisfy investors, acquirers, and auditors. To prevent future disputes over who owns the software powering the business, companies require every engineer, product manager, and technical contributor to assign their rights upfront. However, standard template agreements are drafted by company counsel to be maximally protective of the enterprise, often capturing far more than just the tasks outlined in your job description.

These clauses transfer ownership across several distinct categories of intellectual property:

• Patents and Patentable Inventions: New processes, architectural designs, machines, software algorithms, hardware implementations, or technical improvements conceived during your tenure.
• Copyrights and Works of Authorship: Source code, documentation, technical specifications, user interface layouts, database schemas, and written articles. Under US copyright law, while the "work made for hire" doctrine covers standard employment duties, assignment clauses go further by formally assigning works that might fall outside the statutory definition.
• Trade Secrets and Know-How: Proprietary algorithms, specialized operational configurations, customer data structures, and unpatented methods developed while on the payroll.
• Domain Knowledge and Research: Experimental benchmarks, research papers, and technical prototypes built to solve operational problems.

It is essential to understand the procedural distinction between your core offer letter and the standalone IP schedules that accompany it. Your offer letter typically outlines at-will employment status, starting compensation, reporting lines, and benefits. The offer letter usually incorporates the PIIA or IP assignment agreement by reference as an attached exhibit or a condition precedent to employment. While an offer letter may span two to four pages, the invention assignment schedule is often a dense, standalone legal instrument spanning five to ten pages. If you are conducting a thorough job offer review before your decision deadline, you must treat the IP agreement as an independent document with binding post-employment ramifications.

The Three Core Components of Employment Contract IP Rights

To evaluate what you are signing, you need to break down the mechanics of employment contract ip rights. While agreement titles vary across companies, virtually all enterprise and startup invention assignment agreements rely on three fundamental contractual mechanisms: direct assignment, affirmative disclosure, and attorney-in-fact appointments.

1. Present Assignment of Inventions

The core operative mechanism of any PIIA is the assignment clause itself. Modern agreements use explicit "present assignment" phrasing: "Employee hereby assigns, transfers, and conveys to the Company all right, title, and interest in and to all Inventions."

This phrasing matters immensely. Historically, older agreements used promissory language such as "Employee agrees to assign" in the future. US federal courts established that promissory language only creates an obligation to transfer rights later, which requires an additional executing document. In contrast, present-tense phrasing ("hereby assigns") executes an automatic legal transfer the instant an invention is conceived or reduced to practice. Furthermore, this clause executes an outright transfer of ownership rather than a permissive license. Once an invention falls inside the contractual perimeter, you no longer own it, cannot license it to others, and cannot maintain it as an independent project without explicit corporate authorization.

2. Affirmative Disclosure Requirements

Most IP assignment schedules include an affirmative disclosure covenant. Under this clause, you are legally required to promptly disclose to the company in writing any inventions, software tools, designs, or improvements you conceive, develop, or reduce to practice during your period of employment.

Crucially, standard contracts mandate disclosure of all technical creations, even those you believe qualify as personal projects outside the company's scope. The company reserves the right to evaluate the invention and determine whether it falls under the assignment clause. If you build a mobile application on weekends and do not disclose it, you may commit a technical breach of your agreement—even if the app has nothing to do with your employer's commercial market.

3. Power of Attorney Provisions (Attorney-in-Fact)

Near the end of an invention assignment schedule, you will encounter a power of attorney clause. This provision states that if the company is unable to secure your signature on any patent application, copyright registration, or formal assignment document—whether due to mental incapacity, unavailability, or departure from the company—you irrevocably appoint the company's officers as your attorney-in-fact.

This grant gives corporate officers the legal authority to sign your name on government patent and trademark filings. While this is standard practice to prevent former employees from holding patent filings hostage after resigning, you must verify that the scope of this power of attorney is strictly limited to work properly assigned under the contract, rather than granting open-ended authority over personal intellectual assets.

Deconstructing IP Assignment Clause Meaning: Inventions, Equipment, and Working Hours

Understanding an ip assignment clause meaning requires isolating the three primary triggers that pull an engineering project into corporate ownership. When enterprise employment contracts are drafted, corporate attorneys set traps around three specific vectors: working hours, employer resources, and the employer's business scope.

Vector Trigger	Standard Contractual Language	Real-World Engineering Risk
Equipment & Resources	"Developed using any equipment, supplies, facilities, or trade secret information of the Company..."	Writing personal scripts on a company laptop, pushing to personal Git repositories over corporate VPN, or running code in company sandbox environments.
Working Hours & Time	"Conceived, developed, or reduced to practice during the period of employment, whether during working hours or off-duty..."	Salaried exempt roles lack defined working hours; companies argue daytime ideation or flexible-schedule work occurred on company time.
Business Scope	"Relates directly or indirectly to the current, proposed, or demonstrably anticipated business, products, or research of the Company..."	Broad enterprise definitions where multi-product corporations or venture-backed startups claim any software development overlaps with their expansion roadmap.

The Equipment Vector: Hardware and Cloud Accounts

The cleanest line an employer can draw in an IP dispute is the physical or virtual hardware line. If you write personal code on an employer-provided MacBook, run tests using an employer-subsidized cloud account (such as an AWS dev environment), or test APIs using a corporate cellular device, you have contaminated your project with employer resources.

Modern remote work has amplified this trap. Many engineers utilize personal home offices where personal and corporate machines sit side by side. Commingling assets can instantly void statutory protections:

• SSHing into personal servers from a corporate terminal.
• Storing personal source code on an enterprise-monitored Google Drive or OneDrive account.
• Utilizing an employer-provided GitHub Enterprise Copilot license or proprietary internal dev tool for side-project generation.
• Consulting proprietary internal documentation or Slack discussions to debug an architecture problem in your external project.

Even minor touchpoints—such as installing your personal dotfiles or compiling personal hobby scripts during lunch breaks on a corporate laptop—give corporate litigators an evidentiary foothold to assert ownership.

The Working Hours Vector: The Salaried Exempt Reality

Most mid-career engineers and product managers are hired under Fair Labor Standards Act (FLSA) exempt classifications. Unlike hourly workers, exempt employees do not have legally defined shift boundaries. If your employment agreement asserts ownership over inventions conceived "during working hours," an aggressive employer can argue that your working hours span any time you are actively thinking, problem-solving, or available on messaging channels.

To mitigate this ambiguity, your contract must cleanly distinguish between work performed within designated job duties and work created strictly during off-duty hours without employer compensation.

The "Scope of Business" Vector: Expanding Tech Perimeters

The most dangerous trigger in a modern tech agreement is the "business scope" provision. Typical language claims any invention that:

"Relates to the actual or demonstrably anticipated business, work, research, or development of the Company, or results from any task assigned to or performed by Employee for the Company."

For a niche, single-product manufacturing business, the scope of business is relatively narrow. If the company manufactures medical sensors, building a personal mobile game engine does not overlap. However, if you join a large technology conglomerate, a multi-product SaaS platform, or a venture-backed startup with stated ambitions to enter logistics, consumer finance, artificial intelligence, and developer tooling, the "demonstrably anticipated business" can encompass virtually any software domain. In an environment focused on rapid expansion, reviewing early-stage documentation is critical; candidates evaluating seed or Series A grants should cross-reference IP scope against their startup offer review checklist.

State Statutory Protections for Personal Inventions Across the US

To protect workers from oppressive employment agreements that claim all creative human output, several US states have enacted mandatory employee invention statutes. These statutes place non-waivable legal boundaries around what an employer can claim via contract.

Under California Labor Code Section 2870, any employment agreement provision that requires an employee to assign inventions developed on their own time, without using employer equipment, supplies, facilities, or trade secrets, is legally void and unenforceable against public policy—provided the invention does not relate directly to the employer's business or result from work performed for the employer. This establishes an affirmative baseline: employers cannot contract around the statute to capture purely personal off-hours creations.

Similarly, the state of Washington provides statutory relief under Washington RCW 49.44.140. The Washington statute mirrors the core carve-out criteria, establishing that an assignment clause does not apply to an invention developed entirely on an employee's own time without company property, unless the invention relates directly to the employer's commercial enterprise or demonstrably anticipated research.

Other states provide comparable statutory protections. For example, the Illinois Employee Patent Act (765 ILCS 1060) establishes similar safeguards prohibiting mandatory assignments of inventions conceived on an employee's personal time without company resources. Similar statutory protections exist in Minnesota, Delaware, Kansas, and New Jersey. Across these jurisdictions, the statutory carve-out standard requires satisfying a strict four-part test:

1. The invention was developed entirely on the employee's personal time.
2. No employer equipment, supplies, software licenses, or facilities were utilized.
3. No employer trade secrets or proprietary confidential information were referenced or embedded.
4. The project does not relate to the employer's current or demonstrably anticipated business, products, or R&D, and did not result from any work assigned by the employer.

Because state statutes protect personal developments, states like California explicitly mandate that employers provide written notification of these protections at the time of contract execution. Specifically, California Labor Code Section 2870 governs the scope of statutory exclusions that must be disclosed to employees under companion statutory notification mandates. In a compliant offer packet, you will find an attached "Limited Exclusion Notification" or a "Statutory Notice Exhibit" citing the applicable state code. If your offer packet lacks this disclosure while asking you to assign all creations, or if your governing law is set in a state without statutory protections, you must rely entirely on contractual exclusions negotiated into the agreement itself.

Prior Inventions Disclosures: Documenting Your Existing Work

The single most effective tool for protecting your existing intellectual property is the Prior Inventions Exhibit, commonly labeled as Exhibit A, Schedule 1, or the List of Excluded Inventions. This schedule serves as an explicit contractual carve-out from the general assignment clause.

When you execute an intellectual property assignment agreement, the contract assigns everything you build going forward. The Prior Inventions schedule allows you to identify all original works of authorship, codebases, registered copyrights, filed patents, domain portfolios, and active projects that you conceived or constructed prior to your official start date. By identifying these items on the schedule, you contractually exclude them from the scope of the agreement.

How to Complete the Prior Inventions Schedule

Many candidates make the mistake of leaving Exhibit A blank out of convenience, or writing "None" because they believe a personal side project is too small or informal to document. Doing so creates an immediate legal presumption: if an IP dispute arises later, the absence of an invention on Exhibit A allows the employer to argue that the project was conceived during your employment tenure.

To properly disclose your work without compromising confidential information, follow these descriptive principles:

• List Distinct Identifiers: Include the project title, repository name, domain name, or application name (e.g., "Project Atlas: Open-source container orchestration utility hosted on GitHub under username/atlas").
• Summarize Functionality Broadly: Describe the high-level architecture and purpose without detailing proprietary trade secrets (e.g., "A distributed key-value store optimized for low-latency embedded IoT systems").
• Note Registration Details: If you hold registered patents, provisional patent applications, trademarks, or formal copyright registrations, record the filing serial numbers, registration numbers, and dates.
• Avoid Over-Disclosure: You do not need to paste source code or provide private architectural blue-prints. Provide enough specificity that an objective third party can distinguish between your pre-existing asset and the code you will write for your new employer.

The Threat of "Incorporation by Reference" Clauses

While listing projects on Exhibit A protects those specific assets from being claimed by the company, read the surrounding contract text carefully. Almost every standard PIIA includes an "Incorporation of Prior Inventions" clause. A typical clause reads:

"If, in the course of my employment with the Company, I incorporate into a Company product, service, or process a Prior Invention owned by me, the Company is hereby granted a non-exclusive, royalty-free, fully paid-up, irrevocable, perpetual, worldwide license to make, have made, modify, use, and sell such Prior Invention."

If you take an open-source library, a script, or a modular component listed on your Exhibit A and paste it into your employer's production codebase, you automatically grant your employer an irrevocable, royalty-free, perpetual license to your personal intellectual property. To preserve full control, rarely import your personal modules, scripts, or architectural scaffolding into corporate repositories without formal corporate licensing agreements.

Red Flags to Spot in an Intellectual Property Assignment Agreement

When reviewing your offer documents under a short turnaround window, certain clauses warrant immediate scrutiny. While standard templates protect an employer's business assets, overreaching clauses place unacceptable burdens on your personal development career. Keep an eye out for these contractual red flags, which can easily be categorized alongside broader job offer red flags in your assessment.

1. Holdover and Trailer Clauses

A "trailer" or "holdover" clause extends the reach of the intellectual property assignment agreement beyond the day you resign or are terminated. A holdover clause typically states that any invention conceived by you within 6 to 12 months following termination of employment is presumed to belong to the former employer if it relates to work performed during your tenure.

These clauses are particularly punitive for software engineers and researchers. If you leave a company to build your own startup or pursue independent contracting, an active holdover clause casts a legal cloud over your subsequent creations. While several state courts disfavor post-employment assignment clauses as restraints on trade, signing an agreement containing a trailer clause guarantees friction if your previous employer decides to assert ownership over a launched project.

2. Hypothetical and Expansive "Company Scope"

Be alert to definitions of company business that rely on future speculation rather than active commercial reality. Clauses asserting rights over:

• "Any business the Company may potentially evaluate, investigate, or enter during the term of employment..."
• "Any area of research or commercial interest contemplated by the Company..."

In high-growth companies, founders and leadership evaluate countless emerging markets, enterprise integrations, and open-source tools. An agreement asserting ownership over any commercial interest the company might hypothetically investigate transforms the assignment into a blanket dragnet over your career.

3. Blanket Moonlighting and Side Project Prohibitions

Some companies insert language into their confidentiality or IP attachments prohibiting employees from engaging in any outside commercial activity, secondary employment, or independent software development without prior written approval from an executive officer. These are often titled "Duty of Loyalty" or "Exclusivity of Services" clauses.

If you intend to operate a micro-SaaS, consult on weekends, or publish commercial applications, an outright prohibition creates a contractual violation regardless of whether the side project uses company resources. If the company demands total exclusivity, that requirement must be reconciled with your external commitments before accepting.

4. Total Silence on Open-Source Contributions

If you are an active open-source maintainer, the complete absence of an open-source contribution policy or carve-out in your offer packet is a distinct warning sign. If your agreement asserts ownership over all code produced during employment without setting a path for off-duty open-source contributions, any commits you push to external repositories could technically be claimed by your employer—or run afoul of the company's disclosure covenants.

Questions to Raise with the Hiring Team Before Your Friday Deadline

When you hold an offer with a short decision window, you do not have weeks to engage in extended legal negotiations. You must focus on actionable clarifications that resolve contractual ambiguity before you sign. If your decision deadline is too tight to obtain written responses, you can use an offer deadline request to secure additional business days to work through open questions with the hiring team.

1. Submitting and Executing Exhibit A

Do not sign the core offer letter while assuming Exhibit A can be handled during onboarding. Once you sign the main agreement, your power to exclude prior projects decreases significantly. Send a professional written inquiry to your recruiter or hiring manager:

"I am reviewing the Proprietary Information and Inventions Agreement enclosed with the offer packet. I have several pre-existing, personal software projects and domain holdings that I need to formally document on Exhibit A (Prior Inventions). What is the administrative process for submitting the completed Exhibit A so that it is counter-signed and attached to the executed agreement?"

2. Clarifying Side Project and Moonlighting Guidelines

If your personal work generates revenue or involves active software maintenance, ask for the company's internal written policies on outside activities. These guidelines frequently live in an internal employee handbook rather than the offer packet itself:

"Does the company maintain a formal written Outside Work Policy or Open-Source Contribution Policy? I maintain personal, non-competitive development projects on my own hardware during off-duty hours, and I want to ensure my practices remain fully compliant with the engineering team's standard guidelines."

3. Identifying Terms Worth Independent Legal Review

Some situations present too much technical or financial risk for a candidate to handle alone. If you maintain an existing commercial business with active revenue, hold provisional or issued software patents, or are entering an employer operating in the identical market vertical as your side project, you should take the specific assignment clauses to an independent employment attorney. An attorney can evaluate jurisdictional enforceability and draft custom carve-out amendments tailored to your exact project assets.

Resolving Ambiguity in Offer Documents Under a Tight Clock

When you are managing a 24- to 72-hour deadline, the central challenge is separating signal from noise across dozens of pages of legal exhibits. You must identify every IP restriction, restrictive covenant, and exhibit disclosure requirement across your packet. If you fail to read the fine print, you risk signing away projects you spent years developing.

Candidates must trace every restriction directly to the underlying exhibit, page, and paragraph in their offer packet. For instance, a broad assignment clause on page 2 of a PIIA may be partially modified by a statutory carve-out on page 7, while Exhibit A on page 9 governs your immediate disclosure duties. Tracing these terms across disconnected PDFs requires systematic reading.

OfferMettle reads the offer documents you upload and returns a Decision Brief that traces every statement back to the document and page it came from. The paid service is the 24-Hour Offer Decision Sprint: one fixed, visible price of a measurable budget or a measurable budget for the founding cohort. OfferMettle returns the Decision Brief within 24 hours of intake, and refunds the fee if that window is missed. The Decision Brief is produced by software. There is no reviewer, no call and no human in the fulfilment path. OfferMettle guarantees delivery time, rarely an outcome. Source: Offermettle source.

To evaluate broader company context before finalizing your employment, the Offer Risk Snapshot is the free tool: it summarises publicly reported signals about an employer, with the detail behind an email gate. Four calculators (offer comparison, counteroffer, deadline request, startup equity) compute entirely in the visitor's browser; no offer figures leave their machine. The Decision Brief sets out what the documents say and the questions worth asking. The decision stays with the reader. OfferMettle reports what the offer documents say and names the terms worth questioning or taking to an attorney. It is not legal advice and it rarely interprets whether a clause is enforceable.

Maintaining Ownership Boundaries Post-Signature

Once your paperwork is signed and Exhibit A is countersigned, maintaining absolute ownership over your side projects requires relentless day-to-day discipline. To ensure your employer rarely has an evidential basis to claim your off-duty work, adhere to these operational rules from day one:

• Maintain Total Hardware Separation: rarely install personal development environments, run personal scripts, or connect personal external drives to an employer-issued machine. rarely touch your side project from a company laptop.
• Isolate Network Infrastructure: Do not use corporate VPNs, internal Wi-Fi networks, or corporate proxy servers to push commits, manage cloud deployments, or access personal hosting providers.
• Separate Accounts and Tooling: Keep your personal GitHub, GitLab, Docker Hub, and cloud provider accounts tied strictly to personal email addresses and independent personal billing methods. rarely use enterprise-provided developer licenses or AI coding assistants for personal codebases.
• Document Creation Timestamps: Maintain verifiable git commit logs and timestamped engineering records proving that your personal code was written exclusively outside your standard working hours.

Frequently Asked Questions

Can an employer claim ownership of an app I created before starting the job?

An employer cannot retroactively claim ownership of software created and completely reduced to practice before your first day of employment, provided you do not assign it to them. However, if you leave the Prior Inventions schedule (Exhibit A) blank, fail to document the pre-existing project, or subsequently incorporate portions of that app's source code into the employer's systems during your employment, the employer can assert legal and equitable claims over the intellectual property. Documenting the project on Exhibit A before signing eliminates this ambiguity.

Does an intellectual property assignment agreement apply to my open-source contributions?

Yes. In standard invention assignment agreements, the definition of assigned inventions includes any software, documentation, or technical work of authorship created during employment. Unless your contract contains an express carve-out for open-source contributions or your work falls under protective state statutes, writing code for public repositories during your tenure can fall under company ownership. Many technology organizations maintain separate open-source policies requiring written manager approval before contributing to external repositories.

What happens if I write code for a side project on my personal laptop during weekends?

Writing code on personal hardware during weekends satisfies two of the standard statutory exemption tests: personal time and personal equipment. However, if the side project directly relates to your employer's current business, involves research your team is actively conducting, or incorporates trade secrets you learned on the job, your employer may still claim ownership under the terms of your PIIA. To protect your project, the subject matter must remain completely independent of your employer's commercial and technical operations.

What should I do if the offer packet contains no Prior Inventions Exhibit?

If your offer packet contains an intellectual property assignment agreement that references an Exhibit A or Schedule 1 for prior inventions, but the exhibit itself is missing from the PDF bundle, do not sign the document as-is. Contact your recruiter or hiring manager immediately to request the complete exhibit attachment. If the agreement lacks a designated schedule entirely, you can request that a custom written addendum listing your pre-existing projects be executed and attached to the agreement before your start date.

Facing a 24-72 hour deadline on a new job offer? OfferMettle reads the offer documents you upload and returns a Decision Brief that traces every statement back to the document and page it came from.