EOT Claims Under NHAI GCC: What the Clause Actually Requires

The claim that died before it was filed

A contracts manager at a highway contractor in Uttar Pradesh once brought us a delay claim that had been rejected at the DRB stage. The contractor had a genuine case: the employer's design team had issued revised drawings 11 weeks into a 14-week activity, forcing a restart. The site diary recorded it. The RFI trail was intact. The critical path impact was provable.

The DRB rejected the claim on procedure. The contractor had not issued a notice within 14 days of becoming aware of the delay event.

The notice existed, but it had been sent 31 days after the drawing revision was received on site. The contracts manager had been waiting to understand the full impact before writing. By the time the letter went out, the notice window was closed and the employer's representative had no obligation to respond.

This happens regularly on NHAI projects. Not because contractors do not have valid delay claims. Because the GCC procedure is strict, the windows are short, and the consequences of missing them are final.

What GCC Clause 40 actually requires

Under the NHAI GCC, Extension of Time is governed by Clause 40. The mechanism works in three stages:

Stage 1: Notice within 14 days. The contractor must notify the Engineer in writing within 14 days of the date on which it became aware, or should reasonably have become aware, of the delay event. The notice must describe the event and state that the contractor intends to claim EOT.

Stage 2: Contemporary records. From the moment the notice is issued, the contractor must maintain contemporary records of the delay impact. This means day-by-day site diaries, resource deployment records, and any instructions received relating to the event. The Engineer has the right to inspect these records at any time.

Stage 3: Fully detailed claim within 28 days. The contractor must submit a fully detailed EOT claim within 28 days of the delay event ceasing, or such longer period as the Engineer may approve. The claim must include the full analysis of delay, the critical path impact, and the quantum of extension requested.

Miss Stage 1 and Stages 2 and 3 become largely irrelevant.

The 14-day clock starts earlier than most contractors think

The clause says "within 14 days of the date on which the Contractor became aware, or should reasonably have become aware."

The second half is the dangerous part. If a drawing revision arrives on site on a Monday and the site engineer logs it in the daily diary, the 14-day clock starts on Monday. Waiting until the PM reviews the diary on Friday costs four days. Waiting until the contracts manager in the head office sees the weekly report costs more.

On large NHAI packages with distributed site teams, the information chain from site to head office often adds 7 to 10 days. By the time someone in the contracts team recognises that a delay event has occurred and warrants a notice, the 14-day window is already half-spent or gone.

The fix is not faster review cycles at head office. It is recognising on site, in real time, which events are potentially delay-causing and sending a protective notice immediately. A protective notice that says "we are aware of this event, we are assessing its impact, and we reserve our right to claim EOT" is far better than a detailed claim submitted on day 15.

What qualifies as a delay event

Under NHAI GCC Clause 40, the events that entitle a contractor to EOT include:

• - Employer risk events (late drawings, late access, late decisions on RFIs)
• Force majeure (defined events: floods, earthquakes, war, strikes beyond the contractor's control)
• Employer-directed variations that extend the critical path
• Prolonged suspension ordered by the Engineer or Employer
• Exceptionally adverse climatic conditions (requires advance definition in the Particular Conditions)

Contractor-caused delays do not qualify. Concurrent delay (where both contractor and employer risk events are occurring simultaneously) is one of the most contested areas in NHAI claims. Indian courts and arbitrators have generally applied the dominant cause test: if the employer's event is the dominant cause of the delay period, EOT may be granted for that period even if contractor delays were also present.

The 28-day detailed claim

Once the notice is sent and contemporary records are being maintained, the contractor has 28 days from when the delay event ceases to submit the full claim.

The full claim needs:

1. A description of the delay event and the contractor's basis for it being an employer risk event
2. The critical path position before the event (the as-planned baseline)
3. The critical path position during and after the event (the as-built or impacted programme)
4. The quantum of EOT requested, expressed as calendar days
5. Any additional cost incurred as a result of the prolongation (if a prolongation cost claim is being made in parallel)

The quality of the programme analysis determines whether the claim succeeds. A contractor who maintains an updated Gantt with actual progress, baseline, and a record of what caused deviations is in a fundamentally different position from a contractor who submits a retrospective analysis six months after the event.

Concurrent delay and the employer's counter-argument

The most common employer response to an EOT claim is to cite concurrent contractor delays. If the contractor's own resources were underdeployed on the critical path activity at the same time as the employer's drawing was late, the employer will argue that the contractor's delay was the dominant cause.

This argument is harder to rebut without records. A site diary that shows the employer drawing was the only reason for the work stop is a strong record. A diary that shows "no work done" without recording why gives the employer room to argue that the contractor's resource constraints were the real cause.

The practical implication: the same daily log that records manpower and equipment also needs to record why activities are not progressing when they should be. "Drawing not received from IE" as a daily log entry is worth more than any subsequent claim narrative.

What happens when the EOT is not granted in full

If the Engineer issues a Clause 40 determination granting less EOT than claimed, or issues no determination within the applicable period, the contractor has two options:

1. Accept the determination and move on (with a reservation of rights to raise it at final account)
2. Issue a notice of dissatisfaction under GCC Clause 20 within 14 days of the Engineer's determination

The notice of dissatisfaction is what keeps the dispute alive. Without it, the Engineer's determination becomes final.

This is a second notice window, after the main claim, that contractors routinely miss. Not because they are satisfied with the outcome, but because the contracts team has moved on to the next problem by the time the Engineer's response arrives.

The practical answer

The consistent pattern across NHAI claims we have looked at: contractors with valid delay cases lose not on the merits but on the procedure. The 14-day notice is missed. The contemporary records are thin. The 28-day detailed claim is late. The notice of dissatisfaction is not sent.

Each of these failures is a paperwork failure, not a substantive one. The correspondence drafting tools that help with EOT letters are valuable precisely because they remove the friction from the procedural steps. A notice that takes 20 minutes to draft instead of 3 hours is a notice that actually gets sent on day 5 instead of day 15.

The substantive analysis (what the critical path impact was, what the quantum of extension is) still requires a qualified planning engineer. But the procedural steps that protect the right to make that claim are mostly a drafting problem. And drafting problems are solvable.