Intellectual Property Clause in a SOW: Assignment or Licence – 2026 Guide

Why the IP clause is the most strategic clause in a SOW

When a company commissions software development, a study, a design or any other intellectual service from a freelancer or B2B service provider, it generally signs a Statement of Work (SOW). This contractual document details the deliverables, deadlines and budget. Yet one clause often goes unnoticed even though it underpins the entire economic value of the transaction: the intellectual property clause (IP clause).

Without precise drafting of this clause, the answer to the question "who owns the delivered source code?" can remain legally ambiguous for years — until a dispute, a capital raise or a company sale forces an expensive resolution. In France, Article L.111-1 of the Intellectual Property Code (CPI) establishes the principle that copyright vests with the creator. This principle applies equally to employees (with certain modifications) and to freelancers or external service providers: in the absence of a contrary clause, it is the service provider who retains the rights to their creations.

Within the framework of a well-structured SOW, the IP clause is not limited to a single line stating "rights are assigned to the client". It must specify the exact scope of deliverables, the method of transfer (assignment or licence), geographic and temporal extent, and the treatment of pre-existing works (background IP).

Assignment vs Licence: two legally distinct mechanisms

Assignment of patrimonial rights (art. L.131-3 CPI) permanently transfers ownership of the rights to the assignee. The service provider loses all control over future exploitation of the work. To be valid, the assignment must explicitly state:

• the nature of rights assigned (reproduction, performance, adaptation, translation, distribution, etc.);
• geographic scope (France, European Union, worldwide);
• duration (limited to 70 years post-mortem of the author at most, under art. L.123-1 CPI);
• purpose (commercial use, SaaS, resale, integration into a third-party product, etc.).

The omission of even one of these elements renders the assignment ineffective for the unmentioned right. This legal formality is frequently underestimated in hastily drafted SOWs.

A licence is less radical: the service provider retains intellectual property ownership but grants the client a defined right of use. The licence may be exclusive or non-exclusive, revocable or irrevocable, free or paid. In a B2B software development context, an exclusive irrevocable licence with no time limitation can produce effects practically equivalent to an assignment, while allowing the service provider to retain their moral rights.

Source code and software: a special legal regime

Software is a work of the mind under the CPI (art. L.112-2, 13°), but it benefits from a derogatory regime on several points:

• Moral rights are considerably weakened for software created in the execution of an employment contract (art. L.113-9 CPI). However, for an independent service provider, moral rights remain full and inalienable.
• Delivery of source code is distinct from assignment of rights over that code. A client may receive an executable without ever possessing the source code or the right to adapt it. The IP clause must therefore distinguish: functional deliverables, source files, technical documentation, deployment scripts, databases.
• Third-party open source libraries integrated into the deliverable (React, PostgreSQL, TensorFlow…) remain subject to their own licences (MIT, Apache 2.0, GPL). An IP clause cannot transfer rights that the service provider does not hold. The clause must therefore include a list of third-party components and their licences, on pain of creating a warranty obligation that is impossible to fulfil.

To secure these transactions, recourse to qualified electronic signature guarantees the integrity and certain date of the signed SOW, elements that are decisive in the event of judicial challenge.

Structuring the IP clause in a SOW: the essential building blocks

A robust IP clause in a B2B SOW is built around five distinct blocks. Overlooking any of them leaves blind spots that can turn into disputes.

1. Definition of the scope of covered deliverables

The first block precisely lists what the clause covers: source code, mockups, databases, algorithms, documentation, unit tests, automation scripts. The formula "all deliverables produced under this SOW" is insufficient: it does not cover derivative works created after final delivery or iterative improvements to an initial deliverable.

Provide a contractual definition of the term "Deliverable" at the head of the SOW, broad enough to encompass successive versions and bug fixes.

2. Background IP clause (pre-existing works)

Every service provider brings reusable components to each engagement: in-house frameworks, generic modules, proprietary libraries. These elements constitute the background IP or pre-existing IP. The clause must clearly:

• Identify the background IP that the service provider brings;
• Confirm that the client acquires no rights over this background IP;
• Grant the client a limited licence to use the background IP insofar as necessary to exploit the deliverable.

Without this block, a service provider could theoretically claim destruction of the delivered product because it integrates a module over which they retain ownership — and to which no assignment has been granted.

3. Transfer mechanism and suspensive conditions

In B2B practice, assignment of rights is often conditional upon full payment of the price. This standard suspensive condition protects the service provider but must be drafted carefully: if not explicit, settled case law holds that rights are transferred upon delivery (Cass. 1re civ., 14 October 2010, appeal no. 09-16.385).

The clause must specify:

• The date of transfer (delivery, acceptance, full payment);
• Any formalities (separate assignment deed, INPI registration);
• The treatment of rights in case of contract termination for breach.

The AI-powered contract generator from Certyneo offers IP clause templates that can be tailored according to the type of deliverable and the transfer model chosen.

4. Warranties of originality and indemnification

The service provider must warrant that the deliverables are original (within the meaning of art. L.111-1 CPI), do not borrow from third-party works without authorisation, and do not infringe any patent, trade secret or competing right. This warranty of non-infringement must be supplemented by an indemnification obligation to the client in case of third-party claims, with a reasonable cap (often equal to the amount of the SOW).

5. Moral rights and attribution notices

Moral rights are perpetual and inalienable under French law (art. L.121-1 CPI). The service provider may nevertheless contractually waive the exercise of certain prerogatives — notably the right to attribution of their name to the deliverable. This waiver must be explicit and limited: one does not waive moral rights in bulk, but rather contractually restricts their exercise on a case-by-case basis.

Freelancer vs corporate service provider: impact on the IP clause

The legal nature of the service provider materially affects the drafting of the IP clause.

Freelancer (micro-entrepreneur or sole trader): the creator is a natural person who holds copyright personally. The assignment must scrupulously comply with the formality of art. L.131-3 CPI. Moral rights are fully active. The risk of requalification as an employment contract (and thus application of art. L.113-9 CPI for software) exists if subordination is established.

Corporate service provider (SARL/SAS): the company is not an author under the CPI — its employees are. The corporate service provider must therefore contractually warrant that it has itself obtained the assignment (or licence) from its employee-authors. A clause such as "the service provider warrants that it holds all rights necessary to grant the present assignment" is insufficient if it is not supported by adapted employment contracts.

These subtleties justify that the IP clause of a SOW be reviewed by a specialised legal counsel before signature. Certyneo's electronic signature solution for law firms facilitates the validation and signature of such complex contracts in streamlined workflows.

Best practices 2026 for operational management of IP rights

Attach a list of third-party components

Every software development SOW should integrate a Software Bill of Materials (SBOM) annex, listing all open source components used, their versions and their licences. This practice, recommended by ANSSI in its secure development guides, reduces the risk of licence violation (in particular GPL contamination) and facilitates due diligence during capital raises or company sales.

Provide for a probationary deposit mechanism

Deposit of the work with the INPI (via Certyneo's INPI hub) or with an independent third party creates a presumption of the date of creation and prior rights. In the event of a dispute over the authorship or originality of a deliverable, this deposit constitutes evidence that can be invoked against third parties.

Audit and verification clause

For long-term engagements or framework contracts, incorporate a clause allowing the client to have the source code audited by an independent third party — without this constituting a breach of the service provider's trade secrets — strengthens trust and prevents late disputes over deliverable compliance.

Electronic signature and traceability

A SOW containing a sensitive IP clause must be signed with maximum probative value. The use of an advanced or qualified electronic signature compliant with eIDAS creates a qualified timestamp and cryptographic fingerprint of the document, making any subsequent alteration detectable. This traceability is decisive when the IP clause is invoked years after signature.

Legal framework applicable to the intellectual property clause in a SOW

French Intellectual Property Code (CPI)

The IP clause in a SOW operates within the framework of the French Intellectual Property Code, whose mandatory provisions cannot be overridden by contract:

• Art. L.111-1 CPI: copyright vests with the creator upon the creation of the work, without formality. This principle is cardinal: in the absence of a clause, the service provider retains ownership.
• Art. L.113-9 CPI: for software created by employees in the performance of their duties, patrimonial rights are vested of right in the employer. This regime does not apply to independent service providers.
• Art. L.121-1 CPI: moral rights (attribution, integrity, disclosure) are perpetual, inalienable and imprescriptible. Only the exercise of certain prerogatives may be subject to contractual waiver.
• Art. L.131-3 CPI: any assignment of patrimonial rights must mention each right assigned, its scope, its purpose, its location and its duration, on pain of partial ineffectiveness.
• Art. L.122-6 CPI: specific rights in software include reproduction, translation/adaptation, any form of distribution and placing on the market.

General contract law

The SOW is a contract for work or services (art. 1710 of the Civil Code) subject to general law of obligations. Article 1103 of the C.civ. reminds us that "contracts lawfully entered into are binding upon those who have made them". The IP clause cannot derogate from mandatory provisions of the CPI, but it may freely arrange the conditions for transfer of patrimonial rights.

eIDAS Regulation no. 910/2014 and electronic evidence

Electronic signature of the SOW is governed by eIDAS Regulation no. 910/2014 (art. 25: legal effect of electronic signature) and, in French law, by Articles 1366 and 1367 of the Civil Code relating to electronic documents and electronic signatures. A qualified electronic signature benefits from an irrefutable presumption of reliability and has the same probative force as a handwritten signature. It guarantees the integrity of the document and the identity of the signatory, elements essential when the IP clause is invoked in court.

Risks if clause is absent or deficient

• Risk of blocked exploitation: the client cannot legally exploit the deliverable without the author's permission.
• Risk of third parties claiming rights: an employee of the service provider may claim rights if internal contracts are deficient.
• Risk in due diligence: during a capital raise or M&A, the absence of a clear IP clause on software assets can result in a discount, conditional earn-out or abandonment of the transaction.
• Risk of open source licence violation: undeclared integration of GPL-licensed components may contaminate the entire delivered software (copyleft effect), requiring disclosure of the source code as open source.

Use scenarios: the IP clause in real situations

Scenario 1 — A scale-up SaaS outsources backend development

A French scale-up specialising in fleet management outsources development of its billing API to an independent service provider (SASU). The SOW provides for assignment "of all rights to the deliverables" but mentions neither geographic scope nor duration, and does not list integrated open source components.

Eighteen months later, during a Series A capital raise, the investor's counsel discovers in due diligence that the API integrates an undeclared LGPL-licensed library, and that the assignment of rights is partially ineffective due to missing legal mentions. Closing is delayed by six weeks. The costs of regularisation (new assignment deed, SBOM audit, library replacement) amount to approximately €18,000, not counting the risk of valuation renegotiation.

Lesson: a complete IP clause and a SBOM annex from the time of SOW signature would have prevented this blockage. According to sector reports on tech M&A, defects in the IP chain represent between 15% and 25% of the causes of closing delays in transactions under €10 million.

Scenario 2 — A consulting firm commissions training deliverables from a freelancer

A consulting firm with about twenty consultants specialising in digital transformation commissions a freelance graphic designer to create e-learning training materials (videos, slides, interactive quizzes) via a €12,000 SOW. The IP clause provides for assignment, but the right to modify the materials (adaptation for other clients) is not explicitly mentioned.

Six months after delivery, the firm wishes to resell these adapted materials to a banking sector client. The freelancer, whose moral right of integrity over the work is intact, objects, arguing that the modifications distort her work. A settlement agreement is reached for an additional €4,500.

Lesson: the absence of a clause waiving the exercise of the right of integrity and an explicit right to adapt commercially generated unexpected costs of 37% of the initial SOW amount. Precise drafting of the scope of assignment (including the right to adapt and commercialise to third parties) is non-negotiable for deliverables with strong potential for reuse.

Scenario 3 — An industrial SME integrates custom software into its production line

An industrial SME with 80 employees commissions an integrator to supply production line supervision software (MES). The SOW provides for an exclusive licence to use but does not specify whether the client can evolve the software itself or via a third party after the maintenance contract ends.

Three years later, the integrator ceases operations. The SME is left without access to the source code and without a contractual right to have maintenance entrusted to another service provider. Restoration to operational status requires partial rewriting estimated at €60,000, corresponding to production downtime of several weeks.

Lesson: for mission-critical industrial software, the IP clause must imperatively include a source code escrow clause (deposit with an independent third party) and an explicit right to maintenance by third parties in case of service provider default. These clauses are now recommended by professional IT federations (Syntec Numérique) for any bespoke development exceeding €20,000.

Conclusion

The intellectual property clause is the strategic heart of any SOW involving digital deliverables. It determines who actually owns the value created: without precise drafting, the client exploits without clear title, and the service provider is exposed to future claims. The three pillars of a robust IP clause in 2026 remain constant: exhaustively define the covered deliverables, choose and formalise the transfer mechanism (assignment or licence) in compliance with the formality of art. L.131-3 CPI, and anticipate the treatment of background IP and third-party components.

Signed with an eIDAS-compliant electronic signature solution, the SOW becomes a document with maximum probative value, enforceable in all circumstances. Certyneo enables you to sign, timestamp and archive your SOWs in minutes, with a validation workflow customisable for your legal and procurement teams.

Start for free on [certyneo.com/signup](/signup) and secure your next service contracts with the traceability they deserve.