The Contemporaneous Records That Make or Break a Delay Claim

Most delay claims fail not because the delay did not happen, but because the evidence presented to prove it was assembled long after the fact. The gap between what occurred on site and what can be demonstrated two years later in a claim submission is where entitlements disappear. Delay claim evidence that is contemporaneous, meaning created at or near the time of the event it describes, carries a fundamentally different evidentiary weight than records reconstructed from memory, incomplete files, and backward-looking analysis. The distinction is not procedural. It is the difference between a claim that survives scrutiny and one that does not.

Why Reconstructed Delay Claim Evidence Fails Under Scrutiny

The limitation of current practice across the GCC construction market is that most contractors begin assembling their delay records only after the delay event has concluded and the claim preparation has commenced. The project team experiences the delay in real time but does not document it in real time. Site diaries are incomplete or generic. Progress photographs are sporadic and unlabelled. Correspondence is filed but not indexed against the events it relates to. When the claims consultant arrives six or twelve months later, the raw material for the claim is a collection of fragments rather than a structured evidential record.

Arbitral tribunals and DAABs apply a consistent principle when evaluating delay evidence: records created at the time of the event are inherently more reliable than records created after it. This is not a matter of preference. It is a recognition that contemporaneous records are unaffected by the selective recall, post-hoc rationalisation, and advocacy bias that inevitably colour retrospective accounts. A site diary entry written on the day access was denied is evidence. A witness statement drafted eighteen months later describing the same event is testimony. The two are not interchangeable, and the former will always outweigh the latter when the two conflict.

The practical consequence for contractors is direct. A delay claim built on reconstructed records invites challenge at every point. The Engineer or the employer's representative can question whether the delay actually occurred as described, whether the duration was as stated, and whether the critical path was affected in the manner claimed. Contemporaneous records foreclose those challenges by providing a real-time factual foundation that is difficult to dispute.

The Seven Record Categories That Support a Delay Claim Under FIDIC

Under FIDIC 1999 and FIDIC 2017, the contractor's obligation to maintain records is embedded in multiple clauses, including the general record-keeping obligations and the specific requirements for claims under Clause 20. The following seven categories of as-built records, maintained from day one, constitute the evidential foundation of any delay claim that is built to withstand formal challenge.

Daily Site Diaries and Progress Reports

The daily site diary is the single most important contemporaneous record on any construction project. It should document weather conditions, workforce numbers by trade, equipment deployed and operational status, work activities by location, instructions received from the Engineer or employer, site visitors, and any events that affected progress. The diary must be completed daily, not weekly or retrospectively. A diary entry that reads "rain all day, no work possible" on the date it was written is powerful evidence. The same statement in a claim narrative written a year later is an assertion that the respondent will challenge.

Progress reports, whether weekly or monthly, serve a complementary function. They provide a periodic summary of progress against the programme, flag emerging delays, and record the contractor's contemporaneous assessment of the causes of any slippage. When a progress report identifies a delay cause at the time it occurs, the claim submission that later relies on the same cause gains credibility from the consistency between the real-time report and the retrospective analysis.

Programme Updates and Revisions

The baseline programme is the reference point against which all delay analysis is measured. But the baseline alone is insufficient. The contractor must maintain a record of programme updates, revisions, and re-baselines throughout the project. Each update should reflect the actual progress achieved, the revised forecast for remaining activities, and any changes to the critical path resulting from delay events or variations. Under FIDIC 2017 Clause 8.3, the contractor is required to submit revised programmes whenever the previous programme is inconsistent with actual progress or the contractor's obligations. These revised programmes are not administrative formalities. They are the backbone of any time impact analysis, as explored in our examination of choosing the right methodology between time impact, as-planned, and as-built approaches.

Correspondence Registers and Notice Logs

Every letter, email, and formal notice exchanged between the parties is potential evidence. The discipline is not merely in sending correspondence but in maintaining a register that indexes each item against the contract clause it relates to, the delay event it concerns, and the response received. A notice log that tracks issue dates, contractual deadlines, and response status provides the procedural chronology that a claim submission must demonstrate. Without it, the claims consultant must reconstruct the notice history from scattered files, and gaps in that reconstruction become gaps in the claim.

Photographs and Visual Records

Photographs are powerful evidence when they are dated, located, and contextualised. A photograph of a flooded excavation is useful. A photograph of a flooded excavation with a date stamp, a GPS coordinate, and a caption referencing the specific delay event is evidence that an arbitrator can rely upon without further explanation. The practice of capturing photographs daily, tagging them to the relevant work area and activity, and storing them in a structured folder system indexed by date and location transforms a casual site habit into a systematic evidential record.

Inspection and Test Records

Delays caused by failed inspections, re-inspections, and testing hold-points are among the most common on GCC construction projects. The records of inspection requests, inspection dates, results, and the time elapsed between request and attendance provide direct evidence of whether the Engineer's response was timely under the contract. Under FIDIC, the Engineer is obliged to attend inspections within a reasonable time. Where the Engineer's delay in attending an inspection caused the contractor to be delayed, the inspection records are the primary evidence of that delay. Without them, the contractor is asserting a delay that the Engineer can deny.

Resource Records and Allocation Sheets

Resource records serve a dual purpose. They support the delay claim by demonstrating that the contractor had mobilised the resources necessary to perform the delayed work, thereby establishing that the delay was not caused by the contractor's own under-resourcing. They also support the associated prolongation cost claim by evidencing the resources that were retained on site during the delay period. Daily labour allocation sheets, equipment deployment logs, and material delivery records should be maintained as standard project administration, not assembled retrospectively when a claim is being prepared.

As-Built Records and Completion Documentation

The as-built programme is the definitive record of when work was actually performed, as distinct from when it was planned. It is constructed from the contemporaneous records listed above: diaries, progress reports, programme updates, and resource records. The as-built programme is not a single document created at project completion. It is the product of systematic record-keeping throughout the project, assembled into a coherent timeline that can be compared against the baseline programme to identify and quantify each period of delay. This comparison is the foundation of the delay analysis, regardless of which methodology is applied. As we examined in our analysis of excusable, compensable, and non-excusable delay types, the classification of each delay event depends on evidence that links the event to its cause and its impact on the critical path. That evidence comes from the as-built records.

Organising Records for Retrieval, Not Just Storage

The volume of records on a construction project is substantial. The value of those records depends entirely on whether they can be retrieved, cross-referenced, and presented in a coherent sequence when the claim is assembled. A filing system that stores documents chronologically but does not index them by subject, by contract clause, or by delay event is a storage system, not an evidence management system. The discipline of tagging each record at the point of creation, linking it to the relevant event or issue, and maintaining a master index that allows the claims consultant to locate every record relating to a specific delay event within minutes rather than days, is the discipline that separates projects where claims succeed from projects where valid entitlements are abandoned because the evidence cannot be marshalled.

The investment in record organisation is modest. A structured folder hierarchy, a correspondence register maintained in a standard spreadsheet, and a weekly discipline of filing and tagging records against a delay event register require perhaps two to three hours per week of administrative effort. The return on that investment, measured against the cost of reconstructing the same records twelve months later or the cost of losing the claim entirely, is substantial by any measure.

The Standard That Tribunals Apply

Arbitral tribunals assessing delay claims under FIDIC apply a standard that is consistent across jurisdictions. The tribunal expects the claiming party to demonstrate, on the balance of probabilities, that the delay event occurred, that it caused delay to the critical path, that the delay was of the duration claimed, and that the contractor took reasonable steps to mitigate the impact. Each of these elements requires evidence. Each element is strengthened by contemporaneous evidence and weakened by retrospective reconstruction.

The Society of Construction Law Delay and Disruption Protocol, widely referenced in international arbitration, expressly states that contemporaneous records should be given more weight than retrospective analyses. The protocol does not create binding obligations, but it reflects the consensus of the dispute resolution community on how delay evidence should be evaluated. Contractors who maintain their records to this standard position their claims to succeed. Contractors who do not, position their claims to be challenged on evidentiary grounds before the substance is even considered.

CALIM structures every contract administration engagement around the principle that claim preparation begins on the first day of the project, not on the day the claim is identified. The record-keeping framework described above is embedded into the project's administrative processes from mobilisation, ensuring that the evidential foundation for any future claim is built in real time rather than reconstructed after the fact. CALIM's experience across dozens of delay claim engagements in the GCC confirms that the quality of contemporaneous records is the single strongest predictor of claim outcome.

The evidence you create today is the claim you win tomorrow.

Frequently Asked Questions

What are contemporaneous records in a construction delay claim?

Contemporaneous records are documents created at or near the time of the events they describe. In the context of a delay claim, they include daily site diaries, progress reports, programme updates, correspondence, photographs, inspection records, and resource allocation sheets that were produced during the project rather than assembled retrospectively for the purpose of claim preparation. Arbitral tribunals and DAABs consistently afford greater evidentiary weight to contemporaneous records than to retrospective accounts or reconstructed timelines.

How do I organise project records so they support a future delay claim?

Organise records by indexing each document against the contract clause, the work area, and the delay event it relates to at the point of creation. Maintain a correspondence register that tracks issue dates, response deadlines, and response status. Use a structured folder hierarchy that allows any record relating to a specific delay event to be located within minutes. The filing discipline required is modest, typically two to three hours per week, but the return when a claim must be assembled is substantial.

Which records carry the most weight in a delay claim under FIDIC?

Daily site diaries, programme updates showing critical path changes, and formal notices issued under the contractual procedure carry the greatest weight. Site diaries provide the factual narrative of what happened each day. Programme updates demonstrate the impact of delay events on the critical path at the time they occurred. Notices establish that the contractor complied with the contractual preconditions for claiming, including the time-bar requirements under Clause 20.

What happens if I do not have contemporaneous records for a delay event?

Without contemporaneous records, the contractor must reconstruct the delay narrative from whatever partial evidence is available: incomplete diaries, undated photographs, and witness recollections. Reconstructed claims are not automatically rejected, but they face a significantly higher burden of challenge. The respondent can dispute the timing, the duration, and the causation of every delay event for which real-time evidence is absent. The claim may still succeed, but it will cost more to prepare, take longer to resolve, and recover less than a claim supported by complete contemporaneous records.

When should I start keeping records for a potential delay claim?

From the first day of the project. Delay claim evidence should not be treated as something that begins when a delay event is identified. The baseline records, including the approved programme, the correspondence register, and the daily site diary, must be in place from mobilisation. These records serve dual purposes: they support the project's day-to-day administration and they provide the evidential foundation for any claim that may arise at any point during the contract period.

Note: This article provides a general framework for contemporaneous record-keeping in support of delay claims under FIDIC contracts. The specific evidentiary requirements for any claim depend on the contract terms, the governing law, the dispute resolution forum, and the factual circumstances of the project. Contractors should seek project-specific advice on record-keeping obligations and claim preparation strategy.