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

A statement of work (SOW) in the UAE is the document that defines a specific piece of work: the deliverables, the timeline, the acceptance criteria and the price. It usually sits under a master services agreement (MSA), which holds the standing legal terms, while the SOW captures what changes from project to project. This guide explains what a UAE SOW should contain, how UAE law treats it, and the local points that matter. It is general information, not legal advice. Confirm specifics with a UAE-qualified lawyer. ## What is a statement of work and when do you need one in the UAE? An SOW answers the practical questions of a project: what will be delivered, by when, to what standard, for how much, and when it counts as done. It does not usually repeat the legal terms, because those live in the MSA. You need an SOW whenever you: - Run a defined project under an existing MSA or framework contract.

• Want clear acceptance criteria so both sides know when the work is complete.
• Need to tie payment to milestones or deliverables. Without an MSA, an SOW can also serve as a short standalone service contract, but then it must carry the legal terms too. ## Which law governs a statement of work in the UAE? An SOW is not a separate type of contract; it is read together with its MSA and interpreted under UAE law. Onshore, that means: - The Civil Transactions Law, Federal Decree-Law No. 25 of 2025 (effective 1 June 2026), which sets the general law of contract, including good faith in negotiation and performance. It also recognises the contract for work (muqawala), under which a contractor undertakes to make something or perform work for a defined consideration, with its own rules on performance and liability.
• The Commercial Transactions Law, Federal Decree-Law No. 50 of 2022, for commercial dealings between businesses.
• VAT at 5 percent under Federal Decree-Law No. 8 of 2017, relevant to milestone payments. If the parties are in a free zone (DIFC or ADGM), the SOW is interpreted under that zone's common-law framework instead. ## Key clauses in a UAE statement of work | Clause | Why it matters in the UAE | | --- | --- | | Reference to the MSA | State that the SOW is governed by and incorporates the MSA. | | Scope and deliverables | Define precisely what will be delivered. | | Assumptions and exclusions | Say what is not included, to control scope. | | Timeline and milestones | Dates and dependencies; link to payment if relevant. | | Acceptance criteria | Objective tests and a review period; this is central. | | Price and payment | Fixed price, time and materials, or milestones; VAT. | | Change control | How scope changes are agreed and priced. | | Personnel and roles | Key people and the customer's cooperation duties. | | Intellectual property | Ownership of deliverables (usually under the MSA). | | Dependencies | What the customer must provide for the work to proceed. | ### Acceptance is the clause that prevents disputes For a result-based SOW, acceptance is where most arguments start. Set objective acceptance criteria, a defined review window, what happens if the customer does not respond (deemed acceptance), and a cure process for rejected deliverables. Clear acceptance language reduces the risk of a dispute over whether the work was truly complete. Where the work resembles a muqawala (a contract to produce a result), the deliverable and acceptance wording also affects how performance and contractor liability are judged. ## UAE-specific points to get right - Onshore versus free zone. This follows the MSA and sets the governing law, forum and language. Keep the SOW consistent with the MSA's choice.
• Acceptance and the muqawala. A result-based engagement onshore can resemble a contract for work, which carries its own rules. Draft deliverables and acceptance so it is clear what result is promised.
• Language. Arabic is the official language and onshore courts work in Arabic; a bilingual SOW with a stated prevailing version is common. DIFC and ADGM work in English.
• Payment and VAT. State the payment schedule, link it to milestones if relevant, and set out 5 percent VAT treatment.
• Precedence. Say whether the MSA or the SOW wins if they conflict; most MSAs let the commercial detail in the SOW prevail over general terms. ## A simple SOW template outline for the UAE 1. SOW reference and link to the MSA

2. Project overview and objectives
3. Scope and deliverables
4. Assumptions and exclusions
5. Timeline and milestones
6. Acceptance criteria and review period
7. Price, payment schedule and VAT
8. Change control
9. Project roles and governance
10. Customer dependencies and responsibilities
11. Intellectual property (confirming the MSA position)
12. Order of precedence with the MSA
13. Signatures ## Common mistakes to avoid - Putting legal terms in the SOW and duplicating or contradicting the MSA.

• Vague deliverables and no acceptance criteria, so completion is disputed.
• No change control, so every scope change becomes a conflict.
• Leaving the prevailing language unstated in a bilingual SOW.
• Letting the SOW drift from the MSA's onshore or free zone choice. ## One workspace to draft, review and track your statements of work An MSA usually spawns many SOWs, and each one has to match the master terms, carry clean acceptance and payment language, and have its milestones and deadlines tracked. Doing that by hand, across many projects and inboxes, is where dates and obligations slip. An AI contract workspace keeps it together: draft each SOW from an approved template tied to its MSA, flag per-clause risk against how your company contracts, edit clauses in plain language, and track milestones, acceptance dates and payments on a live timeline. Adira is built for this, India-first today with other jurisdictions including the UAE on the roadmap, so confirm UAE-law specifics with local counsel. The drafting, review and tracking you would otherwise do by hand can live in one workspace tuned to your business. This article is general information and not legal advice.