Reconstructing a chain of title over a codebase: what the decision maker looks at
When a codebase changes hands — through a sale, a financing round, or a licence — the decision maker first reconstructs who actually holds the rights. That means tracing authorship, employment or contractor status, and every assignment document, then flagging any missing link. A gap does not resolve itself; it becomes the single item that stalls the deal.
What the decision maker checks, stage by stage
The review moves through a fixed sequence. Skipping a stage does not save time; it only moves the risk further down the process, usually to a worse moment.
| Stage | What is checked | Typical evidence |
|---|---|---|
| Authorship mapping | Who wrote each module, and under what status: employee or contractor | Commit history, HR records, service agreements |
| Assignment trail | Whether rights moved in writing from the author to the company | Signed assignment, or an IP clause in the underlying contract |
| Third-party components | Open-source or licensed code embedded in the base | Dependency list, licence text for each component |
| Corporate history | Mergers, spin-offs, or transfers between related entities | Transfer agreements, board resolutions |
| Gap resolution | Missing signatures, oral arrangements, lapsed contractors | Retrospective assignment, written declaration, or a disclosed risk note |
Each row can pass on its own and the overall chain can still fail. A single missing signature from a former contractor is enough to reopen the whole file.
Practical consequence for timing and risk
A clean chain adds little to the timetable. A broken one adds weeks, because the fix usually depends on a person who is no longer under contract and has no reason to answer quickly. The review therefore tends to surface at exactly the wrong moment — A proof of concept becomes production technology contract the, and the ownership question that was theoretical during development becomes commercial the day the codebase goes live.
Risk shifts to whoever needs the chain to be clean: the buyer, the investor, or the licensing partner. The seller rarely has an incentive to find gaps on their own initiative.
What to do
- Collect every contract, assignment and non-disclosure agreement from each contributor — the client's legal or HR function gathers the file.
- Map each code module to its author and contractual status — IP counsel performs the mapping against commit history.
- List third-party and open-source components embedded in the codebase — a technical lead compiles the dependency list.
- Request any missing assignment before the deal closes, not after — the counterparty's counsel issues the request.
- Record any unresolved gap as a disclosed risk in the file, rather than leaving it unmentioned.
Who decides
There is usually no court at this stage. The decision rests with the acquiring party's investment committee, or with the licensing counterparty's approval process. A court becomes relevant only if a gap hardens into a dispute over who actually owns a specific module — at which point reconstruction turns from due diligence into evidence.
Two common forks
If the codebase was written entirely by employees under standard employment terms, the chain is usually straightforward. Confirm that employment dates line up with the commit history and move on.
If contractors were involved at any stage, the missing assignment clause is the single most common gap. Treat every contractor period as a point requiring separate verification, not as covered by the general employment file.
If the codebase underpins a token issuance, a second process runs in parallel and cannot be skipped: the Classification assessment: stages and deadlines determines how the asset itself is treated, independently of who owns the underlying code.
Where this page stops — sources and limit
This page does not value the codebase, resolve an existing ownership dispute, or replace a full audit report. It describes the sequence a decision maker follows before either of those becomes relevant.
Where the reconstruction needs to be documented for a counterparty rather than kept internal, structured evidence from public and access-controlled sources fills gaps that internal files leave open — for example, an Asset report poland where corporate history needs external confirmation.
A parallel check on the other side's standing, where the counterparty's own position matters to the deal, can be run through a Debtor in United Kingdom explained report.
The steps described reflect our own procedural practice in handling this type of file and are not tied to a specific statutory provision. Reviewed against current internal practice in 2025.
Related reading
A comparable question arises for structured data rather than code: see Database rights audit: what the decision maker looks at for how a decision maker approaches a similar chain over a database.
FAQ
How long does reconstructing a chain of title over a codebase take in practice?
A clean file with cooperative contributors can be closed within days. A file with a lapsed contractor or a missing signature typically adds two to four weeks, depending on how quickly that person responds.
Which documents are needed to start?
Employment contracts, contractor agreements, any assignment deeds, the dependency and licence list for third-party components, and commit history covering the relevant period.
What happens if the other side does not respond?
The gap is recorded as a disclosed risk rather than left silent. Depending on the deal, the parties either proceed with the risk allocated in the agreement, or the closing is held until a retrospective assignment is obtained.
If your codebase file has a gap that internal records cannot close on their own, we can look at what is missing and what closing it actually requires.