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

Is a statement of work legally binding in the United Kingdom? Yes. A statement of work is a binding contract in the United Kingdom, either on its own or, more often, as an order under a master services agreement (MSA). The SOW describes one project: the deliverables, timeline, acceptance criteria, and fees. The MSA holds the standing legal terms (liability, IP, confidentiality), and the SOW incorporates them. There is no single SOW statute; it is governed by ordinary contract law and the MSA it sits under. This is general information, not legal advice. For a large or fixed-price engagement, ask a qualified UK solicitor. ## What UK law applies to a statement of work An SOW is an ordinary commercial contract, so it needs offer, acceptance, consideration, and intention to create legal relations, under the law chosen in the governing MSA (commonly the law of England and Wales). Because an SOW usually incorporates the MSA by reference, the MSA's governing law, liability cap, IP terms, and dispute resolution flow into it, and the order-of-precedence clause decides which document wins if they conflict. Three statutes form the backdrop through the MSA. The Supply of Goods and Services Act 1982 implies reasonable care and skill, a reasonable time, and a reasonable charge into B2B services unless the SOW sets different standards. The Unfair Contract Terms Act 1977 means any liability limit must be reasonable. The Late Payment of Commercial Debts (Interest) Act 1998 gives a statutory right to interest on late payment. Keep legal terms in the MSA and scope in the SOW, so the SOW does not accidentally change the deal. Electronic signature is valid under UK law. ## Key clauses in a UK statement of work ### Reference to the MSA

State that the SOW is issued under, and governed by, the named MSA, and set the order of precedence for conflicts. ### Scope and deliverables Describe exactly what will be delivered. Specific, testable deliverables prevent disputes; vague scope invites them. ### Out of scope List what is not included, which is as useful as the scope for avoiding scope creep. ### Timeline and milestones Set the schedule, milestones, and dependencies on the customer, and say what happens if a dependency slips. ### Acceptance criteria and process Define how deliverables are reviewed, the acceptance window, and what counts as acceptance or rejection. This controls payment triggers, so be precise. ### Charges and payment schedule State whether the project is time-and-materials, fixed-price, or milestone-based, and tie payment to milestones or acceptance. Cover expenses and VAT, and reflect the statutory late-payment interest. ### Roles and responsibilities Name key personnel and the customer's responsibilities (access, data, approvals). ### Assumptions List the assumptions the estimate relies on, so a wrong assumption triggers a change order rather than a dispute. ### Change control Describe how changes to scope, timeline, or charges are requested, priced, and approved. This is what keeps a fixed-price SOW from bleeding. ### Deliverable IP Confirm how the MSA's IP terms apply to these deliverables, including any customer-owned work product (with an express assignment where needed). ## A simple UK statement of work skeleton 1. SOW number, parties, and reference to the MSA 2. Order of precedence 3. Background and objectives 4. Scope of services and deliverables 5. Out of scope 6. Timeline, milestones, and dependencies 7. Acceptance criteria and process 8. Pricing model and payment schedule 9. Expenses and VAT 10. Key personnel and customer responsibilities 11. Assumptions 12. Change control 13. Deliverable intellectual property 14. Signatures ## Points worth negotiating Make the deliverables and acceptance criteria concrete, because they decide when you get paid and when the project is done. Negotiate the change-control process so new work is priced, not absorbed. For fixed-price work, protect yourself with clear assumptions and dependencies. Confirm the pricing model matches the risk you will carry. Keep legal terms in the MSA so the SOW does not accidentally rewrite the liability cap or IP position. ## Where a single contract workspace helps One MSA can spawn many SOWs, each with its own milestones, acceptance dates, payment triggers, and assumptions, all of which must stay aligned with the parent MSA. Tracking that by hand is where mistakes creep in, and it is exactly what an AI contract workspace is built for: the MSA and every SOW become a linked, structured clause tree, positions are marked favourable, neutral, or unfavourable to your company, and milestone and acceptance dates surface automatically. Adira is one such workspace. Adira is India-first today, and deeper United Kingdom jurisdiction coverage is on its roadmap, so for UK-governed work treat it as a drafting and tracking aid and confirm specifics with a UK solicitor. The structure above does not change; a workspace just keeps the SOWs and their MSA in sync.