World 1 of Projects, level 3: up high
From scope to schedule, resources and cost: how the plan links together. What the baseline is, why no improvement can be proven without the “before”, and who decides when it changes.
Part 3 of 5 of the series World 1 of Projects.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
World 1 of Projects series — level 3 of 5: World 1-1 · World 1-2 · World 1-3 · World 1-4 · World 1-5
In every Super Mario level, up at the top of the screen, there’s a number that counts down from the very first second: the level’s timer. Nobody argues with it halfway through. It’s against that number that the game tells you whether you did well or badly.
A plan plays the same role, with one difference that changes everything: the number is agreed before you start, instead of being imposed by the game, and then frozen, so you can compare the route you meant to take with the route you actually took.
From scope to schedule: how does the plan link together?
The plan is a chain, and the order matters:
- Scope: the WBS from World 1-2, with what will be delivered broken down until it fits in your hand.
- Activities and sequence: what has to be done for each deliverable, and what depends on what.
- Resources: who and what each activity needs (people, machines, materials).
- Schedule: when each thing happens, given what depends on what and who’s available.
- Cost: how much each piece costs, added up over time.
Whoever skips steps in this chain tends to skip the same one: resources. They build the schedule as if the team were infinite and then find out it isn’t. (How to calculate dates rigorously, and what to do when resources call the shots more than the sequence does, are topics for the next world.)
What is the baseline?
When the plan is ready and approved, you take a snapshot of it and freeze it. That snapshot is the baseline: the scope, time and budget against which everything that happens afterwards will be measured [1].
The plan stays alive and gets adjusted every week, while the baseline stays put: it’s the “before”. If it moves along with the plan, there’s nothing left to compare against, and any delay becomes “replanning”.
Why can’t you prove an improvement without the “before”?
Because an improvement is a difference. And a difference needs two numbers.
In my last job in Brazil, on a gas project in Rio de Janeiro, the construction team for the electrical discipline was pressing ahead without any planning. We did the full survey, the labour histogram and the discipline’s schedule. The plan showed that, at most, half the team construction was mobilising would be enough.
We took out half the team. Cost went down, and we still managed to increase billing, because the focus went to where the money was and where it was closest to being invoiced.
Without the plan, that decision would have been one opinion against someone else’s; with the plan, however, it became a calculation. And without the snapshot of the “before”, nobody would have been able to show, afterwards, that the change had worked.
When does the baseline change, and who decides?
The baseline only changes when the agreement changes.
If the client approves new scope, or the company formally decides to change the time or the budget, the baseline is updated, with a record of what changed, when and who approved it. If the project has simply fallen behind, the baseline stays where it is. The delay is exactly what it’s there to show.
Whoever has authority over the agreement decides: the project sponsor, the client, the committee that approved the budget. Never the team on its own, to make the report look better.
A plan that gets rewritten every time reality disagrees with it turns into a diary.
Quick questions
What is a project plan? It’s the chain that runs from scope to activities, resources, schedule and cost, built and approved before execution starts.
What is a project baseline? The snapshot of the approved plan, frozen: the scope, time and budget against which everything that happens afterwards is measured.
What’s the difference between the plan and the baseline? The plan changes every week, whereas the baseline only changes when the agreement changes, and with the approval of whoever has authority over it.
When can the baseline be changed? When there’s an approved change to scope, time or budget. If the project has simply fallen behind, the baseline stays where it is, because showing the delay is exactly its job.
References
- Fleming, Q. W.; Koppelman, J. M. (1995). Monitoring performance against the baseline. PM Network, 9(9), 9–14. https://www.pmi.org/learning/library/monitoring-performance-against-baseline-10416 — accessed 2026-09-25.