Variations are the most common reason an office fit-out ends over budget and late. In Pune and Mumbai projects, late changes to cabins, meeting room counts, MEP routing or imported items often cost several times more than the same decision taken at design stage, because every shift touches approvals, materials and trade sequencing.
This article sets out a practical variation workflow: how to classify a change, price and programme its impact before approval, and keep a variation register that leadership can trust. It also covers the triggers we see most often locally and how a design-build contract changes the dynamics. For the wider contractual picture, see our note on how fixed-price contracts reduce fit-out risk.
Why late variations inflate cost and schedule
A variation is cheap on paper and expensive in sequence. Moving one glass partition sounds like a day of work. In practice it pulls in the partition contractor, the MEP rerouting above the ceiling, the floor box positions, the fire detection layout and a fresh landlord submission if the layout drawing changes.
The direct trade cost is often the smallest part. The real cost sits in re-mobilisation, idle labour, re-tested services and the programme float that quietly disappears. Teams that log variations only as a rate multiplied by quantity typically understate the true impact by a wide margin.
A disciplined variation workflow
Every change request should pass through four gates before anyone lifts a tool:
- Origin: who asked for it and why. Client request, site condition, code requirement or design coordination gap.
- Impact on cost: priced against the bill of quantities, including preliminaries and rework, not just the new item.
- Impact on time: effect on the critical path, stated in working days.
- Approval authority: who can sign at what value, agreed in the contract before work starts.
Nothing proceeds on a verbal instruction. Once approved, the baseline is reissued so the next change is measured against the true current position, not a stale plan.
Typical variation triggers in Pune and Mumbai projects
Most variations in local projects come from a handful of predictable sources. Knowing them lets you resolve many before they become change orders:
| Trigger | Typical cause | Early defence |
|---|---|---|
| Landlord conditions | Building rules on working hours, material lifts or duct routing surface late | Close the landlord submission and logistics plan before mobilisation |
| MEP clashes | Services routed without coordinated shop drawings | Full BIM or drawings-based coordination before ceiling closure |
| Headcount changes | Business growth or restructuring changes desk and cabin counts | Design zones, not fixed desk positions, into the layout |
| Imported items | Lead times on specialist lighting, glass or furniture force redesign | Track long-lead items from day one and freeze specifications early |
The landlord trigger deserves its own attention; our Mumbai landlord submission checklist covers the documents that prevent most of these surprises.
How design-build changes variation handling
With multiple vendors, a variation becomes a negotiation. The interior contractor blames the MEP vendor, the MEP vendor asks for a site instruction, and the client's team spends its weeks arbitrating. Accountability for the combined cost and time impact is diffuse, and each party prices defensively.
Under a design-build contract, one party owns the design, the estimate and the site. A variation is assessed once, against one baseline, by the team that will execute it. That does not make variations cheaper, but it makes their impact visible and single-sourced, which is what leadership actually needs to decide.
The variation register as a governance tool
A variation register is a simple table, but it is the single most honest document on the project. Each row carries the reference, description, origin, cost impact, time impact, approval status and approval date. Reviewed weekly, it answers the question executives actually ask: where does the project stand against the budget we approved?
Three habits keep it useful. Log every request, including ones later rejected, so patterns become visible. Tie each approval to a revised cash flow and programme so finance is never surprised. And report cumulative variation value as a percentage of contract value at every review, because a register that only grows in one direction is a signal to stop and re-plan, not to keep approving.
Where to start on your project
If your fit-out is already running, put the register in place this week, even retroactively, and reconcile it against invoices raised so far. If you are about to start, agree the approval authority matrix and the variation clause in the contract, and freeze the design baseline before site handover.
Variation control is not about saying no to change. Businesses change, and the office should follow. It is about making sure every yes is a priced, scheduled, owned decision. If you want a second opinion on your change control setup before mobilisation, talk to our team.
Frequently asked questions
Any instruction that changes the approved scope, layout, specification, cost or completion date. It includes omissions and substitutions, not just additions.
A pre-agreed authority matrix: small values at project manager level, larger values with the client's leadership. The thresholds should be written into the contract before site start.
Projects with a disciplined design freeze typically need far less than loosely scoped ones. Our budgeting article on fit-out contingency covers typical allowances in detail.
Occasionally, when a simplification removes a coordination constraint. But most additions extend the critical path, which is why every variation needs a written time impact, not just a price.