Baseline, schedule update and lookahead: keep three views connected

Keep the approved baseline, current progress update and crew lookahead distinct. Trace an access or procurement change through all three planning views.

Guide4 min read

Published

Tower crane against an overcast sky

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Give each view a distinct job
  2. Follow one access restriction through the three views
  3. Keep a decision register beside the update
  4. Reconcile the schedule with the estimate

For a GC managing an occupied commercial project, use three connected schedule views: preserve the approved baseline as the reference, update the project schedule with actual progress and a forecast, and use a short lookahead to secure the conditions crews need. When access changes, record the effect in each view and assign someone to resolve it. Do not overwrite the original approval to make the forecast look current.

The decision for the preconstruction leader is whether a changed work window still supports the estimate and trade commitments. A schedule date alone cannot answer that: compare access, delivery, crew availability and any repeat setup against the assumptions carried at bid.

Give each view a distinct job

An approved baseline is the accepted schedule reference against which the team can compare subsequent progress and changes. A progress update records actual work through a stated data date and forecasts remaining work using the current logic and assumptions. A lookahead translates the near-term portion into specific work, constraints and commitments for the people who must perform it. Its horizon should suit the project and procurement lead times; a two-week crew view may need a separate longer procurement view.

Terminology and approval procedures depend on the contract. For example, the basic GSA schedule clause, when included and applicable, calls for weekly updates unless another interval is specified and requires a written explanation of revisions after initial approval. Its alternate and other contract provisions may differ. A lookahead is a field coordination tool in this guide, not a representation that this clause mandates a particular lookahead period.

Follow one access restriction through the three views

Consider an illustrative occupied-facility renovation. The approved baseline shows equipment delivery on April 8, installation April 9–12 and turnover April 15. It assumes daytime loading-dock access and one continuous installation period. The current update has a March 25 data date. The owner has advised that the dock will be unavailable during the day on April 8 and 9; a night delivery window is proposed but not yet approved. The supplier still needs a confirmed receiving window.

ViewWhat it showsWhat the team does
Approved baselineApril 8 delivery and April 9–12 installation with daytime accessRetain the original approved file and its approval record
Current updateActual status through March 25 and a forecast showing the access constraint and resulting datesScheduler models a supported delivery and installation sequence and identifies milestone effects
Two-week lookaheadNight delivery request, dock clearance, receiving labor and installation start are pending confirmationSuperintendent assigns owners and deadlines before releasing crews

Suppose the scheduler's provisional logic moves delivery to the night of April 10, installation to April 11–14 and turnover to April 16. The update is a forecast, not proof that the owner has approved a new contractual completion date. The superintendent asks the owner representative to confirm the dock window by March 29; the procurement lead asks the supplier to hold the April 10 slot until March 30; the mechanical subcontractor confirms receiving labor and installation availability by April 1. If the night window is declined, the scheduler tests another delivery sequence and the estimator prices its consequences before a commitment.

A one-day forecast turnover movement does not by itself establish entitlement, critical-path impact or a price change. Check the schedule logic, calendars, float, contractual milestones and concurrent constraints. The project team must also determine whether a formal revision, notice or change request is required under its own contract.

Keep a decision register beside the update

ItemOwner and due dateStatus and next decisionEstimate or schedule effect
Dock access April 10 at nightOwner representative; March 29Pending written confirmationIf rejected, model another delivery date
Supplier delivery slotProcurement lead; March 30Hold requested, not confirmedCheck storage and redelivery exposure
Receiving and installation crewMechanical subcontractor; April 1Availability and night premium to be quotedCompare quote with original daytime carry
Turnover milestoneScheduler and PM; next updateForecast April 16; contractual status unresolvedCheck logic and any notice or approval route

The register should point to the update version, correspondence and affected activity IDs. Record the decision date and authorization as well as the person responsible. When a constraint is cleared, record the evidence and revise the lookahead; if it remains open, escalate before the crew or supplier must commit. The PM decides the project's contractual response with the appropriate commercial team, rather than treating a field promise as an approved change.

Reconcile the schedule with the estimate

Compare the night delivery quote, any additional supervision, temporary protection and repeated mobilization with the original carry. Avoid pricing the same receiving crew in both the subcontractor proposal and the GC's general conditions. The related guide explains how to price phased work and handoffs and test procurement assumptions against the work sequence.

Keep the original approved baseline and its assumptions accessible even if the contract later permits a revised baseline. Identify the revised file, approval, effective date and reason separately. Archive each statused update and its narrative so the team can reconstruct what was known at each data date. This is a practical recordkeeping method; the contract controls the formal submission and approval process.

FAQ

Does a schedule update replace the baseline?

A progress update is the current status and forecast, while the approved baseline is the comparison reference. Retain the original approval and follow the contract's process if a revised baseline is authorized.

Can a crew lookahead change the completion date?

It can expose a constraint that changes the forecast, but the scheduler should test the effect in the linked project schedule. A lookahead commitment alone does not amend a contractual milestone.

A short lookahead can expose different operating releases behind one completion milestone. The GRB South garage turnover case separates event parking already open from broader access that depends on adjacent work and peak valet overflow that depends on the tunnel.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.