Why the baseline is the foundation of every project
Every construction or capital project begins with a plan, and every plan is only as useful as the reference point it creates. In project scheduling, that reference point is the baseline. The baseline is the approved, locked snapshot of a project’s scope, schedule, and cost against which all future performance is measured. Without it, a project team has no defensible way to quantify progress, identify slippage, or evaluate the true impact of scope changes. With it, teams can track earned value, issue accurate progress reports, and engage owners, clients, and agencies with confidence.
Microsoft Project remains one of the most widely used scheduling tools across commercial construction, industrial facilities, and public-sector projects. Its baseline functionality is straightforward, yet it is frequently misunderstood or applied inconsistently. Many project managers set an initial baseline but then find themselves uncertain about how to handle scope growth, approved change orders, Management of Change events, or internally driven additions. Should new activities be folded into the existing baseline? Should a fresh baseline be created? How do you preserve the integrity of the original plan while also documenting the approved new scope? These are not trivial questions. Handled incorrectly, baseline updates can erase the historical record of a project and make it impossible to demonstrate what was planned versus what was executed.
This article addresses both of those challenges in detail. It walks through the step-by-step process of setting an initial baseline in MS Project, and then explains how to update that baseline selectively when a new scope is added to an existing schedule. It covers the schedule quality checks that should occur before any baseline is established, the mechanics of the “Set Baseline” feature, and the correct application of the “Selected Tasks” update method that keeps the original baseline intact while incorporating approved additions.
Beyond the mechanics, this article also places the topic in the broader context of project controls. CPM scheduling, baseline schedule development, and change management are interrelated disciplines. Understanding how they connect, and how professional project controls firms such as Leopard Project Controls apply these principles on federal, state, and private-sector projects, gives practitioners a more complete picture of what best-in-class scheduling practice looks like. Whether you are a project manager setting a baseline for the first time, a scheduler managing a live project through its first change order, or an owner trying to understand what your contractors are doing with their schedules, this guide provides the knowledge to act with precision.
The purpose of this article is to provide a documented mechanism for the process of baselining a start-up schedule in MS Project, as well as a guide on how to update the baseline for new internal scope added to an existing project that has already been baselined. Such examples include new scope arising from a Management of Change (MOC), Execution Variance (EXV), Missed in Bid (MIB), or an external change requested and approved by the client. Most importantly, this documentation explains how to create a new baseline for new activities and scope without altering the original approved plan.
It is imperative to carefully review the project schedule with all stakeholders and ensure that it meets scheduling and planning best practices, that all errors and inconsistencies have been resolved, and that the logic is sound before setting a baseline. Per solid project management practices, you should have only two open ends in a schedule: one missing predecessor for the first task (often a contract start milestone) and one missing successor for the final task (often a project close-out or completion milestone). Review the schedule for out-of-sequence activities, invalid relationships, and any resource or calendar inconsistencies. Logic integrity is non-negotiable at this stage. A baseline built on a flawed schedule will produce misleading variance data throughout the life of the project.
It is also recommended that you create a backup copy of the MS Project file prior to setting the baseline. A simple file copy with a date stamp in the filename is adequate. This protects the pre-baseline state in the event of an inadvertent change or software error.
The following snapshot contains an example of a schedule that has not yet been baselined:
Setting the initial baseline
With the assumption that the schedule is ready and has been reviewed, select the Project tab in the MS Project ribbon and click on “Set Baseline”:
MS Project allows you to set up to 11 baselines within a single project file, labeled Baseline through Baseline 10. For the initial approved plan, it is good practice to use the default “Baseline” slot. Reserve the numbered baselines (Baseline 1, Baseline 2, and so on) for subsequent re-baselines that may be required if the project scope or schedule undergoes major contract-level revision. Select “Baseline” from the dropdown and click OK.
Once this step is complete, the Baseline Duration, Baseline Start, and Baseline Finish columns are populated for every task and summary task in the schedule. On the Gantt chart, the blue task bars represent current planned duration while the lower gold bars represent the locked baseline. Any future movement in the blue bars will immediately reveal schedule variance relative to the gold baseline, giving the team a clear and continuous picture of performance.
At this point the baseline is established and the schedule is ready for progress tracking. Monthly or periodic updates will record actual start and finish dates, remaining durations, and percentage completions. The baseline remains locked in place, providing the fixed reference for earned value metrics such as the Schedule Performance Index (SPI) and Cost Performance Index (CPI), as well as for any variance reporting required by the owner or agency.
Adding new scope to an already-baselined schedule
On many projects, the scope defined at contract award is not the scope that gets built. Change orders, internally driven modifications, Management of Change events, and Missed in Bid items all introduce activities that did not exist in the original approved schedule. The question is not whether to add them but how to add them while preserving the original baseline record.In the event of a requirement to add new scope and activities to the MS Project schedule, navigate to the project schedule and right-click on the task in the sequence where the new tasks should be inserted. Select “Insert Task” from the context menu.
When two new tasks are added to the schedule, the duration and baseline duration fields default to MS Project settings, and the Baseline Start and Baseline Finish fields will default to “NA”. This is the expected and correct behavior. The “NA” designation tells you and any reviewer that these tasks did not exist in the original baseline, which is precisely the audit trail you want to maintain.
Fill in all relevant data fields: task names, durations, resources, constraint types, calendar assignments, and any special character or coding fields that your project or agency requires. Add the appropriate logic ties to connect the new tasks to predecessors and successors in the existing network. The schedule network should remain intact and continuous; do not leave the new tasks as disconnected activities floating outside the critical path logic.
Notice that the new tasks do not show a gold baseline bar, since they have not yet been baselined. Because the two new tasks are connected to the existing task “ObjectConv001_Creation of PAR01 Non-Live OL10 Section 01,” the blue plan bar for that task has shifted to the right, reflecting the additional duration downstream. The gold baseline bar for the original task remains locked in its original position. This is the visual representation of schedule variance, and it is the system working exactly as intended.
Highlight the two new tasks that need to be incorporated into the schedule baseline. Select the Project tab and navigate to the Set Baseline feature again:
Because this new scope is being incorporated into the existing approved baseline (rather than establishing a new contract-level baseline), use the existing “Baseline” in place. Select the “Selected tasks” option rather than the default “Entire project.” Also check the box for “To all summary tasks,” because the new tasks will roll up into their parent summary and that roll-up must reflect the updated scope.
MS Project will prompt you to confirm the overwrite of baseline data for the selected tasks. Select “Yes”:
The two new tasks are now part of the baseline. Their Baseline Start and Baseline Finish fields are populated, and the gold bars appear on the Gantt chart. All other tasks in the schedule retain their original baseline dates, preserving the complete history of the project’s approved plan.
To understand how a well-structured Baseline Schedule supports advanced planning and 4D integration, explore our in-depth guide.
Best practices for baseline change management
Setting and updating baselines is a process that should be governed by a written change management procedure, not left to the discretion of individual schedulers. The following practices help maintain the integrity of the baseline record across the life of a project.
All baseline updates should be traceable to an approved change document, whether that is a formal change order, an approved MOC form, a client-signed scope addition, or an internal EXV. The baseline should never be updated to reflect scope that has not yet been formally approved. Updating the baseline prematurely, in anticipation of an approval that may not materialize, is one of the most common errors in construction scheduling and one that can expose the contractor to significant claims risk.
Maintain a baseline change log that records the date of each update, the source change document, the tasks added or modified, and the net effect on project duration and critical path. This log is invaluable during delay analysis and claim preparation, because it provides a chronological record of every approved scope addition and its scheduling impact.
When the scale of the change is significant, consider whether the situation calls for a full re-baseline rather than a selective task update. A re-baseline may be appropriate when a major scope revision changes the fundamental character of the work, when the project completion date is contractually revised, or when the owner and contractor jointly agree to reset the measurement basis. In these cases, use one of the numbered baseline slots (Baseline 1, Baseline 2) to preserve the original baseline in the same file while establishing the new measurement basis.
For projects subject to agency oversight by USACE, NAVFAC, DOT, VA, or similar entities, confirm the agency’s specific requirements for baseline updates before making any changes. Many agency contracts have contractual provisions governing the frequency and content of schedule updates, the required narrative for baseline changes, and the approval process that must be followed before an updated baseline is formally accepted.
How Leopard Project Controls supports baseline scheduling and change management
Leopard Project Controls is a Florida-registered engineering company and certified general contractor with more than 20 years of CPM scheduling experience across federal, state, and private-sector construction projects. The firm specializes in baseline schedule development, progress update support, construction delay analysis, and owner’s representative services. Its schedulers hold credentials including PMP, PMI-SP, and PSP certifications and work directly in Primavera P6 and Microsoft Project, delivering native file formats (XER, XML, PDF) with no outsourcing.
For contractors who need an approved baseline schedule on a compressed timeline, Leopard offers a flat-fee baseline schedule development service with unlimited revisions until the schedule is accepted by the reviewing agency or owner. This model is particularly valuable on federal projects where USACE, NAVFAC, VA, DOT, MTA, and similar agencies apply strict formatting and logic requirements that frequently result in rejected schedules when the work is done by teams without agency-specific experience. Repeated rejections delay project mobilization, disrupt billing cycles, and create friction with owners that can persist for the duration of the contract. Leopard’s agency-compliance expertise is designed to eliminate that friction.
The change management and baseline update process described in this article is one area where professional project controls support pays a particularly clear dividend. Many construction firms have project managers who understand MS Project at a functional level but are less confident about the correct procedure for selective baseline updates, the documentation requirements for change-driven schedule revisions, or the difference between a baseline update and a re-baseline in the context of a contract claim. Leopard’s senior schedulers handle these decisions daily and can provide guidance or take over the scheduling function entirely, depending on the client’s needs.
Beyond the initial baseline, Leopard stays with projects through closeout. Its ongoing services include monthly progress updates, KPI dashboards and S-curves, recovery schedule development, Time Impact Analyses (TIAs), earned value reporting (SPI, CPI, EAC, cost variance), and Schedule of Values alignment for payment applications. This continuity matters because the baseline and its subsequent updates form the evidentiary backbone of any delay or acceleration claim. A project that has been carefully maintained with properly documented baseline changes is in a far stronger position than one where the schedule record is inconsistent or incomplete.
For owners and developers who need independent schedule oversight rather than contractor-side scheduling support, Leopard also provides owner’s scheduling consultant and owner’s representative services. These services give owners the independent perspective they need to evaluate contractor schedules objectively, identify unrealistic logic or inflated baselines, and maintain leverage throughout the construction process.Whether the project is a federal infrastructure contract, a commercial development, or a state-funded public works program, Leopard Project Controls brings the scheduling discipline, agency knowledge, and change management expertise that keeps projects on track from baseline to closeout. You can reach the team at consultleopard.com or by calling (833) 777-6276.
Treating the baseline as a living governance tool
The project schedule baseline is often described as a snapshot, which implies something static and fixed. That description is partially accurate. The original approved plan, once set, should remain locked in place as a permanent reference. But the baseline system in a well-managed project is dynamic in a different sense: it grows and updates in a controlled, documented way as approved scope changes are incorporated, while always preserving the historical record that makes variance measurement meaningful.
The two-part process described in this article, setting the initial baseline and then updating it selectively for new scope, reflects that duality. The initial baseline captures the project as it was planned and approved. Each subsequent update, tied to a specific change document and applied only to the tasks affected by that change, extends the baseline without corrupting it. The result is a scheduling record that can answer the questions that matter most on any construction project: what was the original plan, what changed and why, when did the changes occur, and what effect did they have on the completion date?
These questions become especially important when a project encounters delays. Delay analysis methods such as Time Impact Analysis, Windows Analysis, and As-Planned versus As-Built comparison all depend on a credible, well-maintained baseline. A scheduler who has kept careful records of every baseline update, with supporting change documentation, is in a position to conduct a rigorous and defensible delay analysis. A scheduler who has loosely updated the baseline without documentation, or who has re-baselined the schedule multiple times without preserving intermediate states, will find that analysis significantly more difficult.
The same principle applies to earned value management. EVM metrics are only as reliable as the baseline they measure against. An inflated or manipulated baseline produces SPI and CPI values that look acceptable on paper but bear no relationship to actual project performance. Owners and agencies who review these metrics know what to look for, and a schedule that cannot withstand scrutiny erodes the contractor’s credibility in ways that are hard to recover from.
Microsoft Project provides the tools to do this work correctly. The key is understanding how to use those tools with discipline: confirming schedule quality before setting the baseline, documenting the rationale for each update, applying changes only to approved scope, and maintaining the change log that connects every baseline modification to its source document. For teams working on federal, state, or other agency-regulated projects, layering in the specific contractual and formatting requirements of the relevant agency adds another dimension to this discipline, which is where experienced project controls professionals provide the most value.
Project success is rarely accidental. It is the product of planning, documentation, and the willingness to hold the plan accountable even as conditions change. The baseline is the instrument through which that accountability operates. Treat it with the care it deserves, and it will serve the project well from kickoff to closeout.
Questions and Answers
What is the difference between setting a baseline for the entire project versus setting it for selected tasks?
When you use the “Entire project” option in MS Project’s Set Baseline dialog, the tool captures baseline dates and durations for every task and summary task in the schedule at that moment. This is the correct approach when establishing the initial approved plan. The “Selected tasks” option, by contrast, updates baseline data only for the tasks you have highlighted before opening the dialog. This is the correct approach when incorporating approved scope additions into an existing baseline, because it leaves all original tasks untouched while adding the new tasks to the baseline record. Using “Entire project” when you only intend to update a few new tasks would overwrite the baseline dates of every task in the schedule with their current planned dates, effectively erasing the variance history the baseline was created to preserve.
How many baselines can MS Project hold, and when should numbered baselines be used?
MS Project supports up to 11 baselines in a single file: one labeled simply “Baseline” and ten labeled Baseline 1 through Baseline 10. The general recommendation is to use the primary “Baseline” slot for the initial contract-approved plan and reserve the numbered slots for significant re-baselines, such as those resulting from a major contract modification, an owner-directed acceleration, or a mutual agreement to reset the project’s measurement basis. Using a numbered slot rather than overwriting the original Baseline preserves all historical data in the same file, which is valuable for long-term project analysis and any downstream delay or claims work.
When is it appropriate to re-baseline an entire project rather than updating selected tasks?
A selective task update is appropriate when approved scope additions are incremental, well-defined, and do not fundamentally alter the project’s critical path or contractual completion date. A full re-baseline is more appropriate when a contract modification changes the project completion date, when the volume of changes is so large that the original baseline has lost its relevance as a measurement reference, or when the owner and contractor jointly agree to reset the schedule as part of a project recovery effort. On agency-regulated projects, the decision to re-baseline may also be governed by contract language or agency specifications, so it is important to consult those documents and, when necessary, to obtain written approval from the owner or agency before proceeding.
What documentation should accompany a baseline update to support future delay analysis or claims?
Every baseline update should be accompanied by at minimum the following: a reference to the approved change document (change order number, MOC form, EXV log entry, or client correspondence) that authorized the new scope; a brief narrative describing the nature of the change and the tasks affected; the date the update was applied; and the net effect on project duration and critical path, if any. This information is ideally captured in a baseline change log maintained alongside the schedule file. In addition, it is good practice to save a pre-update copy of the schedule file before applying the baseline change, so that the state of the schedule immediately before and after each update can be compared if needed during delay analysis.
How does Leopard Project Controls help contractors who are struggling with rejected baseline schedules on federal or state projects?
Leopard Project Controls offers a flat-fee baseline schedule development service that includes unlimited revisions until the schedule is accepted by the reviewing agency. The firm has direct experience with the formatting requirements, logic standards, and reviewer expectations of USACE, NAVFAC, VA, DOT, MTA, JEA, and other agencies. Schedules are delivered in native Primavera P6 (XER) or MS Project (XML) formats along with reviewer-ready PDFs and a schedule narrative. Because Leopard’s senior schedulers have built and resubmitted hundreds of agency-compliant schedules, they anticipate the specific issues that trigger rejections and address them in the initial draft, reducing or eliminating the resubmission cycle that costs contractors time and credibility. More information is available at baseline schedule development.
