How to Create a Timeline Rebaseline for Education & Training
A formal procedure for revising the program schedule baseline when cumulative changes, delays, or scope adjustments have made the current baseline no longer representative of the realistic program trajectory.
Purpose
To restore the accuracy and usefulness of the program schedule by establishing a new realistic baseline that reflects the current state of the program, enabling meaningful variance tracking going forward.
Scope
Applies when the program manager determines that the current schedule baseline is no longer useful for tracking purposes due to cumulative variances, and a formal rebaseline is warranted.
Prerequisites
- Evidence that the current baseline is significantly out of alignment with the realistic program trajectory
- All approved scope changes have been incorporated into the program plan
- Program sponsor or steering committee has been briefed on the need for a rebaseline
Supports compliance with the ESOS framework, CRICOS requirements, ASQA standards, and state education department reporting.
Step-by-Step Procedure
Document the Case for Rebaselining
Prepare a formal justification for the rebaseline, explaining why the current baseline no longer serves its purpose and the expected benefits of establishing a new one.
- 1.1Summarise the cumulative schedule variances and their root causes
- 1.2Explain how the current baseline is hindering effective program management and stakeholder reporting
- 1.3Describe the expected benefits of the new baseline for program tracking and decision-making
Update the Program Schedule
Revise the program schedule to reflect the current state of all tasks, updated estimates for remaining work, and any approved changes that have not yet been fully incorporated.
- 2.1Update all task statuses to reflect actual progress as of the rebaseline date
- 2.2Revise estimates for all remaining tasks based on current team knowledge and performance data
- 2.3Incorporate all approved scope changes, resource adjustments, and dependency updates
- 2.4Validate the critical path and ensure all task dependencies are accurate
Obtain Rebaseline Approval
Present the revised schedule and rebaseline justification to the program sponsor or steering committee for formal approval.
- 3.1Present the rebaseline justification and revised schedule to the approving authority
- 3.2Highlight the key differences between the old and new baselines
- 3.3Obtain formal written approval to proceed with the rebaseline
Save the New Baseline
Save the approved revised schedule as the new program baseline in the program management tool, preserving the original baseline for historical reference.
- 4.1Archive the original baseline with a clear label indicating it is the superseded version
- 4.2Save the revised schedule as the new active baseline with the approval date noted
- 4.3Verify that variance tracking is now calculating against the new baseline
- Maintain a baseline version log that records the date, reason, and approver for each baseline change
Communicate the Rebaseline
Notify all stakeholders and team members of the rebaseline, explaining the changes and what it means for upcoming milestones and expectations.
- 5.1Distribute a rebaseline notification to all stakeholders explaining the reasons and key changes
- 5.2Highlight any changes to milestone dates or deliverable deadlines that affect external commitments
- 5.3Brief the program team on the updated schedule and any changes to their task timelines
Update Related Documentation
Update all program documentation that references the schedule baseline to ensure consistency across the program management framework.
- 6.1Update the program management plan with the rebaseline details and approval reference
- 6.2Revise any stakeholder-facing documents that contain schedule commitments
- 6.3Update the risk register to reflect any new risks or changed risk assessments resulting from the rebaseline
Quality Checkpoints
Common Mistakes to Avoid
Expected Outcomes
Schedule variance percentage measured against the new baseline in the period following the rebaseline, indicating whether the new baseline is realistic
Number of rebaselines per program, tracked across the portfolio to identify systemic planning issues versus isolated program challenges
Frequently Asked Questions
Does rebaselining mean the program has failed?
No, rebaselining is a legitimate program management technique. Programs operate in dynamic environments and sometimes the most responsible action is to reset expectations based on reality. The key is to understand the root causes, learn from them, and set a realistic path forward.
Who has authority to approve a rebaseline?
Typically the program sponsor or steering committee approves rebaselines since they represent a formal change to the program commitments. The approval authority should be defined in the program governance framework.
When should a program be rebaselined?
Consider a rebaseline when cumulative schedule variance exceeds ten to fifteen percent and the current baseline no longer provides meaningful information for management decisions. Also consider it after a major approved scope change that fundamentally alters the program timeline.
Want this customised for YOUR business?
We'll tailor every step to your exact operations, tools, and team structure.