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

What a statement of work in Germany is A statement of work (SOW) in Germany is the document that describes one specific piece of work ordered under a wider framework agreement (Rahmenvertrag), the German equivalent of a master services agreement. The framework holds the standing terms, such as payment, liability, intellectual property, confidentiality and data; the SOW, sometimes called a Leistungsbeschreibung or Einzelauftrag, adds the project detail: deliverables, timing, price and how the work is accepted. Together they form the binding contract for that project. What makes the German position distinctive is classification. German law has no single SOW statute. Instead the work described in the SOW is classified under the Civil Code (Burgerliches Gesetzbuch, BGB) as either a service (Dienstvertrag, Section 611 BGB), where the provider owes a careful activity but no guaranteed result, or a work result (Werkvertrag, Section 631 BGB), where the provider owes a defined result that the customer formally accepts (Abnahme). Because the SOW is where the actual deliverable is defined, the SOW is usually where the classification is decided, and the classification drives acceptance, payment and warranty. This article is general guidance, not legal advice. Have a German-qualified lawyer review your framework agreement and SOW template before you rely on them. ## What German law requires in 2026 - Classification happens at the SOW level. Each deliverable should be classified as service or work. Under a Werkvertrag the customer accepts the result (Abnahme), which triggers payment and starts the warranty; under a Dienstvertrag there is no acceptance step and no warranty for a result.

• Acceptance (Abnahme). For work results, define how and when acceptance happens and what counts as a defect. Acceptance is the pivot for payment and warranty, so it must be clear.
• Order of precedence. Because the SOW sits under a Rahmenvertrag, state which document governs in a conflict. Usually the framework governs the legal and commercial terms and the SOW governs the project detail, so a short SOW cannot override negotiated liability or IP terms.
• AGB rules on standard terms (Sections 305 to 310 BGB). If the SOW limits liability, the strict standard-terms rules still apply; liability for intent can never be excluded. Keep liability in the framework and do not let the SOW undercut it.
• Intellectual property and rights of use. State who owns deliverables and the rights of use (Nutzungsrechte) granted, consistent with the framework.
• Data protection. If the work handles personal data, an Article 28 GDPR data processing agreement in the framework should cover the SOW work.
• Form and VAT. SOWs can be concluded in writing or electronically; German VAT applies to the fees. ## Key clauses in a German SOW | Clause | Why it matters in Germany | | --- | --- | | Reference to the framework | Confirms the SOW is governed by the Rahmenvertrag and incorporates its terms. | | Classification | States whether the deliverable is a Dienstvertrag or a Werkvertrag. | | Scope and deliverables (Leistungsbeschreibung) | Defines exactly what is in and out of scope, the main source of disputes. | | Timeline and milestones | Dates, dependencies and what happens if they slip. | | Acceptance (Abnahme) | For work results, how and when acceptance happens and what counts as a defect. | | Fees and payment | Fixed price, time and materials, or milestone based, and VAT treatment. | | Assumptions and cooperation | What the provider relies on the customer to supply. | | Change control | How scope changes are agreed and priced, so the SOW cannot drift. | | Rights of use in deliverables | Ownership and Nutzungsrechte, consistent with the framework. | | Data processing | Confirms the Article 28 data terms apply where personal data is handled. | | Order of precedence | States the framework governs legal and commercial terms in any conflict. | ## A simple SOW structure you can adapt 1. Reference to the governing Rahmenvertrag and its date.

2. Classification of the work as service or work result.
3. Scope and deliverables (Leistungsbeschreibung), with what is out of scope.
4. Timeline, milestones and dependencies.
5. Acceptance (Abnahme) process for work results.
6. Fees, payment schedule and VAT.
7. Assumptions and the customer's cooperation duties.
8. Change-control process.
9. Rights of use in deliverables.
10. Data-protection confirmations where personal data is handled.
11. Order of precedence with the framework.
12. Signatures. ## Red flags to avoid - Not classifying the work as service or work result, leaving acceptance, payment and warranty unclear.

• No acceptance (Abnahme) process for a work result, so it is unclear when the result is accepted and payment is due.
• A vague scope with no out-of-scope list, which is the most common cause of SOW disputes.
• An SOW that quietly changes the framework's liability or IP terms with no order-of-precedence clause.
• No change-control process, so scope drifts and work is done unpaid or billed as a surprise.
• Silence on cooperation duties, leaving the provider exposed to delays caused by the customer.
• Forgetting that the Article 28 data terms must cover SOW work where personal data is handled. ## Where a contract workspace helps A template gives you a solid German SOW. The ongoing work starts after signing: confirming each SOW is classified as service or work, that an acceptance process exists for work results, that the SOW does not undercut the framework, and that milestone and payment dates across many SOWs stay on track. Drafting the SOW, reviewing each one for classification, acceptance and precedence gaps, and tracking milestone dates can sit in one AI workspace tuned to how your company contracts. Adira is built around that shape: it drafts from your template, models the SOW and its framework as linked clauses so it can flag a work result with no acceptance step or an SOW that conflicts with the framework, lets you edit clauses in plain language, and keeps milestone and notice dates on one timeline. Adira is India-first today, and deeper Germany-specific coverage is on its roadmap rather than a settled claim, so use it for drafting and review and keep a German adviser for the local-law call. The template above is enough to put a fair agreement in place on its own. Last verified October 2026.