What is a statement of work (SOW)?
Is a statement of work (SOW) legally binding in South Africa?
“Information is not without legal force and effect merely on the grounds that it is not contained in the data message purporting to give rise to such legal force and effect, but is merely referred to in such data message.”
“No assignment of copyright and no exclusive licence to do an act which is subject to copyright shall have effect unless it is in writing signed by or on behalf of the assignor, the licenser or, in the case of an exclusive sublicence, the exclusive sublicenser, as the case may be.”
“the mere provision of functional requirements and a periodic review of progress being made in the development of the program and testing it finally to see if it met its purpose, without more, does not establish control over the making of it or vest authorship therein.”
“A person who accepts or is obliged to accept defective or non-timeous performance shall not be entitled to recover a penalty in respect of the defect or delay, unless the penalty was expressly stipulated for in respect of that defect or delay.”
When you need a Statement of Work
- When a new project, phase or block of sprints starts under an existing master service agreement, professional services addendum or software development agreement, and the scope, dates, fees and acceptance tests for that piece of work need to be pinned down.
- When a supplier sends you its own SOW, quote or proposal to sign — the moment to check that it does not quietly override the liability cap, IP terms or payment terms in your master agreement.
- When you are the supplier quoting a fixed price and need the exclusions, assumptions and client dependencies written down, so that extra work and client-caused delay are paid for rather than absorbed.
- When a project has drifted so far through informal changes that the original SOW no longer describes it, and the scope, price and dates need to be re-baselined in a signed document.
- When there is no master agreement at all and a one-off project must be papered quickly — the SOW then has to carry the legal terms (liability, IP, termination, disputes) itself.
What a Statement of Work should contain
Link to the master agreement and order of precedence
Identify the master agreement the SOW is issued under and incorporate its terms by express reference. Then say which document wins in a conflict. The safer default is that the master prevails and the SOW may change a master clause only where it names that clause expressly, so a liability cap or IP position negotiated once cannot be eroded one project at a time. A signed change order should rank above the SOW it amends.
Scope, deliverables and exclusions
Describe the work and list every deliverable — code, configured systems, documents, training, migrated data. Then list what is out of scope. Exclusions are where most fixed-price disputes are won or lost: if hosting, third-party licences, content loading or post-launch support are not included, say so. Attach the specification or product backlog as a schedule rather than summarising it.
Milestones, dates and delay remedies
Set the milestone dates and say which are firm commitments and which are targets. If late delivery will cost the customer money, decide whether to add a delay penalty or liquidated damages. These are enforceable under the Conventional Penalties Act 15 of 1962, but a court may reduce an amount out of proportion to the actual prejudice (s 3), and the penalty is lost if late delivery is accepted unless it was expressly stipulated for that delay (s 2(2)). Extend the dates automatically for client-caused delay and approved changes.
Acceptance criteria and testing
Set the objective tests each deliverable must pass, who runs them, a fixed review period (for example ten business days), what counts as a defect, how many attempts the supplier gets to fix a failure and what happens after that. Most SOWs add deemed acceptance if the customer does not respond in time. State that acceptance confirms the criteria were met for payment purposes but does not waive hidden defects or warranty claims.
Fees, pricing model and payment triggers
Choose the pricing model: a fixed price per milestone, time and materials at listed rates, or capped time and materials with written notice as spend approaches the cap. Link each payment to an objective event — signature, acceptance of a milestone, approved monthly timesheets — and state VAT, expenses and the payment period. The trigger also fixes when a fee becomes due, which is when the three-year prescription period for an unpaid fee starts to run (Prescription Act 68 of 1969, ss 11(d) and 12(1)).
Assumptions and client dependencies
List what the price and timeline assume — volumes, environments, the number of integrations — and everything the customer must supply, with dates: data, system access, test users, sign-offs and a decision-maker who is actually available. Provide that if an assumption proves wrong or a dependency is late, the supplier gets more time and, where it can show extra cost, more money through change control.
Change control
Require every change to scope, price or dates to go through a written change request, a priced impact assessment and a change order signed by named people before the work starts. Say expressly whether an email counts. In Spring Forest Trading v Wilberry [2014] ZASCA 178 the Supreme Court of Appeal held that typed names at the foot of emails satisfied a requirement that a cancellation be in writing and signed, so an informal email thread can bind unless the contract rules it out.
Key personnel and subcontractors
Name the people whose skills the customer is paying for — the lead developer, architect or project manager — and require the customer’s approval before they are replaced, with a handover at the supplier’s cost. List any approved subcontractors. Keep day-to-day supervision of the supplier’s staff with the supplier: a SOW that reads like a job description invites the argument that the people are really the customer’s employees.
Intellectual property in the deliverables
Say, deliverable by deliverable, whether ownership is assigned to the customer or kept by the supplier and licensed. An assignment must be in writing and signed by the assignor (Copyright Act 98 of 1978, s 22(3)). It can cover code not yet written (s 22(5)) and can be made to take effect once the related fees are paid. Carve out the supplier’s pre-existing tools and libraries, which are licensed rather than assigned, and list any open-source components.
Master service agreement vs statement of work vs change order
| Feature | Master service agreement (MSA) | Statement of work (SOW) | Change order |
|---|---|---|---|
| What it covers | Legal terms for the whole relationship — liability, IP rules, confidentiality, data protection, termination, disputes | One project or phase — scope, deliverables, dates, fees, acceptance tests, people | One change to one SOW — what changes, the revised fee, dates and acceptance criteria |
| When it is signed | Once, at the start of the relationship | For each new project or phase | Each time the scope, price or dates move |
| Which document prevails | Prevails by default | Overrides the MSA only where it expressly names the clause it changes | Overrides the SOW it amends |
| Main risk if it is missing | Every SOW must carry its own legal terms, or default rules fill the gaps | No agreed scope — disputes about what was promised and when it is done | Scope creep — unpriced extra work and arguments over what the fee covered |
| Signing | An ordinary electronic signature is usually enough | An ordinary electronic signature is usually enough; an IP assignment inside it should be signed in wet ink or with an advanced electronic signature | Named signatories; the contract should say whether an email counts |
Common South African pitfalls
- Signing a SOW with nothing behind it. A standalone SOW, or one expressed to be subject to a master agreement that is never signed, may bind only on its own terms — or not at all if the fee was left to be agreed later. Either way there is usually no liability cap, no IP assignment, no termination right and no dispute clause. Sign the master first, or put those terms in the SOW.
- Letting a SOW quietly rewrite the master. A supplier’s SOW template often carries its own liability limits, payment terms or IP wording. If the order-of-precedence clause lets the SOW prevail, one project’s paperwork can undo protections negotiated for the whole relationship. The SOW should change a master clause only where it names that clause expressly.
- Vague acceptance criteria and payment triggers. Criteria framed as the client’s satisfaction or general fitness for purpose turn sign-off into a matter of opinion, and payment on go-live or on completion invites a fight about what those words mean. Use objective tests, a fixed review period, a limited number of fix attempts and deemed acceptance, and tie each payment to a defined event.
- Writing a delay penalty, then accepting the late delivery. Under section 2(2) of the Conventional Penalties Act 15 of 1962, a party who accepts late performance cannot recover the penalty for that delay unless the penalty was expressly stipulated for it. Tie each penalty to a specific milestone, state that accepting a late deliverable does not waive it, and remember that you cannot recover both the penalty and damages for the same delay (s 2(1)).
- Changing scope in email threads. Following Spring Forest Trading v Wilberry [2014] ZASCA 178, a typed name at the foot of an email can satisfy a signed-writing requirement, so a casual exchange between project leads can amend a SOW. The opposite trap appears in Global & Local Investments Advisors v Fouché [2020] ZASCA 8, where a requirement that instructions carry the client’s signature, silent on electronic signatures, was held to call for an ordinary signature. Spell out who may sign a change order, and how.
- Assuming the spec and the sign-off make you the owner. Writing the requirements, reviewing progress and running the final tests did not make the commissioning party the author of the program in Bergh v Agricultural Research Council [2020] ZASCA 30. Without a written assignment signed by the developer, the code the customer paid for usually stays the developer’s. Put the assignment in the SOW or the master, and sign it in wet ink or with an advanced electronic signature.
Frequently asked questions
What is the difference between an MSA and a SOW?
The master service agreement (MSA) is signed once and holds the legal terms that apply to every project — liability, IP, confidentiality, data protection and disputes. A statement of work (SOW) covers one project only: its scope, deliverables, dates, fees and acceptance tests. Each new project gets a new SOW under the same MSA, so the legal terms are not renegotiated every time.
Is a SOW binding if there is no master agreement?
It can be. If both sides intended to be bound and the work and the price, or a clear way to calculate it, are certain, a standalone SOW is an enforceable contract. But it binds only on what it says: without master terms there may be no liability cap, no IP assignment and no termination or dispute clause, and a SOW that leaves the fee to be agreed later may not be a final deal at all.
Who wins if the SOW and the MSA say different things?
Whatever the order-of-precedence clause says. The safer default is that the MSA prevails and a SOW may depart from it only where it expressly names the MSA clause it changes, so project-level negotiations cannot quietly erode the liability cap or IP terms. Without such a clause a court reads the documents together and prefers a sensible, businesslike meaning, but it will not substitute its own view for the words the parties actually signed (Natal Joint Municipal Pension Fund v Endumeni Municipality [2012] ZASCA 13).
Can we sign a SOW electronically?
Yes. Section 22(1) of the Electronic Communications and Transactions Act 25 of 2002 gives agreements concluded by data messages legal force, and an ordinary electronic signature is enough for the SOW itself. The exception is an IP assignment inside the SOW: the Copyright Act requires it to be signed, and ECTA section 13(1) says a signature required by law is met electronically only by an advanced electronic signature, so sign that part in wet ink or with an accredited advanced electronic signature.
Can we charge the supplier a penalty for missing SOW deadlines?
Yes, if the SOW provides for it. The Conventional Penalties Act 15 of 1962 makes delay penalties and liquidated damages enforceable, but you cannot recover both the penalty and damages for the same delay, you lose the penalty if you accept the late delivery unless it was expressly stipulated for that delay, and a court may reduce a penalty out of proportion to your actual prejudice. In Steinberg v Lazard [2006] ZASCA 55 the Supreme Court of Appeal enforced a penalty of R50 000 per month for late completion of a house and held that the party in breach bears the onus of proving that a penalty is excessive.
Does writing the spec and testing the software make us the owner of the code?
Not on its own. The author of a computer program is the person who exercised control over its making, and in Bergh v Agricultural Research Council [2020] ZASCA 30 the Supreme Court of Appeal held that providing functional requirements, reviewing progress and testing the final result does not, without more, establish that control. Ownership is reliably transferred only by an assignment in writing signed by the developer (Copyright Act s 22(3)), which can sit in the SOW and can cover code not yet written (s 22(5)).
Should a SOW be fixed price or time and materials?
Fixed price suits a well-defined scope: the supplier carries the risk of the work taking longer, so it will insist on tight exclusions and change control. Time and materials suits evolving or agile work: you pay for actual hours at agreed rates and carry the overrun risk, so ask for a cap, regular reporting and notice before the cap is reached. Many projects use a fixed or capped discovery phase first, then price each later phase against what it produced.
How long does a supplier have to claim an unpaid SOW fee?
Three years. A fee owed under a SOW is an ordinary debt, which prescribes after three years under section 11(d) of the Prescription Act 68 of 1969, counted from the date the fee is due (s 12(1)). An express or tacit acknowledgement of the debt by the client interrupts prescription and restarts the clock (s 14), and serving summons or other court process on the client interrupts it (s 15), so the SOW’s payment trigger also decides when the clock starts.
Sources & authority
- Electronic Communications and Transactions Act 25 of 2002, ss 11, 12, 13 and 22
- Conventional Penalties Act 15 of 1962, ss 1–3
- Copyright Act 98 of 1978, ss 1(1), 21(1)(a), 22(3) and 22(5)
- Prescription Act 68 of 1969, ss 11(d), 12(1), 14 and 15
- Bergh and Others v Agricultural Research Council (93/2019) [2020] ZASCA 30; [2020] 2 All SA 637 (SCA)
- Haupt t/a Softcopy v Brewers Marketing Intelligence (Pty) Ltd and Others (118/05) [2006] ZASCA 40; 2006 (4) SA 458 (SCA)
- Spring Forest Trading 599 CC v Wilberry (Pty) Ltd t/a Ecowash and Another (725/13) [2014] ZASCA 178; 2015 (2) SA 118 (SCA)
- Global & Local Investments Advisors (Pty) Ltd v Fouché (71/2019) [2020] ZASCA 8; 2021 (1) SA 371 (SCA)
- Steinberg v Lazard (157/05) [2006] ZASCA 55; 2006 (5) SA 42 (SCA)
- Natal Joint Municipal Pension Fund v Endumeni Municipality (920/2010) [2012] ZASCA 13; 2012 (4) SA 593 (SCA)
This guide is general information, not legal advice. It reflects the law as at October 2026.