Free tool · Scheduling
P6 schedule health check
Drop in a Primavera P6 export and get a DCMA 14-point style scorecard: open ends, leads and lags, hard constraints, high and negative float, long durations, invalid dates, missed tasks, BEI and CPLI, with the activities behind every failure. Your schedule never leaves your browser.
1. Load a P6 schedule
Your schedule never leaves your browser. The XER is parsed and checked on this page. Nothing is uploaded; analytics record only counts (activities, checks passed).
Drop a Primavera P6 .xer export here. Schedule (F9) before exporting so float and dates are current.
The sample is a synthetic 44-activity office building with issues planted on purpose. No real project, company, or people.
Next step
Run these checks on every update, not once
The same rules can run on every schedule update, next to a governed connection to P6, so open ends, constraints and float erosion show up before the update goes to the owner. We have built this for P6 and for agentic scheduling; talk to us about your schedules.
The brief is pre-filled with the number of checks passed only, never your schedule.
How we use these checks
Rules do the detection; people make the call. The same kind of deterministic checks run inside the scheduling systems we have built, so a health result is a number the code computed, not a model's estimate.
- AI for CPM scheduling and Primavera P6: what works today
- CPM engine, schedule health and Monte Carlo risk
- Verifying Primavera P6 XER exports before they leave
- Building an MCP server for Oracle Primavera P6
- Demo: P6 MCP server
- Demo: Connect agentic scheduling
- Solutions for scheduling and project controls teams
Frequently asked questions
Is my schedule uploaded anywhere?
No. The XER file is read and checked by JavaScript on this page, in your browser. Nothing is sent to a server unless you email yourself the results, and then only the counts and check names. Analytics record only that a check ran and counts (activities, checks passed), never activity names, codes, dates, or file names.
Is this an official DCMA 14-point assessment?
No. It follows the structure and commonly published thresholds of the DCMA 14-point assessment (for example, at most 5% open ends, no leads, at most 5% of activities with more than 44 working days of float), but it is our implementation, not an official tool, and contracts often set their own thresholds.
Why do some checks say "not computed"?
Some points need data an XER may not carry. Resources need TASKRSRC rows, CPLI needs a must-finish-by date on the project, and missed tasks and BEI need planned dates and a data date. The DCMA critical path test needs a CPM recalculation with an added delay, so it is shown as informational: the list of activities P6 reports as critical. We say what is missing rather than guess.
What baseline does it use for missed tasks and BEI?
The planned dates in the exported project (target_start_date and target_end_date). An XER export does not include a separate baseline project unless you export it too, and P6 can move planned dates on activities that have not started. Treat those two results as a prompt to check against your real baseline.
How are hours converted to days?
Durations, lags and float are stored in hours. Each activity's hours are divided by the hours per day of its calendar (day_hr_cnt), falling back to the default calendar and then to 8 hours.