Comprehensive, contemporaneous documentary evidence can make or break a delay claim. To be reliable, project schedules must be verifiable, requiring supplementary documents like logs, reports, and other project information to corroborate what schedules show. While forensic schedule analysis is effective at demonstrating the impact of changes to sequence, logic, or activity duration, proving the cause behind such impacts requires considering the facts behind the schedule.
In delay claims, experts examine all project documents to conduct schedule delay analysis, opining on when delays occurred, the reasons behind them, and the responsible parties. Various project documents serve as critical evidence in delay and disruption claims. Photographs and videos documenting actual progress can be particularly valuable in illustrating project conditions at specific points in time. These visual records demonstrate the state of work to the trier of fact and clarify complex technical aspects of construction that may not be intuitively understood by non-specialist adjudicators. Project correspondence, including letters, emails, and text messages, provides essential contemporaneous evidence of notice, directions, instructions, and decisions that influenced the project's progression.
Maintaining complete, detailed project documents throughout a project is time-consuming and resource-intensive. Contractors and some owners will have entire project controls teams dedicated to creating and maintaining proper documentation for large, complex projects. While smaller projects cannot sustain this level of activity, maintaining basic project documentation remains critical and should be viewed as an insurance policy for underwriting potential claims. Complete records are also key to dispute avoidance, as a well-documented project provides a more compelling basis for contemporaneous extension of time claims.
The value ascribed to otherwise contemporaneous, accurate records will be influenced by the document's objectivity. Project participants should strive to ensure neutrality in reports, correspondence, and daily communications. When recording observations for minutes and reports, they should be restricted to what is said, heard, and witnessed only. Electronic records should be maintained in native format-schedule files in Microsoft Project or Primavera P6, images as unaltered JPGs, PNGs, or TIFFs, and emails in their original format. Native formats preserve valuable metadata like dates created and modified, demonstrating contemporaneity, and allow forensic experts to assess logic, relationships, and constraints used in developing project schedules.
Contract Documents
Delay claims start with the contract documents. Every project is different, and delay claimants must understand how different delay risks have been allocated between the parties. Contracts establish the interim and final milestones from which extensions of time are calculated, may stipulate agreed-upon rates for standby time, and identify recoverable cost categories in the event of delay. Claimants must also be aware of contractual requirements for notice and minimum requirements for claim substantiation.
Assessing delay requires understanding a project’s scope and how it has changed over time, making an up-to-date record of change orders critical. Notwithstanding contractual terms requiring executed change orders for amendments, parties may agree to changes informally through emails, text messages, or verbally. Maintaining access to such electronic information during a project is important, and verbal agreements should be confirmed in writing as soon as possible.
Project Schedules, Schedule Updates, Schedule Narratives
A quality baseline schedule is one of the most important pieces of documentary evidence in any delay claim. An unreliable baseline schedule will undermine even the strongest claims for delay. Taking time to create a robust, achievable, and credible baseline schedule at project start is vital to any future delay claims. Likewise, maintaining regular, accurate schedule updates based on validated as-built information will bolster forward-looking time impact analyses and retrospective forensic delay analyses.
Ideally, schedule updates should be accompanied by narratives providing reasons or explanations for delays or deviations. When preparing narratives, remember that what may seem obvious to the scheduler at the time may not be obvious years later during forensic analysis. Other project schedules can be equally important, including look-ahead schedules (typically limited to shorter time horizons), which tend to be more detailed at the activity level, and sequencing schedules, which can support lost productivity claims.
Notices
Notices of delay, notices of default, and potentially a notice of termination may be issued over the course of contract work. Where contracts stipulate the form and content of notice, contractors should strive to meet those requirements in every case. Failure to provide timely and proper notice can be fatal to a contractor's delay claim.
Contractors may be reluctant to give notice early for fear of upsetting an owner, but this concern is often misplaced. Owners want transparency and the ability to make informed decisions. While contracts may stipulate formal notice requirements, formalities can be complemented by informal notice, like a simple heads-up email or phone call. When done right, proper, timely claims should build credibility rather than sour relationships. Records of notice should include the paper trail, referenced documents, subsequent responses, and proof of delivery.
Reports and Logs
Daily, weekly, and/or monthly progress reports serve as some of the best contemporaneous records of day-to-day activities on site, making them critical for validating the as-built schedule and supporting delay and disruption events. Site reports should be detailed enough for an independent third party to understand what was occurring on site in any given period and should include: weather conditions; workforce count and hours; equipment usage; work planned vs work progressed; and site constraints and disruptions.
When delays occur, site reports should record the cause and resulting impact (e.g., steel erection delayed eight hours due to high winds). The quality and credibility of a site report depends on its level of detail and, above all, its contemporaneousness. Consistency and completeness in logs and reports bolster credibility and make it easier to document cause-effect relationships. Keeping records factual while avoiding subjective language enhances reliability.
Project logs include time logs; design/drawing logs; RFI logs; material receiving logs; field change logs; equipment logs; non-conformance report logs; quality inspection logs; and milestone logs. Third-party inspection reports can also provide valuable insight, such as an engineer's report showing deficient work that explains contractor delays.
Photos and Videos
Photos and videos provide objective evidence of exactly what is happening on site at a point in time, including progress of different work aspects, site conditions, and causes of interference. Scheduling time for daily or weekly photos of the same site areas or work fronts creates a record of regular progress that can be correlated with delay events in retrospective analysis. For photos and videos to be most useful, they must be maintained in an organised way so reviewers can easily identify what they are looking at and from when.
Increasingly, larger projects utilise drone footage to capture project progress periodically. Fixed cameras positioned throughout a project site can track progress on a 24-hour basis. While the volume of such evidence could previously have overwhelmed project teams, new artificial intelligence applications are making powerful use of this data.
Meeting Minutes
Meeting minutes should be kept during or prepared immediately after meetings to ensure all relevant information is captured. Typically, minutes are circulated amongst and signed off by attendees to confirm their accuracy. Parties must take seriously the contemporaneous review of meeting minutes and respond when information is recorded incorrectly.
Standardized templates make review easier and more efficient. Equally important is updating templates appropriately rather than allowing relics from past meetings to carry forward, thereby tainting record quality. Progress meeting minutes should record current schedule status and critical-path updates. It is also helpful to document specific events causing delay, anticipated impact, responsibility, and any mitigation measures proposed or implemented.
Correspondence
Correspondence often comprises a significant portion of evidence in delay disputes, particularly on larger projects. Emails are the most prevalent form of project communication and represent valuable evidence due to their inherent timestamps, detailed conversation threads, and attachments. Emails should be preserved in native format to retain metadata and maintain attachment integrity. Where impractical, saving them as PDFs is acceptable, but attachments should be retained and clearly labelled separately.
Phone calls and voicemails require prompt documentation. Contemporaneous notes should be made immediately following calls, and voicemails should be downloaded and stored as audio files. Increasingly, important communications are shifting to messaging platforms like Teams, WhatsApp, and iMessage. While generally informal, these can contain vital project information about changes, progress, and disruptions. Text logs or screenshots are acceptable means of preservation, though collection can be onerous and may only be justified for high-value claims.
Formal letters exchanged among project participants, particularly notices related to delay or default, constitute crucial documentation. Transmittal emails demonstrating that a party received notice of specific project issues or delays at a point in time should be carefully preserved.
Cost and Financial Records
Proving delay impacts is only part one of a successful compensable delay claim; the second challenge requires proof of damages. Effective cost tracking and maintaining accurate financial records is essential for substantiating delay damage claims. Most contractors maintain cost control systems tracking project costs to specific cost codes, which should at least track overtime costs, acceleration costs, standby costs, and overhead costs. More sophisticated systems organise costs in accordance with a project’s work breakdown structure, allowing more granular tracking and deeper analysis.
Parties can create unique cost codes to track delay and impact costs but often fail to do so when the delay is incurred, whether because of disconnect between project management and project controls teams or simple lack of foresight. Project teams must balance granularity with usability. Cost codes are only meaningful if used by site crews to properly track labour time and equipment and material usage. Training teams to respond to potential delays by fastidiously tracking impact costs can pay dividends.
BIM Data
BIM is a computer-based tool for designing physical assets, a virtual, 3D representation of all physical and functional characteristics of a facility intended as both a design and maintenance tool. It is also a collaboration tool allowing different project participants to contribute design and constructability feedback directly into the model.
BIM allows designers to model scheduling information and construction sequences (often termed 4D modelling). At its best, BIM links construction specifications, drawings, material procurement information, submittal information, and other data in one place. As a scheduling tool, BIM can be highly valuable in asserting project delay claims, as a properly updated model allows contractors and owners to see a 3D virtual representation of progress status at any point in time. It also allows the impact of different causes to be modelled virtually. This is particularly helpful during the project, as the contractor can visually demonstrate how a change in sequence or late delivery will impact the overall schedule. For these reasons, maintaining BIM data after project completion can be a valuable tool for forensic delay analysis in disputes.
Conclusion
Schedules alone, without comprehensive evidentiary foundation, will not win delay claims. Likewise, not all documentary evidence is created equal: contemporaneity, organization, and objectivity are critical to building a credible delay case. Projects that invest in disciplined documentation are better positioned not only to succeed in disputes, but to avoid them altogether.