What Is a Gantt Baseline in Production Scheduling?

A Gantt baseline is a saved snapshot of the Gantt chart at a reference date, such as project kickoff, kept so the current plan and actuals can be compared against what was originally promised. It is the frozen copy of the plan pinned to the wall, the version everyone agreed to, that stays put while the live schedule keeps moving. Weeks into the job, laying the current bars over the baseline bars shows at a glance how far each operation has drifted from its original dates. That comparison is the raw material of plan-versus-actual variance analysis.

This entry defines the Gantt baseline and shows how it behaves inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the chart it is captured from, read what is a timeline view mode in the Gantt.

How it works

A baseline is captured, not calculated. At a moment you choose to treat as the commitment point, the system stores the position of every bar on the chart: which job, which step, on which work center, from which start to which end. That stored set does not change afterward. As reschedules run and operators log actuals, the live bars shift, but the baseline bars remain exactly where they were saved.

The value comes from the overlay. Displaying the live schedule against the baseline turns an abstract sense of "we are behind" into a concrete, per-bar measurement: this step started two days late, that one finished a day early, this whole job has slid a week to the right. Because the reference is fixed, every drift is measured from the same yardstick, so the comparison is fair and repeatable rather than a moving target.

A baseline complements the per-row original dates that a schedule keeps automatically. Each schedule row remembers its own first-run start and end, which drives fine-grained variance for that step. The baseline works one level up, holding the whole chart at a chosen moment so a project or a group of jobs can be compared as a set. One is automatic and granular; the other is a deliberate, chart-wide reference.

A concrete example

Picture a project plan taped to the wall on day one of a build. Every task has a bar: foundation this week, framing next week, roof the week after. Someone photographs the wall on kickoff day. That photograph is the baseline.

Three weeks in, the real schedule looks different. The foundation ran long, so framing started late, so the roof bar has slid. The team holds the current chart up against the kickoff photograph. The framing bar is now two days to the right of where it was photographed; the roof bar has moved with it. Nobody has to argue about whether the job slipped, because the photograph shows exactly where each bar was promised to be, and the live chart shows where it actually is. The gap between them is the variance, visible bar by bar.

How EDGEBIC uses it

EDGEBIC lets you save a Gantt baseline as a reference snapshot of the schedule at a chosen date, then compare the evolving plan and logged actuals against it. Saving one is read-only: it captures the current bars without touching any planned or actual date, so the act of taking a baseline never disturbs the schedule it records. The live plan continues to change with every reschedule and every actual entry, while the baseline holds its ground.

On the chart, a comparison view overlays the current bars on the baseline so drift is visible where the work is planned, not buried in a report. This pairs naturally with the schedule's own original start and end dates, which each row preserves from its first scheduling run for per-step variance. Together they answer two scales of the same question: how has this step moved, and how has the whole plan moved, since we committed to it.

Because a baseline is tied to the reference date you pick, you decide what counts as the commitment. Most teams baseline at kickoff and leave it, adding a fresh snapshot only when the plan has been formally reset, since re-baselining resets the yardstick that variance is measured against. To see the actual dates that flow into the comparison, read what is an actual date in scheduling, and for the audit trail of every change between baselines, read what is a schedule change log. For the variance measure the overlay makes visible, see what is variance in manufacturing scheduling.