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

A statement of work (SOW) in the Netherlands is the document that sets out 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 Dutch law. Depending on what is promised, it is the operative schedule of either an agreement of assignment (overeenkomst van opdracht, Article 7:400 of the Civil Code) where a service is performed, or a contract for work (aanneming van werk, Article 7:750 BW) where a tangible result is delivered. That classification shapes the acceptance and liability rules, so it is the first thing to settle. This page explains what belongs in a Dutch SOW, the local-law points that shape it, and a simple outline. It is general information, not legal advice. ## How a SOW fits the Dutch legal framework A 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. Two Dutch-law distinctions drive the draft: - Assignment or contract for work. An overeenkomst van opdracht (Article 7:400 BW) covers services such as consultancy, with duties of care. An aanneming van werk (Article 7:750 BW) covers producing a tangible work, with its own rules on acceptance (oplevering) and additional work (meerwerk, Article 7:755 BW). Software and professional services often sit in the assignment category, but a fixed deliverable can bring the contract-for-work rules into play.

• Effort or result. Dutch law distinguishes an effort obligation (inspanningsverplichting) from a result obligation (resultaatsverplichting). State which applies to each deliverable, because it decides what the customer must prove. ## Key clauses in a Dutch SOW ### Scope and deliverables Describe the services and deliverables precisely. Vague scope invites disputes over additional work (meerwerk). ### Standard of performance State for each deliverable whether it is an effort or a result obligation. This is the central Dutch-law choice. ### Acceptance Set an acceptance or delivery (oplevering) process with criteria, a testing period, and the effect of rejection. For a contract for work, acceptance carries specific legal consequences. ### Timeline and milestones Set dates, dependencies and the effect of customer delay, and separate firm deadlines from targets. ### Price and additional work State the charge model (fixed price or time and materials) and a change process. Under Article 7:755 BW, additional work in a contract for work can be charged where the customer should have understood extra cost would follow, so a written change process avoids argument. ### Personnel and subcontracting Name key personnel if relevant and set subcontracting rules, keeping the supplier responsible. ### Liability and IP Liability is governed by the master agreement; confirm the cap applies and keep the intent and conscious-recklessness carve-out. Confirm ownership of deliverables, and point to the Article 28 GDPR terms if personal data is processed. ## A simple SOW outline for the Netherlands 1. Reference to the master agreement and precedence

2. Classification (assignment or contract for work)
3. Scope and deliverables
4. Standard of performance per deliverable (effort or result)
5. Acceptance or delivery criteria and testing
6. Timeline, milestones and dependencies
7. Charges and the change or additional-work process
8. Key personnel and subcontracting
9. Assumptions and customer responsibilities
10. Intellectual property in deliverables
11. Data protection cross-reference
12. Acceptance signatures ## Common mistakes to avoid - Not settling whether the SOW is an assignment or a contract for work, which changes the acceptance and liability rules.

• Leaving the effort-or-result standard unstated, so a court decides.
• No acceptance process, blurring when work is done and payment is due.
• A loose scope with no change control, inviting meerwerk disputes. ## Keeping SOWs aligned with the master agreement SOWs multiply under a single master agreement, and each 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 effort-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 Dutch coverage before relying on it for a Netherlands-governed engagement. More at Adira.