The missing three days
The arbitrator asked for the site diary entry from March 14, 2024. That was the date the employer's representative had allegedly instructed the contractor to stop work on the box culvert approach slab. The contractor's contracts manager searched through the physical diary. There was an entry for March 11. Then March 16. Nothing in between.
Three days of site activity had occurred on that project. Equipment was deployed. Labour was paid. But in the only contemporaneous record the contractor held, those days did not exist.
The contractor's 2.3 crore delay claim became significantly harder to defend that afternoon. The employer's position was that no stop-work instruction had ever been given. The contractor's site manager remembered it clearly. Without a written record from the day itself, memory was all they had.
This is not a story about a careless site team. It is a story about what paper diaries are designed to do and what they are not designed to do.
What a paper site diary actually looks like
Walk into most Indian highway or building project offices and you will find one: a hardbound register, filled in at the end of the day when the site engineer gets around to it, with entries like "Labour: 38 nos. Work progressed at chainage 14+200 to 14+600. Weather: partly cloudy. Plant: 1 roller, 2 JCB."
The site engineer is not being lazy. He is managing three subcontractors, two inspections, a material delivery, and a call from the planning office. The diary gets five minutes at the end of a 10-hour day. Sometimes it gets written the next morning. Sometimes it covers three days with one entry when the site manager comes in on Monday.
This is the norm on Indian construction sites. Not because the industry is behind, but because nobody designed the paper diary for any purpose other than keeping a basic log.
The four ways paper diaries fail as evidence
Gaps and reconstruction. A physical diary filled in retrospectively is not a contemporaneous record. Arbitrators and courts know this. An entry written on March 16 covering March 14 and March 15 is not the same as an entry written on March 14. The timestamps are gone. The sequence is lost. And when the defence lawyer asks "when exactly did you make this entry," the honest answer is usually "I am not certain."
Missing data for claim purposes. A standard paper entry records presence, not events. It tells you that 40 labourers were on site and work progressed on a section. It does not tell you that the employer's IE came at 11am and verbally directed the contractor to stop using the existing limestone aggregate and switch to crusher run. It does not tell you that the switch added 3 crore to material costs. It does not link any of this to the GCC clause under which the contractor will later claim.
An EOT claim under NHAI GCC Clause 40 requires the contractor to demonstrate that a qualifying event occurred, that it caused delay, and that the delay was notified within 28 days. The paper diary entry "work proceeded" does not establish any of these facts for the day when the qualifying event occurred.
No link to contract obligations. Construction contracts run on notice periods. The 28-day notification window for delay events under NHAI GCC Clause 39.2. The 14-day window for variation instructions under Clause 36. These are clock-based obligations. The clock starts on a specific date. If you cannot precisely identify that date in your records, you may not be able to prove the notice was timely.
Paper diaries are sequential logs. They are not indexed to contract events or notice obligations. Finding the first entry that documents a specific qualifying event requires manually searching weeks of entries and then arguing about whether the date on the entry reflects when the event was first recorded or when it was first noticed.
Single point of failure. A physical diary exists in one place. On a site that has seen 4 years of construction and 2 years of O&M, the diary from Year 1 is in a filing cabinet somewhere. Or was. The stories of diaries lost in flooding, fire, and project office relocations are not exceptional. They are common. When the arbitration starts 6 years after the event, the contractor whose records are in a system accessible from any device is in a different position from the contractor looking for a specific register from a specific site office.
What structured daily logs capture
The difference between a paper diary and a structured digital site log is not that one is digital and one is paper. It is that a structured log is designed to capture evidence, not just presence.
A properly structured daily log entry records: timestamps for when the entry was made and when work started and stopped; labour by subcontractor and by cost code; plant by type, hours deployed, and cost code; work quantities by chainage and activity code; weather from an API rather than the site engineer's recall; any instructions received during the day with the instruction type and the name of the person who gave it; any hindrances and what they prevented; IE or authority visits and what was discussed; photos attached to specific activities and geotagged to the location.
The timestamp is the critical element. A system that records when an entry was made cannot be manipulated after the fact the way a physical diary can. When the arbitrator asks "when did you first record that the IE gave a stop-work instruction," the system's log shows the answer. The contractor does not have to rely on memory or estimation.
When a delay event occurs, the daily log entry from that day becomes the starting point for the claim. The entry references the event. The date is fixed. The 28-day notice clock starts from a specific, documented, timestamped moment.
How daily log data becomes claim documentation
The daily log is not just evidence. It is source data.
An EOT claim needs to show the event, the delay it caused, the resources affected, and the costs incurred. All of that information exists in the daily log. Labour deployed on delayed activities: in the log. Plant standing idle waiting for employer instruction: in the log. Work quantities that could not proceed: in the log.
A structured log that connects to a project management system means the claim documentation is largely built as the project runs. The contracts manager filing the EOT claim at Month 9 is not reconstructing what happened at Month 5 from memory and paper records. The data is already there.
The same data populates the monthly progress report, the EVM calculation, and the variation support documentation. The site engineer fills in the log once. It appears everywhere it needs to appear.
Why site engineers resist, and what changes that
The objection is time. A structured digital log takes longer per entry than writing three lines in a notebook.
This is true. The first week is slower. The first two weeks are slower. By Month 2, an experienced site engineer fills in a structured daily log in 15 to 20 minutes at the end of the day. A paper diary takes 5 minutes. The difference is real.
What also changes is what happens with that data. The contracts office does not spend two days at month-end reconstructing site activity from paper diaries. The PM does not ask the site engineer to explain what happened on a specific date six weeks ago. The project director does not have to wait for a manually compiled EVM report.
The adoption threshold, in our experience, is usually the first time a digital log entry directly supports a claim or dispute response. After that, the site team fills it in without being asked.
The site engineer on the box culvert package in our opening scenario eventually did start using a digital log on his next project. When a similar stop-work situation arose 18 months later, the entry was there, timestamped, with a note of who gave the instruction and at what time. The claim went through.