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

A statement of work, usually called an SOW, is the document that defines a specific piece of work under a broader services relationship: what will be delivered, by when, for how much, and to what standard. It is the operational heart of a services engagement. In Indonesia an SOW is not a special legal instrument; it is a contract or part of one, so it is governed by general contract law, with a few local rules that apply to any business agreement here. This guide explains how an SOW works in Indonesia, the clauses that matter, and a template outline. It is general information, not legal advice. ## How does a statement of work fit with a services contract? An SOW almost always sits under a master services agreement (MSA). The MSA holds the terms that stay the same across every project: liability, confidentiality, intellectual property, payment mechanics, governing law. Each SOW then describes one project: scope, deliverables, timeline, acceptance and price. This structure lets the parties start new work quickly by signing a short SOW instead of renegotiating the whole relationship. An SOW can also be a standalone services contract for a one-off engagement. Either way, it needs to be clear enough to stand on its own in a dispute. ## What law governs an SOW in Indonesia? There is no dedicated SOW statute. The governing law is the general law of contract: - The Indonesian Civil Code (KUHPerdata). Article 1320 sets the conditions for a valid contract: consent, capacity, a specific subject, and a lawful cause. Article 1338 gives contracts the force of law between the parties and underlies freedom of contract.

• The Electronic Information and Transactions Law (Law No. 11 of 2008, as amended), which recognises electronic contracts and signatures, so an SOW can be signed electronically.
• Law No. 24 of 2009 on the national language, whose Article 31 calls for an Indonesian-language version where an Indonesian party is involved. If the work involves personal data, the Personal Data Protection Law (Law No. 27 of 2022) may also apply, and the services terms should reflect it. ## Key clauses in a statement of work | Clause | What it should cover | | --- | --- | | Project overview | The business goal and context of the work | | Scope of services | A precise description of what is in scope, and what is out | | Deliverables | Each deliverable, its format, and acceptance criteria | | Timeline and milestones | Start date, milestones, and the overall schedule | | Acceptance | How deliverables are reviewed, accepted or rejected, and cure periods | | Fees and payment | Fixed price or time and materials, invoicing, currency, taxes, late payment | | Personnel and location | Key people, where the work is performed, any on-site requirements | | Customer responsibilities | Access, information and resources the customer must provide | | Change control | How scope changes are proposed, priced and approved | | Intellectual property | Who owns the deliverables and any pre-existing materials | | Dependencies and assumptions | What the plan and price rely on | | Reporting and governance | Status reporting and escalation | | Relationship to the MSA | Confirmation that the MSA terms govern | ## Why acceptance and change control matter most Most SOW disputes come down to two questions: was the deliverable accepted, and was a change properly agreed. A strong SOW defines objective acceptance criteria, a review window, and what happens if a deliverable is rejected. It also sets a change control process so that extra work is priced and approved in writing rather than argued about later. These two clauses prevent the majority of friction, so draft them with care. ## Language and signing Where an Indonesian party is involved, prepare the SOW bilingually, in Indonesian and English, and execute both versions, naming the version that prevails. Because the Electronic Information and Transactions Law recognises electronic signatures, SOWs can be signed online, which is practical when a relationship produces many of them. ## A template outline you can adapt 1. Reference to the master services agreement

2. Project overview and objectives
3. Scope of services and exclusions
4. Deliverables and acceptance criteria
5. Timeline and milestones
6. Fees, payment and expenses
7. Personnel, location and customer responsibilities
8. Assumptions and dependencies
9. Change control
10. Intellectual property in deliverables
11. Reporting and governance
12. Signatures, bilingual where an Indonesian party is involved ## Common mistakes to avoid - A vague scope with no clear line between in scope and out of scope.

• No acceptance criteria, so there is no objective test for a finished deliverable.
• No change control, so extra work turns into a dispute.
• Silence on who owns the deliverables.
• Relying on English alone with an Indonesian counterparty. ## Keeping SOWs and their MSA aligned A services relationship produces one MSA and many SOWs. The hard part is keeping them aligned: making sure each SOW references the right MSA, that acceptance and change terms are consistent, that milestones and payment dates are tracked, and that the signed version is the current one. Across dozens of SOWs in scattered folders, that alignment slips. Teams increasingly keep drafting, per-clause review, version history and milestone tracking in one connected workspace. Adira is an AI contract workspace built for exactly that, linking documents to a case and a live activity timeline. Adira is India-first today, and deeper non-India jurisdiction support, including Indonesia, is on its roadmap, so confirm Indonesian specifics with local counsel. This article is general information and not legal advice.