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

A statement of work, or SOW, defines a specific piece of work under a broader services relationship: what will be delivered, by when, for how much, and to what standard. In Italy an SOW is not a special legal instrument. It is a contract, or part of one, so it is governed by the Civil Code rules on contracts and on service relationships, with the local features that apply to any Italian business agreement. This guide explains how an SOW works in Italy, the clauses that matter, and a template outline. It is general information, not legal advice. ## How does a statement of work fit with a services contract? An SOW usually sits under a master services agreement (MSA). The MSA holds the terms that stay constant across the relationship, such as liability, confidentiality, intellectual property and governing law. Each SOW describes one project: scope, deliverables, timeline, acceptance and price. This structure lets the parties start new work quickly by signing a short SOW instead of renegotiating the whole relationship. An SOW can also be a standalone services contract for a one-off engagement. ## What law governs an SOW in Italy? There is no dedicated SOW statute. The governing law is the general law of contract in the Civil Code (Codice Civile, Royal Decree No. 262 of 1942), together with the rules on service relationships: - Articles 1655 and following on the contract of works and services (appalto), used where a contractor organises means and bears the risk of producing a result.

• Article 2222 and following on the contract for work (contratto d'opera), used for work performed mainly through the provider's own activity.
• Article 1375, the duty to perform in good faith, which Italian courts apply as a substantive obligation, and Article 1322 on freedom of contract. Where the SOW is presented on standard terms drafted by one party, the onerous-clause approval rule in Articles 1341 and 1342 applies to clauses such as liability caps and forum clauses. ## Key clauses in a statement of work | Clause | What it should cover | | --- | --- | | Project overview | The business goal and context | | Scope of services | A precise description of what is in scope and out of scope | | Deliverables | Each deliverable, its format and acceptance criteria | | Timeline and milestones | Start date, milestones and the schedule | | Acceptance | How deliverables are reviewed, accepted or rejected, and cure periods | | Fees and payment | Fixed price or time and materials, invoicing, VAT, late payment interest | | Personnel and location | Key people, where the work is performed, on-site requirements | | Customer responsibilities | Access, information and resources the customer must provide | | Change control | How scope changes are proposed, priced and approved | | Intellectual property | Ownership of deliverables and pre-existing materials | | Assumptions and dependencies | What the plan and price rely on | | Governance | Status reporting and escalation | | Relationship to the MSA | Confirmation the MSA terms govern, and order of precedence | ## Why acceptance and change control matter most Most SOW disputes come down to two questions: was the deliverable accepted, and was a change properly agreed. A strong SOW sets objective acceptance criteria, a review window and the consequence of rejection, and it sets a change control process so that extra work is priced and approved in writing. Under the appalto rules, acceptance also affects when risk and liability for defects pass, so the acceptance clause has legal weight, not just practical convenience. ## A template outline you can adapt 1. Reference to the master services agreement

2. Project overview and objectives
3. Scope of services and exclusions
4. Deliverables and acceptance criteria
5. Timeline and milestones
6. Fees, payment, VAT and expenses
7. Personnel, location and customer responsibilities
8. Assumptions and dependencies
9. Change control
10. Intellectual property in deliverables
11. Governance and reporting
12. Signatures, with specific approval of onerous clauses where the SOW is on standard terms ## Common mistakes to avoid - A vague scope with no clear line between in scope and out of scope.

• No objective acceptance criteria, leaving no test for a finished deliverable.
• No change control, so extra work becomes a dispute.
• Silence on who owns the deliverables.
• Ignoring the specific approval rule for onerous standard clauses. ## Keeping SOWs and their MSA aligned A services relationship produces one MSA and many SOWs. The hard part is keeping them aligned: each SOW referencing the right MSA, acceptance and change terms consistent, milestones and payment dates tracked, and the signed version current. Across dozens of SOWs in scattered folders, that alignment slips. Teams increasingly keep drafting, per-clause review, version history and milestone tracking in one connected workspace that links each document to a case and a live activity timeline. Adira is an AI contract workspace built for that. Adira is India-first today, and deeper non-India jurisdiction support, including Italy, is on its roadmap, so confirm Italian law specifics with local counsel. This article is general information and not legal advice.