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

A Statement of Work (SOW) in Greece is the document that defines one specific piece of work: what will be delivered, by when, and for how much. It usually sits under a Master Services Agreement (MSA), which holds the stable legal terms, while the SOW carries the project detail. This guide covers how an SOW works under Greek law, the clauses to include, a usable skeleton, and the common mistakes. This is general information, not legal advice. Confirm the detail with a qualified Greek lawyer before you rely on an SOW. ## How an SOW fits with an MSA in Greece The MSA sets liability, IP, confidentiality, and payment terms once. Each SOW then describes a project: scope, deliverables, milestones, acceptance, and price. This split lets a long relationship run many projects without renegotiating the legal terms every time. A standalone SOW is possible for a one-off, but then it must carry those legal terms itself. ## Greek law that applies to an SOW ### Freedom of contract and the Civil Code Greece is a civil-law country. Article 361 of the Civil Code recognises freedom of contract, so the parties largely set their own terms. Good faith runs through the Code: Article 200 on interpretation and Article 288 on performance let courts fill gaps and temper terms that are plainly unfair. Keep acceptance and penalty terms proportionate. ### Services as a type of contract Services usually fall under the Civil Code rules on contracts for work or for independent services, depending on how the engagement is framed. The framing affects default obligations, so describe clearly whether the provider owes a defined result or best efforts. ### Payment terms Greek law implements the EU Late Payment Directive: a default 30 day payment period in B2B deals, with anything over 60 days allowed only where expressly agreed and not grossly unfair. Milestone and acceptance-linked payments must respect this. ### Intellectual property Under Law 2121/1993, copyright in created work vests in the author unless assigned. An SOW that produces deliverables should either rely on the MSA's IP clause or assign the rights expressly. ## Key clauses to include - Reference to the MSA. State which MSA governs and that its terms apply.

• Scope of work. A precise description of what is and is not included.
• Deliverables. A clear list, each defined well enough to test.
• Timeline and milestones. Dates, dependencies, and what triggers each payment.
• Acceptance criteria and process. How a deliverable is reviewed, the review window, and what happens if it fails.
• Fees and payment schedule. Fixed price, time and materials, or capped, linked to milestones.
• Assumptions and dependencies. What the customer must provide, and the effect if it does not.
• Change control. How scope changes are requested, priced, and approved.
• Roles and key personnel. Named leads on each side.
• IP for this work. Either defer to the MSA or set out any project-specific assignment. ## A usable SOW skeleton 1. Reference to the governing MSA

2. Project overview and objectives
3. Scope of work (in and out of scope)
4. Deliverables
5. Timeline, milestones, and dependencies
6. Acceptance criteria and process
7. Fees and payment schedule
8. Assumptions
9. Change control procedure
10. Roles and key personnel
11. Project-specific terms (if any)
12. Signatures ## Common mistakes to avoid - Vague scope. The biggest cause of project disputes. Describe the work precisely and state what is out of scope.

• No acceptance process. Without criteria and a review window, a deliverable is never clearly done, and payment stalls.
• Conflicting with the MSA. If the SOW changes legal terms, say so and set the order of precedence, or leave those terms to the MSA.
• Open-ended change control. Scope creep follows when changes are not priced and approved in writing.
• Ignoring IP. If the SOW output is not covered by the MSA's IP clause and not assigned here, ownership can be unclear. ## One workspace for your Greek project contracts SOWs multiply fast: one MSA can spawn dozens, each with its own milestones, acceptance dates, and payment triggers. Keeping the MSA, every SOW, and the deadlines together, rather than scattered across folders and inboxes, is what stops a milestone or acceptance window slipping. Adira is an AI legal workspace built for that: draft, review, and track linked contracts in one place, with each clause modelled so a change flows through consistently. Adira is deepest in Indian law today, and wider jurisdiction depth, including Greece, is on its roadmap, so treat non-India output as a draft for local counsel to confirm. Tie the SOW cleanly to its MSA, define scope and acceptance tightly, and keep the paperwork in one trail.