Reconstructing a chain of title over a codebase: documents to prepare
A clean chain of title links every contributor to a codebase with a signed instrument that transfers or licenses their rights to the company. Reconstructing it after the fact means identifying every contributor, matching each one to a written agreement, and closing the gaps where no such agreement exists. The output is a single register, not a legal opinion.
Why the gap appears
Founders write code before the company exists. Contractors deliver modules against a one-line invoice with no mention of rights. Employees leave without ever signing an assignment clause, because the clause was assumed rather than drafted. Each of these situations creates a break in the chain that stays invisible until someone outside the company looks for proof.
The break rarely surfaces on its own. It appears when an acquirer, an investor, or a licensing counterparty asks for evidence of ownership and the file has none ready. Exit and transition planning for a technology deal usually starts with this exact question, and a codebase without a documented chain slows the whole process rather than stopping it outright.
Practical consequence
An incomplete chain does not void ownership. It shifts the burden onto the company at the worst possible moment: during a deal deadline, a licensing negotiation, or a dispute where a contributor claims a stake in code they once wrote. Buyers and investors treat an unfinished file as a discount on price and a delay on closing, not as a reason to walk away.
The cost of the gap grows with time. A missing signature from a contractor who left last year is a phone call. The same gap five years later, after the contractor has changed jobs twice, is a search.
What to do
Reconstruction follows a fixed sequence. Skipping a step does not save time; it moves the gap further down the file, where it costs more to close later.
| Step | What it produces | Typical source |
|---|---|---|
| List every contributor | Names, roles, dates of contribution | Commit history, payroll records, contractor invoices |
| Match each name to an agreement | Employment contract, contractor agreement, or founder undertaking | Company files, signed PDFs, email confirmations |
| Check the assignment clause | Confirmation that software rights, not only confidentiality, were transferred | The agreement itself |
| Flag missing or weak instruments | A ranked list of gaps by risk | Comparison of the previous two steps |
| Approach the missing parties | A signed confirmatory assignment or licence | Direct contact, sometimes through counsel |
| Close the file | A single register mapping contributor to instrument | Internal document management |
The register in the last row is the actual deliverable. Everything before it is preparation for that one document.
Who decides
Internal counsel, or whoever manages the transaction, decides whether the file is sufficient for the purpose at hand. A financing round sets a different bar than an internal audit. Where a contributor disputes the assignment, the matter leaves the file and moves into negotiation, and, if it stays unresolved, into a national court with jurisdiction over the agreement in question.
Forks
If every contributor worked as an employee under a written contract, the usual problem is the scope of the assignment clause, not its existence — older templates often cover inventions but not software specifically.
If contributions came from contractors invoiced through a foreign entity, the missing piece is frequently the choice of law governing the assignment, which changes how the clause is read and enforced.
If part of the codebase relies on open-source or third-party licensed components, ownership stops at the boundary of that licence. The reconstruction records the boundary rather than attempting to acquire rights that were never on offer.
If the other side does not respond
Non-response is common and rarely fatal on its own. What matters is how the attempt is documented.
- If the contributor is unreachable, a written record of the attempts to contact them protects the file even without a signature.
- If the contributor refuses to sign, the dispute is scoped and isolated rather than left to block the rest of the reconstruction.
- If the codebase also feeds a tokenised product, a missing consent affects downstream disclosure — see how secondary market arrangement token issuance runs in practice for how that disclosure is structured.
Timing
A file with clear records across a handful of contributors closes within a few weeks. A codebase built by dozens of contractors across several jurisdictions, with turnover among them, takes longer. The constraint is rarely legal complexity; it is the pace at which people respond to a request for a signature.
Limit
This page covers how the file is assembled, not what can be registered once it exists, and not what the codebase is worth once ownership is settled. Those questions sit in the reporting layer rather than in the procedure described here — see asset report italy for what a technology asset check can establish once the chain is closed.
Nor does this page cover the cost of acting on a wrong assumption before a write-off decision is made; that comparison belongs in debtor report before writing off: what it costs to.
Verified
Reviewed for procedural accuracy on the date shown in the page footer. This page describes internal file-building practice and does not cite external statutory sources; the substantive software and database protection regimes are addressed on other pages of this section.
Related publications
A related gap shows up in database rights, where the missing records usually concern the underlying data set rather than the code itself — see database rights audit: documents to prepare.
FAQ
How long does reconstructing a chain of title over a codebase take in practice?
Weeks for a small, well-documented team. Months where contributors are numerous, dispersed, or slow to respond. Building the register itself takes little time once every agreement has been located.
Which documents are needed to start?
A contributor list, whatever employment or contractor agreements exist, and the commit or version-control history showing who wrote what. Everything else in the process follows from comparing these three.
What happens if the other side does not respond?
The gap gets documented rather than ignored. A written record of the attempt to obtain a signature, kept in the file, is often enough to satisfy a counterparty even without the signature itself.