---
title: "Build an open-source and contractor-IP issues table for a technology deal"
url: "https://ailawframework.com/practice/technology-media-and-telecommunications-it-contracts/build-an-open-source-and-contractor-ip-issues-table-for-a-technology-dea"
type: "task"
site: "AI Law Framework"
id: "A24-T1-R5"
practice_area: "Technology, Media & Telecommunications / IT Contracts"
tier: "yellow"
lawyer_review: "required"
last_reviewed: "2026-10-22"
---

# Build an open-source and contractor-IP issues table for a technology deal

> From the target contracts and licence notices, list ownership gaps, contractor-created IP and copyleft or attribution conditions with document references.

Canonical page: https://ailawframework.com/practice/technology-media-and-telecommunications-it-contracts/build-an-open-source-and-contractor-ip-issues-table-for-a-technology-dea  
Last reviewed: 2026-10-22

Site index for agents: https://ailawframework.com/llms.txt

## Key facts

| Fact | Value |
| --- | --- |
| Practice area | [Technology, Media & Telecommunications / IT Contracts](https://ailawframework.com/practice/technology-media-and-telecommunications-it-contracts.md) |
| Human involvement | Yellow: Lawyer and AI draft together |
| 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 / versions | 1 jurisdiction versions below |

## Checking plan

**Lawyer review required**

The responsible lawyer reviews the work against the instructions, sources and intended use.

- What the AI does: Potential support includes extracting and organising information and preparing preliminary structure or wording. Confirm the tool’s capability and permitted scope.
- What the lawyer does: Set the scope, verify the evidence, resolve exceptions and approve the final output for its intended use.
- Who reviews: Responsible lawyer with competence in the matter
- Basis: Suggested checking approach based on the task guidance. Complete the assessment for the actual tool, information and jurisdiction.
- Why: The plan reflects the described work and review requirements. Policy colours are not used to determine permission or checking.

## Checks the lawyer makes

1. Review operative clauses in the complete document, including definitions, cross-references, schedules and inconsistencies with the instructions.
2. Confirm that the actual tool, feature and processing terms permit use of this information, including access, retention, training and disclosure conditions.
3. Obtain and inspect the relevant current official register or search result. Confirm identities, interests and the date and scope of the search.
4. Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
5. Resolve exceptions and record the responsible lawyer’s approval of the exact output and intended use.

## Notes

- Confirm the required checking with the responsible lawyer before work starts. The checking approach does not establish permission to use AI.

## Forms and precedents for this task

| Form or precedent | Kind | AI level | Summary |
| --- | --- | --- | --- |
| [Deed of assignment of intellectual property and moral rights consent (contractor or developer software)](https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts/ip-assignment-and-moral-rights-consent-deed.md) | Deed | 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… |
| [Open source licence compliance review checklist (technology transactions and product releases)](https://ailawframework.com/precedents/technology-media-and-telecommunications-it-contracts/open-source-licence-compliance-review-checklist.md) | Checklist | 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… |

Signed-in accounts can read the full text of each one.

## Jurisdiction versions

| Jurisdiction | Level |
| --- | --- |
| [United States](https://ailawframework.com/practice/technology-media-and-telecommunications-it-contracts/build-an-open-source-and-contractor-ip-issues-table-for-a-technology-dea/united-states.md) | Yellow |

*Practice guidance for planning and review. Confirm current primary sources and the requirements of the actual matter. This is general information, not legal advice.*