Statement of Work in France: Template, Key Clauses and Local Law (2026)

A statement of work (SOW) in France is the document that describes the specific services, deliverables, timeline and price for a piece of work, usually under a master services agreement. It is not a separate legal category in French law; it is the operative schedule of a service contract (contrat de prestation de services), which French law treats as a form of contrat d'entreprise or louage d'ouvrage within Article 1710 of the Civil Code. Getting the SOW right is often more important than the master agreement, because this is where scope, acceptance and the performance standard actually live. This page explains what belongs in a French SOW, the local-law points that shape it, and a simple outline. It is general information, not legal advice. ## How a SOW fits the French legal framework Under a framework contract recognised by Article 1111 of the Civil Code, the master agreement sets the standing terms and each SOW fixes the detail of an order. The SOW should expressly incorporate the master agreement and say which prevails on conflict. The single most important French-law choice in a SOW is the standard of the obligation: - An obligation of means (obligation de moyens) promises diligent, best efforts. The customer must prove fault to claim.

• An obligation of result (obligation de resultat) promises a defined outcome. Failure to deliver the result is enough, without proving fault. French courts classify service obligations one way or the other based on how they are drafted, so a SOW should state which standard applies to which deliverable. This single point drives the risk allocation more than any liability clause. ## Key clauses in a French SOW ### Scope and deliverables Describe the services and deliverables precisely. Vague scope leads to disputes and to arguments over additional work. ### Standard of performance State for each deliverable whether it is an obligation of means or of result. This is the French-law pivot and should not be left implicit. ### Acceptance Set an acceptance (reception) process: criteria, a testing period, and what happens on rejection. Clear acceptance protects both sides and fixes when payment and risk shift. ### Timeline and milestones Set dates, dependencies and the effect of customer delay, and distinguish firm deadlines from targets. ### Price and additional work State the charge model (fixed price or time and materials) and a change process for additional work, so scope creep is priced rather than disputed. ### Personnel and subcontracting Name key personnel if relevant and set subcontracting rules, keeping the supplier responsible for subcontractors. ### Acceptance of risk and liability Liability is governed by the master agreement, but confirm the cap applies and remember Article 1170 of the Civil Code strikes clauses that empty an essential obligation of substance. ### IP and data Confirm who owns the deliverables, and if personal data is processed, point to the Article 28 GDPR terms in the master agreement. ## A simple SOW outline for France 1. Reference to the master agreement and precedence

2. Scope and deliverables
3. Standard of performance per deliverable (means or result)
4. Acceptance criteria and testing
5. Timeline, milestones and dependencies
6. Charges and the change or additional-work process
7. Key personnel and subcontracting
8. Assumptions and customer responsibilities
9. Intellectual property in deliverables
10. Data protection cross-reference
11. Acceptance signatures ## Common mistakes to avoid - Leaving the performance standard unstated, so a court decides whether it was means or result.

• No acceptance process, which blurs when work is done and when payment is due.
• A loose scope with no change-control, inviting disputes over additional work.
• Repeating or contradicting the master agreement instead of cross-referencing it. ## Keeping SOWs aligned with the master agreement SOWs multiply under a single master agreement, and each one quietly reshapes scope, acceptance and the performance standard. When they drift apart from the master terms, or from each other, risk builds up unseen. Holding the master agreement and every SOW in one workspace, with scope, acceptance dates, milestones and the means-or-result standard visible and tracked, keeps the set consistent and makes delivery and billing disputes easier to avoid. Adira is one AI workspace to draft, review, track and govern contracts; its depth outside India is on its roadmap, so verify French coverage before relying on it for a France-governed engagement. More at Adira.