How to assess invention assignment exclusions for Employee Invention Assignment Agreements

Assess invention assignment exclusions by separating mandatory statutory protections from negotiated prior-invention reservations, testing each against development history and employment facts, and reviewing any license triggered by company use. The employer-side deliverable is an evidence-linked exclusions matrix identifying the reserved asset, the basis for exclusion, permitted company use, and issues requiring resolution before approval. Reconcile the agreement, schedules, disclosures, and applicable law; do not treat an omitted schedule as proof that no prior inventions exist or an unsuccessful statutory claim as automatic proof of employer ownership.

When to use this workflow

Use this review when onboarding an employee with existing technology, negotiating a research hire’s invention schedule, updating an agreement after a location change, or assessing excluded material before product incorporation. Employment counsel should coordinate with IP counsel and the technical owner responsible for proposed use.

The scope is the boundary between assigned and excluded inventions, not a complete ownership audit. This guide uses a US employer perspective and Washington law as a specific illustration, not a nationwide rule. Record work locations and contractual governing law separately, and have counsel resolve applicable-law questions before approving jurisdiction-specific wording.

What you need

Collect the complete agreement, prior-inventions schedule, incorporated policies, statutory notices, and amendments. Identify draft and executed versions, including separately delivered attachments.

Obtain these inputs:

• Employee work locations, relevant location history, start date, role, and expected technical responsibilities.
• A bounded description of each claimed prior invention, including versions, conception and development dates, contributors, and asserted ownership.
• Available dated design records, repository references, project summaries, and resource-use information.
• Relevant company business activities, assigned work, and actual or demonstrably anticipated research plans.
• Proposed company use, existing licenses, and known third-party restrictions.

Request sufficient evidence without soliciting former-employer secrets. Where technical detail creates that risk, start with a nonconfidential description and assign counsel to determine a controlled verification method.

Use the template

Use the Employee Invention Assignment Agreements — Invention exclusions matrix. You can copy this table into your working document or spreadsheet. Create one row per invention or distinct issue; use linked rows where statutory protection and negotiated treatment require separate decisions.

In ID / source, record an issue ID, document version, and clause or page citation. Link to the source file or extraction record. Keep exact language distinguishable from paraphrase.

Asset / boundary identifies the reserved project, version, and development cutoff. Exclusion basis distinguishes statutory protection, negotiated reservation, and unresolved assertion. Evidence identifies supporting records, not merely the person making the assertion.

Work / resources captures duties, resource use, and business or research connections. Use / license records intended company use and the rights supporting it. The final fields identify uncertainty, disposition, accountable reviewer, approval condition, and completion status. Distinguish “not supplied” from “reviewed and absent”; neither should silently become “none.”

Step by step

1. Fix the review set and jurisdiction question

Assign document IDs before extracting language. Confirm that the agreement references the schedule actually supplied, and check amendments for changes to definitions or exclusions. A signed agreement with a missing attachment is an incomplete review set, not evidence of an empty schedule.

Record work location and governing-law wording separately. Ask employment counsel which protections and notices apply to the employee’s circumstances, including remote work or relocation. Keep legal sufficiency open until that question is resolved.

Matrix output: source version, execution status, missing attachments, jurisdiction question, and responsible counsel.

2. Map the assignment boundary before assessing exceptions

Read defined terms alongside the operative assignment. Separate present-transfer wording, promises to assign, disclosure duties, and further-assurance duties; route questions about their ownership effect to counsel rather than treating them as interchangeable.

Identify statutory carveouts, scheduled prior inventions, side-project exceptions, and negotiated reservations. Compare each with language covering improvements, derivatives, or work related to company business. Flag any broader provision that could contradict the stated reservation.

For review purposes, replace an unbounded description such as “all software developed before employment” with an identifiable project, version, and cutoff, subject to employee confirmation. Specificity makes the boundary reviewable; it does not establish ownership or eliminate mandatory protections.

Matrix output: assignment citation, exclusion source, covered rights, and conflicting definitions or cross-references.

3. Test mandatory exclusions against actual facts

Where Washington law applies, RCW 49.44.140(1)–(2) excludes inventions developed entirely on employee time without employer equipment, supplies, facilities, or trade-secret information, unless they relate directly to the employer’s business, relate to its actual or demonstrably anticipated research or development, or result from work performed for it. Overreaching provisions are void to that extent and cannot be required as an employment condition.

Assess each element separately. Obtain development dates, resource-use facts, assigned-work descriptions, and relevant research records rather than accepting “personal project” as the conclusion. Support an asserted business connection with specifics rather than the label “technology.”

Keep two determinations separate: whether the statute prevents assignment, and whether the agreement otherwise reaches the invention. Failure to establish the first should trigger the second review, not an automatic employer-ownership disposition.

Matrix output: applicable test, supporting and contrary facts, unresolved elements, and counsel’s assessment.

4. Reconcile reservations with development history

Compare the schedule with employee disclosures. Determine whether each entry describes a completed asset, an ongoing project, or future improvements. Separate the baseline from later work and identify the factual period covered by each evidence item. A repository reference supporting an earlier version should not be recorded as proof about undocumented later development.

Check collaborators and prior commitments. Request relevant rights documents where available, without asking for confidential technical content from another employer.

The Authentidate SEC-filed agreement, attached invention agreement § 3, illustrates a prior-inventions list and wording treating an absent list as indicating none exist. That drafting example is not independent verification of an employee’s development history.

Matrix output: defined baseline, date evidence, contributor questions, and proposed schedule corrections.

5. Review company use independently from ownership exclusion

Ask the technical owner whether the company expects to embed, modify, distribute, or otherwise use the excluded asset. Then compare that plan with the license trigger and scope, including sublicensing, transfer, duration, and restrictions relevant to the intended product.

The Authentidate agreement’s § 3 illustrates a broad license triggered by employment use or inclusion in company products or services. It is a drafting example, not evidence of market standards or enforceability in another matter.

Verify the employee’s authority to grant the needed rights. If authority or scope remains uncertain, recommend withholding incorporation pending review. For statutory exclusions, separately escalate whether proposed license wording would undermine the required protection; do not assume a license is an acceptable substitute for an impermissible assignment.

Matrix output: planned use, license trigger and scope, authority evidence, and interim restriction.

6. Check notices and disclosure language for consistency

RCW 49.44.140(3) requires written notification of the statutory exclusion when covered employment agreements containing invention-assignment requirements are made; it applies to agreements entered into after September 1, 1979. The notification must include the statutory exceptions.

Record notice text, version, timing, and delivery evidence. Do not confuse the prior-inventions schedule with that notification, or assume a later notice resolves an earlier delivery issue.

Read disclosure duties separately from assignment. Flag wording that appears to assign everything disclosed or contradict a reservation. Preserve event-based language such as prompt disclosure rather than inventing a fixed reporting period. Route broader confidentiality-notice review separately; this matrix does not establish compliance with every obligation in the agreement.

Matrix output: notice status, delivery gap, disclosure conflict, and correction owner.

7. Resolve each issue and verify coordinated revisions

Assign each row a disposition: accept, revise, investigate, or escalate. State the reason and approval owner. Keep the decision on ownership exclusion separate from approval of company use.

Use a lawyer-maintained negotiation checklist distinguishing mandatory protections from employer preferences, with acceptable fallbacks and escalation triggers. Translate approved decisions into coordinated edits to the assignment, schedule, license, and notice. Reread them together after revision.

Compare the approved draft with the execution package, including schedules and handwritten changes. Retain unresolved rows with owners and approval conditions rather than closing them because the main agreement has been signed.

Matrix output: disposition, linked revision, approver, remaining conditions, and verification status.

Worked example

Fictional scenario: Harborline Sensors hires Mira Chen as a Washington-based firmware engineer. EIAA-04, draft 2, assigns employment-related inventions under § 3, addresses statutory exclusions under § 4, and licenses scheduled technology incorporated into company products under § 5. Schedule A initially contains one blanket reservation: “all home robotics software and improvements.”

Disclosure D1 identifies three projects. Repository references R1 support a pre-employment version of TrailPath, but later development is undocumented. BeaconTune may overlap with planned sensor-calibration research; only manager summary M1 describes that connection. FrameKit has a named collaborator, and engineering requests modification and distribution in a commercial release. No collaborator rights agreement has been supplied. All parties, records, projects, and wording are fictional.

The review produces three decisions rather than blanket acceptance or rejection of Schedule A. TrailPath needs a defined baseline, with later work left open. BeaconTune requires additional facts before applying the statutory test; the manager’s summary does not settle it. FrameKit may be suitable for a reservation while product incorporation remains blocked. None of the missing evidence is treated as supporting the employer’s preferred outcome.

Common mistakes

• Treating personal time as decisive. Assess resource use and each applicable business, research, and assigned-work connection.
• Accepting a project name as a complete boundary. Specify the asset, version, cutoff, and unresolved later development.
• Treating a failed statutory claim as ownership proof. Separately examine the agreement’s reach and supporting rights evidence.
• Equating exclusion with permission to use. Review license scope and grant authority independently.
• Turning a missing schedule into “no inventions.” Obtain a completed disclosure or informed confirmation and review any resulting representation.
• Requesting former-employer technical files. Start with nonconfidential evidence and route sensitive verification through counsel.

Final quality check

Before approving the assessment, confirm:

• Conclusions link to the correct document version and clause or page.
• Applicable jurisdiction is resolved or expressly assigned for determination.
• Statutory protections and negotiated reservations are separately classified.
• Development dates, resources, duties, and research connections have evidence or identified gaps.
• Reserved assets and later-development boundaries are intelligible.
• Company use matches reviewed rights and supported grant authority.
• Relevant legal sources, notice text, timing, and delivery evidence have been verified.
• Revised documents are consistent, with every open issue assigned an owner and approval condition.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. For contract review, choose the employer as the represented party in Word and provide deal-specific instructions on exclusions and license concerns. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; the matrix remains your work product. Retain legal judgment on applicable law, evidence, and approval. Book a demo to assess this workflow.

Frequently asked questions

Should the employer reject every broad reservation?

No. Identify what the employee intends to reserve before proposing narrower wording. Preserve the distinction between mandatory protection and negotiable scope; narrowing a schedule should not be used to erase an applicable statutory exclusion.

Does listing an invention establish ownership?

Treat listing as a disclosure or reservation, not your ownership verification. Check contributors and prior commitments where the employer needs rights, and record unresolved authority rather than relying solely on the schedule.

Can an acceptable exclusion still block product incorporation?

Yes, as a review disposition. Approve the reservation separately from company use. Keep incorporation on hold where the necessary license scope or authority remains unresolved, even if the ownership boundary is acceptable.

What if evidence cannot safely be disclosed?

Identify the precise fact needing verification. Seek a nonconfidential description or limited confirmation, then have counsel determine whether controlled review is appropriate. Keep the issue open if the available evidence does not support a decision.

Sources

• Washington RCW 49.44.140: statutory exclusions, employment-condition restrictions, and written notification.
• Authentidate Holding Corp., SEC Exhibit 10.49: attached invention agreement § 3, used only as a drafting example.

Scope: General professional workflow, not advice for a particular matter or a nationwide enforceability survey. Contract rights depend on actual language, applicable law, facts, and employment context.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.