What Is a Change Order (Variation)?
A change order — also called a variation order or variation — is any modification to the scope of work, cost, or timeline agreed in a development contract. Rather than cancel a contract and start fresh, contractors and procuring entities use change orders to adapt the original agreement as conditions change during project implementation.
In multilateral development bank (MDB) contracts — those funded by the World Bank, Asian Development Bank (ADB), African Development Bank (AfDB), and others — change orders are a formally managed part of the contract lifecycle. They are not exceptions; they're expected tools for managing project reality.
Key principle: A valid change order must be approved in writing by both parties (contractor and procuring entity) and, depending on size, may require MDB no-objection before taking effect.
---
Why Do Change Orders Happen?
Change orders are triggered by several common scenarios in development projects:
- Scope expansion: Client requests additional work not in the original bid (e.g., a road construction includes extra drainage systems).
- Scope reduction: Budget cuts or phasing require eliminating contract scope.
- Design changes: Engineers discover underground utilities or soil conditions not anticipated, forcing design revisions.
- Market changes: Material costs spike (steel, diesel), forcing cost adjustments.
- Regulatory changes: New environmental or labor standards increase compliance costs.
- Force majeure: War, natural disaster, or pandemic disrupts supply chains or site access.
- Productivity delays: Unforeseen site conditions slow work; extension of time (EOT) with cost adjustment is negotiated.
The most common development procurement disputes arise when contractors fail to document change orders properly, leaving cost claims undefended or MDB audits rejecting reimbursement.
---
Thresholds and Approval Levels
The critical question for every contractor: How big must a change be before formal approval is required?
MDBs use percentage thresholds tied to the original contract value:
World Bank Rules
- Changes under 10% of the original contract amount: Procuring entity can approve directly, though MDB no-objection is still recommended.
- Changes 10–15%: Procuring entity approval + World Bank no-objection required.
- Changes exceeding 15%: May exceed MDB's delegated authority; escalation to World Bank headquarters may be needed.
Note: The World Bank's 2023 Procurement Framework refined these rules. Always verify current thresholds in your specific project's Procurement Manual.
ADB Rules
- Under 10%: Implementing agency approval; documented but no MDB pre-approval needed.
- 10–15%: ADB no-objection required.
- Over 15%: May require ADB Board approval (rare).
The ADB's User Guide for Procurement of Works (in contracts for infrastructure and construction) specifies that changes must be documented in writing, with supporting calculations for cost and time adjustments.
IsDB (Islamic Development Bank) Rules
- Up to 15%: Beneficiary (procuring entity) may approve; IsDB no-objection required if the change affects the overall project scope or financing.
- Above 15%: Mandatory IsDB approval.
Practical takeaway: If your change order is under 10% of the original contract price, you have the best chance of fast approval. Between 10–15%, budget 4–6 weeks for MDB review. Above 15%, plan for escalation and extended timelines.
---
The Change Order Process: Step-by-Step
1. Document the Need (Contractor's Responsibility)
The contractor must identify and document what triggered the change:
- Photographs of site conditions
- Engineer's findings memo
- Cost breakdown (labour, materials, equipment, overhead)
- Time impact analysis (how many days does the change add or save?)
Pro tip: Start documenting immediately. Delays of weeks or months weaken your claim.
2. Submit a Formal Change Request
Submit to the Project Engineer or Resident Engineer (on-site representative of the procuring entity). The request must include:
- Clear description of the change
- Reason for the change
- Cost impact (itemized: labour hours × rate, materials, equipment hire)
- Time impact (additional days to completion, if any)
- Supporting evidence (photos, soil test results, market quotes for materials)
3. Procuring Entity Review
The Project Engineer reviews the contractor's proposal and either:
- Accepts it: If justified and within threshold, issues a Change Order (CO) draft.
- Negotiates: If the cost or time seems excessive, counter-offers a lower adjustment.
- Rejects it: If the change is deemed out of scope or the contractor's calculation is unreasonable.
This step typically takes 2–4 weeks.
4. MDB No-Objection (If Threshold Crossed)
If the change exceeds 10% of the original contract value (or the MDB's delegated threshold), the procuring entity submits the proposed Change Order to the MDB for review. The MDB verifies:
- Cost is reasonable (compared to market rates)
- Change doesn't violate project design or MDB policy
- Financing is available to cover the additional cost
Timeline: 3–8 weeks for MDB review, depending on complexity and MDB workload.
5. Formal Execution
Once approved (or deemed approved if no objection is raised by the MDB), both contractor and procuring entity sign the Change Order. It becomes part of the contract.
Total timeline: 6–12 weeks for changes over 10%, or 2–4 weeks for changes under 10%.
---
Extension of Time (EOT) vs. Cost Variation
A common confusion: Do I get paid for delays caused by others' actions?
Development contracts distinguish between two types of changes:
Extension of Time (EOT) – Time Only, No Cost
Contractor gets extra time to complete, but no additional payment. Examples:
- Procuring entity delays site handover to contractor
- Unforeseen subsurface conditions require additional investigation (contractor absorbs the cost)
- Extreme weather outside normal seasonal patterns
Contractor's protection: The contract should clearly state what conditions trigger an EOT without cost (e.g., "acts of God beyond contractor's control").
Cost Variation – Increased Cost (± Time)
Contractor gets additional payment because external factors increase genuine costs. Examples:
- Material cost inflation (steel, cement prices jump 20% mid-project)
- Labor escalation per contract terms
- Procuring entity-requested scope addition
Key rule: Changes requested by the procuring entity almost always result in cost variation. Changes caused by contractor error usually do not.
How to Read Your Contract
Look for sections titled:
- "Variations" or "Contract Changes"
- "Extension of Time" or "EOT"
- "Cost Adjustment Clause" or "Escalation"
- "Clause 13" or similar (contract clause numbers vary)
If your contract is silent on variations, this is a red flag — it means disputes are unmanageable. Always negotiate variation terms before signing.
---
Common Pitfalls That Cost Contractors Money
1. Verbal Approvals
Mistake: Supervisor says "go ahead," no written order issued. Later, contractor claims payment; MDB says "not documented, no cost adjustment."
Protection: Insist on a written Change Order before proceeding. Document every request in writing.
2. Backdating Change Orders
Mistake: Contractor incurs cost, then retroactively requests a change order weeks later.
MDB response: Audit flags it as unsupported; reimbursement denied.
Protection: Submit change requests immediately, not after work is done.
3. Burying Costs in the Wrong Line Item
Mistake: Cost caused by a change order is hidden in "general overhead" or another budget line.
MDB audit: Rejects allocation; contractor absorbs cost.
Protection: Always link costs directly to the approved change order reference number.
4. Ignoring the Threshold
Mistake: Contractor splits one large change (30%) into three small orders (10% each) to avoid MDB scrutiny.
MDB response: Related changes are aggregated; project flagged for audit; contractor loses credibility.
Protection: Group related changes and submit together, even if it crosses the threshold.
5. No EOT Claim When Delay Was Procuring Entity's Fault
Mistake: Project runs late due to procuring entity's delayed decisions, but contractor doesn't formally claim Extension of Time.
Result: Contract completion date passes; contractor penalized (liquidated damages), even though delay wasn't their fault.
Protection: Submit EOT claims immediately when delay occurs, with supporting evidence. EOT is separate from cost variation.
---
Contractor Rights in Change Order Disputes
What if the procuring entity denies a reasonable change order?
Right to Escalate
If the procuring entity refuses a justified change order (e.g., cost inflation on materials), the contractor can:
- Appeal to the Project Manager or Resident Engineer's superior.
- Submit a formal dispute notice to the MDB Grievance/Disputes Resolution mechanism (most MDBs have one).
- Invoke Dispute Resolution Clause in the contract (typically mediation, then arbitration).
Documentation Is Everything
MDB arbitrators prioritize contemporaneous documentation. Prove:
- When the change was identified
- What the original contract said
- Market evidence for cost (quotes from suppliers, labor market data)
- That work was actually performed
Partial Payment
Even if a change order is disputed, contractors can sometimes secure partial payment for work performed while disputes are resolved. Request this explicitly in your appeal.
---
MDB Fraud Risk: Variation Orders
Development banks scrutinize change orders closely because they're frequent vehicles for corruption:
- Inflated cost claims (contractor and engineer collude)
- Fake changes to hide kickbacks
- Retroactive orders masking unauthorized work
What this means for you: Use only certified suppliers for materials, keep detailed daily records, and document everything with photos/timestamps. Audits are rigorous; clean records protect both you and your reputation.
---
Key Takeaways for Contractors
- Variations are normal — expect them; budget for negotiation time and legal review.
- Know your thresholds — changes under 10% are faster; over 15% require escalation.
- Document immediately — costs claimed weeks after work are often rejected.
- Write it down — verbal approvals don't count for MDB reimbursement.
- Separate time from cost — EOT claims and cost variations are distinct; claim both if justified.
- Read your contract's variation clause — every MDB and country has different rules.
- Appeal if needed — wrongful denial is challengeable through MDB grievance mechanisms.
---
Related Resources on BidsFactory
For more context on development procurement and contracting, explore:
- World Bank Procurement Framework
- ADB Procurement Rules
- Works Contracts
- Understanding Bid Bonds and Performance Securities
- Contractor Debarment and Eligibility in MDB Sanctions
Browse active works procurement opportunities on BidsFactory to see how variations and change order clauses are mentioned in real RFPs.
