Baseline versus current schedule: what subcontractors should track

Define three different kinds of date

A baseline is a saved reference at an agreed point in time. An actual date records what happened. A current forecast is the best estimate for unfinished work. Keeping these separate lets a PM explain a change without forcing the field team to work from an obsolete plan.

For example, a drawing approval baseline may be March 1, the actual approval March 12, and the current delivery forecast April 25. These dates answer different questions. A single overwritten cell cannot answer all three.

• Save a baseline when the initial plan is reviewed.
• Record actual starts and finishes as they happen.
• Use one current forecast for execution.

Choose what to compare

Track the milestones that matter to your trade and the handoffs that explain movement. A day-by-day comparison of every minor task can overwhelm the team. Compare approved drawings, purchase release, production start, delivery, and installation by area where those dates govern the work.

A variance is a prompt to investigate, not a verdict. The baseline may have relied on assumptions that were never confirmed. Note the event, source, and effect before assigning responsibility.

• Compare meaningful milestones, not every administrative task.
• Keep notes on original assumptions.
• Separate cause from the visible date variance.

Use the current plan to manage work

The current schedule should incorporate accepted changes, actual progress, and feasible recovery actions. It should be dated and distributed to the people using it. If an option is still awaiting approval, label it as a scenario rather than mixing it into the committed forecast.

On a complex job, several revisions may exist. Name the current version and archive superseded ones. Ask the shop, field, and GC which plan they are looking at when their dates differ.

• Date every issue of the current schedule.
• Mark scenarios as conditional.
• Retire outdated versions from active circulation.

Worked example

A concrete subcontractor planned to pour Area B on June 10. Actual formwork completion occurs June 13 after an access issue, and the current pour forecast is June 17 subject to inspection. The baseline remains June 10, the formwork actual is June 13, and the pour forecast is June 17. No one should report June 17 as an actual pour.

The weekly report can explain the change and the pending inspection while the field works from the current sequence. This preserves accountability without sacrificing a usable plan.

• Do not overwrite a baseline to make variance disappear.
• Do not describe a conditional forecast as an accomplished event.

Explain variance without rewriting history

A baseline comparison becomes credible when the original assumptions are visible. If the initial plan assumed access on June 1 and access was later granted June 8, record both the assumption and the actual event. The schedule can then show the effect without quietly changing the original date.

Avoid treating every variance as a delay to the finish. Some tasks had float; others can be resequenced. Compare the milestone forecast as well as the intermediate activity. If a recovery action has been accepted, show its resources and cost assumptions so the current forecast remains believable.

The field team usually needs the current plan first. A variance report can sit beside it for the PM and GC, but it should not force crews to interpret three dates on every line. Keep the working view simple and the audit trail available.

Version check

Before sending an update, verify that the dates and labels tell one coherent story. A baseline comparison is only useful when the current execution plan is credible.

• When was the baseline saved?
• Which dates are actual?
• Which forecast is current?
• What decision or event explains the variance?
• Who has received the revised plan?

Common questions