Does Your New Employer Own Your Side Projects? How to Read a Proprietary Information Agreement

The Document You Skipped Is the One That Follows You

Knowing how to read a job offer proprietary information agreement determines whether you retain ownership of your weekend code, personal SaaS projects, and pre-existing intellectual property after signing. While your offer letter states your compensation, title, and start date, the proprietary information agreement dictates what you own, what you are obligated to disclose, and what intellectual property you surrender to your employer both during and after your employment.

If your written offer arrived yesterday with an acceptance deadline of Friday afternoon, your packet likely contains four or five attachments. Candidates naturally spend their first evening reviewing base salary, equity vesting schedules, and health benefits. The longest document in that PDF bundle—often titled a Proprietary Information and Inventions Assignment agreement (PIIA), an Employee Invention Assignment Agreement, or an Intellectual Property Agreement—is routinely signed without a close reading.

That oversight creates lasting exposure. An offer letter establishes the basic terms of your working relationship, but the PIIA establishes legal covenants that frequently survive termination. Unlike the single-page offer summary, the PIIA typically carries its own separate signature page. Signing the offer letter does not automatically execute the PIIA, but employers almost universally condition employment on executing both simultaneously. If you sign it without reviewing the text, you may assign rights to projects you conceived years before joining or forfeit side businesses you build strictly on personal time.

This guide provides an analytical framework for reading this agreement before your deadline expires. It names specific terms, structural gaps, and statutory provisions you should verify across your documents. It is an informational reading guide, not legal advice, and it does not tell you whether to sign, negotiate, or walk away.

How to Read a Job Offer Proprietary Information Agreement: A Section-by-Section Pass

When facing a tight deadline, reading a ten-page legal agreement from top to bottom is inefficient. Standard legal boilerplate obscures the operational mechanics. To understand how to read a job offer proprietary information agreement systematically, follow this repeatable six-step reading order:

1. Definitions: Locate the definitions of "Company," "Confidential Information," and "Inventions."
2. The Assignment Clause: Pinpoint the operative verbs transferring ownership rights.
3. The Prior Inventions Schedule: Inspect the exhibit intended for pre-existing work.
4. Statutory Carve-Out Language: Check for mandatory state law exceptions.
5. Post-Employment Covenants: Identify survival periods, non-solicitation restrictions, and notification duties.
6. Remedies and Enforcement: Note provisions covering injunctive relief, attorney fees, and moral rights waivers.

1. Definitions

The downstream reach of the agreement is determined entirely by its definitions section. Pay close attention to two definitions: "Company" and "Confidential Information." Check whether "Company" includes only the direct corporate entity hiring you or extends broadly to "all parents, subsidiaries, affiliates, predecessors, successors, and assigns." If defined broadly, an invention that competes with a distant subsidiary of a holding company could trigger an assignment claim. Similarly, assess whether "Confidential Information" is restricted to proprietary trade secrets or drafted expansively to cover "all information, in whatever form, disclosed to or observed by the Employee." Compare this clause against any standalone job offer confidentiality agreement in your packet to see if the definitions conflict.

2. The Assignment Clause

The assignment section contains the operative legal mechanism. Search for the core verb phrase: "hereby assigns," "agrees to assign," or "shall be the sole and exclusive property of the Company." Modern agreements use present assignment phrasing ("hereby assigns") to ensure an immediate, automatic transfer of title the moment an invention is created, rather than creating a promise to transfer rights in the future.

3. The Prior Inventions Schedule

This section is usually placed at the very end of the agreement as "Exhibit A," "Schedule 1," or the "List of Prior Inventions." It provides a space to list intellectual property created before your official start date. If this schedule is left blank, the agreement almost universally contains a clause stating that you represent and warrant that you own no pre-existing inventions.

4. Carve-Out Language

Examine the text detailing what the employer cannot claim. Standard carve-outs protect work "developed entirely on my own time without using Company equipment, supplies, facilities, or trade secret information." Check whether these conditions are linked conjunctive ("and") or disjunctive ("or"). To qualify for an exclusion, you must typically meet every listed criterion simultaneously.

5. Post-Employment Covenants

Review the provisions that remain binding after your employment ends. Identify the exact survival period for confidentiality obligations, requirements for returning company data, and any non-solicitation restrictions regarding clients or colleagues. Look closely for a "Notice of Subsequent Employment" clause, which may require you to disclose the identity of your next employer so your current company can send them a copy of your signed PIIA.

6. Remedies and Moral Rights

Examine the enforcement remedies specified by the agreement. Most agreements include an acknowledgment that monetary damages alone are insufficient for a breach, entitling the employer to immediate injunctive relief without the obligation to post a bond. Additionally, check for a waiver or assignment of "moral rights"—the legal doctrine that allows an author or creator to retain attribution and prevent modification of their work regardless of copyright ownership.

Invention Assignment: The Clause That Decides Who Owns Your Side Project

An employment invention assignment agreement functions as a blanket title transfer. It reallocates property rights that would otherwise belong to you under common-law copyright or patent frameworks. Employers require this to ensure that all code, documentation, and product designs created by workers belong indisputably to the corporate entity, clearing title for future venture capital rounds, bank credit facilities, or acquisitions. However, the exact phrasing of the assignment clause dictates whether that transfer covers your private, off-hours work.

Consider three typical formulations of assignment language found in modern offer packets:

• Clause A (Broad Temporal Scope): "Employee agrees that all Inventions conceived, reduced to practice, authored, or made by Employee, solely or jointly, during the period of employment shall be the sole property of the Company." This language makes no reference to equipment, company time, or business relevance. On its face, it captures anything created between your start date and end date, including a personal blog post or a mobile game coded on a personal computer over a weekend.
• Clause B (Subject-Matter Scope): "Employee hereby assigns all right, title, and interest in and to any Inventions created during employment that relate directly or indirectly to the actual or reasonably anticipated business, research, or development of the Company." This clause links ownership to business relevance rather than time or equipment.
• Clause C (Resource-Restricted Scope): "Employee assigns all Inventions developed using Company equipment, supplies, facilities, or Confidential Information, or resulting from work performed by Employee for the Company." This is the narrowest common structure, explicitly tethering company ownership to the use of employer resources or assigned job duties.

Understanding the distinction between "conceived" and "reduced to practice" is critical. An idea is "conceived" when the inventor forms a definite, complete mental concept of the invention. It is "reduced to practice" when it is physically constructed, coded, or can work. If you drafted architectural specifications for a personal developer tool last month, but write the initial code two weeks after starting your new job, a contract claiming all inventions "conceived or reduced to practice during employment" could pull that project into the employer's ownership domain.

The phrase "or reasonably anticipated business" represents the broadest common trap in an intellectual property assignment agreement covering side projects. If you join an enterprise infrastructure firm that currently sells database migration software, but company leadership has informally discussed launching developer productivity tools in the future, an internal project roadmap could be cited to argue that your independent, weekend-built developer extension falls within their "reasonably anticipated business."

Furthermore, many PIIA documents impose an affirmative disclosure duty. These clauses state that you must promptly disclose to the employer in writing all inventions created during your employment, even if you believe the invention qualifies fully for an exemption under state law or contract terms. Once disclosed, the burden often shifts to you to prove that the project is exempt.

State Law Sets a Floor, Not a Ceiling

State labor statutes restrict how far an employer's invention assignment clause can legally extend into an employee's personal life. Several states have enacted statutory exemptions that void contractual terms assigning specific employee inventions. These states include California, Washington, Illinois, Minnesota, Delaware, Kansas, North Carolina, Utah, and Nevada.

Under California Labor Code § 2870, any employment agreement provision that requires an employee to assign their rights to an invention developed entirely on their own time without using the employer's equipment, supplies, facilities, or trade secret information is unenforceable, subject to two specific statutory exceptions:

1. The invention relates at the time of conception or reduction to practice to the employer's business, or actual or demonstrably anticipated research or development of the employer.
2. The invention results from any work performed by the employee for the employer.

Similarly, the state of Washington regulates these contracts under Washington Revised Code RCW 49.44.140. Washington law provides that assignment clauses do not apply to inventions developed entirely on personal time without company resources, and explicitly mandates that employers provide written notice of this statutory protection to employees at the time the agreement is executed.

In addition, Minnesota Statutes § 181.78 establishes a comparable standard, declaring that employment agreements requiring assignment of inventions developed entirely on an employee's own time without company resources or trade secrets are void and unenforceable, provided they do not relate directly to the employer's business or result from assigned work.

The operational reality of these statutes depends on two factors: the governing law stated in your contract and your physical work location. A remote engineer living in Washington working for a Delaware corporation headquartered in California must verify which state's legal framework governs the contract. Standard PIIAs typically include a "Governing Law" clause near the end. If your contract specifies Delaware law, but you live and work in California or Washington, resolving which public policy applies can introduce complex legal jurisdictional questions that require consultation with an attorney licensed in that jurisdiction.

Crucially, state statutory carve-outs do not apply to confidentiality, trade secrets, or non-solicitation covenants. If a personal project uses an algorithm, customer lead, or technical design pattern learned through your employment, statutory protections will not shield that project from an employer's trade-secret misappropriation claim.

The Prior Inventions Schedule: Why a Blank Page Is a Decision

The Prior Inventions Schedule is the contract exhibit where you register intellectual property you created before joining the company. By listing your existing assets on this schedule, you establish documented evidence that the work was conceived and reduced to practice prior to your start date, excluding it from the agreement's forward-looking assignment scope.

Treating this schedule as administrative boilerplate to be skipped is a serious mistake. If you sign an agreement with a blank Prior Inventions Schedule, you are usually signing a formal contractual warranty that you own zero pre-existing intellectual property. If a dispute arises eighteen months later regarding ownership of an open-source library or indie SaaS application you built prior to being hired, the employer's legal counsel can present an executed document where you attested in writing that no such prior inventions existed.

Items that professionals should evaluate for inclusion on a Prior Inventions Schedule include:

• Open-source libraries, packages, or major documentation projects maintained under an employer-neutral identity.
• Registered patents, provisional patent filings, and formal copyright registrations.
• Published technical books, academic papers, training courses, and substantive technical newsletters.
• Unfinished prototypes, design systems, or proprietary research co-developed with outside collaborators.

When completing the schedule, avoid entering ambiguous, one-line descriptions. A note that reads "Developer tooling software" or "Personal website" fails to define the boundaries of the excluded asset. If the project expands later, the employer can argue that the advanced features were developed during employment using their knowledge base. Instead, list the title, public repository URL, primary functional description, version number or commit hash existing on the signing date, and any applicable copyright or patent application serial numbers.

Be aware of the disclosure tradeoff. Listing a pre-existing project informs your employer that the project exists. If your side project operates in a technical domain adjacent to your new employer's core product, disclosing it on the schedule may prompt hiring managers or internal legal teams to ask questions about your time commitments or potential business conflicts before confirming your start date.

PIIA in a Job Offer: Where It Overlaps With the NDA and the Non-Solicit

A standard offer packet often bundles several legal documents together. Understanding how each document operates prevents confusion over which terms govern your conduct. When reviewing a PIIA in job offer documentation, map the distinct functions of the individual agreements:

Agreement Type	Primary Legal Focus	Standard Duration	Key Risk Area
Non-Disclosure Agreement (NDA)	Protection of non-public business information	2–5 years (perpetual for trade secrets)	Overbroad definition of confidential data
Proprietary Information Agreement (PIIA)	Ownership transfer of inventions + IP confidentiality	Duration of employment plus post-employment assignment	Assignment of off-hours personal side projects
Non-Solicitation Agreement	Restricting recruitment of employees or clients	Typically 12–24 months post-employment	Barring informal peer networking or referrals
Non-Compete Covenant	Restricting work for competing market entities	Typically 6–12 months post-employment (where legal)	Restrictions on career mobility in specific domains

Watch for structural duplication. An offer packet may contain both a standalone NDA and an extensive confidentiality section inside the PIIA. Compare the definitions of "Confidential Information" in both documents. If the standalone NDA includes standard commercial exclusions (such as excluding information already known to you, publicly available data, or information independently developed without reference to company files) but the PIIA omits those exclusions, the broader PIIA language governs your intellectual property obligations.

Employers also frequently embed non-solicitation clauses inside the body of a PIIA rather than drafting a separate document. A paragraph buried under "Employee Covenants" may stipulate that for twelve months following termination, you cannot directly or indirectly solicit, recruit, or encourage any company employee or contractor to leave their position. Similarly, review the final sections for a "Notice of Subsequent Employment" requirement, which obligates you to notify your former employer in writing of your new company's address and contact details whenever you change jobs within one to two years after departure.

What the PIIA Usually Does Not Say

What a contract omits is just as consequential as the language it contains. PIIA documents are drafted by company counsel to protect the business; they rarely include operational mechanisms designed to safeguard your outside projects. Look closely for what the document leaves unaddressed:

• No Expedited Project Clearance Process: Agreements rarely specify a formal, repeatable pathway for an employee to request a written exclusion for a new side project initiated after the start date.
• Unclear Definitions of "Company Resources": Agreements prohibit the use of company resources, but rarely define how that applies to modern remote setups. If you read work email on your personal phone, connect a personal computer to a corporate virtual network, or access a company Slack channel via a home internet connection, does that configure your personal device as a "company resource"? The contract is usually silent.
• Artificial Intelligence and Third-Party Tools: Modern agreements frequently fail to distinguish between code generated through enterprise AI subscriptions and scripts written on an employee's personal machine using local open-weight models, leaving intellectual property ownership in a gray area.
• Absence of Objective Standards for "Reasonably Anticipated": Standard PIIA language often claims rights over inventions relating to the company's "reasonably anticipated business" without defining objective criteria or required documentary evidence (such as product roadmaps or leadership presentations) to substantiate what was genuinely anticipated.
• Asymmetric Post-Employment Terms: While employee non-solicitation and restrictive covenants usually carry a fixed expiration date (such as one or two years), confidentiality requirements and ownership assignment clauses apply perpetually, binding your past contributions indefinitely without providing reciprocal obligations from the company.

Questions to Ask Before the Deadline, and How to Ask Them

If you identify ambiguities or need to exclude a personal asset before your acceptance window closes, route your inquiries to the right stakeholders. Recruiters are talent acquisition specialists; they generally lack the authorization or legal background to interpret contract clauses. Verbal assurances from a recruiter—such as "Oh, don't worry about that, nobody enforces that clause"—hold zero legal standing when contradicted by an integrated, signed written contract containing an integration clause.

When you have clarifying questions, email the recruiter and request that the inquiry be reviewed by the appropriate human resources operations or corporate legal representative. Frame your inquiries professionally, precisely, and neutrally:

• "I am reviewing Exhibit A (Prior Inventions Schedule) in the Proprietary Information Agreement. If I attach an exhibit listing pre-existing open-source repositories and personal software tools, what is the formal internal process and turnaround time for written confirmation of that schedule prior to my start date?"
• "The agreement outlines an assignment of inventions relating to the company's 'reasonably anticipated business.' Could you clarify how the company formally defines that boundary for side projects developed entirely off-hours without company hardware?"
• "Section X references governing law in Delaware, while this role is fully remote based out of California. Could you confirm whether the company provides an addendum reflecting state-specific statutory protections under California Labor Code Section 2870?"
• "Is there an established internal review process for employees seeking written clearance to contribute to non-competing open-source projects during their tenure?"

Raising analytical questions about contract terms is standard professional practice, not an adversarial negotiation. However, if your deadline is Friday at 5:00 PM and you receive your offer documents on Wednesday, routing legal questions may require more time than the company initially allotted. You can submit a structured job offer deadline extension request to secure the breathing room needed to complete your review. If you need a formal email template to send your recruiter, you can generate one using an online offer deadline request tool.

Where OfferMettle Fits — and Where It Does Not

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.

Understanding the exact boundary of what the service does—and does not do—is critical:

• 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 never interprets whether a clause is enforceable.
• The 24-Hour Offer Decision Sprint is delivered by software. There is no call, no session and nobody to schedule.
• The paid service is the 24-Hour Offer Decision Sprint: one fixed, visible price of $599, or $399 for the founding cohort. Nothing is charged as a percentage of any increase.
• OfferMettle guarantees delivery of the Decision Brief within 24 hours of intake and refunds the fee if that window is missed. It never guarantees a negotiation outcome.
• OfferMettle reports what the documents state and where they are silent. It produces no market range, no benchmark and no valuation of the offer.
• The Decision Brief sets out what the documents say and the questions worth asking. The decision stays with the reader.
• OfferMettle asks for payment and the offer documents. There is nothing to sign.

In addition to the sprint, the Offer Risk Snapshot is the free tool: it summarises publicly reported signals about an employer, with the detail behind an email gate. For quantitative evaluations, four calculators (offer comparison, counteroffer, deadline request, startup equity) compute entirely in the visitor's browser; no offer figures leave their machine.

Frequently Asked Questions

Is a proprietary information agreement the same thing as an NDA?

No. While both documents manage sensitive information, a Non-Disclosure Agreement (NDA) focuses primarily on restricting the unauthorized disclosure and use of confidential company information. A Proprietary Information and Inventions Assignment agreement (PIIA) incorporates those confidentiality restrictions but adds affirmative intellectual property assignment clauses. The PIIA legally transfers ownership of inventions, code, designs, and discoveries you create to your employer, establishing who owns the underlying intellectual property.

Does a PIIA give my employer ownership of side projects I build on my own laptop?

It depends on the specific phrasing of the assignment clause and your governing state law. If the contract states that the employer owns all inventions related to the company's "actual or reasonably anticipated business," using your personal laptop outside working hours will not protect the project if the software directly overlaps with your employer's market products. However, if the project is completely unrelated to the company's business, uses zero company confidential data, and was developed strictly on personal time and equipment, statutory protections in states like California, Washington, or Minnesota often void employer ownership claims.

Can I amend the prior inventions schedule after I sign the offer?

Amending the schedule after execution requires written consent and an executed contract amendment from your employer. Once you sign the PIIA, your representations regarding prior intellectual property are legally locked. While an employer might agree to execute an updated schedule or addendum later, they are under no legal obligation to do so. Any side project or pre-existing asset must be listed on Exhibit A before you sign and return the paperwork.

What does 'reasonably anticipated business' mean in an invention assignment clause?

The phrase "reasonably anticipated business" refers to commercial products, technologies, or services that the company has actively planned, researched, or prepared to enter, even if those products have not yet been launched publicly. In a dispute, employers demonstrate anticipated business using internal documents such as product roadmaps, board presentations, customer research, or prototype code bases. Because this language extends an employer's intellectual property ownership claims beyond their current public catalog, it represents one of the broadest assignment provisions in standard employment contracts.

Do I need a lawyer to read a proprietary information agreement before my deadline?

You do not need a lawyer simply to locate, read, and understand the plain language of your agreement, verify what is listed on the prior inventions schedule, or note where the text is silent. However, if you are bringing valuable pre-existing software, active commercial businesses, registered patents, or consulting practices into a new role, or if you need an authoritative legal opinion on whether a specific restrictive covenant is legally enforceable under your state's labor codes, you should consult an employment attorney licensed in your jurisdiction.

The Twenty-Minute Read That Protects the Next Five Years

Follow the disciplined reading sequence: review the definitions of "Company" and "Confidential Information," verify the operative verbs in the assignment clause, check the prior inventions schedule, identify statutory carve-outs, review post-employment covenants, and inspect the enforcement remedies.

When you finish your review, ensure you have documented three critical items:

1. The precise scope of the assignment language (whether it claims inventions based strictly on resources, time, or business relevance).
2. The governing law and jurisdiction specified in the contract's final provisions.
3. A list of material omissions—such as undefined remote resource policies, absent open-source contribution procedures, or an empty prior inventions exhibit.

This systematic review names terms worth questioning; it does not tell you whether to accept, reject, or negotiate the terms. If you uncover substantive overlaps between your outside work and the employer's assignment scope, take action immediately. Submit an itemized Prior Inventions Schedule, route written clarification inquiries regarding governing law to HR, or consult an independent attorney licensed in your state. Offer deadlines do not pause on Friday afternoon, and an ambiguous intellectual property schedule is far easier to clarify before signing than it is to contest five years down the road.

If the PIIA is sitting in your packet and Friday is close, 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 Decision Brief sets out what the documents say and the questions worth asking. The decision stays with the reader. OfferMettle guarantees delivery of the Decision Brief within 24 hours of intake and refunds the fee if that window is missed.