If you do not baseline the project, you are not really managing it

lorenaflorian0
6 hours ago
10 min read

One of the most common weaknesses in project delivery is not the absence of activity. Most projects are full of activity. Teams are busy. Meetings are held. Reports are produced. Actions are tracked. Risks are discussed and progress is described.

The problem is that activity is too often confused with control. A project is only under control when progress can be measured against an agreed baseline. Without a baseline, project reporting becomes subjective. The project may feel busy, but leaders cannot reliably answer the most important questions:

Are we ahead or behind schedule?
Are we over or under budget?
Are we delivering the scope we committed to?
Are we using resources efficiently?
Are we forecasting the likely outcome honestly?
Are we making decisions early enough to protect value?

A baseline is the reference point that allows these questions to be answered with evidence. At its simplest, a project baseline captures the approved scope, schedule and cost position at a point in time. It defines what has been agreed, when it should be delivered, what it should cost and what success looks like. Once approved, it becomes the benchmark against which performance is measured.

Without that benchmark, project reporting becomes vulnerable to optimism, opinion and selective storytelling. This is why baselining is not an administrative exercise. It is a governance discipline.

The uncomfortable truth is that many projects do not fail because the team is not working hard enough. They fail because leaders do not have a reliable view of what is really happening until it is too late to intervene effectively. This is where baselining, scheduling discipline and earned value analysis become essential.

The baseline Is the foundation of project control

A good baseline creates transparency. It enables the project manager, sponsor, steering committee and delivery team to see whether the project is progressing as planned. It also protects decision-making.

If a project is slipping, the baseline helps identify the variance. If costs are increasing, the baseline helps quantify the impact. If scope is changing, the baseline helps distinguish approved change from uncontrolled drift. This matters because many projects do not fail suddenly. They drift gradually.

A week of slippage becomes a month. A small change becomes a new deliverable. A minor cost increase becomes a funding issue. A delayed dependency becomes a critical path problem. By the time the organisation recognises the scale of the issue, the project may already have lost the ability to recover without significant intervention. Baselining helps make drift visible early by allowing leaders to move from anecdotal confidence to evidence-based control.

Scheduling tools Are not optional for serious delivery

For small pieces of work, a simple action list may be enough. But for projects with multiple workstreams, dependencies, milestones, resources and deadlines, proper scheduling tools become essential.

Tools such as Microsoft Project allow teams to build an integrated schedule, define dependencies, allocate resources, establish milestones, identify the critical path and track progress against an approved baseline.

This is important because projects are systems. Activities do not exist in isolation. A delay in one task can affect another. A late dependency can change the critical path. A resource constraint can undermine a milestone. A change in sequencing can alter the entire delivery forecast. A well-constructed schedule helps make these relationships visible and Microsoft Project and similar scheduling tools allow project teams to do more than record dates. They support active management by enabling the project manager to:

Capture the approved baseline
Track actual start and finish dates
Record percentage complete
Monitor slippage against planned dates
Assess critical path impacts
Identify resource over-allocation
Forecast revised completion dates
Report progress in a structured and defensible way.

The value is not in the software itself. The value is in the discipline the software enables. A schedule that is not maintained is just a document because a schedule that is actively managed becomes a decision-making tool.

How to baseline a project in microsoft project

Baselining in Microsoft Project should occur once the scope, schedule, resources, costs and key assumptions have been reviewed and approved. It should not be done too early, when the plan is still immature, and it should not be delayed until after delivery has already started.

Before setting the baseline, the project manager should ensure that:

The work breakdown structure is complete enough for delivery control
Tasks are logically sequenced
Dependencies are included
Durations are realistic
Milestones are clearly defined
Resources are assigned where appropriate
Costs are included or linked to the project budget
The critical path has been reviewed
Assumptions and constraints are documented
The sponsor or governance forum has approved the delivery plan.

Once this has been done, the baseline can be saved in Microsoft Project. The common process is:

Open the approved project schedule in Microsoft Project.
Go to the Project tab.
Select Set Baseline.
Choose Set Baseline again from the dropdown.
Select Baseline for the full approved project baseline, or another baseline field if saving a later approved version.
Choose Entire Project if baselining the whole schedule.
Click OK.

Microsoft Project then stores the approved baseline start dates, finish dates, durations, work and costs. These fields remain fixed unless the project is formally re-baselined through change control.

As the project progresses, actual performance should be entered into the schedule. This may include:

Actual start dates
Actual finish dates
Percentage complete
Remaining duration
Actual work
Actual costs
Revised forecasts.

The project manager can then compare the current schedule against the baseline using views such as tracking Gantt, variance table, earned value table and project reports.

This allows the team and governance group to see whether the project is still aligned to the approved plan or whether corrective action is required.

The key point is that the baseline should not be casually overwritten. If every delay simply results in a new baseline, then the organisation loses the ability to understand true performance. Re-baselining should only occur following approved change, not because the project has drifted from the plan.

The difference between reporting progress and measuring performance

Many project reports state that a project is “on track” or “progressing well”. The difficulty is that these statements often lack evidence. A project may have completed several activities and still be behind schedule. It may have spent less than planned but delivered even less than expected. It may appear financially healthy because invoices have not yet arrived. It may report high percentage completion while the most complex work remains unresolved.

This is where earned value analysis becomes powerful. Earned value analysis provides a structured way to compare planned work, completed work and actual cost. It helps answer three critical questions:

What did we plan to achieve by now?
What have we actually achieved?
What has it cost us to achieve it?

These questions matter because time and cost data by themselves can be misleading. A project that has spent 50 per cent of its budget is not necessarily healthy. The real question is whether it has delivered 50 per cent of the planned value. A project that is under budget may not be performing well if it is also behind schedule. A project that is on schedule may still be financially inefficient if it is costing more than planned to deliver the same amount of work. Earned value analysis helps reveal this difference.

How earned value analysis works

Earned value analysis compares three core measures:

Planned value, which is the approved value of the work that should have been completed by a point in time.
Earned value, which is the approved value of the work actually completed by that point in time.
Actual cost, which is the actual cost incurred to complete the work.

These measures allow project performance to be assessed more objectively. For example, if a project planned to complete $100,000 worth of work by the end of the month, the Planned Value is $100,000. If the team has only completed $80,000 worth of that planned work, the Earned Value is $80,000. If the actual cost of completing that work was $90,000, the Actual Cost is $90,000. This tells a much richer story than cost alone.

The project is behind schedule because it has earned less value than planned. It is also over cost for the work completed because it has spent $90,000 to deliver $80,000 of value. From these measures, the project can calculate:

Schedule variance, which is earned value minus planned value.
Cost variance, which is earned value minus actual cost.
Schedule performance index, which is earned value divided by planned value.
Cost performance index, which is earned value divided by actual cost.

In simple terms:

A negative schedule variance means the project is behind schedule.
A negative cost variance means the project is over budget for the work completed.
A schedule performance index below 1.0 indicates schedule underperformance.
A cost performance index below 1.0 indicates cost inefficiency.

These measures are not intended to replace judgement. They are intended to improve judgement by giving leaders better evidence.

Performing earned value analysis in practice

To use earned value analysis effectively, the project must have a credible baseline. Without a baseline, there is no reliable planned value. Without reliable progress data, there is no credible earned value. Without actual cost data, there is no meaningful cost variance. This means the project manager needs to ensure that:

The project baseline has been approved
The schedule is structured around measurable deliverables
Costs are assigned to tasks, work packages or control accounts
Progress is measured based on evidence of work completed
Actual costs are captured consistently
Reporting periods are clearly defined.

In Microsoft Project, earned value can be supported by assigning costs to tasks or resources, setting the baseline, updating actual progress and using earned value fields and reports. The broad process is:

Build the project schedule with tasks, milestones, dependencies, durations and resources.
Assign costs through resources, fixed costs or budgeted work.
Save the approved baseline.
Set the project status date for the reporting period.
Update actual progress, including actual starts, finishes, percentage complete, actual work and remaining duration.
Review earned value fields such as Planned Value, Earned Value, Actual Cost, Schedule Variance, Cost Variance, Schedule Performance Index and Cost Performance Index.
Analyse the variances and determine whether corrective action is required.
Report the results to the sponsor or governance forum with recommended decisions.

The technique is only as useful as the quality of the underlying data. If the schedule is poorly built, if percentage complete is guessed, or if actual costs are not captured properly, the earned value outputs will be misleading. This is why earned value is not just a calculation. It is a discipline. It requires clear planning, honest progress reporting, reliable cost capture and mature governance.

Governance needs evidence, not reassurance

Project governance is only as strong as the information it receives. A steering committee cannot govern effectively if it receives vague status updates, optimistic commentary or red, amber, green ratings that are not supported by evidence. Too many projects suffer from the “watermelon effect”: green on the outside, red on the inside. The project appears healthy in reports, while the underlying position is deteriorating.

Baselines, integrated schedules and earned value analysis help reduce this risk. They provide a clearer line of sight between planned performance and actual performance. They allow sponsors and governance groups to challenge constructively. They make it harder for poor performance to hide behind narrative confidence.

This does not mean governance should become overly bureaucratic. The goal is not to create reporting for its own sake. The goal is to create meaningful control. Good governance should help the project answer:

What has changed?
What is the impact?
What decisions are required?
What options are available?
What happens if we do nothing?
What does the data tell us about likely future performance?

A strong baseline and reliable performance data make those conversations more productive.

Baselining also protects change control

One of the most important benefits of a baseline is that it supports disciplined change control. Once the scope, schedule and budget have been approved, any material change should be assessed against the baseline. This allows the project to understand the impact of a change before it is accepted.

Without a baseline, change becomes informal. Scope expands quietly. Deadlines shift without approval. Costs increase without transparency. Stakeholders assume changes can be absorbed, and the project team is left trying to deliver more with the same time and resources.

This is how projects lose control. A baseline does not prevent change. Projects often need to change as new information emerges. But a baseline ensures change is visible, assessed and approved. That is the difference between adaptive delivery and uncontrolled drift, which we often see where at first a few tasks are tacking behind schedule, then over the subsequent reporting periods more and more track late and the project director is still stating the project is on track – the data is saying a different story, that is they have lost control of their project!

The cultural discipline of honest measurement

Baselining, scheduling and earned value analysis are often presented as technical project management tools. They are more than that. They are cultural disciplines.

They require teams to be honest about progress. They require leaders to accept evidence, even when it is uncomfortable. They require sponsors to make decisions based on reality rather than hope. They require governance forums to value early warning signs rather than punish bad news. This is why project controls must be embedded in the culture of delivery. If the culture rewards positive reporting, the data will be softened.

If the culture punishes escalation, risks will be hidden. If the culture values delivery theatre over delivery evidence, governance will receive reassurance instead of insight. The best project environments treat baselines and performance data as tools for learning and control, not blame. The purpose is not to catch people out. The purpose is to see clearly, act early and protect value.

The bottom line

Projects do not fail because people forgot to create a Gantt chart. They fail because leaders lose visibility of the truth. A project baseline gives the organisation a reference point. Scheduling tools such as Microsoft Project help show how delivery is progressing against that reference point. Earned value analysis helps reveal whether the project is performing efficiently in terms of both time and cost.

Together, they create the evidence base needed for effective governance and timely intervention. Without a baseline, there is no meaningful variance. Without variance, there is no reliable control. Without control, governance becomes theatre.

For organisations serious about delivery, baselining is not optional. Scheduling discipline is not bureaucracy. Earned value analysis is not academic. They are practical tools for protecting time, cost, scope and value. Most importantly, they help leaders replace hope with evidence. And in complex projects, evidence is what allows good decisions to be made before it is too late.

If some of these points are ringing true for you, please contact the PMLogic team to discuss how we can help strengthen your project controls, scheduling discipline and delivery governance.

Get in Touch