The site meeting nobody wrote down
A Planning Engineer at a mid-size EPC contractor in Rajasthan once told us about a ₹1.8 crore variation claim that went nowhere. The work was real. The drawings existed. The employer's site team had clearly asked for it. But when the contractor submitted the claim, the employer's project director denied it ever being instructed. There was no written instruction. No RFI. No site order. Just a conversation at the weekly review meeting.
The contractor had nothing.
This is not unusual. Across Indian highway and building contractors, verbal instructions are the default mode of operation on site. The engineer is busy, the contractor wants to stay on the right side of the relationship, and nobody wants to slow things down with paperwork. So work gets done on a handshake, and the variation claim comes later, if at all.
What the GCC actually says
Under the NHAI General Conditions of Contract (GCC), a variation is only valid when issued in writing under Clause 44. The clause is explicit: verbal instructions have no contractual standing. Unless the contractor follows up a verbal instruction with a written confirmation, and the engineer either approves it or fails to object within 7 days, the instruction does not exist for payment purposes.
CPWD contracts carry a similar requirement under Clause 12 of the General Conditions. MoRTH model contracts follow the same principle.
The problem is not that contractors do not know this. Most contracts managers do. The problem is that the site team does not have the time, the tools, or the habit to follow up every verbal instruction before the next concrete pour.
The cost compounds
In our conversations with contractors managing 5 to 15 active NHAI packages, unrecovered variation from verbal instructions typically runs between 2% and 4% of contract value on any given project. On a ₹500 crore package, that is ₹10 crore to ₹20 crore in work the contractor did and did not get paid for.
The loss does not show up as a line item. It shows up at final account. The contractor submits a claim for ₹42 crore in extras and the employer settles at ₹28 crore, and nobody can fully reconstruct why.
Why the follow-up letter never gets written
The barrier is friction. A contracts manager handling three packages does not have 90 minutes to draft a formal written confirmation of every site-level instruction. The letter needs to reference the right GCC clause, use the right tone, go to the right person, and arrive within the right notice window.
Most do not get written. Some get written three weeks later, by which point the argument is already about whether the instruction was ever given.
What a contractor can do
The practical fix is not a new process. It is faster execution of the existing process.
When a verbal instruction is received on site (scope addition, design change, employer-directed acceleration), a written confirmation should go to the engineer within 24 hours. Not a long letter. A short, formal one: what was instructed, when, by whom, and what the contractor proposes to do. The engineer's failure to object within the notice period then creates a deemed approval under most GCC forms.
AI-assisted letter drafting can reduce the time to draft that confirmation from two hours to two minutes. The legal substance stays the same. The clause reference, the notice period, the formal tone, all preserved. The barrier to sending it drops enough that more letters actually get sent.
The real asset: a complete record
The second benefit of written instructions is not just payment. It is evidence.
When a dispute goes to arbitration (and NHAI arbitration is a real possibility on large packages), the contractor who can produce a chronological paper trail of every instruction, every objection, and every response is in a fundamentally different position from the contractor relying on witness statements from site staff.
Written confirmation letters are evidence. Verbal agreements are memories. Memories are not admissible.