An EOT application on an NHAI EPC package is a formal submission to the Authority Engineer, not a letter of complaint. It should read as an administrative document: what the contract provides, what happened, what the effect was, and what extension is sought. The tone that works is procedural and evidenced. Argument belongs in the annexures' facts, not in the prose.
The skeleton
| Part | Content |
|---|---|
| Covering letter | Reference number per your numbering convention, project and package identification, the contract provision under which the application is made, and the extension sought in days with the revised scheduled completion date |
| 1. Background | Contract date, scheduled completion date, appointed date, current status of the works in one paragraph |
| 2. Contractual basis | The EOT provision of your EPC agreement as executed, the notice provision and the dates on which notices were given, and any provision on hindrances and the register |
| 3. Statement of hindrances | Each hindrance as a numbered item: description, chainage, occurrence and removal dates, responsible agency, the notice letter reference, AE countersignature status |
| 4. Effect on the programme | For each hindrance, the activities affected, whether they were on the critical path, and the delay to the scheduled completion date; reference the approved programme and its updates |
| 5. Period claimed | The total extension sought, how concurrent or overlapping hindrances have been treated, and the revised completion date |
| 6. Reservation of cost | A statement that the application concerns time, and that the Contractor reserves its rights to compensation for the extended period under the relevant provisions |
| 7. Annexures | Hindrance register extract, notice letters, AE correspondence, programme and updates, photographs, site records, each numbered and referenced in the text |
Section 3: the register does the work
The statement of hindrances should be a restatement of the hindrance register, entry by entry, in the same order and with the same numbers. If the register was kept properly, this section writes itself and carries the weight of a contemporaneous record. If it was not, this is where the application becomes a reconstruction, and the AE will see it.
Section 4: programme, not assertion
Each hindrance needs to be connected to the programme: which activities it held, and why those activities drove completion. Reference the approved baseline and the monthly updates that were submitted at the time. A planning engineer's time impact or windows analysis belongs here, named as such. A bare statement that the works were delayed by the number of days the hindrance lasted is the most common weakness in Indian EOT applications.
Overlaps and concurrency
Where two hindrances ran in the same period, say so and explain how the period claimed avoids double counting. An application that sums every hindrance's duration without addressing overlap will be reduced on that basis before the merits are considered.
Tone and format
- Formal, numbered paragraphs, no rhetorical language.
- Dates in one consistent format throughout.
- Amounts, if any appear, in the Indian lakh and crore notation the AE uses.
- Every clause citation from the executed agreement, not from a model form, since Schedules and amendments vary by package.
What this means in practice
- Number the hindrances in the application exactly as in the register.
- Connect each hindrance to programme activities; do not assert delay days equal to hindrance days.
- Address overlap explicitly.
- Reserve cost separately and keep it out of the time argument.
For NHAI and CPWD families the DraftMyEOT claim wizard produces an EOT application letter with a hindrance annexure in authority style, built from the register entries and their linked evidence.
Start a 48-hour draft →Sources
This article is general information about how these contract mechanisms typically work. It is not legal advice, and it is not a substitute for review of your specific contract by a qualified professional.