Ownership, Licensing and Assignment: What Do the Documents Show?

A person may possess a file, operate a product or receive revenue from an asset without owning every right connected to it. Another person may own a right but have granted someone else permission to use it. Ownership may also have moved through one or more assignments over time.

Understanding the difference between ownership, licensing and assignment is essential when preparing intellectual property, software, data, contractual rights or other document-backed assets for review.

Key point: Documents can support a rights position, but a document upload or registry entry does not by itself establish complete, current and enforceable ownership.

Three different questions

The three concepts answer different questions:

1. Ownership: Who holds the relevant right?
2. Licensing: Who has permission to use the right, and on what terms?
3. Assignment: Has ownership of all or part of the right been transferred to someone else?

A well-prepared asset package should identify which question each document addresses instead of placing every agreement under a general label such as “proof of ownership”.

Possession is not necessarily ownership

Holding a copy of a contract, source-code repository, model file, design, image, dataset or certificate does not necessarily mean that the holder owns the underlying rights.

For example:

• a company may use software under a licence;
• a customer may possess commissioned work while the creator retains some rights;
• a developer may have created code before assigning it to an employer or client;
• a distributor may market a product without owning its trade mark;
• a platform operator may have contractual access to data without owning the data or all related rights; and
• physical equipment and the intellectual property embodied in it may have different owners.

The relevant position depends on the type of right, applicable law, the identity and capacity of the parties, and the documents forming the chain of title.

What may support an ownership position?

Documents that may be relevant to ownership include:

• official registration or filing records for registered rights;
• creation records, dated drafts and source-control history;
• employment terms and internal intellectual-property policies;
• contractor, consultant and development agreements;
• deeds or agreements assigning rights;
• corporate acquisition, merger or restructuring documents;
• probate, insolvency, court or settlement documents;
• renewal and maintenance records; and
• correspondence acknowledging ownership or resolving an earlier gap.

No single item is automatically conclusive in every situation. A registration record may identify the registered proprietor but not disclose every underlying dispute, licence, security interest or unrecorded transaction. A development agreement may allocate rights, but a reviewer may still need to confirm that the correct parties signed it and that it covers the work being presented.

What does a licence show?

A licence generally gives another party permission to use specified rights without transferring ownership of those rights. The UK Intellectual Property Office, for example, describes an IP licence as an agreement between a rights owner and another party that permits an activity that might otherwise infringe the relevant rights.

A licence review may need to identify:

• the licensor and licensee;
• the exact rights, products, versions or materials covered;
• permitted and prohibited uses;
• whether the licence is exclusive, sole or non-exclusive;
• territory, customer group or field-of-use restrictions;
• start date, duration, renewal and termination rights;
• fees, royalties and reporting obligations;
• rights to modify, reproduce, distribute or commercialise;
• sublicensing and assignment rights;
• change-of-control provisions;
• confidentiality, data-use and security obligations;
• ownership of improvements, derivatives or new versions; and
• the effect of expiry or termination.

A licence to use an asset does not necessarily allow the licensee to sell the underlying right, grant sublicences or transfer the licence. Those powers should be checked against the actual agreement and applicable law.

What does an assignment show?

An assignment is intended to transfer ownership of all or a defined part of a right from an assignor to an assignee. It should be distinguished from a licence that permits use while ownership remains elsewhere.

An assignment document may need to show:

• the identities and authority of the parties;
• the rights being transferred;
• whether the transfer is complete or limited;
• relevant applications, registrations, contracts or asset identifiers;
• the effective date and any conditions;
• treatment of earlier infringements, accrued revenue or unpaid royalties;
• existing licences, security interests and other encumbrances;
• treatment of related materials, records, goodwill or domain names;
• consideration, where relevant;
• governing law and dispute provisions; and
• the required signatures and execution formalities.

Formal requirements differ by right and jurisdiction. As one example, UK Intellectual Property Office guidance states that a UK copyright assignment must be recorded in a written, signed document. Registered rights may also require or benefit from recording the transfer with the relevant official authority. The applicable requirements must be checked for the particular asset and jurisdiction.

Why chain of title matters

Chain of title is the documented sequence connecting the origin of a right to the person who currently claims to own or control it.

A simple chain might be:

1. an individual creates the work;
2. an agreement assigns specified rights to a company;
3. the company grants a limited licence to a customer; and
4. the company later transfers the remaining rights to another company.

The review becomes more difficult when a link is missing, inconsistent or wider than the rights a party actually held. Common warning signs include:

• work created by contractors without clear rights clauses;
• agreements signed after development was completed;
• conflicting company names or registration details;
• assignments that do not identify the relevant work or version;
• unsigned schedules or missing appendices;
• licences granted before a later assignment but not addressed in it;
• expired registrations or unpaid renewal fees;
• restrictions on transfer or sublicensing;
• security interests, insolvency or ongoing disputes; and
• rights claimed over third-party or open-source components.

A later document cannot safely be assumed to repair every earlier gap. The complete sequence and the applicable legal effect need to be assessed.

Software and AI assets may contain several layers of rights

Software, AI systems and digital products rarely involve only one right. A package may include:

• copyright in source code, documentation, interfaces and visual materials;
• contractual rights relating to hosted services or APIs;
• database rights and contractual controls over datasets;
• licences for open-source and third-party components;
• rights and restrictions relating to training data, model weights and outputs;
• trade marks, product names and domain names;
• patents or registered designs;
• confidential information, trade secrets and know-how; and
• customer, developer, employee and supplier agreements.

Ownership of one layer does not establish ownership of every other layer. For example, owning custom application code does not automatically give the owner unrestricted rights to embedded third-party software, training data or a provider's hosted model.

What the documents may not establish

Even a substantial evidence package may not prove that:

• every document is authentic, complete and current;
• each signatory had authority to bind the named party;
• the claimed owner originally acquired all relevant rights;
• no conflicting licence, assignment or security interest exists;
• the asset does not infringe third-party rights;
• confidential information or personal data was lawfully obtained;
• a licence or assignment remains valid after termination, insolvency or a corporate transaction;
• the right can be transferred in the proposed manner; or
• official records have been correctly updated in every relevant jurisdiction.

These are due-diligence questions. Some require searches of official registers, confirmation from counterparties or advice from qualified professionals.

Preparing a clearer evidence package

Before sharing an asset for review:

1. List each right separately. Avoid treating a product, company or project name as a single indivisible asset.
2. Identify the claimed owner. Use the correct legal entity name and explain its role.
3. Build a timeline. Connect creation, registration, licensing, assignment, renewal and dispute events.
4. Attach the complete instruments. Include referenced schedules, amendments and signature pages.
5. Record scope and restrictions. Highlight territory, duration, exclusivity, sublicensing and transfer limits.
6. Identify third-party components. Include relevant licences and usage conditions.
7. Check official records. Where relevant, compare the package with current registry information.
8. State known gaps and disputes. Do not present assumptions as confirmed facts.
9. Protect sensitive material. Redact unnecessary personal data and use controlled or NDA-based access for confidential agreements, source code, trade secrets and commercially sensitive terms.

What DaDepo does—and does not do

DaDepo can help organise documents, record their provenance, extract available information and present a structured history of the rights described by those documents. Users review the extracted information and control how the package is shared.

Creating an Asset Passport, uploading an agreement or recording a rights event does not mean that DaDepo has:

• established legal ownership or a complete chain of title;
• authenticated every document or signature;
• confirmed that a licence or assignment is valid or enforceable;
• registered a transfer with an official intellectual-property authority;
• cleared third-party rights or infringement risk;
• confirmed that an asset or licence is transferable; or
• provided a legal opinion, valuation or transaction recommendation.

Important: DaDepo provides technology and information tools. It does not provide legal, financial, investment, tax, accounting, intellectual-property or valuation advice. Parties should perform their own due diligence and obtain appropriate professional advice before relying on, licensing, acquiring or transferring rights.

Clear labels lead to better review

The most useful asset package does not simply declare “ownership”. It shows which rights are involved, who claims them, which documents support that position, what permissions have been granted, how the rights have moved and where uncertainty remains.

Separating ownership, licensing and assignment helps reviewers understand the actual transaction being considered—and the questions that still need answers.

Further reading

• UK Intellectual Property Office: Licensing intellectual property
• UK Intellectual Property Office: License and sell copyright
• UK Intellectual Property Office: Record a patent ownership transfer, licensee or security interest
• EUIPO Guidelines: transfers and changes of ownership