Daily progress reports that hold up in a delay claim

On any construction project, the Target Date of Completion and liquidated damages make daily progress records critical. This guide explains what makes a DPR strong enough to support an extension-of-time or delay claim - contemporaneous records, planned vs actual, cause and effect - and how to produce claim-ready reports on the go.

Every construction project is a race against a date. The contract fixes a Target Date of Completion, the programme works backwards from it, and if the works finish late, liquidated damages can start eating into the contractor's money. That is the pressure everyone on site lives under. What gets forgotten until it is too late is that not every delay is the contractor's fault, and when the argument over whose fault it was finally arrives, the side with the better daily records almost always comes out ahead.

The daily progress report is that record. This article is about what separates a DPR that quietly supports a delay claim from one that falls apart the moment it is questioned, and how to produce strong reports every day without losing your evenings to them.

Please note. This is general, practical guidance for site teams, not legal advice. Delay and extension-of-time entitlements depend entirely on your specific contract and the law that governs it. For an actual claim, work with your contracts and legal advisers and follow your contract's notice and record-keeping provisions.

TDC, liquidated damages, and why daily progress is watched

The Target Date of Completion (TDC) is the promise at the centre of the contract. Tied to it, most contracts carry liquidated damages: a pre-agreed sum the contractor pays for each day of culpable delay. That is why progress is monitored so closely. Daily monitoring does two jobs at once. In the moment, it warns you that the work is slipping while there is still time to react. Later, it becomes the evidence of why it slipped, and whether the cause was something the contractor should carry or something they should be relieved of.

Miss the first job and you lose time you could have recovered. Miss the second and you lose the argument about who pays for it.

What a delay claim actually needs

When a project is delayed by something outside the contractor's control, late drawings, a client change, exceptional weather, delayed access, most standard forms of contract allow the contractor to ask for an Extension of Time (EOT). A granted EOT moves the completion date and protects the contractor from liquidated damages for that period; sometimes it carries cost as well.

But an EOT is not given for the asking. In broad terms, a claim has to show three things, in order:

An event occurred that the contract recognises as a relief event.
That event delayed the works — there is a real, traceable link from the event to a hold-up on site.
The delay affected completion — it pushed out the finish date, not just some activity with time to spare.

On top of that, most contracts require notice within a set time of the event. Each of those four things, the event, the on-site effect, the impact on completion, and timely notice, has to be supported by evidence. That evidence is overwhelmingly your daily records.

Why contemporaneous records win or lose claims

There is a word that decides most delay disputes: contemporaneous. It means the record was made at the time the events happened, not pieced together months later when the claim is being prepared. Contemporaneous records carry weight precisely because they were written before anyone knew there would be an argument. A diary reconstructed after the fact, by contrast, is easy to challenge and easy to dismiss.

This is where the DPR earns its importance. Written honestly every single day, it is the strongest contemporaneous record a site produces. And the reverse is just as true: a gap in the daily reports is a gap in your case. If the diary is silent on the three weeks you were waiting for a drawing, it is very hard to later claim those three weeks.

You cannot create contemporaneous records after the event. Either they were written on the day, or they were not. That is the whole reason a daily habit matters.

What makes a DPR hold up

Not every daily report is claim-ready. The ones that hold up under scrutiny share a few qualities:

Complete. Manpower, plant and equipment, weather, the work done with its location and quantity, materials, instructions received, and hold-ups.
Honest about delays. The single most valuable line in a DPR is the one recording a hold-up and its cause: "no concreting at pier 4, reinforcement drawing awaited", not a blank space.
Consistent. The same format every day, with no missing days. Gaps and changing formats invite doubt.
Specific. Quantities and locations, not generalities. "Excavation" proves little; "excavation, pier 4, 60 m³" proves a lot.
Evidenced. Backed by dated site photographs tied to the entry.
Signed and dated. Authorship and date are what make it a record rather than a note.

Planned vs actual: showing the slip

A claim usually starts by showing the gap between what was planned and what actually happened. Plot cumulative progress against time and you get the familiar S-curve: slow at the start, fast in the middle, tailing off at the end. The baseline programme gives you the planned curve, reaching 100% at the TDC. Your as-built records, built up day by day from the DPRs, give you the actual curve.

Planned vs actual progress: the as-built curve, built from daily reports, slips past the Target Date of Completion. The gap is the delay you may need to explain.

The S-curve shows there was a delay, but on its own it does not say whose it was. For that you have to go from the curve down into the daily detail, which is the next step.

Linking cause, effect and the completion date

Here is the point most weak claims miss: a delay only matters if it pushes out completion. Activities that have spare time, or float, can slip a little without moving the end date. It is the activities on the critical path — the chain that determines the finish — where a delay turns directly into a late project.

So a strong claim builds a clear chain: a relief event happened, it held up a critical activity, and that pushed the completion date. Each link in that chain has to be evidenced, and the DPR is where the links live.

A delay claim is a chain of cause and effect. The DPR supplies the evidence for every link.

Strong DPRs without the daily grind

Everything above asks the same thing of you: a complete, consistent report, every single day, for the life of the project. That is simple to say and hard to keep up by hand, which is exactly why so many diaries have gaps in the weeks that later matter most. This is the practical problem our Railway DPR tool is built to solve, and it applies to any construction work, not only railways.

On the go. Write the report on site, on your phone, while the detail is fresh, instead of from memory that evening.
Ready, versatile templates. Start from a structured format that already prompts for manpower, plant, work, quantities, instructions and hold-ups, so nothing important is left blank.
Add the template you need. Different projects and contracts want different formats; you can add the template that matches yours and keep working.
One-click progress. Pull the progress for a single day, or across all days, in one click, which is exactly the as-built picture a claim leans on.
Photos stored with the entry. Attach site photographs to the day, so the visual evidence never drifts away from the words.

The tool does not win a claim for you; the facts and the contract do that. What it does is make the daily record easy enough that it actually gets made, completely, every day, which is the part that usually fails.

Mistakes that sink a claim

Missing days. A gap in the diary is a hole in the timeline you cannot fill later.
Recording work but not hold-ups. If the report only ever says what was done and never what was stopped, it cannot support a delay claim.
Vague causes. "No work at pier 4" is half a record. "No work at pier 4, awaiting revised drawing" is evidence.
No photos. Words are stronger with dated images behind them.
Reconstructing later. Records written after the dispute starts carry little weight.
Ignoring notice. The best records do not help if the contract's notice period was missed.
Forgetting instructions and variations. Unrecorded instructions are claims you cannot prove were given.

A claim-ready DPR checklist

Filled in every working day, with no gaps, in a consistent format.
Manpower, plant and equipment actually on site.
Weather, especially anything that affected work.
Work done with its location and quantity.
Materials received and used.
Every instruction or variation received that day.
Hold-ups and delays, each with a clear cause.
Dated photographs tied to the day's entry.
Signed and dated by the responsible person.
Notice of delay events raised in line with the contract.

A delay claim is rarely won by a clever argument at the end. It is won, or lost, in hundreds of small daily entries made while the work was happening. Keep them complete, keep them honest about the hold-ups, and keep them every day, and the record will speak for you when you need it to.

Frequently asked questions

When a project is delayed by an event outside the contractor's control, most contracts let the contractor request an Extension of Time. If granted, it moves the completion date and protects the contractor from liquidated damages for that period, and sometimes carries cost. Entitlement depends entirely on the specific contract, so this is general information rather than legal advice.

Because claims are decided largely on contemporaneous records, meaning records made at the time the events happened. The daily progress report is the strongest such record a site produces. A complete daily diary supports your timeline, while gaps in it become gaps in your case that are very hard to fill later.

It should be complete (manpower, plant, weather, work done with location and quantity, materials, instructions and hold-ups), honest about delays and their cause, consistent in format with no missing days, specific rather than vague, backed by dated photos, and signed and dated. The most valuable habit is recording every hold-up and its cause on the day it happens.

No. Only delays to activities on the critical path push out the finish date. Activities with spare time, or float, can slip without affecting completion. A strong claim shows a clear chain from the event, to a held-up critical activity, to the delayed completion date.

Yes, provided it is contemporaneous, complete, consistent and traceable, with entries and photos clearly dated. Many sites now keep their daily reports digitally. Always follow your contract's specific requirements for notice and for the form and retention of records.

About this article. Written and reviewed by the Ornova Labs Engineering team from direct experience building these tools. Spotted something that needs correcting? Email ornovalabs@gmail.com — we update articles when facts change, and the “Updated” date above reflects the last revision.