Video summary
07 | How to Read a Primavera P6 Time Schedule | Project Management Fundamentals
Main summary
Key takeaways
How to Read a Primavera P6 Time Schedule
A Primavera P6 time schedule helps project managers plan work and monitor whether activities are progressing on time. It combines activity data in a table with a visual timeline in a Gantt chart.
1. Understand the Two Main Schedule Views
- Table section: Shows information for each activity, such as its ID, name, duration, planned dates, actual or forecast dates, and percentage complete.
- Gantt chart: Displays activities as bars over a time scale. Each row represents an activity:
- The bar’s position indicates when the activity is scheduled or has occurred.
- The bar’s length represents its duration.
- The time scale may be divided into months, weeks, or days.
The Gantt chart makes it easier to see timing, progress, delays, and possible overlaps than a table alone.
2. Read the WBS and Activity Rows at the Right Level
- The Work Breakdown Structure (WBS) groups activities into phases or project components, helping organize complex work.
- In the example shown, WBS groups are indicated by colors.
- Activities are the basic building blocks of the schedule and are grouped under WBS items.
- Each activity has a unique Activity ID for reference and tracking.
- Check which row you are reading:
- A WBS row shows information for that group of work.
- An activity row shows information for that specific task.
For example, use the relevant WBS row to review the overall dates or progress for a ground-floor package, and an activity row to review one specific task within it.
3. Interpret the Key Schedule Fields
- Activity name: Describes the work to be done. Clear names help prevent confusion about the task.
- Duration: Indicates how long the activity is expected to take.
- Baseline or planned start and finish: The original schedule dates used as a reference for measuring performance. Differences between baseline and current dates can indicate slippage.
- Actual or forecast start and finish:
- An “A” suffix after a date indicates that it is actual.
- A date without “A” is forecast in the examples shown.
- Actual dates record when work started or finished; forecast dates indicate when it is expected to start or finish.
- Planned percentage: How much work was expected to be complete by a given date.
- Actual percentage: How much work has actually been completed. Comparing the two helps show whether progress is on track.
4. Use the Data Date to Assess Progress
- The Data Date is a vertical marker showing the schedule’s current reporting date.
- It helps distinguish work that has already occurred from work that remains planned or forecast.
- In the chart described in the lesson, activities to the left of the line represent work that should already have occurred; dates to the right are future or forecast.
- Compare progress around the Data Date with the baseline and the actual or forecast dates to identify variance.
5. Compare Baseline and Current Activity Bars
- In the example schedule, a black line indicates baseline dates, while the activity bar shows current progress.
- The displayed colors distinguish completed and ongoing portions: dark blue represents completed work, and green represents work still in progress.
- If actual and forecast dates match the baseline dates, the activity is progressing as planned.
- If an activity starts later than its baseline start or is forecast to finish after its baseline finish, it is delayed or slipping.
6. Examples of Interpreting Schedule Status
- On schedule: The activity’s actual start and finish align with the baseline dates.
- Started late and still in progress: The actual start is later than planned, and the forecast finish is later than the baseline finish. The chart may show a completed portion followed by a remaining in-progress portion.
- Not yet started and delayed: The activity’s forecast start is later than its planned start, with no “A” after the start date. A predecessor activity that has not finished may be holding it up.
Tracking such delays can help project managers identify bottlenecks and take corrective action.
Main Takeaway
To read a P6 schedule, first identify whether you are looking at a WBS row or an activity row. Then use the table to check dates and progress, and the Gantt chart to visualize timing. Comparing baseline dates with actual and forecast dates around the Data Date helps reveal whether work is on schedule or delayed.
Speakers and Sources Featured
- Hany Ismail — presenter, identified as being from the Planning Engineer website.
- Henry Gantt — mentioned as the American engineer associated with the early development of the Gantt chart; he does not speak in the video.
- Primavera P6 — the scheduling software discussed and demonstrated as the context for the lesson.
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.