When presenting a delay-type of claim on a construction project, a claimant MUST be in a position to properly PROVE the claim.  Trying to present a delay claim loosey-goosey is not a recipe for success.  In fact, it can be a recipe for an easy loss. This is not what you want.  To combat this, make sure you engage a delay expert that understands delay methodologies and how to calculate delay and do NOT present a total time claim. Presenting a delay claim using a total time approach, discussed below, makes it too easy to attack the flaws and credibility of the approach.  Per the discussion of the case below, a total time claim with a contractor that used its project manager, versus a delay expert, to support its claim turned the contractor’s claim into a loss.

In French Construction, LLC v. Department of Veteran Affairs, 2022 WL 3134507, CBCA 6490 (CBCA 2022), a contractor submitted a delay claim to the government for almost $400,000. The contractor was hired to construct a two-story corridor to connect hospital buildings.  The contractor was required to be complete within 365 days. It was not.  The contractor was seeking 419 days of delay from the government. The contractor’s “delay expert” was its project manager who compared the contractor’s as-planned schedule to an as-built schedule he prepared for the claim.

To show how the critical path of contract performance evolved over the life of the contract and how excusable delays impacted that path, a contractor, at a minimum, needs a reasonable ‘as planned’ schedule and an ‘as built’ schedule, which it can incorporate into an analysis to show ‘the interdependence of any one or more of the work items with any other work items’ as the project progressed.” French Construction, supra (quotation and citation omitted).

Unfortunately, because the project manager was not a true delay expert, there were material flaws in his methodology from a critical path causation standpoint and a calculation of delay standpoint.  Basically, which is a big no-no, the project manager did a total time claim by simply taking the delta between as-planned and actual completion dates and focusing on durations while skipping the causation.

Under the ‘total time theory,” the contractor simply takes the original and extended completion dates, computes therefrom the intervening time or overrun, points to a host of individual delay incidents for which defendant was allegedly responsible and which ‘contributed’ to the overall extended time, and then leaps to the conclusion that the entire overrun time was attributable to defendant. The [total time] theory of proving delay is insufficient to meet the contractor’s burden to prove that government-caused delay actually delayed the overall completion of the project. [The contractor’s project manager] testified about the drawing delays and other problems that delayed demolition of the building without providing a sufficient showing that all the days of delay were attributable to this cause….

The remainder of [the contractor’s] delay claim suffers from the same problem. [The project manager] simply subcontracted the planned duration from the actual duration and identified that as the period of delay. [The project manager], in his report, then generally describes challenges or issues that [the contractor] faced during periods…without any specifics, to those issues.  [The project manager’s] opinions regarding the causes of delay amount to ‘broad generalities and inferences” that are insufficient to carry [the contractor’s] burden to prove compensable delay.

French Construction, supra (internal quotations and citations omitted).

Please contact David Adelstein at or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.



If you need to prove and allocate construction project delays, you should engage a scheduling consultant qualified with CPM (critical path method) analysis.  You should also engage counsel to assist in preserving your rights, as well as presenting and maximing your arguments for delay.

There are numerous methodologies used to quantify and allocate delay. You want to discuss the most effective analysis for your case and facts including whether you want/should use a forward-looking prospective analysis or a backward-looking retrospective analysis that factors in as-built data.  In doing so, you want to make sure you understand the pros and cons of each methodology including the bases to attack the methodology that will be subject to cross-examination.  The five primary CPM methodologies are as follows:





  1. As-Planned Versus As-Built. This methodology compares the as-planned baseline schedule to an as-built schedule reflecting progress to assign delay.  An as-built schedule that reflects progress includes actual start dates, finish dates, and durations.  The actual dates and durations are compared with the as-planned dates and durations on the baseline schedule to determine delay.  Under this methodology, the delay impact is determined retrospectively.


  1. Windows Analysis. This methodology divides the project into windows of period of time and focuses on an as-built critical path analysis that relies on progress schedule updates and as-built data.  The as-built critical path is then quantified for each of the periods (or windows).   The methodology compares the as-planned baseline schedule’s critical path to the as-built schedule (and as-built conditions) during the window to quantify delay. Under this methodology, the delay impact is determined retrospectively.


  1. Collapsed As-Built. This methodology is the “but for” methodology as it analyzes the earliest date the project would have been completed “but for” identified delays.  This methodology removes delay events from the as-built schedule to determine when the project would have been completed “but for” the delay event(s).  Under this methodology, the delay impact is determined retrospectively.


  1. Impacted As-Planned. This methodology inserts potential delay events/activities into the as-planned baseline schedule to determine impacts.  By inputting new delay activities into the baseline as-planned schedule, new logic and a new critical path is created to result in a new completion date (i.e., an impacted, as-planned schedule).  The difference between the completion date in the impacted, as-planned schedule and the (unimpacted) as-planned baseline schedule represents the delay.  This methodology does not rely on as-built data and prospectively determines delay.


  1. Time Impact Analysis. This methodology analyzes delay events individually based on the schedule update immediately prior to the delay event.  The difference between the project’s completion date before and after the delay event quantifies the delay.  Under this methodology, the delay event is added into the updated schedule closest to the event to see if the project completion date changes based on the event’s impact to the completion date.  This methodology does not rely on as-built data and prospectively determines delay based on when the event occurred.


It is not uncommon for parties to use different methodologies to quantify and assign delay.  It is also not uncommon for the parties to attack the other methodology as unreliable– whether not focusing on what actually occurred or not focusing on an event the moment it occurred based on the schedule or plan in-place as of the delaying event(s).  As an example only, in K-Con Building Systems, Inc. v. U.S., 131 Fed.Cl. 275 (Fed.Cl. 2017), a contractor asserted claims relative to the government’s delay. The contractor claimed the critical path should be analyzed with a prospective analysis predicated on its as-planned performance.  The government disagreed claiming the critical path should be analyzed based on a retrospective as-built analysis.  The Court of Federal Claims agreed with the government “that the proper way to determine what activities were on the critical path of performance in this case is to examine what actually occurred during contract performance.”  K-Con Building Systems, supra, at 329.  The Court reached this conclusion because: (1) “a critical path schedule that relies solely on the [baseline] schedule set forth in the contract specifications does not account for subsequent changes to the schedule authorized by the contracting agency” and (2) “the use of a contractually based critical path schedule does not reflect that the [contractor] did not actually perform in accordance with the [baseline] schedule set forth in the contract specifications.”  Id. at 329-330.  Stated differently, the as-planned approach that the contractor employed did not “fully reflect the reality of what occurred on the project.”  Id.


Please contact David Adelstein at or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.