When a contractor claims ownership of the code: what it costs to be wrong
When a contractor claims ownership of the code, the immediate cost is control. You lose the right to modify, license or sell the software until ownership is settled. Deployment stalls, investors start asking questions, and every day of delay hands the contractor more negotiating leverage. The question stops being abstract once a client depends on the code.
The legal basis
Software written under a contract is protected as a literary work under Directive 2009/24/EC. The directive sets the default: copyright in a computer program belongs to the author, unless national law or a written agreement says otherwise. A contractor who wrote the code without a signed assignment clause keeps the rights by default, not the client who paid for the work.
National law implementing the directive typically requires that transfer to be recorded in writing, though the exact formalities differ between member states. A verbal understanding that "the client owns everything" rarely survives a dispute if nothing was signed.
This asymmetry surprises many clients. Code written by an employee within their employment typically vests in the employer by default. Code written by an independent contractor does not, unless the contract says so explicitly. The label on the relationship changes the starting point of the whole dispute.
If the disputed material includes a structured dataset built around the software, a second layer applies. Directive 96/9/EC protects databases separately, through copyright in the original selection and arrangement of the data and, in parallel, a sui generis right for substantial investment in compiling it. A contractor's claim can therefore reach further than the source code itself.
What changes once the claim lands
Every further use of the software becomes a question of authorisation. Continued deployment without a licence or an assignment turns routine business activity into a potential infringement, even if the software has been running in production for years without complaint.
Commercial conversations pause for the same reason. A buyer's counsel will ask for proof of clean title before signing anything, and a financing round slows down until that proof exists. A court asked to intervene can order the disputed use to stop while the ownership question is decided, which is the outcome every side wants to avoid.
The same problem surfaces during a sale of the business. Buyers run diligence specifically to catch unresolved ownership questions, and an open claim on core code can lower the price or stall the transaction until it is cleared.
The timeline compresses further if the contractor stops cooperating. Bug fixes, security patches and feature work that depend on their knowledge of the codebase freeze until the dispute is resolved, and the business absorbs that gap regardless of who turns out to be right.
Proving where the code came from
Ownership disputes are decided on provenance, not on who feels more entitled to the result. The party that can show, step by step, who wrote which part and when, starts the negotiation from a stronger position.
Repository history carries most of that proof. Commit logs, branch history and code review records show authorship with a timestamp that is hard to contest after the fact. Correspondence about scope, and invoices tied to specific deliverables, fill in the gaps that the repository alone does not answer.
Gaps in this record are common when work started informally, before any contract was signed, or when several contractors touched the same repository under different agreements. Reconstructing provenance after the fact takes longer and costs more than keeping the record as the work happens.
What to do next
Move in a fixed order. Do not renegotiate the fee before the ownership question is closed, and do not build new features on the disputed code while it remains unresolved.
| Step | Who acts | Typical timing |
|---|---|---|
| Locate the contract and check the assignment or licence clause | In-house counsel or contracted lawyer | Day 1 |
| Freeze further payments until ownership is confirmed in writing | Finance or management | Day 1–2 |
| Request written confirmation of authorship, including any subcontractors used | Project lead or procurement | Within a week |
| Preserve the repository history and correspondence as they stand | Engineering lead | Immediately |
| Draft an assignment deed or a licence agreement covering the disputed code | External counsel | 1–2 weeks |
| Escalate to negotiation, mediation or court if the contractor will not sign | External counsel | Depends on the response |
The same discipline applies whenever a counterparty tries to shift risk mid-negotiation. See A customer demands unlimited liability technology contract what it for a comparable pattern in a different contract fight.
Who decides, and on what evidence
Most disputes are resolved through negotiation between the parties, before either side reaches a court. If the contract names an arbitration forum, that clause controls the process. Otherwise, the competent national court decides, applying the contract terms in force and the conduct of the parties around the disputed work.
Evidence carries the case, not intent. Courts and arbitrators weigh the written contract, correspondence about scope, repository history showing who built what, and the payment record tied to specific deliverables. Verbal assurances rarely survive a dispute; what was signed and what was paid for do.
Mediation sits between the two options and is often faster than either. It does not bind the parties unless they agree, but it narrows the dispute before legal costs accumulate.
Verifying the underlying documentation matters just as much outside software disputes. A comparable evidentiary test applies to When the offering document is questioned in practice, where the paper trail decides the outcome in much the same way.
Cross-border complications
Many contractors work across borders, and the contract may name one country while the work happens from another. Which national law applies to the ownership question depends on the choice-of-law clause in the contract, or on the rules that apply in its absence. Get that answer before assuming your local rules cover the dispute.
Enforcement follows a similar pattern. A ruling obtained in one member state is not automatically the end of the matter if the contractor's assets sit somewhere else entirely.
Scenarios worth separating
If the contractor is a freelancer without a written assignment clause, the default rule under Directive 2009/24/EC favours them. They keep the rights until a signed transfer says otherwise, and negotiation from that position starts from a weaker point for the client.
If the contractor is a company or an agency, the picture splits into two layers. Its own staff may have assigned their rights to the company under local employment arrangements, but the agency's contract with your business is the document that decides what you actually received. Check both layers before assuming either one covers you.
If several contractors touched the same codebase under separate agreements, ownership can end up shared rather than singular. A joint claim is harder to negotiate than a single one, because every co-owner needs to agree before a clean licence can be granted.
If the disputed code contains third-party open-source components, ownership is often not the real question. Licence compliance is, and it survives the ownership dispute regardless of who wins it.
Sources and the limit of this page
This page sets out the ownership rule and the sequence of steps that follow a claim. It does not value the software, and it does not establish whether the contractor has assets worth pursuing if the dispute turns into a damages claim.
Those questions sit in a separate register of factual reports. See Asset in Belgium: what can be established for what an asset check can confirm before litigation starts.
If the dispute already produced a judgment and the other side is not paying, the relevant question changes entirely. See Debtor report after a judgment in practice for what that stage covers.
Verified
Checked: 4 March 2025. Sources: Directive 2009/24/EC on the legal protection of computer programs (EUR-Lex); Directive 96/9/EC on the legal protection of databases (EUR-Lex).
Related situations
A comparable ownership dispute plays out on the design side of a project. See When an agency keeps the design files in detail for the same sequence applied to visual and creative work, from missing assignment clauses to the negotiation that follows.
Frequently asked questions
What is the first step when a contractor claims ownership of the code?
Locate the contract and read the assignment or licence clause before anything else. Do not pay disputed invoices or build new work on the code until that clause is confirmed in writing.
Which deadline is already running?
The clock that matters most is operational rather than statutory. Every day without a signed assignment or licence is a day the business runs on unauthorised use, and that exposure compounds the longer it goes unaddressed.
Who decides, and on what evidence?
The forum named in the contract decides, or the competent national court if none is named. The evidence that carries weight is the written contract, correspondence on scope, repository history and the payment record tied to what was actually delivered.