---
title: 'Construction CPM schedules: test the logic behind the completion date'
url: 'https://piper-ai.com/resources/construction-cpm-schedule-baseline-review'
description: 'Review a CPM schedule''s logic, constraints and procurement assumptions before committing a bid. Test which sequence controls the proposed completion milestone.'
contentTypes: [guide]
publishedAt: '2026-11-18T11:28:31.790Z'
updatedAt: '2026-11-19T09:43:35.021Z'
author: 'Ido Gedanken, CEO'
readingTime: 3
---

# Construction CPM schedules: test the logic behind the completion date

A critical path method (CPM) schedule models activities, durations and their logical relationships to calculate paths through the work. The preconstruction decision is whether the dates can be achieved with the assumed procurement, access and work windows, not whether a bar reaches the owner's deadline. The [FHWA guide to contract time](https://www.fhwa.dot.gov/construction/contracts/t508015.cfm) describes critical-path and bar-chart approaches in its highway context; the project schedule specification governs the actual submission.

A baseline is the agreed reference schedule as defined by the project; subsequent updates record progress and revised forecasts. Review the native logic, calendars, constraints and status dates with the scheduler. A polished PDF alone may conceal an omitted predecessor or a constraint that holds a milestone in place.

## Follow the equipment to turnover

Trace design release to submittal, approval, fabrication, delivery, installation, power, startup, integrated testing and acceptance. Check each duration with the responsible party and identify the source of the assumption. A supplier quote that starts fabrication after approved submittals cannot support a schedule that starts fabrication at bid day without explanation.

Test owner access, available shifts, shutdown windows and required inspections. Ask whether activities have missing predecessors or successors and whether constraints or calendars produce misleading float. [Price phasing and handoffs](https://piper-ai.com/resources/preconstruction-phasing-estimate-review) where the sequence requires temporary facilities, repeat mobilization or premium shifts.

## Test a path change

In this illustrative simplified network, two independent paths start on day zero and converge at a day-100 completion requirement. The equipment path takes 90 working days: submittal 10, fabrication 45, delivery 5, installation 20 and commissioning 10. A parallel interior path takes 95 working days. Assume one common calendar, finish-to-start links, no other constraints and a day-100 required finish.

| Path | Initial duration | Initial illustrative float to day 100 | After 8-day fabrication increase |
| --- | --- | --- | --- |
| Equipment | 90 days | 10 days | 98 days, 2 days float |
| Interior | 95 days | 5 days | 95 days, 5 days float |

The equipment path becomes the longer controlling path at 98 days, while the modeled completion still meets day 100. Its float falls from 10 to two days under these simplified assumptions. A further three-day increase would produce a day-101 forecast, one day beyond the requirement, if nothing else changes. This arithmetic does not decide contractual ownership of float or entitlement to an extension.

## Record the assumptions that can move the date

Maintain a schedule review register with activity ID, source of duration, predecessor, calendar, constraint, responsible party, evidence and decision date. Ask for a revised run when a material assumption changes, retaining the previous version and reason for change. Escalate unresolved access or procurement assumptions with both schedule and estimate consequences, rather than hiding them in a single contingency.

Review the milestone terms against the latest bid addendum before accepting the dates in a schedule. In [TxDOT’s I-10 White Oak Bayou bid package](https://piper-ai.com/resources/txdot-i10-white-oak-girder-bid-code-reconciliation), Addendum 2 changed an interim traffic-switch window from 10 to 11 calendar days. Addendum 3 retained that window and corrected girder pay codes elsewhere in the package.
