How Digital Site Diaries Reduce Construction Disputes: A Complete Guide

Most construction disputes are not decided by the better argument. They are decided by whoever can show what actually happened on a particular Tuesday, eighteen months earlier, on a part of the site that no longer exists.

That is what a site diary is for. Not a compliance chore, not a box to tick before going home. It is the only record most projects keep of what the day genuinely looked like: who was there, what was happening, what stopped, and why.

This guide covers what a site diary has to capture to be worth anything in a claim, why the daily habit matters more than the format, how the notice clocks in JCT and NEC4 punish a poor record, and where paper diaries reliably fail.

Key Takeaways: Site Diaries and Construction Claims

• A diary written up on Friday for the whole week is not a contemporaneous record. It is a recollection, and it carries the weight of one.
• The Society of Construction Law Delay and Disruption Protocol puts records first: parties should agree what records to keep and resource that agreement properly.
• Under NEC4, a compensation event not notified within eight weeks of the contractor becoming aware of it leaves the prices and programme unchanged. The diary is often what proves when awareness began.
• An exceptionally adverse weather claim depends on weather data compared against historical records, supported by photographs and site diary entries.
• The most valuable single field is the delay entry: cause, area affected, duration, and a photograph taken at the time.
• Completion rate beats detail. A brief diary filed every day beats a thorough one filed four days a week.

What a site diary is actually for

A site diary is a daily record of the conditions in which work was carried out. Typically that means labour on site by trade and number, plant and equipment, weather, deliveries received, visitors, instructions given, and anything that stopped or slowed the work.

On a quiet project none of it gets read. On a project that goes wrong, the daily site diary becomes the most consulted document in the file, because it is the only one that was written before anybody had a reason to argue.

That is the whole value. Every other document produced during a dispute has been written with the dispute in mind. A diary entry made at four o’clock on the day, recording that the riser was inaccessible because a subcontractor was still working in it, was written by somebody who had no idea it would matter. Evaluators know the difference, and so do adjudicators.

If you want the equivalent argument for quality records rather than progress records, our guide on evidencing RAMS sign-off for an HSE inspection makes the same point about safety documentation: the record has to exist before anyone needs it.

Why disputes turn on daily records

The Society of Construction Law’s Delay and Disruption Protocol, second edition, opens its core principles with records rather than with programming technique. Core Principle 1 states that contracting parties “should reach a clear agreement on the type of records to be kept and allocate the necessary resources to meet that agreement”.

It is deliberate that this comes first. The Protocol’s guidance notes that those assessing claims often find uncertainty and a lack of records about what was actually delayed or disrupted, and that good record keeping removes a significant amount of that uncertainty. That is the same logic that runs through construction compliance records generally: the document is only worth what it can prove about a specific day. Where the records are poor, the uncertainty does not disappear. It gets resolved by argument, which is slow, expensive, and unpredictable.

The Protocol is also explicit that records must be generated as the work progresses rather than reconstructed afterwards. A reconstructed record is evidence of what somebody remembers. A contemporaneous one is evidence of what happened.

The four claims a site diary usually decides

Extension of time

Delay claims live or die on the link between an event and its effect on progress. A diary that records the event on the day it occurred, names the area affected, and shows what work was standing as a result, supplies that link directly. A programme alone does not: it shows the plan and the outturn, not the reason for the gap between them. Weekly progress reports summarise the outturn. The diary explains it.

Exceptionally adverse weather

Under the JCT forms, exceptionally adverse weather is a Relevant Event, which means it can support an extension of time. There is no fixed definition of “exceptional”, so the test is comparative: current conditions against weather records from previous years, ideally from the weather station nearest the site.

Proving it needs three things together. Weather data for the actual days. Photographic evidence of the disruption. And site diary records showing which works were affected and what mitigation was attempted. Miss any of the three and the claim becomes an assertion. Worth knowing too that under JCT this Relevant Event supports time but not loss and expense, so the commercial risk stays with the contractor, which makes the time award worth defending properly.

Disruption and loss of productivity

Disruption claims are the hardest to prove because the effect is spread thin. Nothing stops entirely, everything just takes longer. The only way to evidence it is a daily record of labour allocated against work achieved over a long enough run to show the pattern. A diary that logs gang sizes by trade every day is doing analytical work nobody notices at the time, and it is far stronger when the numbers reconcile against workforce records rather than standing alone.

Verbal instructions and undocumented variations

Instructions given on site and never confirmed in writing are a standing source of argument. A diary entry naming who gave the instruction, when, and what was said is not a substitute for a formal confirmation, but it is often the only contemporaneous evidence that the conversation happened. Recording it in the diary and raising it properly the same day through a variations tracker, or an RFI where the instruction is really a question, is the combination that holds.

The notice clock, and why the diary controls it

This is the part that costs contractors the most money, and it has nothing to do with the merits of the claim.

Under NEC4, clause 61.3 gives the contractor eight weeks from becoming aware that an event has happened to notify a compensation event. Miss that window and there is no change to the prices or the programme. The entitlement can be perfectly good and still be worth nothing.

Note what starts the clock. It runs from awareness that the event happened, not from the moment somebody concluded it was compensable. In a dispute about whether a notice was late, the question becomes when the contractor first knew. A diary entry describing the event on the day it occurred is evidence of exactly that, and it cuts both ways: it can prove the notice was in time, or prove it was not. Either way, the team that keeps a good diary is the team that knows where it stands.

Under the JCT forms, the duty is framed differently but rests on the same information. Taking Design and Build 2016 as the example, clause 2.24.1 requires notice “if and whenever it becomes reasonably apparent” that the works are or are likely to be delayed, stating the cause or causes and identifying any event that is in the contractor’s opinion a Relevant Event. Clause 2.24.2 requires particulars of the expected effects and an estimate of the effect on the Completion Date. Clause 2.24.3 requires the employer to be told forthwith of any material change in the estimated delay, plus any further particulars reasonably required.

“Reasonably apparent” is doing a lot of work in that sentence. What was reasonably apparent, and when, is answered by what the site team was recording at the time. A diary that goes quiet for three weeks around the event is not neutral. It suggests nothing was apparent, which is exactly the opposite of what the claim will need to argue.

What a diary has to capture to be useful

Eight fields cover almost every claim.

Labour by trade and number. Not “busy”. Six carpenters, four electricians, two labourers. Gang sizes over time are what disruption analysis is built from.

Plant and equipment on site. Including what was standing idle, which is often the point.

Weather. Conditions, not adjectives. This is the field most often left blank and most often needed later.

Deliveries received, and deliveries that did not arrive. The second one matters more and is almost never recorded.

Areas worked and areas not accessible. Access is the most common practical cause of delay on a busy site, and the easiest to evidence if somebody writes it down.

Delays and stoppages, with cause, area, duration and a photograph. The single highest value entry in the whole diary.

Instructions given and visitors on site. Who attended, who said what.

Photographs attached to the entry, not to a folder. A progress photo that is not tied to a date, a location and an entry is decoration. Attached to a specific delay entry, it is evidence.

Where paper diaries fail

The failures are consistent and none of them are about the quality of the person writing the diary.

The Friday write-up. A week reconstructed on Friday afternoon is a recollection. Detail thins, exact dates blur, and the entries begin to sound the same. This alone removes most of the evidential value.

Missing days that nobody notices. A paper book in a cabin has gaps that stay invisible until somebody reviews it a year later, at which point the gap is a hole in the claim.

Weather left blank or written as “wet”. Useless against the comparative test an adverse weather claim requires.

Photographs kept separately. On a phone, in a WhatsApp thread, or in a folder by date. Nothing connects them to the entry they support.

One copy, on site. The office cannot see it, cannot spot the gaps, and cannot act on what it contains while there is still time to mitigate.

Nothing searchable. Finding every entry that mentions a particular riser across eleven months of handwriting is a job nobody will do until it is unavoidable.

Lost or damaged books. Cabins flood, books go home with people who leave. Our overview of progress tracking and site records covers where the diary sits alongside the rest of the record.

Contemporaneous is a habit, not a format

The most common mistake when people try to improve their diaries is to make them longer. More fields, more detail, a better template. It rarely works, because the constraint is not the form. It is the five minutes at the end of a long day.

Push the effort up and the completion rate falls, and a diary completed four days in five is worth far less than a brief one completed five days in five. Gaps are what get attacked. A thin entry saying nothing notable happened is still a record that nothing notable happened. No entry at all is an invitation to argue.

So the target is a diary that takes a few minutes, is completed on site rather than later, and is visible to somebody in the office who will notice when a day is missing. Everything else is secondary.

Digital changes the economics, not the principle

Nothing about the principle changes when the diary moves to a phone. The entry still has to be made on the day by somebody who was there. What changes is how expensive that is, and how visible the gaps become.

Time drops, because the fields are structured and the repetitive ones carry over. Weather can be captured automatically for the site location rather than typed. Photographs attach to the entry that they evidence. The record becomes searchable, so finding every mention of an area takes seconds rather than an afternoon. And missing days stop being invisible, because the office sees the gap the same week rather than the following year.

That last point is the underrated one. The value of spotting a missing diary is not tidiness. It is that a delay recorded on the day can still be mitigated, notified in time, and priced. A delay discovered during a claim can only be argued about.

Subcontractors keep diaries too, and should

If you are the subcontractor rather than the main contractor, the diary is more important to you, not less. You are usually the party whose progress depended on somebody else’s, which means your entitlement almost always rests on proving that access was not available, that preceding works were incomplete, or that an instruction changed the scope.

None of that is recorded in the main contractor’s diary in the terms you will need. Keeping your own, daily, with your own labour figures and your own access notes, is the only way a subcontractor can evidence a claim that is fundamentally about someone else’s performance. It is also why signing-in data matters: site attendance records corroborate the labour figures in the diary, and a claim where those two agree is much harder to challenge.

Why Insite Is the Best Choice for Digital Site Diaries

The point of every section above is that the record has to be made on the day, by the person who was there, without costing them twenty minutes. That is what Insite’s digital site diaries are built to do.

Completed on site, in minutes. Insite customers average four minutes to complete a daily diary, and 98% of diaries are submitted on the day rather than written up later. That completion rate is the whole ball game, because the Friday write-up is what destroys evidential value.

Weather captured automatically. Conditions are recorded for the site location without anyone typing them, which removes both the blank field and the argument about whose recollection of the weather is right.

Delays recorded properly. Each delay entry captures the cause, the area affected, the duration and attached photographs taken when the incident occurred. Insite customers photograph 100% of delay events.

Evidence attached to the entry. Labour counts, plant, deliveries and photographs sit on the entry they belong to, time-stamped and attributed, rather than in a separate folder somebody has to reconcile later.

Works offline. Diaries can be completed in site cabins and areas with no signal, and synchronise automatically when a connection returns, so the record is never postponed for technical reasons.

Missing days are visible immediately. Diaries land centrally as they are submitted, so the office sees a gap the same week, while there is still time to do something about it.

Exports as a dated report for claims. The record is searchable, and a dated diary report exports for a claim or a query rather than being assembled from a book and a camera roll. Our sample reports show what that output looks like on the page.

Frequently asked questions

What is a construction site diary?

A construction site diary is a daily record of the conditions in which work was carried out on a project. It typically records labour on site by trade, plant and equipment, weather, deliveries, visitors, instructions given, areas worked, and anything that delayed or stopped the work. It is kept as a contemporaneous record rather than written up later.

Are site diaries a legal requirement in the UK?

There is no statute that requires a site diary by name. The requirement is contractual and practical. Standard forms impose notice duties that depend on knowing what happened and when, and the Society of Construction Law Delay and Disruption Protocol recommends that parties agree what records will be kept at the outset and resource that agreement.

How do site diaries help with construction claims?

They provide contemporaneous evidence of what was happening on a specific day, which is what extension of time, disruption and adverse weather claims all need. Because a diary is written before anyone has a reason to argue, it carries more weight than documents produced once a dispute has started.

What does contemporaneous mean in construction records?

It means the record was created at or near the time of the events it describes, rather than reconstructed afterwards. A diary completed on the day is contemporaneous. A week written up on a Friday is a recollection, and it is treated as one.

How long should site diaries be kept?

Keep them for the life of the project and well beyond. Claims and disputes that turn on daily records frequently arrive years after practical completion, and limitation periods for contract claims run long. Treat the diary as a record with the same retention as your contract file.

Do subcontractors need their own site diaries?

Yes, and arguably more than main contractors do. A subcontractor’s entitlement usually rests on proving that access was unavailable, preceding works were incomplete, or scope changed. The main contractor’s diary will not record those things in the terms a subcontractor needs, so keeping your own is the only reliable option.

What should a site diary record about weather?

Actual conditions rather than adjectives, recorded daily even when the weather is unremarkable. An exceptionally adverse weather claim is proved by comparing conditions against historical records for the area, so a run of ordinary days is part of the evidence, not filler.

Can a digital site diary be used as evidence?

Yes. What matters is whether the entry can be shown to have been made at the time, by an identified person, and not altered afterwards. Time-stamped, attributed entries with photographs attached generally evidence that better than a handwritten book with no way to establish when a page was filled in.

Where to start

Pick your most exposed live project and check one thing: how many of the last thirty days have a diary entry, and how many of those entries were made on the day they describe.

If the answer is uncomfortable, fix the completion rate before you improve the template. A short diary filed every day is worth more than a detailed one filed when somebody remembers, and it is the only version that will still be there when you need it.

If you want to see how Insite handles site diaries, delays and daily records against the criteria in this guide, the product pages walk through it.