Baseline vs Target Schedule: Understanding the Difference

Two Terms, Different Purposes

In construction project management, "baseline" and "target" schedules are often used interchangeably — but they represent fundamentally different concepts with different purposes. Understanding the distinction is essential for effective schedule communication and control.

The Baseline Schedule

The baseline schedule is the official, approved, frozen version of the project schedule at the time of contract award or project authorization. It represents the original plan — the agreed-upon roadmap against which all future progress will be measured. Once approved, the baseline should not change except through formal change control processes.

Key characteristics of a baseline schedule:

• Contractually Significant: Usually referenced in the contract as the standard for time-related obligations.
• Approval Required: Typically requires formal owner approval before becoming effective.
• Preserved Intact: The baseline is preserved as-is for historical comparison throughout the project.
• Delay Analysis Reference: Used as the "planned" reference in forensic delay analysis and Extension of Time claims.
• Cost Integration: Often cost-loaded to align with the Schedule of Values and support earned value measurement.

The Target Schedule

A target schedule is an internal working version of the schedule that represents the team's current plan for completing the work. Unlike the baseline, the target can be updated as conditions change, priorities shift, or the team identifies opportunities to accelerate or adjust the sequence.

Key characteristics of a target schedule:

• Internal Tool: Used by the project team for planning and coordination, not necessarily shared with the owner.
• Flexible: Can be updated as project conditions evolve.
• Multiple Versions: A project may have several target schedules representing different scenarios or recovery plans.
• Not Contractual: Generally has no contractual standing unless specifically incorporated into contract documents.

Why Both Matter

In Primavera P6

Oracle Primavera P6 has native support for both concepts. The baseline is maintained as a separate schedule snapshot that can be attached to the current schedule for comparison. The active schedule functions as the "target" — it reflects the current plan and can be updated regularly.

In P6, you can have multiple baselines simultaneously. For example, you might have an Original Baseline (the approved contract schedule), a Current Baseline (the most recent approved change-order-adjusted schedule), and various Working Baselines (snapshots taken at different points for analysis).

Baseline Changes — When and How

The baseline should rarely change. The whole point of a baseline is to provide a stable reference for measuring progress. However, there are legitimate reasons to rebaseline:

• Major Scope Changes: A significant change order that adds or removes substantial scope may warrant a baseline adjustment to reflect the new contractual scope.
• Extended Delays: If a lengthy excusable delay occurs (e.g., force majeure, owner-caused delay extending many months), the baseline may need adjustment to remain meaningful.
• Contract Amendment: If the contract itself is amended with new terms, a new baseline reflecting the new terms is appropriate.

Rebaseline decisions should be made carefully and with owner concurrence. Frequent rebaselining destroys the baseline's value as a measurement tool and can look like an attempt to hide poor performance.

Common Confusion

"Our Baseline Is the Current Schedule"

If your "baseline" is updated every month to match the current schedule, it isn't a baseline — it's just a label on the current working schedule. Without a preserved reference point, you have no way to measure schedule performance.

"We Don't Need a Target; We Have the Baseline"

If your baseline and your working schedule are the same thing, you can't adjust the working plan without losing the baseline. You need both — a frozen baseline for measurement and a working schedule for management.

"Target Schedule Means Aspirational"

Some teams use "target" to mean a best-case, stretch goal that isn't realistic. That's not what we mean here. The target schedule should reflect the current realistic plan, not an aspirational one. Aspirational schedules create false expectations and undermine credibility.

Baseline in Delay Claims

The baseline plays a starring role in delay claims and forensic analysis. Methodologies like Time Impact Analysis and Impacted As-Planned rely on the baseline as the reference point for measuring delay impacts. A well-preserved, properly approved baseline strengthens claims; a changed or poorly documented baseline weakens them.

This is another reason why baseline integrity matters — the version you have at the end of the project may need to defend your claims against challenges from the owner or their consultants. Make sure you can produce the original approved baseline, not a rebaselined version.

Practical Workflow

Here is a practical workflow that maintains baseline integrity while providing working flexibility:

1. Develop and submit the baseline schedule for approval.
2. Upon approval, save the baseline as a protected copy in P6 (Project → Maintain Baselines).
3. Use the active schedule as your working target schedule — update it monthly to reflect actual progress and current plans.
4. Each month, compare the working schedule against the baseline to report variance.
5. If a rebaseline becomes necessary, document the reason thoroughly and obtain owner concurrence before replacing the baseline.

This workflow gives you the stability of a baseline for measurement and the flexibility of a target for management — both essential for effective project control.