Intellectual Property Clause in an SOW: Assignment or License – Complete 2026 Guide

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

When a company orders software development, a study, a design, or any other intellectual service from a freelancer or B2B service provider, it typically signs a Statement of Work (SOW). This contractual document details the deliverables, deadlines, and budget. Yet one clause often goes unnoticed despite conditioning 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?" may remain legally ambiguous for years — until a dispute, fundraising round, or 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 modifications) and to freelancers or external service providers: absent a contrary clause, the service provider retains rights to their creations.

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

Assignment vs. License: Two Legally Distinct Mechanisms

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

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

The omission of any single element renders the assignment unenforceable against the unmentioned right. This legal formalism is frequently underestimated in hastily drafted SOWs.

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

Source Code and Software: A Special Legal Regime

Software is an intellectual creation 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 execution of an employment contract (art. L.113-9 CPI). Conversely, for an independent service provider, moral rights remain complete and inalienable.
• Delivery of source code is distinct from assignment of rights to that code. A client may receive an executable without ever obtaining the source code, nor adaptation rights. The IP clause must therefore distinguish: functional deliverable, source files, technical documentation, deployment scripts, databases.
• Third-party open-source libraries integrated into the deliverable (React, PostgreSQL, TensorFlow…) remain subject to their own licenses (MIT, Apache 2.0, GPL). An IP clause cannot transfer rights that the service provider does not own. The clause must therefore include a list of third-party components and their licenses, on pain of creating an impossible warranty obligation.

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

Structuring the IP Clause in an SOW: Essential Building Blocks

A robust IP clause in a B2B SOW revolves around five distinct blocks. Omitting them leaves blind spots that transform into disputes.

1. Definition of 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 nor 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 patches.

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 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 to this background IP;
• Grant the client a limited license to use the background IP insofar as necessary for exploitation of the deliverable.

Without this block, a service provider could theoretically claim destruction of the delivered product because it incorporates a module they own — and for which no assignment has been granted.

3. Transfer Mechanism and Suspensive Conditions

In B2B practice, assignment of rights is often subject to full payment of the fee. This classic suspensive condition protects the service provider but must be drafted with care: if not explicit, consistent case law deems rights transferred upon delivery (Cass. 1st civ., October 14, 2010, appeal no. 09-16.385).

The clause must specify:

• The transfer date (delivery, acceptance, full payment);
• Any formalities (separate assignment deed, INPI filing);
• The treatment of rights if the contract is terminated for cause.

The AI-powered contract generator from Certyneo offers customizable IP clause templates based on deliverable type and chosen transfer model.

4. Warranties of Originality and Indemnification

The service provider must warrant that deliverables are original (within the meaning of art. L.111-1 CPI), do not incorporate third-party works without authorization, and violate no patent, trade secret, or competing right. This warranty against eviction must be completed by an indemnification obligation to the client in case of third-party claims, with a reasonable cap (often equal to the SOW amount).

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 on the deliverable. This waiver must be explicit and limited: one does not waive moral rights in bulk; rather, one contractually restricts their exercise case by case.

Freelancer vs. Service Provider in Corporate Form: Impact on IP Clause

The legal status of the service provider substantially modifies drafting of the IP clause.

Freelancer (sole proprietor or individual enterprise): the creator is a natural person holding copyright in their personal capacity. The assignment must scrupulously comply with the formalism of art. L.131-3 CPI. Moral rights are fully active. The risk of reclassification as an employment contract (and thus application of art. L.113-9 CPI for software) exists if the relationship of subordination is established.

Service Provider in Corporate Form (SARL/SAS): the company is not an author within the meaning of the CPI — its employees are. A corporate service provider must therefore contractually warrant that it has itself obtained assignment (or license) from its employee-authors. A clause stating "the service provider warrants owning all necessary rights to grant this assignment" is insufficient unless backed by adapted employment contracts.

These subtleties justify having the IP clause in an SOW reviewed by a specialized lawyer before signature. Certyneo's electronic signature solution for law firms facilitates validation and signature of these complex contracts in a streamlined process.

Best Practices for 2026: Operational Management of IP Rights

Attach a List of Third-Party Components

Any software development SOW should integrate a Software Bill of Materials (SBOM) annex, listing all open-source components used, their versions, and licenses. This practice, recommended by ANSSI in its secure development guides, reduces the risk of license violation (notably GPL contamination) and facilitates due diligence during fundraising or company sales.

Provide a Mechanism for Evidential Deposit

Depositing the work with the INPI (via Certyneo's INPI hub) or with a trusted third party creates a presumption of creation date and priority. In case of dispute over authorship or originality of a deliverable, this deposit constitutes evidence opposable to third parties.

Audit and Verification Clause

For lengthy engagements or master service agreements, incorporate a clause permitting the client to have the source code audited by an independent third party — without this constituting a violation of the service provider's trade secrets — strengthens confidence and prevents late disputes over deliverable compliance.

Electronic Signature and Traceability

An SOW containing a sensitive IP clause should be signed with maximum evidentiary value. Use of an advanced or qualified electronic signature compliant with eIDAS creates qualified timestamping and a cryptographic fingerprint of the document, making any subsequent alteration detectable. This traceability is determinative when the IP clause is invoked years after signature.

Applicable Legal Framework for the IP Clause in an SOW

Intellectual Property Code (CPI)

The IP clause in an SOW operates within the French Intellectual Property Code, whose mandatory provisions cannot be waived by contract:

• Art. L.111-1 CPI: copyright vests with the creator upon creation of the work, without formality. This principle is fundamental: absent a clause, the service provider retains ownership.
• Art. L.113-9 CPI: for software created by employees in the exercise of their duties, economic rights pass to the employer by operation of law. 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 limited contractual waiver.
• Art. L.131-3 CPI: any assignment of economic rights must state each assigned right, its scope, purpose, location, and duration, on pain of partial unenforceability.
• Art. L.122-6 CPI: specific software rights include reproduction, translation/adaptation, any form of distribution, and placing on the market.

General Contract Law

The SOW is a contract for hire of work (art. 1710 French Civil Code) governed by general law of obligations. Article 1103 C.civ. recalls that "contracts lawfully formed take the place of law for those who made them." The IP clause cannot derogate from mandatory provisions of the CPI, but it may freely arrange the conditions of transfer of economic 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, under French law, by articles 1366 and 1367 of the Civil Code concerning electronic writing and electronic signature. A qualified electronic signature benefits from an irrebuttable presumption of reliability and enjoys the same evidential force as a handwritten signature. It guarantees document integrity and signer identity, essential elements 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 authorization from the author.
• Risk of third parties claiming rights: an employee of the service provider may assert rights if internal contracts are deficient.
• Risk in due diligence: during a fundraising round or M&A, absence of a clear IP clause on software assets may result in a valuation discount, conditional earn-out, or deal abandonment.
• Risk of open-source license violation: undisclosed integration of GPL-licensed components may contaminate the entire delivered software (copyleft effect), obliging open-source code disclosure.

Usage Scenarios: IP Clause in Real Situations

Scenario 1 — A Scale-up SaaS Outsources Backend Development

A French scale-up specializing in fleet vehicle management employs ten developers and outsources development of its invoicing API to an independent service provider (SASU). The SOW provides for assignment of "all rights to deliverables" but mentions neither geographic scope nor duration, and lists no integrated open-source components.

Eighteen months later, during a Series A fundraising round, the investor's counsel discovers in due diligence that the API integrates an undeclared LGPL-licensed library, and the rights assignment is partially unenforceable due to missing legal statements. Closing is delayed six weeks. Costs for regularization (new assignment deed, SBOM audit, library replacement) total approximately €18,000, not counting the risk of valuation renegotiation.

Lesson: a complete IP clause and SBOM annex from 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 causes of closing delays in transactions below €10M.

Scenario 2 — A Consulting Firm Orders Training Deliverables from a Freelancer

A consulting firm specializing in digital transformation, with about twenty consultants, orders creation of e-learning training materials (videos, slides, interactive quizzes) from a freelance graphic designer via an €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 materials adapted to a banking sector client. The freelancer, whose moral right to integrity of the work remains intact, objects, contending that modifications distort her work. A settlement protocol is concluded for an additional €4,500.

Lesson: absence of a waiver clause for the integrity right and an explicit right to commercial adaptation and modification generated an unforeseen cost of 37% of the initial SOW amount. Precise drafting of the assignment scope (including the right to adapt and commercialize to third parties) is non-negotiable for deliverables with high reuse potential.

Scenario 3 — An Industrial SME Integrates Custom Software Into Its Production Line

An industrial SME with 80 employees orders from an integrator a production-line supervision software (MES). The SOW provides for an exclusive license but does not specify whether the client may evolve the software itself or via a third party after the maintenance contract ends.

Three years later, the integrator ceases business. The SME finds itself without access to the source code and without contractual right to entrust its maintenance to another service provider. Operational restoration requires a partial rewrite estimated at €60,000, corresponding to production interruption of several weeks.

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

Conclusion

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

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

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