Contractors working highway packages and building works in the same company deal with two distinct contract families. NHAI packages run on the Ministry's model EPC and Hybrid Annuity agreements, administered by an Authority Engineer. CPWD and most state PWD works run on the CPWD General Conditions of Contract, administered by an Engineer-in-Charge. The register culture is shared; the machinery is not.
Side by side
| Aspect | NHAI EPC and HAM | CPWD and state PWD GCC |
|---|---|---|
| Governing document | Model EPC or HAM Agreement with package-specific Schedules | CPWD General Conditions of Contract, with the version in force at tender |
| Administering engineer | Authority Engineer (an appointed consultant) | Engineer-in-Charge (a departmental officer) |
| Typical trigger for notice | Occurrence of the event, in many packages | Occurrence of the hindrance |
| Time-bar character | Varies by package; often drafted as a condition precedent, sometimes softer | Application within a stated period is required; treatment of late applications varies in practice |
| Contemporaneous record | Hindrance register, countersigned by the AE where possible | Hindrance register maintained at site, countersigned by the Engineer-in-Charge |
| Application format | Formal application to the AE with statement of hindrances and programme effect | Application to the Engineer-in-Charge on the departmental pattern, referencing the register |
| Dispute route | Conciliation and arbitration historically; January 2026 circular moves larger NHAI disputes away from arbitration | Departmental dispute redressal and arbitration under the GCC |
| Payment structure interaction | HAM annuity and EPC milestone regimes affect what cost relief looks like | Item-rate or lump-sum, with extension applications often tied to variations |
The shared foundation
Both families expect the hindrance register. Both expect the contractor to have written promptly. Both will, at a hearing, weigh a countersigned contemporaneous entry far above a later chronology. A planning engineer who keeps one disciplined register format across both families loses nothing and gains a habit that transfers.
Where teams make mistakes
- Copying an NHAI application format onto a CPWD job. The Engineer-in-Charge expects the departmental pattern and the GCC vocabulary. A FIDIC-style narrative reads as foreign.
- Assuming the same notice window. Windows and triggers differ by package and by GCC version. Read the executed document.
- One numbering series for two authorities. Keep letter numbering per project so an audit can follow one package's correspondence cleanly.
- Treating a soft time-bar as harmless. Even where lateness is not fatal, it is held against the contractor when the engineer weighs the claim.
What this means in practice
- Label each project with its family and administer it with that family's vocabulary and format.
- Extract the notice trigger and window from the executed document; do not assume.
- Keep the hindrance register discipline identical across both.
- Maintain per-project letter numbering.
DraftMyEOT carries separate profiles for NHAI EPC, NHAI HAM, and CPWD or state PWD GCC, verifies each against the uploaded document, and drafts letters and applications in the family's own register.
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.