Esc

↑↓ move↵ openIndex · Pagefind

Concurrent delay: establish the facts before labeling the overlap

Distinguish overlapping events from effects on completion, document independent paths and prepare the evidence needed for concurrent-delay review.

Charley Forey2 min readSchedulingSchedule forensics
On this page
  1. Separate occurrence, effect and treatment
  2. Work a simple overlap carefully
  3. Build an evidence matrix
  4. Report uncertainty explicitly

Two events occurring at the same time do not, by themselves, establish concurrent delay to completion. A useful review identifies the affected work, the path to the relevant milestone and what each event did during the period under examination.

The contractual and legal treatment of concurrency varies. This guide organizes schedule evidence; it does not determine entitlement, compensation or a jurisdiction’s legal test. For published discussion, see the Society of Construction Law’s Delay and Disruption Protocol, read alongside the applicable project terms.

Separate occurrence, effect and treatment

Layer Question Evidence
Occurrence When was each event present? Notices, logs, correspondence and timestamps
Schedule effect Did each event affect work driving the same milestone? Updates, logic, actual progress and path analysis
Contract treatment What follows from the established facts? Applicable terms and project-specific professional review

Keep these layers distinct in the report. A bar chart showing overlapping dates answers only part of the first question.

Work a simple overlap carefully

In a fictional example, event A runs from day 3 to day 9 and event B from day 6 to day 12. Using half-open time intervals, their overlap is day 6 to day 9: three elapsed days.

01 / OCCURRENCESame time. Different question.

Next question: Did both events affect work driving the same completion milestone?

Illustrative elapsed-day timeline: event A occupies [3, 9), event B occupies [6, 12), and their overlap is [6, 9), or three elapsed days. Overlapping occurrence alone does not establish concurrent delay to completion.

That arithmetic does not establish three days of concurrent delay. Perhaps A affects the completion path while B affects work with available float. Perhaps they affect separate milestones. Perhaps B could not have progressed even without its event because another prerequisite was missing.

Build an evidence matrix

For each event record the description, affected activity IDs, start and end evidence, alleged cause, relevant milestone, path position and unresolved questions. Retain the update closest to the period and the records that support actual progress.

Check independence rather than assuming it. If one event is simply a consequence of the other, treating them as two separate causes can misdescribe the history. If both relate to the same work, explain the interaction rather than merely stacking two delay bars.

Report uncertainty explicitly

State what the files establish, what other records establish and what remains disputed. Label assumptions about event boundaries or progress. Explain whether a different assumption changes the period or the identified path effect.

Bring the evidence matrix to the people responsible for contract interpretation. A precise factual record helps them address the actual issue instead of debating an unexplained concurrency label.

Continue with method selection, float and the Schedule Forensics resource library.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file