Change Order
Template — South Africa
An attorney-drafted Change Order template designed specifically for South African businesses. This comprehensive document formally records modifications to project scope, timeline, budget, or deliverables under an existing Statement of Work or service agreement — ensuring both parties agree to variations in writing before additional work begins, as required by the non-variation principle upheld in South African contract law.
Drafted by qualified South African attorneys
Reviewed for compliance with current legislation · Last updated April 2026
Why Your Business Needs This Agreement
Unpaid Additional Work Due to Missing Written Variations
Service providers who perform additional work based on verbal instructions or email requests — without a signed Change Order — face the risk of non-payment with limited legal recourse. Where the original agreement contains a non-variation clause (upheld in SA Sentrale Ko-op v Shifren), the provider cannot enforce the verbal agreement as a contractual variation. The only potential remedies — unjust enrichment or estoppel — are significantly harder to prove, more expensive to litigate, and yield lower recoveries than a straightforward contractual claim. This is one of the most common sources of commercial loss in South African professional services.
Scope Disputes Escalating to Costly Arbitration or Litigation
When scope changes are handled informally — through emails, meeting notes, or verbal discussions — both parties develop different understandings of what was agreed. By the time the project is complete, the client expects deliverables that the provider believes were never part of the scope, or the provider has performed work the client believes was already included in the original price. Without a formal Change Order documenting each variation, the resulting disputes require extensive evidence gathering and often proceed to arbitration or litigation. AFSA arbitration costs R100,000-R500,000 for commercial disputes, and High Court litigation can exceed R1 million — costs that a simple Change Order process would have prevented entirely.
Budget Overruns Without Client Awareness or Approval
Without a formal Change Order process, scope changes accumulate incrementally — a small addition here, an extra feature there — until the project budget has been exceeded by 30-50% without the client ever formally approving the additional expenditure. This creates a dual problem: the service provider has performed work they may not be compensated for, and the client faces unexpected costs they did not budget for. A formal Change Order process with cost impact assessment and budget sign-off ensures that both parties understand and approve the financial implications of every scope change before additional work begins.
Timeline Slippage from Unassessed Scope Changes
When scope changes are added without formal impact assessment, the cumulative effect on the project timeline is not quantified or communicated. Additional deliverables and modifications consume project resources without corresponding timeline adjustments, leading to missed milestones and delayed completion. For projects with penalty clauses for late delivery, this can result in significant financial exposure for the service provider. A formal Change Order process requires timeline impact assessment for every change, ensuring that both parties understand how each modification affects the overall project schedule.
Audit and Compliance Failures from Poor Change Documentation
In regulated industries and large enterprises, contract variations must be documented and auditable. Informal scope changes that are not captured in signed Change Orders create compliance gaps — particularly for organisations subject to public procurement regulations, financial services compliance requirements, or corporate governance standards such as King IV. Auditors and regulators expect a complete paper trail from original agreement through every variation to final deliverables. Missing Change Orders can result in audit findings, compliance penalties, and in the public sector, potential Auditor-General qualifications.
What is a Change Order?
Projects rarely proceed exactly as planned. Requirements evolve as business conditions change, new information surfaces during delivery, stakeholder priorities shift, and technical discoveries alter the optimal approach. A Change Order provides the formal mechanism to document and approve these modifications without renegotiating the entire agreement — creating a legally binding record of what changed, why it changed, how it affects cost and timeline, and that both parties consented to the variation.
In South African contract law, the ability to vary a contract is governed by both common law and specific case law. The landmark Supreme Court of Appeal decision in SA Sentrale Ko-op Graanmaatskappy Bpk v Shifren established that a non-variation clause in a written agreement is enforceable — meaning that if the original agreement requires amendments to be in writing and signed by both parties, an oral or informal agreement to change the scope is unenforceable. This principle was affirmed in Brisley v Drotsky and makes the formal Change Order process not merely a best practice, but a legal necessity for agreements containing non-variation clauses.
The Consumer Protection Act 68 of 2008 (CPA) adds regulatory requirements where the client qualifies as a consumer. Section 49 requires that material changes to service terms be communicated clearly and that the consumer understands the cost implications before agreeing to additional work. Section 22 prohibits unconscionable conduct, including taking advantage of a consumer's inability to understand the cost implications of scope changes. These provisions require that Change Orders present cost and timeline impacts in plain, understandable language — not buried in technical jargon or attached as dense appendices.
Under common law, the variation of a contract requires the same elements as the formation of a new contract: consensus (genuine agreement between the parties), capacity, legality, and possibility of performance. A Change Order that is signed under duress, that contains terms that are illegal, or that requires performance that has become impossible would be unenforceable on these grounds. The Change Order must reflect genuine agreement — not merely the service provider presenting a fait accompli after work has already been performed.
The Electronic Communications and Transactions Act 25 of 2002 (ECTA) validates electronic signatures on Change Orders under Section 13 and gives legal recognition to electronic communications used in the change request and approval process. In modern project delivery, where change requests are often initiated by email and approvals need to happen quickly, ECTA ensures that electronic Change Orders carry the same legal weight as their paper counterparts. However, the approval must come from an authorised representative — an email from a project coordinator who lacks signing authority may not constitute a binding variation.
This template is designed to work alongside Master Services Agreements and Statements of Work, providing a structured process for documenting and approving project variations. It captures the original terms, the proposed changes, the impact on cost and timeline, the business justification, and the formal approval of both parties — creating an auditable trail of how the project evolved from its original scope. Whether you are managing IT development projects, consulting engagements, construction works, or marketing campaigns, this Change Order template provides the contractual rigour needed to manage scope changes effectively under South African law.
Who Needs This
Want early access to the Change Order template?
We'll email you the moment early access opens
The Supreme Court of Appeal in SA Sentrale Ko-op v Shifren [1964] established that non-variation clauses are enforceable — verbal or informal scope changes are unenforceable where such a clause exists
Under CPA Section 49, material changes to service terms must be communicated in plain language with clear cost implications before the consumer agrees
Electronic signatures on Change Orders are valid under ECTA Section 13, enabling rapid digital approval cycles for agile project delivery
A Change Order is a variation of the original contract, not a novation — all non-modified terms of the MSA and SoW remain in full force and effect
Claims relating to Change Order work prescribe after three years under Section 11(d) of the Prescription Act 68 of 1969 — timely invoicing and record-keeping are essential
Key Clauses Included
This Change Order template covers 10 essential sections, each drafted by South African attorneys.
Change Order Identification and Reference
Establishes the administrative framework for the Change Order, including a unique sequential number, the date of the request, the party initiating the change, and full cross-references to the parent MSA, SoW, and any prior Change Orders affecting the same scope area. This section creates the audit trail that links the Change Order to the original contractual commitments. In South African commercial practice, clear document numbering and cross-referencing is essential for contract administration — particularly where multiple SoWs and Change Orders are active simultaneously under the same MSA.
Description and Justification of the Change
Provides a detailed description of the proposed modification — what is being added, removed, or altered in the scope, deliverables, or approach. The business justification explains why the change is needed, linking it to business requirements, technical discoveries, regulatory changes, or stakeholder feedback. This section is critical for governance and audit purposes, ensuring that scope changes are driven by legitimate business needs rather than arbitrary requests. Under the CPA, where applicable, the description must be in plain language that the client can understand without specialist technical knowledge.
Impact on Project Timeline and Milestones
Analyses how the proposed change affects the project schedule — whether milestones need to move, whether new milestones are created, whether the overall project end date is affected, and whether the change impacts the critical path. The section presents the original timeline, the revised timeline, and the specific milestones affected. Dependencies are updated to reflect the new scope, and any impact on other active SoWs or workstreams under the same MSA is documented. For construction and engineering projects governed by penalty clauses for late completion, the timeline impact assessment is particularly critical.
Cost Impact and Revised Budget
Quantifies the financial impact of the change — additional fees for new scope, cost savings for removed scope, changes to the pricing model for modified deliverables, and any adjustments to expense budgets. The section presents the original budget, the change amount, and the revised total. All amounts are stated exclusive of VAT at 15% under the Value-Added Tax Act 89 of 1991. For time-and-materials engagements, the cost impact is expressed in estimated additional hours at the agreed rate card. For fixed-price engagements, the cost impact is a specific additional or reduced amount with clear pricing justification.
Revised Acceptance Criteria
Where the change modifies existing deliverables or introduces new deliverables, this section documents the revised acceptance criteria against which the modified deliverables will be assessed. Maintaining clear, measurable acceptance criteria through Change Orders is essential — without them, the acceptance of modified deliverables becomes subjective and prone to dispute. Under CPA Section 56, the implied warranty that deliverables must be of good quality applies to modified deliverables just as it does to the original scope.
Impact on Other Provisions
Documents any impact the change has on other SoW provisions — resources and roles, assumptions, risks, testing requirements, or IP deliverables. If the change introduces new third-party components, open-source software, or subcontractor dependencies, these are captured here. This section ensures that the Change Order is comprehensive and does not create inconsistencies with the remaining provisions of the SoW that continue in effect. Under South African common law, an amendment to one part of a contract does not automatically amend other parts — each modification must be expressly documented.
Risk Assessment
Evaluates the risks associated with implementing or not implementing the proposed change. The assessment covers delivery risks (will the change introduce new complexity or dependencies?), commercial risks (does the change affect the project's commercial viability?), technical risks (does the change affect system architecture or integration points?), and regulatory risks (does the change affect compliance with applicable laws?). Risk owners and mitigation strategies are identified. This section supports informed decision-making by the approving authorities on both sides.
Approval and Authorisation
Provides signature blocks for authorised representatives of both parties, the approval date, and the effective date from which the change applies. The section explicitly requires that the signatories have the authority to bind their respective organisations — this is critical under South African agency law, where a person acting without authority cannot bind the principal (subject to the doctrines of estoppel and ratification). If the Change Order exceeds a specified value threshold, it may require additional approvals such as steering committee or board-level sign-off, as defined in the MSA or SoW's governance provisions.
Confirmation of Continuing Terms
States explicitly that all terms and conditions of the original MSA and SoW that are not modified by this Change Order remain in full force and effect. This boilerplate provision is legally important under South African contract law — without it, a party might argue that the Change Order constituted a novation (replacement) of the original agreement rather than a variation (amendment). The distinction matters because novation extinguishes the original agreement entirely, while variation preserves it with specific modifications.
Document Control and Distribution
Specifies the number of original copies, the distribution list for signed copies, and the document management procedures for incorporating the Change Order into the project's contractual records. In South African contract disputes, the production of original signed documents carries significant evidentiary weight. The section also addresses electronic storage and ensures that the Change Order is incorporated into both parties' contract management systems for reference during project delivery and any future dispute resolution proceedings.
South African Law Compliance
South African Common Law of Contract — Non-Variation Principle
The landmark decision in SA Sentrale Ko-op Graanmaatskappy Bpk v Shifren [1964] established that non-variation clauses — provisions requiring all amendments to be in writing and signed by both parties — are enforceable under South African law. This was affirmed in Brisley v Drotsky [2002] by the Supreme Court of Appeal. Where the original MSA or SoW contains such a clause (as most commercial agreements do), any variation that is not documented in a signed written Change Order is unenforceable. This makes the formal Change Order process a legal necessity, not merely a best practice. A party that performs additional work based on an oral or email agreement without a signed Change Order assumes the risk of non-payment.
Consumer Protection Act 68 of 2008
Where the client qualifies as a consumer under Section 5, the CPA imposes specific requirements on Change Orders. Section 49 requires that changes to service terms — including cost implications — be drawn to the consumer's attention in plain and understandable language before the consumer commits to the variation. Section 22 prohibits unconscionable conduct, including taking advantage of a consumer's inability to understand the implications of a scope change. Section 48 provides that a contract term is unfair if it is excessively one-sided — a Change Order that benefits only the service provider without genuine benefit to the client may be challenged on this basis.
Electronic Communications and Transactions Act 25 of 2002
ECTA validates electronic signatures on Change Orders under Section 13(1), provides legal recognition for data messages used in the change request and approval process (Section 11), and establishes the legal framework for electronic formation of contractual variations (Section 22). This is particularly important in agile project delivery where change requests are frequent and require rapid turnaround. However, the approval must come from a person with the authority to bind the organisation — an electronic communication from an unauthorised person does not constitute a binding variation.
Value-Added Tax Act 89 of 1991
Change Orders that increase the project value must address VAT implications. All additional fees must be stated exclusive or inclusive of VAT at 15%, and the service provider's invoicing for Change Order work must comply with the tax invoice requirements of Section 20. Where a Change Order changes the nature of the services (for example, adding a supply of goods component to a services engagement), different VAT treatment may apply to the new scope elements. The cost impact section must be clear on VAT treatment to avoid disputes during invoicing.
South African businesses are lining up for My-Contracts — be first in when we launch
Create Your Change Order in Minutes
Our guided wizard walks you through every clause — no legal knowledge required. Attorney-drafted, South African law compliant.
Identify and document the change requirement
When either party identifies a need to modify the project scope, timeline, or budget, document the change requirement with a clear description of what needs to change and why. Reference the specific sections of the SoW that are affected. The change can be initiated by either party — the client requesting additional functionality or the provider identifying a necessary technical modification. Use the Change Order template's description section to capture the full details and business justification.
Assess the impact on timeline, cost, and other provisions
The service provider prepares a formal impact assessment documenting how the change affects the project schedule, budget, resources, deliverables, acceptance criteria, and any other SoW provisions. The assessment should be transparent and based on the same pricing methodology used in the original SoW. Present the original terms, the proposed changes, and the revised totals clearly. Ensure all cost figures are stated with consistent VAT treatment.
Review and negotiate the Change Order terms
Both parties review the proposed Change Order, negotiate the cost and timeline impact if necessary, and reach agreement on the final terms. If the CPA applies, ensure the cost implications are presented in plain language. For Change Orders above the value threshold defined in the MSA or SoW governance provisions, obtain the required additional approvals (steering committee, procurement, board) before proceeding to execution.
Execute the Change Order before work begins
Have authorised representatives of both parties sign the Change Order. Electronic signatures are valid under ECTA Section 13. The signed Change Order becomes effective from the date specified in its terms. Critically, no out-of-scope work should commence until the Change Order is fully executed — starting work before sign-off creates the risk of non-payment if the client subsequently refuses to approve the change.
Integrate the Change Order into project management
Update the project plan, budget tracker, milestone schedule, and resource allocation to reflect the approved Change Order. Distribute copies to both project teams and update the contractual document register. File the signed Change Order with the original MSA and SoW for audit trail purposes. Ensure the revised scope, timeline, and budget are reflected in ongoing project reporting and status meetings.
Frequently Asked Questions
A Change Order is a formal document that records an agreed modification to an existing contract, Statement of Work, or service agreement. It captures what is changing, why the change is needed, how it affects the budget and timeline, and the approval of both parties. In South African law, the Change Order is critically important because of the non-variation principle established in SA Sentrale Ko-op v Shifren — where the original agreement requires amendments to be in writing and signed, any variation that is not documented in a signed Change Order is legally unenforceable. This means that if a service provider performs additional work based on a verbal agreement or email request without a signed Change Order, they may have no contractual basis to demand payment for that work. The Change Order provides the legal certainty both parties need when project scope evolves.
What You Get With This Template
Drafted specifically for South African law — aligned with the Shifren non-variation principle, CPA plain language requirements, and ECTA electronic signature provisions
Comprehensive impact assessment framework covering timeline, cost, acceptance criteria, resources, risks, and downstream effects on related workstreams
Clear authorisation requirements that ensure only persons with binding authority can approve changes — preventing unauthorised scope variations
VAT-compliant cost impact documentation with transparent pricing methodology referenced to the original SoW pricing framework
Audit-ready document structure with sequential numbering, cross-references, and document control provisions for regulated environments
Express confirmation that non-modified terms remain in force — preventing arguments that the Change Order constituted a novation of the original agreement
Risk assessment section that supports informed decision-making by evaluating delivery, commercial, technical, and regulatory risks of the proposed change
Flexible enough for both traditional waterfall and agile delivery methodologies with guidance on threshold-based change management