5.7 Control Schedules, Variance Analysis, Forecasts, and Management Summaries
Key Takeaways
Control-level schedules provide enough integrated detail to measure progress, calculate paths, forecast milestones, and manage interfaces.
Variance and trend analysis compares baseline, prior forecast, current forecast, and actual performance without confusing value variance with time delay.
Schedule analysis should explain causal paths, constraints, resources, changes, risks, and constructability—not only list late activities.
Progress reports and management summaries must be traceable, decision-focused, and tailored to the recipient while preserving one source model.
5.7 Control Schedules, Variance Analysis, Forecasts, and Management Summaries
A control schedule is the integrated logic model used to baseline, status, analyze, and forecast the project. It is detailed enough to manage scope and interfaces but not so detailed that status and logic become unmaintainable.
Control-level outputs
The schedule should support:
- contractual and internal milestones;
- critical and near-critical path review;
- work-package progress and remaining duration;
- procurement, owner, regulator, and contractor interfaces;
- resource and cost time-phasing where required;
- change and recovery analysis; and
- rollups to executive and near-term views.
Variances and trends
Compare the right references:
| Comparison | Question answered |
|---|---|
| Actual vs baseline | What performance deviation has occurred? |
| Current forecast vs baseline | What commitment variance is expected? |
| Current vs prior forecast | Is the outlook improving or deteriorating? |
| Actual productivity vs estimate | Are remaining assumptions credible? |
| Float/path trend | Is schedule flexibility eroding or shifting? |
A negative earned-value schedule variance is denominated in value, not days. Use CPM dates or time-based methods for delivery-date conclusions.
Schedule analysis
A useful analysis explains why dates moved. Review:
- progress and remaining-duration changes;
- logic, calendar, constraint, and lag changes;
- critical-path migration and parallel paths;
- resource availability and productivity;
- approved and pending changes;
- risk events and mitigation;
- out-of-sequence work; and
- constructability of the remaining plan.
Do not infer causation from an activity’s lateness alone. An activity can be late but noncritical, or on time while a successor interface controls completion.
Forecasts
Forecast major milestones from the current network and state key assumptions. Provide ranges or risk-informed dates when uncertainty matters. Compare independent trend forecasts with the CPM result as a reasonableness check, not a substitute for logic.
If a recovery plan exists, show baseline, current forecast, and recovery target separately. Report whether committed resources and production are materializing.
Constructability review during control
Field conditions change. Periodically confirm access, workfront sequence, temporary works, trade congestion, permits, inspections, commissioning boundaries, and turnover strategy. Update the working logic through control procedures when the actual plan changes.
Progress report
A detailed report may include:
- data date and reporting period;
- milestone table with baseline, prior, current, and variance;
- critical and near-critical path narrative;
- progress quantities and productivity;
- lookahead and readiness constraints;
- change and risk status;
- resource or cost highlights;
- recovery actions and decisions needed; and
- schedule-quality exceptions.
Management summary
Executives need decision-relevant synthesis:
- current completion forecast and variance;
- primary causal path or risk;
- material change since the prior report;
- consequence if no action is taken;
- alternatives and recommendation; and
- decision owner and required date.
The summary should trace to the control schedule. Avoid manually maintained dates that cannot be reproduced.
Example
The baseline completion is 30 November, the prior forecast 10 December, and the current forecast 18 December. The report should say the outlook deteriorated eight days this period and eighteen days versus baseline, then identify the driving path and changes. Listing “18 days late” without distinguishing these comparisons loses important trend information.
Schedule outputs are valuable when they convert a maintained network into clear decisions for each audience while preserving technical traceability.
Applied review: turn schedule data into decisions
Control-level schedules contain enough detail to assign responsibility, measure progress, analyze drivers, and forecast milestones. Status them to a common data date using agreed rules. Variance is the difference between comparable values—such as current forecast versus baseline milestone—not an explanation. Trend records how that difference changes over time. Analysis identifies the activities, logic, production, decisions, resources, or risks causing the movement.
Forecasts should use current remaining work and transparent assumptions. A deterministic date may be appropriate for routine control, while a range or quantified risk result may better communicate material uncertainty. Do not hide a worsening forecast by moving the reference. If an approved change establishes a revised baseline, preserve the old reference and authorization so users can understand both performance and change.
Reports should match the audience while reconciling to the same controlled schedule. Include data date, status basis, key milestone variances and trends, driving paths, material changes, risks and opportunities, decisions needed, recovery actions, and responsible owners. A management summary is concise, but concision does not mean removing adverse facts. Test every statement against schedule evidence and explain limitations. In exam scenarios, select the output that enables a defined decision and distinguishes observation, cause, forecast, and recommended action.
Current forecast moved from 10 December last month to 18 December this month. What is the forecast trend?
Eight days of deterioration during the period
Eighteen days of improvement
No change because the baseline is unknown
Eight days of earned value
What belongs in an executive management summary?
Every activity in the native schedule
Forecast, variance, causal path, consequence, alternatives, recommendation, and decision needed
Only a percent-complete value
Only the original baseline date
Sections you finish are checked off in the contents.