Imported schedule versions
Review the schedule version and data date that frame the current project discussion.
Project controls
Review the imported programme alongside progress, dependencies and linked risks. Your source schedule remains the reference.
Potential delay Review context ↗
What your team can do
Review the schedule version and data date that frame the current project discussion.
Move between time-based and activity-based views when you need more detail.
Compare recorded progress with the baseline and keep the imported programme as the reference.
01 / In detail
Confirm the imported version and data date before discussing a movement in the programme.
Check the version and data date so everyone is working from the same programme.
Compare recorded progress with the baseline to see where work is ahead or behind.
02 / In detail
Read the sequence in the Gantt, then open the activity behind a delivery question.
Move from the overall sequence to the dates and details of a specific activity.
Use imported dependency information to explain how one activity relates to the work that follows.
03 / In detail
If an activity is under pressure, use its linked risks to discuss the cause and response.
Review the risk attached to an activity, including its owner and proposed mitigation.
Bring the finding to the planning team before changing the programme. Imported schedules remain authoritative; these views do not replace the source scheduling tool.
Putting it into practice
Start with the record, check the evidence and agree who does what next.
A clearer project conversation