Ecvc Draft Ip Assignment Agreement

Skill: Draft IP Assignment Agreement for Early-Stage Biotech Financing

1. Subject-matter triage

• Confirm the primary deliverable is the executed-style IP assignment agreement; treat the partner-facing risk memo as secondary and prepare it only after the agreement is complete.
• Identify every assignor, every IP category, and every source-document dependency before drafting substantive provisions.
• If the source set shows multiple inventors, multiple development periods, or multiple software/code bases, handle each separately rather than using a single generic recital.
• Surface any internal-document language verbatim only where necessary for accuracy, and avoid copying source text beyond what is needed to draft the work product.

2. Failure modes the skill is correcting

• The assignment can be underinclusive if it transfers only named patents or code repositories while omitting trade secrets, know-how, inventions, improvements, and rights to sue.
• Open-source contamination can be missed, leaving unclear whether copied, modified, or combined code can be owned exclusively or must remain subject to external license terms.
• Employee-invention carve-outs can be omitted for jurisdictions that limit assignment of off-hours inventions, creating enforceability gaps.
• Federally funded invention obligations can be ignored, leaving undisclosed government or institutional rights attached to the assigned technology.
• Prior-employer overlap can be overlooked, allowing hidden right-to-invent or pre-assignment obligations to surface after closing.
• Moral-rights language can be absent in jurisdictions where waiver or consent is needed to make the assignment operational.
• A risk memo that only describes the issues without tying each to the deal process leaves the client without usable remediation steps.

3. Legal frameworks / domain conventions that apply

• Draft the omnibus assignment to cover present and future rights in patents, patent applications, trademarks, copyrights, mask works if relevant, trade secrets, inventions, discoveries, improvements, domain names, data, documentation, and associated causes of action.
• Use assignment language that reaches both existing IP and after-acquired IP to the extent permitted by applicable law, with present assignment of future rights where customary.
• For software and related materials, distinguish proprietary deliverables from third-party or open-source components and preserve the fact that upstream license obligations may travel with the code under their governing licenses.
• For copyleft or reciprocal licenses, address compliance with the applicable license terms rather than assuming they disappear on assignment; the contract should allocate responsibility for disclosure, source availability, or replacement where needed.
• For employee-invention limitations, include the applicable statutory carve-out and any required notice language under the governing law for each assignor to whom it applies.
• For government-funded or sponsored research, include representations and disclosure obligations tied to the governing funding regime and any institutional rights that may attach.
• For prior-employer conflicts, include a representation that the assignor has disclosed any conflicting invention assignment, confidentiality, noncompete, or right-to-invent obligation and that no assigned contribution was wrongfully taken from a prior employer.
• Include a moral-rights waiver or consent to the extent recognized under the governing law.
• Where the source documents identify a specific legal regime, use that regime’s cited authorities; otherwise anchor the drafting in generally recognized assignment and IP principles.

4. Analytical scaffolds

• Build a complete inventory of the IP to be assigned, then map each item to a schedule by type and status.
• For each assignor, test four questions in order: what was created, when it was created, under what resources or funding it was created, and what third-party obligations may already attach.
• Separate company-owned work product from third-party components, licensed inputs, and preexisting materials incorporated into the technology stack.
• For software and data, distinguish source code, object code, build scripts, model artifacts, datasets, documentation, and derivative works.
• For patent materials, separate issued patents, pending applications, provisionals, continuations, continuations-in-part, divisions, and abandoned or lapsed filings if they appear in the source set.
• For each representational statement, draft it so the assignor can truthfully answer only after checking employment history, grant terms, lab notebooks, and contributor records.
• In the memo, identify issues that the agreement can mitigate versus issues that require pre-closing cleanup, disclosure, or business decisions.
• Tie each memo issue to a transaction consequence, such as title uncertainty, closing diligence friction, indemnity exposure, financing delay, or post-closing enforcement weakness.
• If a source document is silent on an item that is material to ownership, treat the silence as a diligence gap to flag, not as a fact to assume.

5. Vertical / structural / temporal relationships

• Draft the agreement from ownership source to present assignment to confirmatory mechanics to post-closing cooperation, so the chain of title reads cleanly.
• Track timing by creation date, employment period, funding period, and filing period; ownership risk often turns on which period the work falls into.
• If multiple assignors are involved, draft each representation and carve-out as assignor-specific rather than global, unless the source set clearly supports a shared statement.
• Preserve the distinction between pre-existing IP, during-engagement developments, and post-signing cooperation duties.
• If the source record includes a financing milestone, make the memo recommendations align with the closing timetable and any conditions to funding.

6. Output structure conventions

• Deliver a standalone omnibus IP assignment agreement in conventional transaction form: parties, recitals, definitions, assignment grant, further assurances, representations, carve-outs, waiver/consent language, schedules, and signature blocks.
• Use schedules that actually carry the inventory: assigned IP, software/components, funded-research items, known third-party materials, and any disclosed exceptions.
• Draft representations to cover title, authority, no conflicting obligations, no undisclosed third-party rights, funding disclosures, and cooperation obligations.
• Draft the companion risk memorandum in issue-spotting format with a clear severity ranking, a short rationale for each item, and a practical remediation path.
• Include a Recommended Actions section in the memo with imperative steps, the responsible role, and timing tied to the closing process or diligence response window.
• Confirm at the end of drafting that the agreement file is the primary completed work product and that the memo is complete only as a secondary deliverable.
• Keep the drafting operational: write clauses, not summaries of clauses; write actionable remediation, not abstract concern statements.