What Makes an Intellectual Property Asset Ready for Review?

An intellectual property asset may be commercially important but still difficult for another person to review. The underlying right may be unclear, documents may be spread across different systems, registration details may be outdated, or important licences and restrictions may be missing from the package.

Review readiness does not mean that the asset has been legally validated, valued or approved for sale. It means that the available information is organised well enough for a buyer, licensee, adviser or other authorised reviewer to understand what is being presented and begin appropriate due diligence.

Key point: A review-ready IP package clearly identifies the asset, connects it to its supporting documents and discloses known limitations. It does not replace independent legal, technical, commercial or financial assessment.

Start by defining the asset

“Intellectual property” is not a single asset type. A product or project may involve several separate rights and materials, including:

• patents and patent applications;
• registered and unregistered trade marks;
• registered and unregistered designs;
• copyright in software, text, images, video, music or documentation;
• database rights and contractual rights relating to data;
• confidential information, trade secrets and know-how;
• domain names and product identities;
• licences to use third-party rights; and
• contractual rights to royalties, distribution or commercialisation.

The package should state precisely what is being reviewed. A company name, software product or AI system may be a useful commercial label, but it does not by itself identify all the rights included in the proposed asset or transaction.

1. The scope is clear

A reviewer should be able to determine:

• which specific rights and materials are included;
• which versions, territories and fields of use are relevant;
• whether each right is registered, pending, unregistered or contractual;
• which items are owned and which are only licensed;
• whether related goodwill, domains, documentation, data or physical materials are included; and
• what is expressly excluded.

Use registration numbers, application numbers, agreement identifiers, repository references, product versions and dated schedules where available. Avoid broad statements such as “all technology” or “all IP” unless the underlying documents support that scope.

2. The claimed ownership history can be followed

The package should connect the origin of each material right to the person or entity that currently claims to own it.

Relevant documents may include:

• creation and development records;
• employment and contractor agreements;
• founder and shareholder arrangements;
• assignments and deeds of transfer;
• corporate acquisition or restructuring documents;
• official registration records;
• settlement, court, probate or insolvency documents; and
• confirmations or corrective assignments addressing earlier gaps.

Present these in chronological order. Identify missing links, inconsistent legal names, unsigned schedules and work created before the relevant agreement was signed. A clean timeline is more useful than a folder containing unexplained documents.

For a fuller explanation of ownership, licences and transfers, see Ownership, Licensing and Assignment: What Do the Documents Show?.

3. Official records and deadlines are current

For registered rights, include current information from the relevant official authority. Depending on the right and jurisdiction, a reviewer may need to see:

• the registered proprietor or applicant;
• application and registration status;
• relevant classes, claims, representations or designated territories;
• filing, priority, grant and expiry dates;
• renewal or maintenance deadlines;
• recorded licences, transfers or security interests; and
• pending objections, oppositions, cancellations or other proceedings.

A certificate issued in the past may not show the current status. Compare the package with the relevant live register and record the date on which the register was checked.

Official records also have limits. They may not reveal every contract, dispute, beneficial interest or unrecorded event. They should be reviewed together with the underlying documents.

4. Licences and commercial restrictions are mapped

IP may be owned by one party while another has exclusive, territorial or field-specific rights to use it. A reviewer should be able to understand existing commitments that affect the asset.

Prepare a schedule showing:

• licensors and licensees;
• exclusive, sole or non-exclusive status;
• territory and field of use;
• duration, renewal and termination rights;
• royalty, fee and reporting terms;
• sublicensing and assignment permissions;
• change-of-control restrictions;
• rights to improvements, derivatives and new versions;
• confidentiality and data-use obligations; and
• outstanding breaches, notices or disputes.

Include amendments, side letters and referenced schedules. A summary is useful for navigation, but reviewers may still need controlled access to the complete signed agreements.

5. Third-party dependencies are identified

An asset can depend on materials that the claimed owner does not own. This is particularly important for software, AI systems, media products and datasets.

The package may need an inventory of:

• open-source software and applicable licence terms;
• commercial libraries, APIs and hosted services;
• stock media, fonts, music and design assets;
• training, testing and reference datasets;
• contractor and supplier contributions;
• customer-provided materials;
• standards, protocols or interoperability dependencies; and
• restrictions on copying, modification, distribution or commercial use.

Do not describe third-party components as owned IP merely because they are embedded in the product. Explain the basis on which each important component is used.

6. Technical and creation evidence is organised

Legal documents may identify rights, but technical evidence helps a reviewer understand what the asset actually contains and how it relates to those documents.

Depending on the asset, useful material may include:

• dated design and development records;
• source-control history and release records;
• a defined source-code or model snapshot;
• architecture and dependency documentation;
• product specifications and user documentation;
• dataset descriptions and provenance records;
• testing, performance and security documentation;
• records of authors, inventors and contributors; and
• hashes or other integrity references for important files.

Technical material should be linked to the relevant asset version. A repository that changes every day should not be presented as a fixed review object without an identified snapshot or date.

This evidence supports traceability; it does not prove originality, non-infringement, legal ownership or technical performance by itself.

7. Commercial information is separated from legal status

Reviewers may also need to understand how the IP is used commercially. Relevant information can include:

• products and services that use the asset;
• active customers, licensees or distribution partners;
• royalty and revenue records;
• maintenance and development obligations;
• geographic and sector use;
• material supplier or platform dependencies; and
• known plans to discontinue, replace or materially modify the asset.

Keep commercial performance claims tied to their source and period. Revenue associated with a product does not necessarily equal revenue generated by a particular IP right. A recorded royalty rate, revenue figure or asking price is also not a valuation of the asset.

8. Risks, disputes and encumbrances are disclosed

A review-ready package should not contain only positive documents. It should identify known matters that may affect ownership, use, enforcement or transfer, such as:

• infringement allegations or freedom-to-operate concerns;
• ownership or inventorship disputes;
• oppositions, cancellation proceedings or validity challenges;
• expired or abandoned registrations;
• security interests, charges or insolvency issues;
• contractual restrictions on assignment or sublicensing;
• employee, contractor or former-founder claims;
• open-source compliance concerns;
• confidentiality or trade-secret exposure;
• privacy, data-protection or consent issues; and
• missing, unsigned or inconsistent documents.

Disclosing a known issue does not resolve it. It allows an authorised reviewer to understand its relevance and decide what additional investigation or professional advice is needed.

9. Confidential access is controlled

Some of the most important IP evidence may also be the most sensitive. Source code, unpublished patent material, algorithms, model information, customer agreements, trade secrets and security documentation should not automatically be placed in a public listing.

Before sharing:

1. separate public descriptions from confidential evidence;
2. remove unnecessary personal data and credentials;
3. redact information that is not needed for the review stage;
4. verify that disclosure is permitted under existing agreements;
5. use role-based or selected-party access;
6. use an NDA where appropriate; and
7. keep a record of what was shared, with whom and when.

The person preparing the package remains responsible for deciding whether they have authority to disclose the information.

A practical readiness checklist

Before inviting another party to review the asset, ask:

• Is the asset described precisely enough to identify it?
• Are owned and licensed elements separated?
• Can the claimed ownership history be followed?
• Are current official records and deadlines included?
• Are licences, assignments and restrictions summarised and linked?
• Are third-party components and dependencies identified?
• Is there a dated technical or documentary snapshot?
• Are commercial statements tied to supporting records?
• Are disputes, security interests and missing documents disclosed?
• Is confidential information protected by appropriate access controls?
• Does the package clearly distinguish recorded facts from user statements, estimates and professional conclusions?

If several answers are “no”, the asset may still be important, but it is not yet easy for another party to assess efficiently.

What DaDepo does—and does not do

DaDepo can help organise available documents, record their provenance, extract information and present a structured Asset Passport for review. Users review the information, correct errors and control how it is shared.

Preparing or publishing an Asset Passport does not mean that DaDepo has:

• confirmed ownership, validity or enforceability;
• completed an official IP registration or registry search;
• cleared third-party rights or infringement risks;
• authenticated every document, signature or contributor;
• confirmed that the asset or any licence is transferable;
• audited technical, financial or commercial claims;
• valued the IP or recommended a transaction; or
• guaranteed a buyer, licensee, revenue, price or successful transfer.

Important: DaDepo provides technology and information tools. It does not provide legal, intellectual-property, financial, investment, tax, accounting, technical-certification or valuation advice. Parties should perform their own due diligence and obtain appropriate professional advice.

Readiness is about clarity, not certainty

An IP asset is ready for review when another authorised person can understand what it is, why the presenting party says it controls the relevant rights, which documents support that position, which restrictions apply and what remains uncertain.

The purpose of preparation is not to make unresolved questions disappear. It is to make them visible, traceable and easier to investigate.

Further reading

• UK Intellectual Property Office: IP Health Check
• UK Government: Intellectual Property Policy Checklist
• UK Government: Knowledge Asset Commercialisation Guide
• EUIPO public register and help services