Concurrent Delay: Who Pays When Both Parties Are at Fault?

Sarwar Toor

Principal Consultant

A construction schedule is only as good as its baseline. If the foundation is flawed, every update, forecast, and delay analysis that follows will be compromised. In my 30 years of reviewing Primavera P6 schedules for mega-projects like the Panama Canal and nuclear power plants, I consistently see the same logic errors repeated.

These errors don’t just mess up the dates—they expose the contractor to massive liability when claims arise. Here are the five most critical errors to avoid.

1. Open Ends (Missing Logic)

Every activity in a schedule (except the Project Start and Project Finish) must have at least one predecessor and one successor. “Open ends” disrupt the critical path calculation.

  • The Risk: If an activity has no successor, delaying it won’t push the project end date in the software, masking the true impact of delays.
  • The Fix: Run a logic report and ensure all activities are tied into the network.

2. Excessive Use of Lags

Lags are often used as a lazy way to create buffers or force dates. For example, putting a “Start-to-Start + 10 day lag” instead of modeling the actual workflow.

“Lags are invisible scope. They represent time where no work is defined but the schedule is consuming duration. In a forensic analysis, unexplained lags are the first thing we attack.”

Instead of a lag, insert a tangible activity like “Concrete Cure Time” or “Submittal Review” so the time is accounted for transparency.

3. Constraints Abuse

Using “Must Finish By” or “Start No Earlier Than” constraints hard-codes dates into P6, overriding the logic network. While sometimes necessary for contractual milestones, overuse freezes the schedule dynamic.

If you overuse constraints, the schedule stops reacting to progress updates, rendering the critical path meaningless.

4. Improper Calendar Assignments

Assigning a 7-day calendar to tasks that can only happen 5 days a week (or vice versa) creates artificial float. We often see “Cure Time” on a 5-day calendar (concrete cures on weekends too!) or “Government Review” on a 7-day calendar.

5. Lack of Resource Loading

A schedule might look logically sound, but if it requires 500 pipefitters in Month 3 and you only have access to 200, the baseline is a fantasy. Resource leveling is the final sanity check that many planners skip.

Conclusion

Building a defensible baseline takes more than just connecting boxes in software. It requires understanding the construction means and methods. By avoiding these five errors, you protect your company’s interests and ensure your schedule is a useful management tool, not just a wall decoration.

Share this article:

Facebook
Twitter
LinkedIn

Need Schedule Support?

Don’t let a bad baseline cost you millions. Our forensic team can audit your P6 schedule today.

Tags