A delay claim is rarely won by the party with the loudest account of what happened. It is won by the party that can connect a defined event to a critical impact, prove entitlement under the contract, and quantify the resulting time and cost. The best evidence for delay disputes is therefore not one document. It is a disciplined record that makes that chain difficult to challenge.
For contractors, employers, developers, and project managers, the evidence strategy must begin while the works are ongoing. By the time a dispute reaches adjudication, arbitration, or court, memories have changed, personnel have moved on, and project narratives have hardened. Contemporaneous records become the project’s most credible witness.
Best Evidence for Delay Disputes Starts With the Baseline
The approved baseline program is usually the starting point for any serious delay analysis. It shows the agreed logic of the works, sequencing, durations, milestones, critical path, and planned completion date. Without a reliable baseline, it becomes much harder to demonstrate what was delayed, when the delay occurred, and whether it mattered to completion.
But a baseline schedule is not automatically persuasive simply because it exists. A tribunal will test whether it was properly developed, contractually accepted, and consistent with the actual scope and method of working. A program submitted only to satisfy an administrative requirement, then ignored by the site team, has limited value.
The strongest position is built on a baseline that is detailed enough to test, regularly updated, and tied to real project controls. In FIDIC-based projects and other complex construction contracts, the distinction between an accepted program and a practical management tool can be decisive.
The Records That Prove Cause and Effect
A delay dispute requires more than proof that an event occurred. The claimant must ordinarily show that the event caused delay to a contractual milestone or completion, and that the delay was not absorbed by available float, resequencing, mitigation, or contractor-caused delay.
Contemporaneous notices and correspondence
A prompt contractual notice is often the first formal record of a claim event. It should identify the event, reserve rights where appropriate, describe the expected impact, and comply with the applicable time bar provisions. A late or vague notice can create a major entitlement issue even where the underlying event was real.
Correspondence then gives the event its commercial and factual context. Instructions, requests for information, design comments, access restrictions, suspension directions, meeting minutes, and emails may establish who knew what, and when. The key is precision. A message saying that progress is “affected” is weaker than a record identifying the affected activity, the missing information, the required decision, and the anticipated impact on the completion path.
Site records and daily evidence
Daily reports, site diaries, labor allocation records, equipment logs, delivery tickets, inspection records, photographs, and weather data can prove conditions on the ground. They are particularly valuable where a dispute concerns late access, disrupted productivity, defective design information, unforeseen conditions, or an employer-directed change.
These records must be authentic and consistent. A daily report completed weeks later, using generic language repeated across multiple days, invites challenge. Site teams should record facts rather than arguments: which workfront was unavailable, which crew stood by, what instruction was awaited, and what activity could not proceed.
Updated programs and schedule data
Regular schedule updates are where the project story becomes measurable. They can show movement in the critical path, slippage of key activities, changes in logic, and the effects of recovery measures. Native scheduling files, not merely PDF exports, are essential where forensic delay analysis is likely.
The quality of schedule updates matters as much as their frequency. Unexplained changes to logic, artificial constraints, out-of-sequence progress, or retrospective revisions can undermine credibility. If the project team changes the program, it should be able to explain why the change reflects a genuine development in the works.
Change and instruction records
Variations are common sources of delay, but they do not automatically justify an extension of time. The evidential question is whether the change affected critical work and whether the contractor responded reasonably.
Keep the instruction, proposal, technical submissions, approval trail, pricing correspondence, procurement impact, and program assessment together. Fragmented records make it easy for the other side to argue that the contractor chose an inefficient method, delayed mobilization, or failed to warn of consequences.
Proving Critical Delay, Not Just Disruption
Projects can suffer significant disruption without delaying completion. This is where many claims fail. A party may prove lost productivity or a delayed activity but still fail to establish an extension of time because the activity was not on the critical path.
A credible delay analysis should answer four questions: What event occurred? Which activities did it affect? Did those activities drive completion at the relevant time? What delay would have occurred without the event?
There is no universally correct delay methodology. A prospective time impact analysis may be appropriate where the effect is assessed close to the event. A retrospective analysis may be more reliable when complete progress data is available. Window analysis, as-planned versus as-built analysis, and collapsed as-built approaches each have strengths and vulnerabilities.
The right method depends on the contract, available data, schedule quality, and issues in dispute. The commercial objective is not to select the most complicated model. It is to use a transparent method that fits the records and can withstand cross-examination.
The Difficult Issues: Concurrency and Mitigation
Concurrent delay is rarely resolved by simply identifying two events that occurred in the same month. The real question is whether employer-risk and contractor-risk events were both effective causes of delay to completion during the same period. The answer depends on the governing contract and applicable law.
For a contractor, records of mitigation are essential. Recovery schedules, revised work sequences, additional resources, acceleration instructions, and correspondence about alternative workfronts can show a reasonable response. For an employer, the same records may show that the contractor had practical options but failed to use them.
Mitigation does not mean accepting unlimited cost or abandoning contractual rights. It means acting reasonably, documenting decisions, and making the consequences of each option clear before the dispute becomes entrenched.
Build an Evidence System Before the Claim Exists
The best evidence is often lost through ordinary project behavior: informal instructions on calls, decisions recorded only in personal inboxes, overwritten schedules, and photographs stored without dates or locations. A basic evidence protocol protects both claim and defense positions.
Project leadership should ensure that the team follows a small set of non-negotiables:
- Maintain a controlled register for notices, instructions, RFIs, variations, and potential claim events.
- Preserve native schedule files, update narratives, and records of all logic or duration changes.
- Require daily reports to identify affected workfronts, labor, equipment, access, and material status.
- Confirm material oral instructions in writing and assign owners for follow-up actions.
- Capture mitigation decisions, including rejected alternatives and their time or cost implications.
This is not administrative excess. It is a commercial control. On a major project, poor records can turn a valid claim into an unrecoverable cost or expose an employer to a delay position that cannot be properly defended.
Presenting Evidence So Decision-Makers Can Use It
A tribunal, dispute board, or court should not have to reconstruct the project from thousands of unindexed emails. Strong claims present evidence through a clear chronology, an event-by-event matrix, properly referenced records, and a delay analysis that speaks the same factual language as the project documents.
Avoid overstating the case. If a period includes contractor delay, address it directly. If a notice was imperfect, explain the factual context and the contractual consequences. Credibility is built when the evidence is organized, candid, and aligned with the relief sought.
For high-value projects, legal strategy and delay analysis should be coordinated early. The scheduler may establish technical impact, but entitlement turns on the contract, notices, risk allocation, and the evidential burden. That is where focused construction and dispute counsel adds practical value.
When a critical event occurs, preserve the record before debating the narrative. The project team that can prove the facts, explain the schedule, and show a reasonable response is the team best placed to protect the result.