Variation Orders in Pakistan Construction: How to Manage, Negotiate & Protect Yourself

On nearly every project we manage — from a 1,200 sqft retail fit-out in Clifton to a multi-storey commercial build in DHA — a variation order shows up sooner or later. Handled well, a VO is a routine adjustment to scope. Handled badly, it becomes the single biggest source of cost overruns, programme slippage, and breakdowns in trust between owner and contractor. This guide walks through how VOs actually work on Pakistani sites, the documentation habits that protect both sides, and the negotiation approach we use to keep variation pricing fair and defensible.

01 — DefinitionsWhat Is a Variation Order — and What It Isn't

In its simplest form, a variation order (VO) is an instructed change to the scope, quantity, quality, sequence, or method of the works that affects the contract price, the completion date, or both. The word "instructed" matters more than anything else in that sentence.

On site in Pakistan, the terms "VO," "extra item," and "deviation" tend to get used interchangeably — and that loose usage is itself part of the problem. Contractually, a VO sits on one side of a clear line: on one side is an instructed, documented, and priced change to the contract; on the other side is unrecorded extra work that someone simply carried out because they were asked to, with no paper trail to support payment later.

Variations generally fall into three categories:

• Additions — new work not included in the original scope, such as an extra partition wall, additional power points, or a new boundary wall.
• Omissions — work removed from the original scope, such as a deleted false ceiling or a cancelled external staircase.
• Substitutions — one specification swapped for another, such as vitrified tiles instead of marble, or a different brand of split AC units.

Each category affects the contract sum differently, and each needs its own paper trail. Omissions, in particular, are the variations most often forgotten — because nobody chases a credit the way a contractor chases a debit. A disciplined VO process tracks both directions equally.

02 — ContextWhy Variation Orders Are So Common on Pakistani Sites

A handful of recurring patterns explain why VOs are the rule rather than the exception on most projects we see:

• Drawings that keep evolving. Tender drawings are often issued before the design is fully resolved, particularly on interior fit-outs and renovation work. "Design development" continues well into construction, and every revision is a potential variation.
• Provisional sums and ambiguous BOQ items. Finishes, MEP fixtures, and specialist works are frequently tendered against provisional sums or loosely worded descriptions. When the final selection happens, the gap between the provisional allowance and the actual cost becomes a VO — sometimes a large one.
• Site conditions that don't match assumptions. Existing structures, buried services, soil conditions, and the real state of an older building rarely match what was assumed at tender stage — especially on renovation and fit-out projects in older parts of Karachi.
• Owner-driven changes mid-project. Private residential and commercial clients frequently change their minds once work takes physical shape. A kitchen layout that looked fine on a drawing suddenly needs to move once the walls are up.
• A culture of verbal instructions. "Just start, we'll sort the paperwork later" is one of the most common — and most expensive — sentences on a Pakistani construction site. It feels efficient in the moment and almost always creates a dispute later.

None of these causes are unusual, and most aren't even avoidable. What separates a well-run project from a troubled one isn't the absence of VOs — it's whether each one is captured, priced, and agreed close to the moment it happens.

03 — ProcessThe Variation Order Process — How It Should Work

Most consultancy-administered contracts in Pakistan — particularly those following FIDIC-based conditions, whether applied directly or adapted through PEC, NHA, or similar standard forms — set out a variation procedure resembling FIDIC's Clause 13 (Variations and Adjustments). Stripped of the legal language, the process should run through seven steps:

1. Identification — someone (the consultant, contractor, or client) identifies that a change is needed.
2. Written instruction — the person with contractual authority (usually the Engineer or Project Manager named in the contract — not "anyone on site") issues the instruction in writing, referencing drawings or specifications as needed.
3. Confirmation of Verbal Instruction (CVI) — if, in genuine urgency, an instruction is given verbally, the contractor issues a written confirmation within the period stated in the contract. If the Engineer doesn't object within that timeframe, the instruction is treated as confirmed.
4. Priced proposal — before, or very shortly after, starting the additional work, the contractor submits a breakdown of quantities, rates, and any time impact.
5. Valuation — the change is priced using the contract's own hierarchy (see table below), not an open negotiation from scratch.
6. Formal agreement — a signed VO instrument is issued, referencing the relevant drawing or specification revision, the agreed value, and any agreed time adjustment.
7. Incorporation — the VO is logged in the running VO register and reflected in the next interim payment certificate and, where relevant, a revised programme.

The most common breakdown point is step 2 jumping straight to step 4 — work simply gets done, and the "discussion" about value and time happens months later, when memories have faded and leverage has shifted entirely.

04 — On SiteManaging VOs on Site: Documentation Discipline

Good VO management is mostly a documentation habit, not a negotiation skill — the negotiation only goes well if the documentation underneath it is solid. A few practices we insist on across every project:

• A live VO register. One document — even a simple spreadsheet — listing every VO by number, date raised, description, who instructed it, current status, value, and time impact. Updated weekly, reviewed monthly.
• A daily site diary with photographs, especially before work is covered up. Foundation levels, reinforcement before pouring, services routing before plastering — once it's covered, a dispute over "what was actually there" becomes very hard to resolve in anyone's favour.
• Nothing starts without paper. Even a WhatsApp message with a marked-up drawing and a clear scope description is better than nothing — but it should be followed within days by a formal CVI or instruction. Make this a known rule for the whole site team, not just the project manager.
• A drawing register. Keep a log of every drawing revision issued, with dates. Without this, it becomes almost impossible to prove what was "in scope" at tender stage versus what was added later.
• Monthly reconciliation. At every interim valuation, the VO register should be reviewed against the payment certificate. VOs sitting "pending pricing" for more than a month or two are a red flag — chase them while the work is still fresh in everyone's memory.

05 — NegotiationNegotiating Variation Order Pricing

When it's time to agree a number, a few habits consistently lead to fairer outcomes for both sides:

• Start from the contract's own rates. If the contract BOQ already contains a rate for the same or similar work, that rate is the starting point — not a "special VO rate." Contractors sometimes propose a fresh market rate for work that is, in substance, identical to something already priced. Push back on this directly.
• Insist on a transparent rate build-up for genuinely new items. A defensible new rate shows material quantities and current supplier prices, labour productivity (output per day), and equipment time — each referenced to a verifiable source, such as recent local supplier quotations or a recognised schedule of rates. A one-line lump sum is not a basis for agreement; it's an opening position.
• Separate — but synchronise — cost and time. Price and programme impact should be discussed in the same conversation, but recorded as two distinct items in the VO instrument. This stops one being used as leverage to inflate the other.
• Watch for bundling. A single VO submission sometimes mixes a small, clearly legitimate change with a much larger, more debatable claim. Unbundle it — agree the straightforward parts quickly, and give the contested parts the scrutiny they need without holding up the rest of the project.

06 — ContractsProtecting Yourself Contractually

Most of the protection against VO disputes is built — or lost — before construction even starts, at the contract drafting stage:

• Define who can instruct a variation. The contract should name a single role (the Engineer, Consultant, or PM) with authority to issue variation instructions. Circulate this to the site team and the contractor at project kickoff, in writing, so "instructions" from anyone else carry no contractual weight.
• Know your notice periods. FIDIC-based contracts typically require a party to give notice of a claim within a defined period — commonly around 28 days — of becoming aware of the event giving rise to it. Missing this deadline can bar an otherwise valid claim, for contractors and clients alike. A simple tracker for notice deadlines on significant events pays for itself many times over.
• Set a threshold for cumulative variations. Agree in the contract how a significant accumulation of variations — commonly discussed around the 10–15% mark of the original contract value — will be handled: a re-rate negotiation, a revised overhead and profit allowance, or an option to competitively re-tender the remaining scope.
• Guard against "constructive variations." These are situations where informal approvals — a nod on site, a verbal "fine, go ahead" — create a de facto obligation to pay, even without a formal instruction. The defence is cultural as much as contractual: make "no written instruction, no entitlement" a rule everyone on site actually knows and follows.
• Retain against disputed amounts. Where a VO's value is genuinely contested, don't certify it in full just to keep the relationship smooth. A reasonable, clearly communicated retention against the disputed portion keeps both parties motivated to resolve it properly — rather than letting it drift to the end of the project.

07 — DisputesCommon VO Disputes — and How to Avoid Them

A few dispute patterns come up again and again on Pakistani projects:

• "We were told to do it." A verbal instruction with no paper trail, raised as a claim months later. Avoided by enforcing the CVI procedure from day one, with a clear, short deadline for written confirmation.
• The end-of-project "VO dump." A large batch of variation claims surfaces near completion, often with the implicit pressure of a "global settlement" before handover. Avoided by monthly VO register reconciliation as part of every interim payment — nothing gets "saved up."
• "Is this even extra?" Genuine disagreement about whether something was already covered by the original scope, usually rooted in ambiguous drawings or BOQ descriptions. Avoided at source by tighter scope definition at tender stage, and — once ambiguity does arise — by resolving it with a written clarification before work proceeds, not after.
• Disputed daywork records. Daywork sheets reconstructed after the fact, with disagreement over hours, headcount, or materials used. Avoided by same-day, co-signed daywork records — never reconstructed from memory a week later.

08 — ChecklistPractical VO Management Checklist

A short list to pin up in the site office — if any of these are missing on your project, that's where to start.

• Maintain a single, shared VO register — updated weekly, reviewed monthly.
• No work proceeds without a written instruction or a Confirmation of Verbal Instruction (CVI).
• Daily site diary with dated photographs, especially before covering up work.
• Drawing revision log kept up to date and cross-referenced to each VO.
• Every VO priced using the contract rate hierarchy, in order — contract rates first, daywork last.
• New rates supported by a transparent build-up, never a bare lump sum.
• Cost and time impact assessed together, but recorded as two separate items.
• Notice periods tracked for every potential claim, on both sides.
• VO register reconciled against every interim payment certificate — nothing left "pending" for months.
• No "agree now, price later" — provisional values with a firm finalisation deadline if work is urgent.

ClosingFinal Thoughts

Variation orders aren't a sign that something has gone wrong with a project — they're a normal, expected part of how construction works, especially in Pakistan's fast-moving residential, commercial, and fit-out markets. The difference between a VO that's a minor administrative step and one that becomes a months-long dispute almost always comes down to discipline: written instructions, a live register, transparent pricing, and a shared understanding — agreed before the first variation ever happens — of how changes will be valued.

If your project's VO register is starting to feel less like a log and more like a list of arguments waiting to happen, that's usually a sign it's time for an independent review before — not after — the next valuation. Our cost management and quantity surveying teams help owners and contractors across Karachi keep VOs under control from day one.