contracts

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

Adira EditorialLegal AI desk4 min read

What a statement of work in Denmark is A statement of work (SOW) in Denmark is the document that defines one specific piece of work: what will be delivered, by when, for how much, and how it will be accepted. It usually sits under a master services agreement (MSA), which holds the standing legal terms, so the SOW can stay focused on scope and delivery without repeating liability, IP, and confidentiality clauses. Denmark has no dedicated SOW statute. A SOW is a contract, or part of one, governed by general Danish contract law. Its value is precision: a good SOW removes the ambiguity that causes most delivery disputes. This page explains the law and the clauses. It is general information, not legal advice. ## The law that governs it in Denmark - Contract law. The Danish Contracts Act (Aftaleloven) and general contract principles govern a SOW. There is no requirement that it be in writing, but a written SOW is what makes scope, price, and acceptance enforceable.

  • The MSA link. Where the SOW sits under an MSA, the MSA supplies the legal terms and an order of precedence clause decides which document wins in a conflict. A standalone SOW must carry those legal terms itself.
  • Sale of goods by analogy. The Danish Sale of Goods Act (Koebeloven) is built around the sale of goods. A services SOW falls outside it, so the written terms control, though its principles can apply by analogy where goods are delivered.
  • Limitation. The Danish Limitation Act (Foraeldelsesloven) sets a general three-year limitation period, which affects how long claims about the delivered work stay live.
  • Data protection. Where the work involves processing personal data, the GDPR and the Danish Data Protection Act apply, and a data processing agreement may be needed. ## Key clauses to include ### Scope and deliverables
  • A precise description of the work and the specific deliverables, with what is expressly out of scope.
  • Assumptions and dependencies, including what the customer must provide and when.
  • Milestones and the delivery schedule. ### Acceptance and quality
  • Acceptance criteria and the testing or review process.
  • A defined acceptance period and what happens if a deliverable fails.
  • Quality or performance standards the work must meet. ### Commercial terms
  • Price and payment model: fixed price, time and materials, or milestone-based.
  • Invoicing triggers, usually tied to accepted milestones.
  • Expenses and any rate card. ### Change and governance
  • Change control: how scope changes are requested, priced, and approved.
  • Named contacts, governance meetings, and reporting.
  • Reference to the governing MSA and its order of precedence. ## A simple clause skeleton 1. Reference to the governing MSA (or standalone legal terms).
  1. Scope of work and deliverables.
  2. Out of scope.
  3. Assumptions and customer dependencies.
  4. Milestones and schedule.
  5. Acceptance criteria and testing.
  6. Price and payment model.
  7. Invoicing and expenses.
  8. Change control.
  9. Governance, contacts, and reporting.
  10. Data protection, where relevant.
  11. Order of precedence and governing law (Danish law). ## Common mistakes to avoid - Vague deliverables with no out-of-scope list, so every assumption becomes a dispute.
  • No acceptance criteria, so no one can say objectively whether the work is done.
  • Missing change control, so scope creep has no price and no sign-off.
  • Ignoring customer dependencies, then blaming the supplier for delays the customer caused.
  • Treating a standalone SOW as if an MSA existed, leaving liability, IP, and confidentiality unaddressed. ## Managing Danish statements of work in one workspace One MSA can spawn dozens of statements of work, each with its own milestones, acceptance dates, and invoicing triggers, all of which have to stay consistent with the framework above them. That is far easier when drafting, review, and tracking sit in one place rather than across inboxes and spreadsheets. Adira is an AI legal workspace where you can draft each SOW against its MSA, see every clause flagged as favourable, neutral, or unfavourable to you, edit clauses in plain English, and track milestones and acceptance dates across your whole contract portfolio. Adira is deepest on Indian law today, and Denmark-specific depth is on the roadmap, so pair it with Danish counsel for the local detail.

Frequently asked questions

Which law governs a statement of work in Denmark?
There is no dedicated SOW statute. A SOW is a contract governed by general Danish contract law and the Danish Contracts Act (Aftaleloven). Where it sits under a master services agreement, the MSA supplies the legal terms and an order of precedence clause resolves conflicts between the two.
Does a statement of work need to be in writing in Denmark?
Danish law does not require it, but a written SOW is strongly advisable. Writing is what makes scope, deliverables, acceptance criteria, and price enforceable, and it is what prevents the ambiguity that causes most delivery disputes. It also helps with the three-year limitation period for claims.
What is the difference between an MSA and a SOW?
The MSA holds the standing legal terms such as liability, intellectual property, and confidentiality. The SOW defines one specific piece of work: scope, deliverables, schedule, acceptance, and price. The SOW points back to the MSA, and an order of precedence clause decides which wins if they conflict.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free