Product · Hindrance & EOT

Hindrance register and EOT claim software

Log every hindrance the day it happens, and BuildCore starts the right contractual clocks for your form of contract — CPWD, NHAI, Indian Railways, FIDIC or NEC4. It sweeps every deadline daily on both sides, drafts the letters, and assembles the evidence an extension of time will need.

BuildCore's Hindrance and EOT dashboard: 14 open hindrances, 1 notice overdue, 4 claims due within 14 days, 5 awaiting the client; 186 EOT days claimed and 92 granted; liquidated-damages exposure of 3.84 crore rupees; breakdowns by responsible party, by project and by age; a 60-day deadline calendar and the actions awaiting the user.
The Hindrance & EOT dashboard in BuildCore — contract clocks, the EOT position, deadlines on both sides and the actions waiting on you. Sample data.
Why it matters

A late hindrance notice becomes liquidated damages

Site teams record hindrances in diaries and spreadsheets. The contract counts days from the event. When the EOT application finally goes in, the notice clock has often already run — and the damages clock has not.

Start the right clock, automatically

Pick the project's form of contract once. Every hindrance logged afterwards gets its notice, claim, response and determination deadlines calculated — on calendar or business days, as the contract requires.

Watch both sides

A daily sweep checks every open clock — yours, and the Engineer's or Employer's obligation to reply or decide. Silence on their side is a fact worth recording too.

Arrive with evidence

Link each hindrance to the affected schedule activity, with its float at the time of the event, and to the daily reports that show idle resources.

Deadline calendar for the next 60 days listing notice, detailed-claim, interim-claim and NOD deadlines, each marked as the contractor's or the client's, next to the list of actions awaiting the user, one of them overdue.
Deadlines on both sides — yours and the Engineer's or Employer's — with the actions awaiting you. Sample data.
Contract regimes

Preset clocks for the forms Indian and international projects use

Each preset fills in the defaults below. Every clock can then be edited to match your contract's particular conditions.

Form of contractNoticeWhat else the preset tracks
CPWD GCC 2023Immediate written notice (Cl. 5.2 / 5.3)EOT application on Appendix XVI within 14 days (Cl. 5.4); decision within 21 days (Cl. 5.4.1); Engineer-in-Charge reply to the hindrance notice within 10 days; compensation up to 1% a month, capped at 10% (Cl. 2)
NHAI / MoRTH EPC 202215 business days, with particulars (Art. 10.5(ii))Authority's Engineer clarifications within 15 days, reply within 10, determination within 30 (Art. 10.5(iv)); interim claims by the 10th of the month; final within 30 days (Art. 10.5(v)); force majeure notice within 10 days (Art. 21.5)
NHAI HAM15 business daysThe same article structure as the EPC agreement; damages of 0.1% of the Performance Security per day after a 30-day grace period
Indian Railways GCC 2022Within 15 days (Cl. 17A(ii))EOT application not less than one month before the completion date; liquidated damages on a sliding scale capped at 5% (Cl. 17B)
FIDIC 201728 days from awareness (Sub-Cl. 20.2.1)Engineer may object within 14 days, otherwise deemed valid (20.2.2); fully detailed claim within 84 days (20.2.4); agreement 42 days, then determination 42 days (3.7); notice of dissatisfaction within 28 days (3.7.5)
FIDIC 199928 days from awareness (Sub-Cl. 20.1)Fully detailed claim within 42 days; interim claims monthly; final claim within 28 days after the effect ends; Engineer responds within 42 days
NEC4 ECC8 weeks (Cl. 61.3)Project Manager's reply in 1 week; quotation within 3 weeks (Cl. 62.3); Project Manager's reply in 2 weeks; deemed acceptance after a further 2 weeks' notice
CustomAnyFor private clients and other conditions of contract — set every clock yourself
Clause references and periods are the preset defaults BuildCore ships with. Always check them against your own contract and its particular conditions. BuildCore tracks deadlines and keeps the record — it does not give legal advice or decide entitlement.
What is in the module

Register, letters, client response, evidence

Hindrance register and dashboard

  • One record per hindrance, with its log and full history
  • A dashboard of clock tiles, the project's EOT position, deadlines on both sides, and the actions waiting on you
  • A daily sweep of every open deadline
  • Export of the register

Contractual letters

  • Letter templates with merge fields from the hindrance record
  • Draft, review, approve, issue, dispatch and acknowledgement — each step with its own permission
  • Only people with access to the project can see its letters

The client's side, without accounts

  • Send the Engineer or Employer a secure link — no account needed
  • Each link allows only what you choose: acknowledge the hindrance, record a determination with the days granted, or counter-sign the register entry
  • Every response is confirmed with a one-time code sent to the recipient's email; a link revokes itself after repeated failed codes
  • Client or consultant users with a login can counter-sign or dispute an entry inside BuildCore

Evidence for the EOT claim

  • Link the hindrance to the affected schedule activity, capturing its float at the event
  • A summary of idle resources from the daily progress reports over the affected dates
  • Rebaseline requests recorded against the hindrance
  • An indexed evidence-pack PDF: the record, its clocks, letters, links, attachment hashes and timeline, with the attached documents appended
Where it is used

Built for Indian contracting — and beyond

India

Highway contractors on NHAI EPC and HAM agreements, building contractors on CPWD work, and railway contractors on Indian Railways GCC — with GST, TDS and customs in the same platform.

FIDIC projects

ADB-, World Bank- and JICA-funded packages across South Asia, South-East Asia and Africa, where FIDIC's harmonised conditions apply.

NEC4 and South Africa

NEC4 ECC compensation events preset; JBCC and GCC contracts configured with the custom regime.

Questions

Hindrance registers and EOT claims — common questions

A hindrance register records every event that delays or disrupts the work — late drawings, site not handed over, utility shifting, stoppages ordered by the client. On Indian government contracts it is the basis for any extension of time, so each entry needs a date, a cause, the work affected and, ideally, the client's acknowledgement.

The CPWD GCC 2023 preset tracks the EOT application on Appendix XVI within 14 days of the hindrance (Cl. 5.4) and the decision within 21 days. Letters are drafted from templates you set up with merge fields from the hindrance record.

Yes. You send a secure link that allows only the actions you choose — acknowledge, record a determination, or counter-sign. Each response is confirmed with a one-time code sent to the recipient's email address.

Yes. A preset only fills in the defaults. Every clock can be edited per project to match the particular conditions of your contract, and a fully custom regime is available for private clients.

See it on your contract

Bring one hindrance from a live project

We will set the project's contract regime, log the hindrance, and show you its clocks, the letter and the evidence pack.