Schedule Baseline: How to Measure Real Progress

What is a schedule baseline and why does every project need one?

A schedule baseline is a snapshot of your original approved plan — every task, its planned start and finish dates, and the dependencies between them — saved before any work begins. From the moment the first shovel breaks ground, actual progress creates a second set of dates alongside it. The gap between where your plan says you should be and where your crew has actually reached is your schedule variance. Without a fixed baseline to measure against, a project manager who shifts dates after every setback is not managing a schedule — they are rewriting history each week, and no one can see how far the project has drifted from what was originally promised.

Planning a project and setting the baseline are two different acts

This distinction catches contractors out. A plan is a working document: you adjust it while estimating, scoping, and sequencing tasks. The moment the owner signs off and work is about to begin, that plan is locked into a baseline. Everything that changes after that is actual progress or a formal revision — but the baseline stays frozen so the comparison remains honest. Contractors who keep updating the plan to match reality lose the most valuable thing a schedule gives them: early warning. When the plan always agrees with reality, it cannot tell you that reality is going wrong.

A worked example: Khun Siriporn's 3-storey office fit-out in Chiang Mai

Khun Siriporn was managing a 3-storey office fit-out in Chiang Mai for 2.8 million baht over 36 weeks. She locked her Gantt baseline at contract signing: partition walls in week 4, MEP first fix by week 10, ceiling grid by week 14, and handover at week 36. By week 8 the MEP first fix was sitting at 40 percent instead of the planned 75 percent because the electrical conduit supplier delivered the wrong specification. Comparing actual to baseline, she saw immediately that she was 4.5 weeks behind on the MEP chain, which would push ceiling grid and handover if nothing changed. That number — baseline versus actual, not a gut feeling — let her negotiate accelerated delivery with the supplier and add one electrician for three weeks, recovering 3 weeks of the gap before the ceiling grid phase.

What does schedule variance actually measure?

Schedule variance is the distance between your baseline milestone date and your current forecast for that same milestone, measured in days or weeks. If your baseline says the roof structure completes on day 60 and current progress tracking shows it will complete on day 68, your variance is minus eight days. Negative means behind; positive means ahead. The number itself is useful, but the trend matters more. A variance that is stable — minus eight days for three weeks running — is a project drifting steadily behind. A variance that is shrinking — from minus ten to minus eight to minus five — is a team recovering, and knowing the trend lets you decide whether to keep accelerating or ease off.

How do you read a baseline gap before it becomes a crisis?

The answer is momentum. A gap of two weeks on a 40-week project is not a crisis in week 5; it could well be in week 30. What you watch is whether the gap is growing, stable, or shrinking, and whether the tasks still ahead carry enough float to absorb it. When a slip in an early task has consumed all the float in the tasks behind it, the variance has effectively become a fixed delay. Catching a growing gap in week 6 while the schedule still has buffer means you have options: resequence, add resource, or compress a later task. Catching the same size gap in week 28 means you are renegotiating the handover date.

When should you revise the baseline versus preserving it?

This is the question that separates disciplined project management from schedule chaos. Revise the baseline only when scope has formally changed: the owner has added work in writing, a variation has been documented, or an event outside your control — a permit authority delay, a restricted site-access period — has been formally recorded. A task running long because the crew was short-staffed is not a reason to revise the baseline; it is a variance you manage and recover. Revising the baseline whenever reality diverges from the plan gives you a schedule that always looks on time and a project nobody can actually steer.

How on-site progress updates keep the comparison honest

A baseline is only valuable when the actual progress compared against it is reported truthfully and often. The weak link in most construction schedules is that progress numbers are estimated in the office once a week rather than reported from the field daily. When a foreman updates task percentage from the site using on-site progress updates — even a simple ten-percent increment and one photo — the variance calculation draws from what is actually happening on the ground, not from what someone thinks is happening. That difference in data quality is what separates a baseline the team trusts from one that gets ignored by the third week. SiteBoard is built around that link: field updates flow directly into the Gantt planning view, so the gap between baseline and actual always reflects real site data.

Using the baseline in owner conversations

A baseline-driven update is the most credible kind of owner conversation you can have. Instead of saying "we are a bit behind," you say: "We are 6 days behind on the MEP chain, the cause was a supplier delivery error, and we have recovered 3 of those days this week." That sentence is built entirely from variance data, and it tells the owner three things at once: the size of the problem, the reason, and your response. Owners who receive that level of clarity rarely escalate. Sharing the Gantt through the owner sharing link means they can follow the trend themselves, which makes every conversation shorter and more productive.

FAQ: Should I reset the baseline when scope changes?

Yes — but only when scope changes are formally agreed and documented. A written variation order signed by the owner is the right trigger. Include the changed tasks and their new dates, record the reason for the revision, and keep the original baseline so you can show the delta between the original promise and the revised one. Never reset the baseline to cover up slippage. Owners and auditors who review the schedule history will see the pattern, and it will undermine any delay claim you may need to file later.

FAQ: How often should I review baseline variance?

Weekly is the minimum for most projects. Check variance on your three most critical milestones at the start of each week before the Monday morning meeting. If any milestone is more than one week behind baseline, identify the responsible task, name who owns the recovery, and set a deadline for the first action. For fast-moving projects or projects already behind, check every two to three days. The more frequently you compare actual to baseline, the smaller the gap is when you find it — and smaller gaps are always cheaper to close.