My Work/Schedule analysis

Schedule health checks: can this schedule be trusted?

A forecast is only as good as the schedule behind it. Eight DCMA-style checks run on every update and list the activities behind each number.

Primavera P6DCMA 14-pointSchedule qualityPower BI

8health checks every update

22%missing logic in the example

24out-of-sequence activities found

47hard constraints found

The problem

Missing logic, hard constraints and out-of-sequence progress make a P6 forecast look reliable when it is not. These issues are rarely checked every month because finding them by hand is slow.

How it works

Run the checks on each update. Future actuals, stuck forecasts, out of sequence, negative float, missing predecessors, missing successors, hard constraints and invalid starts.
Show the size of the problem. Each check has a count, with missing logic and constraints shown as a share of open activities.
List the activities. Click a check to get the exact activities to fix.

Schedule health page — Eight checks with the activities behind the selected one.

Walkthrough

Result

Schedule quality is measured every update, so poor logic is fixed before it distorts the forecast.

Project and client identifiers are hidden in the screenshots.