If you work with project schedules, especially in Primavera P6, you’ve probably heard people talk about baseline, recovery schedule, and revised schedule.
The problem is that these terms are often mixed up. I’ve seen projects where a recovery plan was wrongly presented as a revised schedule, and that alone caused serious arguments between the contractor and the client.
In this article, I aim to break it down simply and practically, just as I would in a real project meeting or training session.
Before we even talk about recovery or revision, we must speak of the baseline schedule.
Think of the baseline as the original promise of the project.
It is the schedule that says:
When will the project start
When will it finish
When will key milestones happen
This schedule is usually:
Prepared during project initiation
Reviewed and agreed by both the contractor and the client
Signed and approved
Once that happens, the baseline becomes the official reference.
From that point onward:
You use it to measure progress
You compare actual dates against it
You analyze delays using it
Important rule:
Once a baseline is approved, you don’t just change it because things are difficult. Any change must be agreed to by both parties.
A recovery schedule comes into the picture when the project is already behind schedule.
The scope has not changed.
The contract finish date has not changed.
But the work is not progressing as planned.
Simple Example
Let’s say:
An activity was planned to start on 15 September
It was supposed to finish on 11 November
Today is 18 October, and the activity is already late
If nothing is done:
The activity will finish late
Successor activities will be affected
The project completion date will slip
This is when the planner or project controls engineer must ask:
“How do we bring this project back on track?”
That answer is a recovery schedule.
A recovery schedule is not about changing the baseline.
It is about:
Accepting that a delay has occurred
Taking action to recover lost time
Still aiming to meet the original contract completion date
In practice, recovery is done in two main ways.
Crashing simply means adding more resources to finish the work faster.
This could be:
More workers
Extra equipment
Longer working hours
For example:
An activity originally planned for 41 days
Due to poor progress, it is now forecast to take 46 days
By adding resources, you reduce the remaining duration and pull the finish date back
But crashing is not magic.
You must consider:
Whether the resources are available
The extra cost involved
The risks of working faster
Fast tracking means doing some activities in parallel instead of one after the other.
In Primavera P6, this usually involves:
Changing logic from Finish-to-Start (FS)
To Start-to-Start (SS) with lag or lead
This method can save time, but it also increases risk because work may start before all information is ready
Imagine an activity on the critical path (red bar in the Gantt chart).
Because of delays:
Its forecast finish date moves by 6 days
That alone pushes the project completion date by 6 days
As a planner, you:
Review the remaining duration
Analyze resource options
Compress the duration realistically
After rescheduling:
✔ Baseline remains intact
✔ Delay is managed
✔ Project is back on track
The activity finishes on the baseline date
The project completion date is restored
That is a recovery schedule.
A revised schedule is a completely different situation.
This happens when the project scope changes.
Not because of the delay, but because the project itself has changed.
Original plan:
Project duration: 12 months
Midway into the project:
Client introduces a new design
Additional work is added
Some activities are removed
New systems (like telecom or utilities) are introduced
Now:
The original plan no longer reflects the project
New activities have no baseline dates
Logic, duration, and milestones change
At this point:
You are not trying to recover time
You are redefining the project plan
This is a revised schedule.
Stay informed with valuable Primavera P6 tips and project controls insights delivered straight to your inbox.

Gbemi Jacob Adebayo brings about a decade of experience in project planning and controls across engineering and construction projects. Alongside his professional practice, he actively contributes to capacity building and knowledge transfer, delivering Primavera P6 training and providing hands-on job support to planning and project controls professionals. Gbemi also applies his expertise through consulting engagements, supporting organizations in schedule development, progress monitoring, and data-driven project decision-making.
Get in touch
Feel free to get in touch with us via email: support@glintpm.com