Build an open-source and contractor-IP issues table for a technology deal
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- From the target contracts and licence notices, list ownership gaps, contractor-created IP and copyleft or attribution conditions with document references.
- What the lawyer must review
- Read the licence family in the actual notice
- Check GPL version differences and inbound assignment gaps; both are easy to mis-state
- Written for / version
- US
Open a jurisdiction version of this task to see which instruments apply: US
Who does what
| Role | What they do |
|---|---|
| Assistance | Consider narrowly defined preparation support after confirming the tool’s capability and permitted scope. |
| Lawyer | Set the scope, supervise the work closely, verify every part relied on, resolve omissions and exceptions, and approve the exact output. |
Checklist
- Review operative clauses in the complete document, including definitions, cross-references, schedules and inconsistencies with the instructions.
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Resolve exceptions and record the responsible lawyer’s approval of the exact output and intended use.
Forms and precedents for this task
| Form or precedent | Kind | AI use | Summary |
|---|---|---|---|
| Deed of assignment of intellectual property and moral rights consent (contractor or developer software) | Deed | AI use Yellow | A deed by which a contractor, freelance developer or former founder assigns copyright and other IP in software and related material to a company, with a moral rights consent, further assurance, a schedule of pre-existing and open-source material, and execution blocks. |
| Open source licence compliance review checklist (technology transactions and product releases) | Checklist | AI use Yellow | A checklist for reviewing open source use in a codebase for a sale, investment, licence-out or product release: inventory, licence classification, distribution and network-use triggers, notice and source obligations, licence conflicts, AI-generated code and remediation. |
Signed-in accounts can read the full text of each one. All precedents.