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

A statement of work (SOW) is the document that describes one project in detail: what is delivered, by when, for how much, and how it is accepted. In Belgium an SOW usually sits under a master services agreement, and its drafting is driven less by special statutes than by one practical legal question: has the supplier promised a result, or only to use reasonable skill. This guide covers the law, the key clauses and a working skeleton. It is general information, not legal advice; confirm a live deal with a Belgian lawyer. ## What law governs an SOW in Belgium? There is no SOW statute. The SOW is a contract document under general contract law, now in Book 5 of the Belgian Civil Code (in force since 1 January 2023), and it inherits the terms of the master services agreement it hangs off. The B2B unfair terms rules in Book VI of the Code of Economic Law still apply to any penalty, liability or acceptance clause that sits in the SOW rather than the master agreement. The legal distinction that matters most for an SOW is the nature of the obligation: - Obligation of result (obligation de resultat): the supplier must deliver a defined outcome. If the outcome is not achieved, that alone is breach, and the customer need not prove fault.

• Obligation of means or best efforts (obligation de moyens): the supplier must apply reasonable skill and care toward the goal. The customer must prove the supplier fell short of that standard. An SOW with firm deliverables and acceptance criteria tends toward an obligation of result; an open-ended advisory engagement tends toward an obligation of means. Saying which one applies, deliverable by deliverable, prevents most disputes. ## Key clauses in a Belgian SOW - Link to the master agreement: reference the MSA and state that its terms govern, with the order of precedence.
• Scope and deliverables: a precise list of what is produced, with specifications. Vague scope is the main cause of disputes.
• Nature of the obligation: state whether each deliverable is an obligation of result or of means.
• Timeline and milestones: dates, dependencies and the effect of customer delay.
• Acceptance: objective acceptance criteria, a review window, and what deemed acceptance means if the customer does not respond.
• Charges and payment model: fixed price, time and materials, or capped time and materials, tied to milestones.
• Change control: how scope changes are requested, priced and signed off.
• Customer responsibilities: access, information and resources the supplier depends on.
• Intellectual property: who owns the deliverables and any pre-existing material; make assignments explicit.
• Service credits or penalties: keep them proportionate, mindful of the B2B grey list on excessive penalty clauses.
• Data protection: reference the data processing agreement where personal data is involved. ## A simple drafting skeleton 1. SOW reference and link to the MSA

2. Project summary and objectives
3. Scope and detailed deliverables
4. Nature of each obligation (result or means)
5. Timeline, milestones and dependencies
6. Acceptance criteria and process
7. Charges and payment schedule
8. Change control
9. Customer responsibilities
10. Intellectual property in deliverables
11. Service credits or penalties (kept proportionate)
12. Assumptions and exclusions
13. Data protection reference
14. Signatures ## Common mistakes - Leaving scope vague, so the customer expects more than the supplier priced.

• Not stating whether a deliverable is an obligation of result or of means, which decides how breach is proved.
• Writing no acceptance process, so payment and sign-off stall.
• Putting a heavy penalty clause in the SOW that the B2B grey list may presume unfair.
• Contradicting the master agreement without a clear order of precedence. ## Keeping statements of work under control If you run many SOWs under one master agreement, the hard part is tracking which is active, which milestone is due, and whether an acceptance or penalty clause is consistent across projects. That work (drafting from a tuned template, flagging risky clauses, tracking milestones and keeping versions straight) is what an AI contract workspace can hold in one place. Adira is built for this, with per-clause risk review and plain-English clause editing; it is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for Belgian law. More at Adira. The law above stands on its own. ## Bottom line A Belgian SOW is a project-level contract under Book 5 of the Civil Code that inherits its master agreement's terms. State the scope precisely, say whether each deliverable is an obligation of result or of means, write a clear acceptance process, keep penalties proportionate under the B2B rules, and get Belgian advice before signing a real deal.