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

What a statement of work in Singapore is A statement of work (SOW) in Singapore is the document that describes one specific piece of work ordered under a wider contract, usually a master services agreement (MSA). The MSA holds the standing terms, such as payment, liability, intellectual property, confidentiality and data; the SOW adds the project detail: what will be delivered, by when, for how much, and how success is measured. Together they form the binding contract for that project. An SOW can also stand alone as a short services contract where there is no MSA, but it works best as a focused order under a framework. Singapore contract law is based on English common law and gives business parties wide freedom to agree their own terms, so the SOW and the MSA above it are where most rights live. The clearer the SOW, the fewer disputes about scope, acceptance and payment. This article is general guidance, not legal advice. Have a Singapore-qualified lawyer review your MSA and SOW template before you rely on them. ## What Singapore law requires in 2026 - Freedom of contract. The parties set scope, deliverables, acceptance, fees and milestones. The SOW is enforceable as part of the contract once agreed.

• Order of precedence. Because an SOW adds to an MSA, say which document wins in a conflict. Usually the MSA governs the commercial and legal terms, and the SOW governs only the project detail, so a one-page SOW cannot quietly rewrite negotiated liability or IP terms.
• Acceptance and payment. Define how deliverables are accepted and tie payment to milestones or acceptance. Clear acceptance criteria reduce disputes about whether the work is done.
• Unfair Contract Terms Act (Cap 396). If the SOW tries to limit liability, the UCTA limits still apply: liability for death or personal injury from negligence cannot be excluded, and other exclusions face a reasonableness test. Keep liability in the MSA and do not let an SOW undercut it.
• Intellectual property. State who owns deliverables created under the SOW and the licence granted, consistent with the MSA.
• Personal Data Protection Act 2012. If the work handles personal data, the PDPA applies and the supplier may be a data intermediary, so the data terms in the MSA should cover the SOW work.
• Electronic Transactions Act 2010. SOWs can be signed electronically.
• GST. GST is 9 percent from 2024; state whether SOW fees are inclusive or exclusive. ## Key clauses in a Singapore SOW | Clause | Why it matters in Singapore | | --- | --- | | Reference to the MSA | Confirms the SOW is governed by the MSA and incorporates its terms. | | Scope and deliverables | 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 criteria | How a deliverable is tested and accepted, which usually triggers payment. | | Fees and payment | Fixed price, time and materials, or milestone based, and GST treatment. | | Assumptions and dependencies | What the supplier is relying on the customer to provide. | | Change control | How scope changes are agreed and priced, so the SOW cannot drift. | | Resourcing and key personnel | Who does the work and any named personnel. | | IP in deliverables | Ownership and licence, consistent with the MSA. | | Data protection | Confirms PDPA data terms apply where personal data is handled. | | Order of precedence | States the MSA governs commercial and legal terms in any conflict. | ## A simple SOW structure you can adapt 1. Reference to the governing MSA and its date.

2. Project background and objectives.
3. Scope and deliverables, with what is out of scope.
4. Timeline, milestones and dependencies.
5. Acceptance criteria and process.
6. Fees, payment schedule and GST.
7. Assumptions and customer responsibilities.
8. Change-control process.
9. Key personnel and resourcing.
10. IP in deliverables and any data-protection confirmations.
11. Order of precedence with the MSA.
12. Signatures. ## Red flags to avoid - A vague scope with no out-of-scope list, which is the most common cause of SOW disputes.

• No acceptance criteria, so it is unclear when a deliverable is done and payment is due.
• An SOW that quietly changes the MSA's liability or IP terms with no order-of-precedence clause to stop it.
• No change-control process, so scope drifts and the supplier does unpaid work or the customer is billed for surprises.
• Silence on assumptions and customer dependencies, leaving the supplier exposed to delays outside its control.
• Forgetting that PDPA data terms must cover SOW work where personal data is handled.
• Not stating whether fees include GST at 9 percent. ## Where a contract workspace helps A template gives you a solid Singapore SOW. The ongoing work starts after signing: checking each SOW against the MSA so it does not undercut negotiated terms, confirming acceptance criteria and change control are present, and keeping milestone and payment dates across many SOWs on track. Drafting the SOW, reviewing each one for scope, 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 MSA as linked clauses so it can flag an SOW that conflicts with the MSA or a missing acceptance clause, lets you edit clauses in plain language, and keeps milestone and notice dates on one timeline. Adira is India-first today, and deeper Singapore-specific coverage is on its roadmap rather than a settled claim, so use it for drafting and review and keep a Singapore 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.