ElyForma

Statement of Work Guide

Statement of Work Guide South Africa

A statement of work, often called an SOW, is a project or services document that describes exactly what work a supplier, contractor, consultant, or service provider will deliver for a client. In South Africa, it is commonly used alongside a master services agreement, consulting agreement, service agreement, procurement contract, or supplier appointment letter. Public-sector and procurement documents in South Africa also use “scope of work” and “statement(s) of work” as standard project-planning and contract-management terms. :contentReference[oaicite:0]{index=0}

This guide explains what a statement of work is, when to use one in South Africa, how it differs from a contract, and what a strong SOW should include. It is especially useful for consulting, implementation projects, software work, maintenance services, professional services, and supplier engagements where the parties need clear written scope before work starts. :contentReference[oaicite:1]{index=1}

What is a statement of work?

A statement of work is a written document that sets out the scope, deliverables, timing, responsibilities, assumptions, and acceptance criteria for a specific piece of work. In simple terms, it answers questions like:

  • what work will be done
  • what will be delivered
  • when it will be delivered
  • what is included
  • what is excluded
  • who is responsible for what
  • how payment will be linked to the work
  • how the client will accept the work

A good SOW turns a vague project idea into a workable delivery document.

Why statements of work matter in South Africa

Statements of work matter because many disputes happen when the contract says services will be provided, but nobody has defined the scope properly. In South African practice, public and private contracts commonly separate the main agreement from the detailed scope or work package. Public procurement and contract documents regularly use annexures headed “Scope of Work,” and standard services agreements often say that schedules, annexures, and proposals form part of the agreement. :contentReference[oaicite:2]{index=2}

A strong SOW helps reduce disputes about:

  • scope creep
  • delayed deliverables
  • unclear responsibilities
  • billing disagreements
  • missing milestones
  • whether the work was actually completed

It is especially useful where the work is technical, staged, customised, or project-based.

Statement of work vs contract

These are related, but they are not the same.

Statement of work

The SOW usually contains the project-specific delivery details.

Contract or service agreement

The contract usually contains the broader legal terms, such as:

  • payment rights
  • confidentiality
  • liability limits
  • IP ownership
  • breach and termination
  • dispute resolution
  • governing law

In South Africa, many service agreements are structured so that the main agreement and its schedules or annexures must be read together. That means the SOW often becomes part of the contract once attached properly. :contentReference[oaicite:3]{index=3}

Statement of work vs scope of work

These terms are often used interchangeably.

Scope of work

Usually refers to the detailed description of what is included and excluded.

Statement of work

Usually refers to the full project document, which may include:

  • scope
  • deliverables
  • timeline
  • assumptions
  • pricing
  • acceptance criteria
  • responsibilities

In South African project-planning and procurement documents, both terms appear frequently, and the core purpose is the same: define the work clearly. :contentReference[oaicite:4]{index=4}

When to use a statement of work

A South African statement of work is useful when:

  • a consultant is engaged for a defined project
  • a service provider is delivering milestone-based work
  • a company wants to outsource a specific work package
  • the parties already have a master agreement and need a project-specific schedule
  • the scope is too detailed to place in the main contract body
  • the work needs clear deliverables and acceptance criteria
  • the pricing depends on stages, hours, or outputs

It is especially useful for:

  • software development
  • implementation projects
  • IT support projects
  • marketing campaigns
  • design work
  • facilities and maintenance projects
  • consulting and advisory work
  • procurement-based service delivery

When not to rely on an SOW alone

A statement of work may not be enough on its own if:

  • there is no main contract or legal framework behind it
  • the work involves major IP, confidentiality, or liability issues
  • the supplier relationship is long-term and broader than one project
  • the engagement needs employment-style control and structure instead of contractor-style delivery
  • the parties have not agreed on core commercial or legal terms yet

In those cases, the SOW should usually sit under a service agreement, consulting agreement, or master services agreement rather than stand alone.

South African commercial and practical points to know

1. Scope must be defined clearly

South African project-planning guidance says scope defines project boundaries by identifying what the project will and will not deliver and by setting out expected outcomes, objectives, timelines, costs, quality needs, and what is in scope and out of scope. :contentReference[oaicite:5]{index=5}

2. Schedules and annexures often form part of the agreement

South African standard services agreements commonly state that the agreement includes schedules, annexures, RFP documents, and proposals, all read together as part of one contract framework. :contentReference[oaicite:6]{index=6}

3. VAT and invoicing still matter separately

If the work is taxable and the supplier is a VAT vendor, the SOW should be clear on pricing and whether VAT is included or excluded. SARS says South African VAT is destination-based and is charged by vendors on taxable supplies of goods or services. The commercial SOW should therefore align with the invoicing and VAT treatment that will follow. :contentReference[oaicite:7]{index=7}

4. Services contracts often need milestone and acceptance structure

South African public and services contracts frequently include penalty, reporting, labour, compliance, and delivery obligations at the scope level, which shows how important it is to document operational details properly instead of leaving them implied. :contentReference[oaicite:8]{index=8}

What to include in a South African statement of work

A strong SOW should usually include the following.

Project title and reference

Give the work package a clear title and reference number.

Parties

Identify the client and the service provider clearly.

Background or purpose

Briefly explain what the project is for and why the work is being commissioned.

Scope of work

Describe exactly what work the supplier will perform.

Out of scope

State clearly what is not included. This is one of the best ways to reduce later scope creep.

Deliverables

List the outputs the provider must deliver, such as:

  • reports
  • designs
  • software modules
  • implementation tasks
  • training sessions
  • documentation
  • maintenance outputs

Timeline and milestones

State:

  • commencement date
  • milestone dates
  • delivery deadlines
  • completion date

Roles and responsibilities

Record what the supplier must do and what the client must provide, such as:

  • access
  • approvals
  • data
  • facilities
  • decision-makers
  • feedback timelines

Acceptance criteria

State how the client will determine whether the deliverables are acceptable.

Pricing and payment structure

State whether pricing is:

  • fixed fee
  • milestone-based
  • hourly or daily rate
  • retainer plus project fee

The SOW should also say whether VAT is included or excluded and how invoicing will work. SARS guidance makes clear that VAT treatment must be handled properly in service transactions. :contentReference[oaicite:9]{index=9}

Assumptions and dependencies

List the assumptions the pricing or timeline depends on.

Change control

State how scope changes will be handled, such as through written change requests or signed variations.

Sign-off

Include signature or approval lines where appropriate, especially if the SOW is meant to become part of the contract.

Why out-of-scope wording matters

One of the biggest SOW mistakes is defining what is included without saying what is excluded. South African project-planning guidance specifically notes the importance of identifying what is and what is not included under “in scope” and “out of scope.” :contentReference[oaicite:10]{index=10}

That means a South African SOW should usually say things like:

  • post-launch support is excluded unless separately agreed
  • travel costs are excluded unless stated otherwise
  • third-party licence costs are excluded
  • client-supplied content is assumed
  • change requests are outside the original fee

Clear exclusions often prevent more disputes than the rest of the document.

Pricing, VAT, and invoicing

A South African SOW should align with the commercial and tax reality of the project. If the supplier is VAT-registered, the SOW should make pricing treatment clear so that later invoices match the commercial terms. SARS’s VAT guides explain that VAT applies to taxable supplies of goods or services by vendors and that construction and services transactions can involve specific VAT consequences depending on the nature of the work. :contentReference[oaicite:11]{index=11}

This means a strong SOW should ideally say:

  • whether fees are VAT-inclusive or VAT-exclusive
  • when invoices may be issued
  • whether billing is milestone-based, monthly, or on completion
  • whether reimbursable expenses are allowed

Common mistakes

Common South African statement-of-work mistakes include:

  • using vague scope descriptions
  • not defining deliverables properly
  • leaving acceptance criteria out
  • no out-of-scope section
  • no milestone dates
  • pricing not linked to deliverables
  • not stating VAT treatment clearly
  • assuming the proposal email is enough
  • treating the SOW as a replacement for the main contract
  • not explaining client dependencies

These mistakes often lead directly to payment disputes and project friction.

Practical questions before using an SOW

Before using a statement of work in South Africa, ask:

  • Is the work clearly defined?
  • Do we have a main contract behind this SOW?
  • What is specifically out of scope?
  • How will the client accept the work?
  • Are milestones and deadlines realistic?
  • Is pricing linked properly to the work?
  • Does the SOW align with VAT and invoice handling?
  • What happens if the scope changes?

These questions help turn the SOW into a real delivery document rather than just a project summary.

Example of when this guide is useful

This guide is useful for:

  • a South African consultant delivering a defined project
  • a company hiring a service provider under a master agreement
  • a software or IT team documenting implementation scope
  • a procurement team needing a structured project schedule
  • a contractor wanting clearer written deliverables before work begins

FAQ

What is a statement of work in South Africa?

It is a project or services document that defines the specific work, deliverables, timelines, responsibilities, and payment structure for a supplier or service-provider engagement.

Is a statement of work the same as a contract?

No. The SOW usually sets out the project-specific details, while the main contract contains the broader legal terms. In South African services agreements, schedules and annexures are often expressly incorporated into the contract. :contentReference[oaicite:12]{index=12}

Is a statement of work the same as a scope of work?

Not always, but the terms are often used interchangeably. In practice, the scope of work is usually one major section inside the full statement of work. :contentReference[oaicite:13]{index=13}

Should a South African SOW include VAT wording?

Yes. If the supplier is VAT-registered, the SOW should make pricing treatment clear so the commercial document aligns with later invoicing and VAT administration. :contentReference[oaicite:14]{index=14}

Why should an SOW include an out-of-scope section?

Because it helps define project boundaries and reduce scope creep. South African project-planning guidance specifically highlights the need to identify both in-scope and out-of-scope items. :contentReference[oaicite:15]{index=15}

Can an SOW be attached to a services agreement?

Yes. South African services agreements commonly use schedules, annexures, and proposals as integral parts of the contract framework. :contentReference[oaicite:16]{index=16}

Related guides

You may also want to read:

  • Service Agreement
  • Consulting Agreement Guide
  • Contractor Agreement Guide
  • Purchase Order Guide
  • Quote Template Guide
  • Invoice Template
  • Equipment Sale Agreement Guide
  • Statement of Work Template

A strong South African statement of work should define scope clearly, identify what is out of scope, tie deliverables to milestones and pricing, and sit properly inside the wider contract framework so the project can be delivered and billed with less room for dispute.