XER Schedule Check: the DCMA 14-point assessment of a P6 schedule
Open a Primavera P6 .xer export and get the DCMA 14-point assessment with every activity behind each failing point, a critical path recomputed from the logic, the critical path test, and the faults the 14 points miss (logic loops, out-of-sequence progress, open finishes, float that no longer matches the logic). Everything runs in your browser: the schedule is never uploaded.
Check a schedule How it was checked against P6
For owners' reps and claims consultants reviewing a contractor's update, schedulers checking their own before submission, and subcontractors handed a schedule they have no P6 licence to open.
Your schedule
Choose an XER file exported from P6 (File, Export, Primavera PM XER).
Compare with the previous update
The monthly review before a pay application: open last month's XER here and this month's above. You get what progress was claimed, which actual dates were edited after they were reported, which logic, durations, constraints and calendars changed, how much float was used, how the driving path moved, and a half-step run that splits the finish movement into the part progress caused and the part revisions caused.
Open this month's file above first, then last month's here.
Update-to-update comparison
To ask the contractor about
| Severity | What | Count |
|---|
Assessment
| # | Check | Result | Threshold | Count |
|---|
Beyond the 14 points
Stored dates against the logic
Driving path to the forecast finish
| Activity | Name | Start | Finish | Float (days) |
|---|
The schedule CSV lists every open activity with its recomputed early and late dates, total float and free float, beside the values the file stores. Free float matches P6's own on 19,809 of 19,822 activities in six public files.
Written review to send
One document for the contractor: a summary, the corrections ranked high, medium and low with the exact activities behind each, the scorecard and the driving path. If you compared with the previous update above, the changes are in it too. Print it or save it as a PDF from the print dialog.
How it works
The file is read table by table (TASK, TASKPRED, CALENDAR, PROJECT, SCHEDOPTIONS, TASKRSRC). Each activity is scheduled on its own work calendar, holidays and changed days included, with finish-to-start, start-to-start, finish-to-finish and start-to-finish links and their lags, the project's lag-calendar and float settings, primary and secondary constraints, the planned start and must-finish-by dates, and progress at the data date under retained logic or progress override. The forward and backward passes give early and late dates, total float and free float, the same quantities P6 computes.
Checked against P6 itself: six public XER files exported from P6 versions 5.0 to 24.12, 19,822 open activities in all. Early finish, late finish and total float all equal what P6 stored on 19,808 (99.9%): 100% on five files, including a 4,200-activity hotel schedule, and 99.9% on a 16,000-activity programme with heavy out-of-sequence progress. Free float equals P6's on 19,809 (99.93%). Method and every number: README.
The DCMA points use the published thresholds: 5% for logic, lags, hard constraints, high float, high duration and missed tasks; none for leads, negative float and invalid dates; 90% finish-to-start links; 0.95 for CPLI and BEI; 44 working days for high float and high duration, counted on each activity's own calendar.
Questions
What is the DCMA 14-point assessment?
A set of fourteen schedule-quality checks published by the US Defense Contract Management Agency and now used across construction and engineering: missing logic, leads, lags, relationship types, hard constraints, high float, negative float, high duration, invalid dates, resources, missed tasks, the critical path test, the critical path length index (CPLI) and the baseline execution index (BEI). Each has a published threshold.
Is my schedule uploaded anywhere?
No. The file is read and analysed in this browser tab. There is no server, no account and no analytics vendor, so a confidential project schedule never leaves your computer.
Does it recompute the schedule or trust the dates in the file?
Both. The float checks use the total float P6 stored in the file, as a reviewer would see it. Separately the tool recomputes every open activity's early and late dates from the logic, calendars, constraints and progress, uses that to run the critical path test, and lists every activity where the file's stored dates disagree with the recomputed ones.
How close is the recomputed schedule to P6's own?
On six public XER files exported from P6 versions 5.0 to 24.12 (19,822 open activities), early finish, late finish and total float all agree with the values P6 stored on 19,808 activities (99.9 percent), and free float on 19,809. Every one of the six files agrees on 99.9 to 100 percent, including a heavily progressed 16,000-activity file with over 2,000 out-of-sequence links.
Why does missed tasks use planned dates instead of a baseline?
A single XER export usually holds only the current project, not the baseline project. P6 keeps each activity's planned start and finish, but it moves the planned dates of an activity that has not started to its early dates every time it schedules, so they stand in for the baseline only on activities that have started or finished. Late work that has not started yet is therefore not counted as missed, and both missed tasks and BEI can read better than against the true baseline. The tool says so next to the result; compare against the baseline project where you have it.
What does the critical path test do?
It adds 600 working days to an open activity on the longest path and recomputes the schedule. The project finish should move by at least that much. If it moves less, a constraint, a lag, an open end or a broken link is stopping delay from flowing through the path, and the reported critical path cannot be trusted.
Which P6 settings are honoured?
Each activity's own calendar with its holidays and changed days, the lag calendar setting, total float as finish, start or smallest float, retained logic or progress override, the project's planned start and must-finish-by date, primary and secondary constraints including as late as possible, and external dates from links to projects not in the file. Resource levelling and expected finish dates are not modelled.
How does the update-to-update comparison work?
Open this month's XER and last month's. Activities are matched by activity ID and relationships by predecessor, successor and type. The report lists progress claimed, actual dates edited after they were reported, logic, duration, constraint and calendar changes, float used and driving-path changes. A half-step run recomputes last month's schedule with only this month's progress applied, so the change in the forecast finish splits into the part progress caused and the part the revisions caused. On six real P6 files with 720 planted edits, every edit was reported and nothing else.
Does a pass mean the schedule is good?
No. The fourteen points are screening metrics that find common faults; a schedule can pass them all and still be unrealistic, and some failures are justified. Use the lists to decide what to fix or explain, and have a qualified scheduler review the schedule before relying on it.