Read-only analysis
PlanProof reads the values supplied in the XER. It does not recalculate or edit the source schedule.
TRANSPARENT BY DESIGNKnow exactly what
Know exactly what
PlanProof checks.
A schedule score is only credible when reviewers can understand the rules behind it. PlanProof discloses its current diagnostic framework, evidence model and limitations.
Activity-level evidence
Every finding carries the activity code, name and specific condition that triggered the rule.
Severity with context
Critical, high, medium and review levels help teams prioritise without pretending every exception has equal impact.
Data minimisation
The raw XER is processed in memory and discarded. A report is saved only when the user chooses the signed-in save workflow; local checks stay in the browser.
Every current production check
Thresholds are intentionally visible so results can be reviewed, challenged and applied consistently.
PP-101–PP-103, PP-701, PP-704
Logic integrity
5 checksPP-101
Open ends
Flags incomplete activities without required predecessor or successor logic, excluding the first unconnected start and first unconnected finish encountered in file order.
PP-102
Multiple unconnected starts
Identifies additional incomplete activities with no predecessor.
PP-103
Multiple unconnected finishes
Identifies additional incomplete activities with no successor.
PP-701
Duplicate activity codes
Finds repeated activity codes that weaken update traceability and audit trails.
PP-704
Missing calendar references
Finds incomplete activities assigned to a blank or unavailable calendar.
PP-201–PP-301
Float and constraints
3 checksPP-201
Negative total float
Identifies incomplete activities whose total float is below zero.
PP-202
Excessive total float
Identifies incomplete activities with more than 352 hours (44 eight-hour equivalent days) of total float.
PP-301
Hard constraints
Finds mandatory-start, mandatory-finish and equivalent hard constraints that can override logic.
PP-401–PP-402, PP-702
Duration quality
3 checksPP-401
Long original durations
Flags incomplete activities longer than 352 hours (44 eight-hour equivalent days) for work-package review.
PP-402
Zero-duration non-milestones
Finds zero-duration activities that are not identified as milestones or level-of-effort tasks.
PP-702
Negative remaining duration
Finds incomplete activities with invalid negative remaining duration.
PP-501–PP-502, PP-703
Progress integrity
3 checksPP-501
Status and actual-date conflicts
Finds completed work without actual finish, not-started work with actual dates, and related inconsistencies.
PP-502
Potential out-of-sequence progress
Finds started successors connected to incomplete predecessors for planner review.
PP-703
Future actual dates
Finds actual starts or finishes later than the project data date.
PP-601–PP-606
Relationship quality
6 checksPP-601
Negative lag / leads
Finds relationships with negative lag and recommends modeling visible scope.
PP-602
Long positive lag
Flags relationship lag above 40 hours (five eight-hour equivalent days).
PP-603
Non-FS relationships
Surfaces SS, FF and SF relationships for necessity and driving-path review.
PP-604
Dangling relationships
Finds relationship records that reference activities absent from the XER.
PP-605
Self-links
Finds activities linked to themselves.
PP-606
Invalid relationship types
Finds blank or unsupported relationship-type values.
SCORING MODEL
A quality indicator with traceable inputs.
The PlanProof health score begins at 100 and applies weighted deductions based on finding severity and affected-record volume. Category scores isolate performance in logic, float, constraints, progress, durations and relationships.
Scores are bounded from 0 to 100. They are intended for triage, quality improvement and consistent review—not contractual acceptance, forensic conclusions or certification.
Implementation notes · scoring model v1.2
Duration, float and lag thresholds use fixed eight-hour equivalents, not each activity calendar. PP-502 is a broad started-successor/incomplete-predecessor heuristic and can flag valid SS overlap. PP-703 is skipped if the data date is missing. PP-704 is skipped when TASK has no calendar field. PP-701 checks duplicate activity codes, not duplicate internal task IDs. Evidence lists contain up to 250 records per finding; counts include all matches.
Category scores are rounded after deductions; their weighted sum is then rounded for the overall score. Missing numeric values may be read as zero. A clean result does not prove a complete export or contract compliance.
See expected vs actual results and known limitations · Run the versioned demonstrationPROFESSIONAL BOUNDARIES
What PlanProof does not claim.
- It does not replace Primavera P6 scheduling calculations.
- It does not certify compliance with a contract, owner specification or the DCMA 14-point assessment.
- It does not determine entitlement, responsibility or delay damages.
- It does not replace review by a qualified planner or scheduler.
Turn the next XER into an evidence-led review.
Validate the current update, keep the report, then compare the next submission against it.
Validate a P6 schedule