How to Rebaseline a Project After an Approved Change

A significant change has been approved, but the team is still reporting against a plan that no longer represents the authorised work. Rebaselining establishes a newly approved reference plan after an appropriate decision. It should preserve the history of what changed rather than erase missed commitments.

A man presenting bar charts on a large screen to colleagues.

Photo by Vitaly Gariev on Unsplash.

A forecast is your current expectation. A baseline is the agreed reference used to assess performance. Updating the forecast does not automatically authorise replacing that reference.

Confirm the authority to change the baseline

Start with the approved change and the organisation's control process. Check its scope, conditions and decision-maker. If the change is still a proposal, prepare an impact assessment rather than treating a revised schedule as permission.

APM's change-control guidance describes evaluating requests before approval, rejection or deferral. Keep that decision connected to the plan it authorises.

Rebuild the affected delivery logic

Review more than the finish date:

  • Changed deliverables and acceptance conditions.

  • Task sequence and supplier dependencies.

  • People, availability and operational commitments.

  • Cost and resource implications for the appropriate approver.

  • Risks, assumptions and outstanding decisions.

  • Milestones, communication and downstream commitments.

Check affected owners can actually meet the proposed arrangement. A sponsor-approved scope addition does not create extra capacity by itself.

Preserve a bridge between versions

Use a short baseline change note showing the earlier reference, the approved change, the reason for movement and the new reference. Retain the decision and the prior version in the agreed record location.

In a hypothetical project, the sponsor approves an additional acceptance stage after a new stakeholder requirement. The revised plan includes reviewer availability and dependent activities, not just an extra box labelled “review”. The note distinguishes the approved addition from any delay that had already occurred.

This makes subsequent reporting more honest. The team can explain performance against the new agreement without making the original commitment disappear.

Communicate what people must now follow

State the effective version, changed dates and responsibilities. Update affected working records and confirm that external commitments have been handled by the appropriate owners. Keep later forecast movement visible instead of repeatedly resetting the baseline to match reality.

Related guidance: small-team project planning guide.

If approved changes leave your project reporting against several competing plans, Hili Consulting can help establish a clear reference, credible forecast and traceable change history.

Previous
Previous

How to Resolve a Resource Conflict Between Project Work and Daily Operations

Next
Next

A Project Closure Checklist That Gives Unfinished Work an Owner