Construction Schedule Control: Critical Path & Recovery
A practical guide to construction schedule control: baselines, logic, data dates, critical paths, float, updates, delay signals, and recovery plans.
A construction schedule is a model of how scope is expected to move through time. Schedule control maintains that model, records actual performance, forecasts the remaining work, and tests whether corrective action can protect contractual milestones.
The schedule is not controlled because it is updated monthly. It is controlled when the update produces an honest forecast and a decision.
What a credible schedule contains
A control schedule should include:
- Complete project scope
- Logical relationships
- Realistic durations and calendars
- Contract and internal milestones
- Procurement and submittals
- Owner and design decisions
- Testing, commissioning, and closeout
- A defined status or data date
- Actual starts and finishes
- Remaining durations
- Critical and near-critical paths
- Constraints and assumptions
The GAO Schedule Assessment Guide presents ten practices for a reliable schedule, including capturing all activities, sequencing work, assigning resources, establishing durations, confirming horizontal and vertical traceability, conducting schedule risk analysis, updating actual progress, maintaining a baseline, and correcting logic problems.
Commercial contractors may apply these principles proportionately without adopting a federal audit framework.
Baseline, update, forecast, and scenario
| Schedule view | Meaning |
|---|---|
| Original baseline | Initially approved time plan |
| Current approved baseline | Plan revised by authorized change |
| Current update | Actual progress and remaining logic through the data date |
| Forecast | Expected dates based on current update |
| What-if scenario | Proposed alternative not yet approved |
Do not overwrite actual history to make the schedule appear aligned. Do not present a recovery scenario as the current forecast before resources and authority exist.
Logic is the operating model
Dates without logic create a calendar, not a schedule.
Relationships should reflect how work can actually proceed:
- Design approval before release
- Release before fabrication
- Fabrication before delivery
- Area readiness before installation
- Installation before testing
- Testing before acceptance
Common logic problems include:
- Open-ended activities
- Excessive date constraints
- Long unexplained lags
- Out-of-sequence progress
- Missing procurement interfaces
- Summary activities used as logic
- Artificial relationships inserted to force a desired date
The goal is not a “clean” schedule. It is a model that reacts credibly when actual conditions change.
Critical path
The critical path is the controlling sequence that determines a defined completion or milestone under the current logic.
It can change when:
- Progress differs from plan
- Remaining durations change
- Logic changes
- Calendars or constraints change
- A new procurement or design condition appears
The critical path should be reviewed as a narrative:
- What work currently controls completion?
- Why is it controlling?
- What changed since the last update?
- What decisions or resources could alter it?
- Which party owns the controlling work?
Float
Total float represents the amount an activity may move before affecting a defined completion or constraint, subject to schedule configuration.
Float is not a physical reserve. It is an output of the model.
Monitor:
- Negative float
- Declining near-critical float
- Large positive float suggesting weak logic
- Changes driven by constraints rather than work
- Float paths feeding contract milestones
Near-critical work matters because a project can have several paths close to becoming controlling.
The data date
The data date separates actual history from future forecast.
Every update should answer:
- What started?
- What finished?
- What is physically complete?
- What remains?
- What changed in duration?
- What is out of sequence?
- What new constraint exists?
Mixing information from different cutoff dates makes cost and schedule comparison unreliable.
Procurement and submittal control
Procurement should be modeled backward from need date:
- Installation or use
- Delivery
- Fabrication
- Release
- Submittal approval
- Submittal preparation
- Award or design information
Late submittals are not merely document metrics. They are schedule risks when they affect release or delivery.
Schedule recovery
A recovery plan is credible only when it identifies:
- Specific affected activities
- Revised logic or sequence
- Additional labor, shifts, equipment, or supervision
- Required access and predecessor conditions
- Incremental cost
- Safety and quality effects
- Authority and responsible parties
- Expected time benefit
- Measurement dates
Common recovery strategies include resequencing, work-area release, additional crews, overtime, prefabrication, alternate procurement, partial turnover, and removing decision constraints.
The cheapest recovery plan may not protect the milestone. The fastest may destroy margin or increase safety risk. Compare cost, time benefit, feasibility, and residual risk.
Schedule and cost integration
Schedule change should inform:
- General conditions and supervision
- Equipment and temporary facilities
- Procurement cash flow
- Billing milestones
- Labor productivity assumptions
- Owner and subcontract changes
- Liquidated-damage or incentive exposure
If the schedule extends but duration-sensitive cost does not, the forecast is incomplete.
Schedule-control reporting
A decision-ready update includes:
- Data date
- Contract milestone forecast
- Critical and near-critical paths
- Milestone variance from baseline and prior update
- Procurement and design constraints
- Out-of-sequence or logic concerns
- Recovery actions and owners
- Cost and change relationships
- Decisions required by date
Syntecton’s schedule-control direction
Syntecton connects schedule, tasks, milestones, risks, RFIs, submittals, changes, meetings, and financial workflows. The objective is to prevent schedule information from becoming an isolated specialist report.
A late decision should become a responsible action. A critical procurement issue should reach the risk and commercial view. A recovery plan should carry resources, cost, authority, and evidence.
Frequently asked questions
What is construction schedule control?
It is the process of maintaining the approved time plan, recording actual progress, analyzing logic and critical paths, forecasting future dates, and directing corrective action.
Is the critical path fixed?
No. It can change as progress, remaining durations, logic, calendars, and constraints change.
Is float owned by a contractor or owner?
Float ownership can be a contractual issue. The schedule calculation alone does not resolve entitlement.
What makes a recovery schedule credible?
Defined activities, resources, access, cost, authority, time benefit, responsibility, and a method to measure results.