Watch the original video, then use the written guidance below. Watch on YouTube ↗
A dashboard is valuable when it helps a project manager decide what to do next. A colourful chart without an agreed data date, progress rule or source can hide the very problems it is intended to show. Use the accompanying video as a starting point, then design your report around a small number of project decisions.
Define the question before selecting the chart
- Are contractual milestones moving? Show baseline and current forecast dates with variance.
- Is near-term work ready? Show upcoming activities and their unresolved constraints.
- Can the planned resources deliver the work? Compare time-phased demand with confirmed availability.
- Is performance changing? Compare planned and measured progress on the same scope and weighting basis.
Give every number a clear definition
State the schedule revision, data date, reporting period, units and source. Explain whether progress is quantity based, duration based or earned against agreed weights. Schedule percent complete, physical progress and earned value are different measures; do not label them all “project progress”. If cost information is incomplete, identify that limitation rather than presenting a precise-looking total.
A fictional milestone example
Suppose an installation milestone moves from 10 June in the agreed baseline to 17 June in the current forecast. The dashboard should show a seven-calendar-day movement, identify the controlling predecessor, and name the decision required. If the contract measures variance in working days, calculate and label it using the relevant calendar instead. The colour of the indicator is secondary to the explanation.
Check the report before issue
- Use the same status cut-off across schedule and progress inputs.
- Reconcile totals with the source schedule and agreed budget where applicable.
- Distinguish missing data from zero performance.
- Check that filters and exports include the intended activities.
- Add action owners, target dates and the next review point.
Choose the reporting tool for the audience
P6 layouts and exports can support reporting; external spreadsheets or BI dashboards may also be used where the scope requires them. An external dashboard is not automatically a live connection. Document how data is transferred and refreshed, and protect the underlying assumptions from accidental changes.
Discuss the outputs your team needs through progress reporting services.
Reference: Oracle Primavera P6 Professional User Guide. Check the guide for your installed version; available features and settings differ between products and editions.
Apply this to your project
Need to develop your scheduling skills or review a live project requirement? Share your scope and the planning problem you want to solve.
Primavera P6 training · Scheduling services · Ask Wiznic World
Have a question or a correction? Contact the editorial team and include this article's title.



