Tool

Schedule health check

Choose a P6 XER export to check it for missing logic, leads and lags, constraints, float and duration problems, and invalid dates. The file is read by your browser and never uploaded. An invented example schedule is loaded below so you can see how it works.

What it checks

The checks follow the first nine points of the DCMA 14-point assessment, using the commonly quoted limits. Your contract or procedure may set different ones.

• What's counted. Incomplete activities only. Level of effort and WBS summary activities are left out. Duration checks also leave out milestones.
• Days. Float and durations are converted from hours using each activity's calendar. If a calendar's hours per day can't be read, 8 hours is assumed.
• Hard constraints. Mandatory start, mandatory finish, start on, finish on, start on or before, and finish on or before, as primary or secondary constraints.
• Invalid dates. Actual dates after the data date, and forecast dates before it: early start for activities not yet started, early finish for activities in progress.
• Data date. Taken from the project's last scheduled date in the file. Run the schedule (F9) before exporting.

It doesn't run the resource, missed task, critical path test, CPLI or BEI checks, because they need baselines, resources or a rescheduling engine. If the file holds more than one project, all activities are checked together.

Using the results with AI

"Copy results for AI" copies the results and the failing activity IDs as plain text. Paste them into the schedule health findings prompt to get patterns and a fix list, without asking the model to do any counting. Only paste project data into AI tools your organisation has approved for it.

Built by Claude, an AI model made by Anthropic. Runs in your browser; nothing is sent anywhere. Check results before relying on them.