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

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

When a company commissions software development, a study, 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 deliverables, deadlines and budget. Yet one clause often goes unnoticed even though it determines 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 source code delivered?" can remain legally ambiguous for years — until the day a dispute, fundraising or company sale forces an expensive answer. In France, Article L.111-1 of the Code of Intellectual Property (CPI) establishes the principle that copyright is born in the hands of the creator. This principle applies equally to employees (with modifications) and to freelancers or external service providers: in the absence of a contrary clause, it is the service provider who retains ownership of 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), the geographical and temporal extent, as well as the fate 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 mention:

• the nature of rights assigned (reproduction, performance, adaptation, translation, distribution, etc.);

• the geographical scope (France, European Union, worldwide);

• the duration (limited to 70 years after the author's death at maximum, under art. L.123-1 CPI);

• the purpose (commercial use, SaaS, resale, integration into a third-party product, etc.).

The omission of even one of these elements renders the assignment unenforceable as to the right not mentioned. 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. A licence may be exclusive or non-exclusive, revocable or irrevocable, free or paid. In a B2B software development context, an exclusive irrevocable licence without duration limitation can produce effects practically equivalent to an assignment, whilst allowing the service provider to retain their moral right.

Source code and software: a particular legal regime

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

• The moral right is considerably weakened for software created in performance of an employment contract (art. L.113-9 CPI). Conversely, for an independent service provider, the moral right remains intact and inalienable.

• The delivery of source code is distinct from the assignment of rights to that code. A client may receive an executable without ever owning the source code or adaptation rights. The IP clause must therefore distinguish between: functional deliverable, source files, technical documentation, deployment scripts, databases.

• Third-party open source libraries integrated into the deliverable (React, PostgreSQL, TensorFlow, etc.) remain subject to their own licences (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 licences, failing which it creates an impossible-to-fulfil warranty obligation.

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

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

A robust IP clause in a B2B SOW revolves around five distinct building blocks. Overlooking them leaves blind spots that transform 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 within the scope of 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 corrections.

2. Background IP clause (pre-existing works)

Every service provider brings reusable components to each assignment: 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 licence to use the background IP to the extent necessary for the exploitation of the deliverable.

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

3. Transfer mechanism and suspensive conditions

In B2B practice, the assignment of rights is often subject to payment in full of the price. This standard condition precedent protects the service provider but must be drafted with care: without an express assignment clause, nothing is transferred to the client: the assignment of copyright must distinctly specify each right assigned, its scope, its purpose, its territory and its duration (article L. 131-3 of the French Intellectual Property Code), failing which the rights remain with the service provider.

The clause must specify:

• The transfer date (delivery, acceptance, full payment);

• Any formalities (separate assignment deed, INPI filing);

• The fate of rights in case of contract termination for fault.

The Certyneo AI contract generator offers parameterizable IP clause templates according to the type of deliverable and the chosen transfer model.

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 authorization, and violate no patent, trade secret or competing right. This warranty against eviction must be supplemented by an obligation of indemnification of the client in the event of a third-party claim, with a reasonable cap (often equal to the amount of the SOW).

5. Moral right and attribution notices

Moral right is 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 right in bulk; one contractually restricts its exercise on a case-by-case basis.

Freelancer vs service provider in company: impact on the IP clause

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

Freelancer (micro-entrepreneur or sole proprietorship): the creator is a natural person, holder of copyright rights in a personal capacity. The assignment must scrupulously respect the formality of art. L.131-3 CPI. Moral rights are fully active. The risk of recharacterization 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 SARL/SAS: the company is not an author within the meaning of the CPI — its employees are. The service provider in corporate form must thus contractually guarantee 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 necessary rights to consent to this assignment" is insufficient unless it is supported by adapted employment contracts.

These subtleties justify that the IP clause of a SOW be reviewed by a specialized legal counsel before signature. The electronic signature solution for law firms from Certyneo facilitates the validation and signature of these complex contracts in short order.

Best practices for 2026 in operational management of IP rights

Annex 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 (notably GPL contamination) and facilitates due diligence during fundraising or business sales.

Provide a mechanism for evidential deposit

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

Audit and verification clause

For lengthy assignments or framework contracts, incorporating a clause allowing 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

A SOW containing a sensitive IP clause must be signed with maximum evidentiary value. The 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 decisive when the IP clause is invoked years after signature.

Legal framework applicable to the intellectual property clause in a SOW

Code of Intellectual Property (CPI)

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

• Art. L.111-1 CPI: copyright is born in the hands of the creator at the moment of 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 exercise of their functions, patrimonial rights are devolved as of right to the employer. This regime does not apply to independent service providers.

• Art. L.121-1 CPI: moral right (attribution, integrity, disclosure) is perpetual, inalienable and imprescriptible. Only the exercise of certain prerogatives may be the subject of a limited contractual waiver.

• Art. L.131-3 CPI: any assignment of patrimonial rights must mention each right assigned, its scope, its purpose, its place and duration, failing which it is partially unenforceable.

• Art. L.122-6 CPI: the specific rights attaching to software include reproduction, translation/adaptation, any form of distribution and putting on the market.

Common contract law

The SOW is a contract for work (art. 1710 French Civil Code) subject to common law of obligations. Article 1103 of the French Civil Code reminds us that "contracts legally entered into take the place of law for 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

The 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 French Civil Code relating to electronic documents and electronic signatures. A qualified electronic signature benefits from an irrebuttable presumption of reliability and has the same probative force as a handwritten signature. It guarantees document integrity and signatory identity, 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 authorization from the author.

• 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 fundraising or M&A, the absence of a clear IP clause on software assets may 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), obliging disclosure of the source code in open source.

Illustrative use-case scenarios: the IP clause

Scenario 1 — A French scale-up outsources its backend development

These scenarios are illustrative: they describe typical situations and do not report any measured outcome from a client. A French scale-up specialising in vehicle fleet management employs around ten developers and outsources the development of its billing API to an independent contractor (SASU). The SOW provides for an assignment of "all rights in the deliverables" but mentions neither the geographical scope nor the duration, and does not list the open-source components integrated.

Some time later, during a Series A fundraising round, the investor's lawyer may discover during due diligence that the API incorporates an undeclared LGPL-licensed library, and that the assignment of rights is partially unenforceable for lack of required legal particulars. Closing may then be delayed. The costs of rectification (new assignment deed, SBOM audit, replacement of the library) can be significant, not to mention the risk of renegotiating the valuation. Their scale is to be assessed case by case, on the actual scope concerned.

Lesson: a complete IP clause and an SBOM appendix from the signing of the SOW onwards can help avoid this type of blockage. Gaps in the IP chain are among the possible causes of closing delays in technology transactions.

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

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

A few months after delivery, the firm wishes to resell these adapted materials to a client in the banking sector. The freelancer, whose moral right to the integrity of the work remains intact, may object, considering that the modifications distort her work. A settlement agreement, at an additional cost, then becomes necessary.

Lesson: the absence of a waiver of the right to invoke the integrity right and of an explicit right of commercial adaptation can generate an unforeseen cost, to be negotiated after the event. Precise drafting of the scope of assignment (including the right of adaptation and commercialisation 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 of 80 employees orders an integrator to supply production line supervision software (MES). The SOW provides for an exclusive licence but does not specify whether the client may evolve the software itself or via a third party after the end of the maintenance contract.

A few years later, the integrator ceases trading. The SME finds itself with no access to the source code and no contractual right to entrust its maintenance to another provider. Restoring operations may require a partial rewrite, with a risk of production downtime.

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 the event of the provider's default. These clauses should be considered for any large-scale bespoke development.

Frequently Asked Questions

What happens if a Statement of Work contains no intellectual property clause?

In the absence of an IP clause, French law (article L.111-1 of the Intellectual Property Code) automatically awards economic rights to the creator, that is, the service provider or freelancer. The client who funded the work does not thereby become the owner of the deliverables. They therefore risk being unable to freely exploit the code, design or study delivered, unless they renegotiate the contract afterwards.

What is the practical difference between an assignment of rights and an exclusive licence in a Statement of Work?

An assignment permanently transfers ownership of the economic rights to the client: the service provider can no longer exploit the work or prohibit its future use. An exclusive licence, even if irrevocable and unlimited in duration, leaves the service provider as the rights holder whilst granting the client monopolistic use. This choice has tax, accounting and implications in the event of a sale of the client's business.

Can a Statement of Work assign rights to open source components incorporated into the deliverable?

No. A service provider can only transfer the rights they actually hold. Components distributed under MIT, Apache 2.0 or GPL licences remain subject to their original conditions, regardless of any contractual clause. The IP clause must list these third-party components and specify their applicable licences; otherwise, the client could mistakenly believe they own rights that the contract cannot legally confer upon them.

Is delivery of the source code sufficient to prove assignment of rights to software?

No. Handing over the source files is a material act distinct from the assignment of economic rights. A client may receive the entire source code without holding the right to modify it, distribute it or create derivative versions. To be enforceable, the assignment must be set out in a written instrument that expressly mentions the nature of the rights, the geographical scope, the duration and the purpose, in accordance with article L.131-3 of the Intellectual Property Code.

Can the moral right of an independent service provider prevent exploitation of an assigned deliverable?

In principle, yes: moral right is inalienable under French law, even after a complete assignment of economic rights. This means the service provider retains in particular the right of paternity and the right to the integrity of the work. In practice, IP clauses often include a waiver of the exercise of these rights in the context of commercial exploitation of the deliverable, although this cannot extinguish them permanently.

Conclusion

The intellectual property clause is the strategic heart of any SOW involving digital deliverables. It determines who truly owns the value created: 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 invariant: exhaustively define the covered deliverables, choose and formalize the transfer mechanism (assignment or licence) in accordance with the formality of art. L.131-3 CPI, and anticipate the fate of background IP and third-party components.

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

Start free on certyneo.com/signup and secure your next service contracts with the traceability they deserve.