{"id":1098,"date":"2026-08-14T14:01:58","date_gmt":"2026-08-14T18:01:58","guid":{"rendered":"https:\/\/steelray.com\/blog\/?p=1098"},"modified":"2026-08-16T05:47:52","modified_gmt":"2026-08-16T09:47:52","slug":"construction-delays-why-comparison-isnt-causation","status":"publish","type":"post","link":"https:\/\/steelray.com\/blog\/?p=1098","title":{"rendered":"Construction Delays: Why Comparison Isn\u2019t Causation"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Every construction litigator knows the moment. A project finished months late, the claim is worth millions, and the whole case turns on a deceptively simple question: <em>which delays actually drove the late completion?<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not which activities slipped. Not what changed between schedule updates. Which delays were <strong>causative<\/strong> \u2014 the ones that actually pushed the finish date out, as opposed to the dozens of changes that were noise, float-absorbed, or off the critical path entirely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Answering that question well is the difference between an expert opinion that survives challenge and one that gets picked apart on cross. And too often, the analysis behind it can&#8217;t bear the weight.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The problem: comparison is not causation<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The instinct \u2014 and the output of most scheduling tools \u2014 is to compare two schedule updates and produce a list of differences. Hundreds of activities changed. Durations shifted. Logic was revised. Actual dates rolled in.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That list tells you <em>what changed<\/em>. It does not tell you <em>what mattered<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A delay claim doesn&#8217;t hinge on the fact that an activity slipped. It hinges on whether that slippage propagated through the critical path to move the completion date \u2014 and whether other delays were happening concurrently, and whether the schedule would have finished late anyway &#8220;but for&#8221; a particular party&#8217;s delay. Those are causation questions, and a difference report is silent on all of them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When the underlying analysis can&#8217;t cleanly separate causative delays from immaterial changes, the consequences show up exactly where they hurt:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Vulnerable expert testimony.<\/strong> An opinion built on &#8220;these activities changed, therefore this delay caused the overrun&#8221; invites the obvious cross-examination: <em>how do you know this change drove the finish date and not one of the other three hundred?<\/em> If the expert can&#8217;t show the mechanism, the opinion wobbles.<br><\/li>\n\n\n\n<li><strong>Disputes that drag.<\/strong> When each side&#8217;s analysis is subjective and hard to reproduce, the parties argue about methodology instead of merits. That&#8217;s more months, more fees, and more uncertainty.<br><\/li>\n\n\n\n<li><strong>Reproducibility challenges.<\/strong> If two analysts running the same schedules can reach different conclusions, the analysis looks like advocacy dressed as engineering \u2014 and opposing counsel will say exactly that.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The core problem isn&#8217;t a lack of data. It&#8217;s that raw schedule comparison leaves the hardest, most consequential work \u2014 establishing causation \u2014 to manual interpretation that&#8217;s slow to produce and easy to attack.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The solution: objective, reproducible causation analysis<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the gap Steelray Delay Analyzer was built to close. Rather than handing you a haystack of differences, it performs a fully-automated <strong>half-step delay analysis<\/strong> following AACE recommended practice (RP 29R-03, MIP 3.4) \u2014 the method that isolates, period by period, which delays actually impacted the completion date.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the litigator commissioning or defending the analysis, a few things matter more than the mechanics:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>It answers the causation question directly.<\/strong> Delay Analyzer identifies and quantifies the delays that impacted the finish date \u2014 including concurrent delays, with but-for analysis available in the current beta version \u2014 instead of leaving that inference to the analyst. The output speaks to causation, which is what the case actually turns on.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>It&#8217;s objective and follows a recognized standard.<\/strong> Because the analysis applies a consistent, AACE-compliant methodology rather than analyst judgment applied change-by-change, the same schedules produce the same results. That reproducibility is a feature in a courtroom: it makes the opinion defensible and harder to dismiss as results-driven.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>It shows the work.<\/strong> Contemporaneous critical paths for each window, a longest-path change analysis showing precisely how the critical path shifted over time, period-by-period detail on which activities caused impact, and clear visualizations \u2014 including a Gantt you can scrub through time to <em>watch<\/em> delays and recoveries unfold.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>It compresses timelines and cost.<\/strong> Work that once took days of an analyst manually applying changes and recording finish-date impacts now runs in seconds across any number of schedule updates. That means faster case assessment early, and lower expert cost throughout.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why this matters<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The best time to know whether a delay claim is solid isn&#8217;t at deposition \u2014 it&#8217;s at intake. An objective, reproducible causation analysis lets you evaluate the real strength of a claim or defense early, decide what&#8217;s worth pursuing, and avoid building a case on an analysis that won&#8217;t hold up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It&#8217;s no accident that Delay Analyzer is the tool of choice for the forensic and claims professionals who perform analyses in these disputes \u2014 teams at firms like HKA, FTI Consulting, Ankura, and JS Held. When the analysis has to survive scrutiny, the methodology behind it is the whole game.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>See it on a real schedule<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nothing makes the distinction clearer than watching it work on an actual project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/steelray.com\/DelayAnalyzer\/DelayAnalyzerP6.php?code=blog081426#more_info\">Request a demo of Steelray Delay Analyzer<\/a><\/strong> \u2014 we&#8217;ll walk through how it isolates causative delays, handles concurrency, and produces the kind of defensible, reproducible analysis a construction dispute demands. We can also set you up with a trial license to run it on your own schedules.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every construction litigator knows the moment. A project finished months late, the claim is worth millions, and the whole case turns on a deceptively simple question: which delays actually drove the late completion? Not which activities slipped. Not what changed between schedule updates. Which delays were\u2026<\/p>\n","protected":false},"author":1,"featured_media":1101,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,37,63,12],"tags":[70,69,71,72],"class_list":["post-1098","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analyzers","category-delay-analysis","category-productivity","category-project-management","tag-construction-claims","tag-delay-analysis","tag-forensic-schedule-analysis","tag-primavera-p6"],"_links":{"self":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1098"}],"version-history":[{"count":5,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1098\/revisions"}],"predecessor-version":[{"id":1105,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1098\/revisions\/1105"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/1101"}],"wp:attachment":[{"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/steelray.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}