HomeDecisionsThe variation decision

A change lands mid-build.

Do you absorb, replan, value-engineer — or claim?

Case study Illustrative walkthrough · scenario numbers Construction High-rise fit-out

01 · The situation

A change lands mid-build. The decision it forces takes nine days.

High-rise fit-out. Mid-build, the structural engineer issues a revised drawing, and your crew is already working right up against the zone it changes. The change is logged as a formal variation, V-118, and it lands on your desk as a decision you now owe an answer on.

BIM (the Building Information Model) is live. The programme (the project schedule) is updated. The cost report is current. And the variation eating your margin sits undecided for nine days, because three people have worked out three different answers and none of them is the number you can decide on.

ProjectHigh-rise fit-outPackage 04
TriggerRevised structural drawingLogged as variation V-118
Notice windowCloses in 4 daysAnswer owed before it shuts
EntitlementMust holdChecked against the contract
OwnerYouStatus: open

02 · Decision points

Four ways to take V-118 forward — each costs something different.

A · AbsorbEat the cost and keep building to plan. The schedule holds, but the margin takes the hit, and it may never come back.Is it small enough to swallow?
B · ReplanResequence the works around the change. Cost stays down, but the completion date slips and every trade that follows gets disturbed.How much float is left?
C · Value-engineerRedesign or substitute the affected scope. It can claw the cost back, but the redesign burns the very time you are trying to protect, and the client has to sign it off.Will approval come in time?
D · ClaimRaise the change formally and recover the cost and time. Works only if entitlement holds, and only if notice goes in before the contractual window shuts.Is the window still open?
In practice

On paper, a clean four-way choice. In practice you can't make it, because nobody can yet say what each path would cost.

03 · As-is

How it gets made today: nine days, three people, no agreed number.

Day 0Trigger

Revised structural drawing issued against a partly-built package. The change is real. The decision is now live, but nobody owns the number yet.

Day 1–4Reconcile

The QS (quantity surveyor) works out the extra cost in a spreadsheet. The planner works out how many days of delay it adds to the schedule. The contracts lead checks whether the contract even lets you claim for it. Three people, three separate answers, no single agreed number.

Day 5–8Drift

The crew keeps building toward the affected zone, so the cheap fix gets more expensive by the day, while the model lags the as-built and the notice window quietly runs down.

Day 9Forced

A call is finally made under pressure, on half-reconciled numbers, usually the safe, expensive one. Sometimes the window to claim has already closed.

~9days the decision sat open
3separate answers, none of them agreed
Risingcost of the cheap fix, for every day you wait
1call, finally made blind

04 · Assisted

The machine prepares the decision overnight. You make it before lunch.

Same change, V-118. The nine days collapse, because the three separate manual jobs become one automatic one.

Day 0It watches

Catches the change as it lands. The same revised drawing is issued. The system is already reading the instruction log, the model, the schedule and the cost position, so it catches V-118 the moment it's issued, instead of waiting for someone to notice and chase it.

Minutes laterIt thinks ahead

Gives the decision an owner and a clock. It logs V-118 as a live decision and starts the notice deadline running, so the call has an owner and a countdown from minute one, instead of drifting unowned for days.

OvernightIt prepares

Does the three jobs as one. Instead of the QS, planner and contracts lead each working a separate file, it pulls all three together by morning — cost to carry, days of delay, and whether you can claim — then shows what each of the four options would cost in money and in time, on one agreed set of numbers.

Next morningYou decide

One screen, four costed options. You open one view, see all four options costed side by side, and pick — that morning, not on day nine. The system did the reconciliation. The judgement is still yours.

05 · The options, costed

All four on one basis: cost, time, and what has to hold true.

A · Absorb
Net cost+ ₹4.2 Cr
ScheduleNo change
ConditionNone. The only certain option today.
B · Replan
Net cost+ ₹2.6 Cr
Schedule+ 11 days
Condition₹1.8 Cr in delay damages if the float runs out.
C · Value-engineer
Net cost+ ₹1.9 Cr
Schedule+ 6 days for approval
ConditionReverts to Absorb if the client rejects the redesign, six days later.
D · Claim Flagged
Net cost+ ₹1.1 Cr₹3.1 Cr and 9 days recovered
Schedule+ 9 days, recoverable
ConditionEntitlement must hold, and the notice window closes in 4 days.

Illustrative figures · scenario data, not a live system or a real project

06 · The playbook

What the options were weighed against.

R1Absorb only if it is small enough to swallow — the margin takes the hit, and it may never come back.
R2Replan only while float is left — ₹1.8 Cr in delay damages if it runs out, and every trade that follows gets disturbed.
R3Value-engineer only if client approval can come in time — otherwise it reverts to Absorb, six days later.
R4Claim only if entitlement holds, and only if notice goes in before the contractual window shuts.

This is judgment your best people already carry. Written into the decision, it works on every variation — not just the ones they happen to see.

07 · The call

Claim — four days to spare.

Decisome // Recommendation Scenario: variation V-118 84
01

Claim: ₹3.1 Cr and 9 days recovered — net cost falls to + ₹1.1 Cr, not + ₹4.2 Cr.

Net cost impactSchedule · recoverable
02

Entitlement holds — notice goes in before the window closes in 4 days.

Contract clauseNotice window · 4 days
03

Notice, EOT submission, evidence pack and cost submission drafted overnight.

5 of 5 items readyDrawing revisions · RFI thread · daywork sheets
04

Queued for the QS and contracts lead to sign — a person still reviews and issues.

Routing & deadlineAwaiting you
Challenge any line — it shows its work. Choices weighed: 4 // Rules applied: 4
Flagged —
Claim, window open

08 · After the call

Pick a direction and the whole process is already staged.

V-118 · Claim package · assembled the moment the direction was chosen✓ 5 of 5 items ready

Variation notice

Drafted against the contract clause, dated, referencing the revised drawing.

Drafted

EOT submission

Delay analysis run from the schedule, nine days, with the affected activities attached.

Drafted

Evidence pack

Drawing revisions, the RFI thread, daywork sheets and site photos, pulled and indexed.

Compiled

Cost submission

Priced from the live cost position, broken down line by line, ready to attach.

Priced
!

Routing & deadline

Queued for the QS and contracts lead to sign. Notice window closes in four days, flagged.

Awaiting you
Nothing has been issued. The whole submission is staged and waiting on review. A person still reviews and issues.

What happened next

The decision leaves the room.

Day 1

Site lead drops the EOT to 7 days — two clawed back on the slab pour; affected activities re-linked, cost submission unchanged, notice draft updated.

Day 1

Contracts lead adds the soil report to the evidence pack, then issues the claim to the client, copied to the QS.

Day 2

QS confirms the cost submission, priced from the live cost position, line by line.

Next

V-118 closed as a claim and saved to the knowledge base — what was decided, and why. Learned: structural revision mid-build; entitlement clear, window open, claimed cost plus 7 days.

Illustrative follow-through · scenario data

V-118 New
Claim

Structural revision mid-build; entitlement clear, window open, claimed cost plus 7 days.

V-117
Absorb

Minor finishes change under the variation threshold, carried, no programme impact.

V-116
Replan

Client-driven layout change; float available, resequenced without a claim.

Every decision you close teaches the system. The next variation starts from what your firm already knows, not from scratch.

09 · As-is vs assisted

Same decision, V-118. Two very different projects.

As-is manual · todayAssisted with Decisome
Time to decide~9 days, made under pressureBy the next morning
Basis for the callThree rival spreadsheets, no agreed numberOne agreed set of numbers
Options exploredOne path worked out by hand, no time to weigh the restAll four, costed on the same basis
Cost outcomeUsually the safe, expensive optionThe cheapest path that still works, chosen with the trade-off visible
Value recoveredClaim window often missed before anyone checksWindow tracked from day one, so where entitlement holds, notice goes in on time
EvidenceScrambled together at the end, if at allPack pre-assembled, indexed and ready
After you decidePaperwork assembled by hand, laterWhole process staged, ready to issue
Company knowledgeLives in heads, leaves with the peopleCaptured in your knowledge base
Who decidesYou, late, on partial factsYou, on time, fully informed

V-118 is an illustrative example built from how variations are commonly handled on fit-out projects, not a client result. The nine days, the three workstreams and the figures on this page describe the shape of the problem.

Is this your decision — or close to it?

Bring Us This Decision → Download the case study ↓