See the evidence
before you sign in.
Both reports below are generated by the PlanProof Quick Check diagnostic engine from two synthetic XER teaching samples: a file with known issues and an edited revision. The same versioned results power the homepage and every export.
What improved between submissions
The edited input removes the configured findings below. Each category is calculated from the same rule results and scoring model. Findings can overlap on a single activity.
Every score deduction has evidence.
Incomplete activities have open ends
Add valid predecessor and successor logic, or document approved project start/finish exceptions.
Multiple unconnected starts detected
Confirm that each start activity is tied to an authorised project or phase start.
Multiple unconnected finishes detected
Confirm that each finish activity is tied to an authorised project or phase finish.
Activities have negative total float
Review the driving path, imposed dates, calendars, and recovery actions.
Activities have excessive total float
Check for weak logic, missing scope ties, or calendar effects.
Hard constraints restrict schedule logic
Confirm each hard constraint is contractually required and replace it with logic where possible.
Activities exceed 352 hours (44 eight-hour days)
Break long activities into measurable work packages with clear handoffs.
Potential out-of-sequence progress detected
Review retained-logic settings and correct predecessor status or actual dates.
Relationship leads were detected
Replace negative lag with explicit activities so the overlap is visible and measurable.
Relationship lags exceed 40 hours (five eight-hour days)
Model significant waiting periods as activities with ownership and calendars.
Non-finish-to-start relationships need review
Confirm SS, FF, and SF relationships are necessary and do not obscure the driving path.
Actual dates occur after the project data date
Correct the data date or remove future actuals before using the schedule for status reporting.
Before-to-after finding movement
One isolated activity, three findings.
A160 has no predecessor or successor. PP-101, PP-102 and PP-103 each list internal task 7. The edited file ties A140 → A160 → A150. Inspect whether a real project would justify that handoff before adding it.
See the triggering evidence · Read the practical guideA future actual undermines the update.
A140 is active with actual start 12 September 2026, later than the 1 September data date. Its predecessor A130 is incomplete. PP-703 and PP-502 flag these conditions. The edited sample removes that actual and marks the activity not started; this is a teaching edit, not a verified site-record correction.
See the future-actual evidence · Read the practical guideA better score still needs an execution case.
The score moves from 81 to 100. A130 duration changes from 480 to 240 hours, negative-float values are replaced, and relationships change. None of that demonstrates an achieved or feasible time saving by itself.
- Use the live change register to identify the exact edits.
- Request the scope, crew, productivity and interface basis for the duration and logic changes.
- Recalculate the proposal in P6 and review the approved completion obligation. This sample has no verified forecast or recovered-days result.
Download the inputs and matching reports.
PDF and Excel include the same score, categories, model and sample version. CSV includes activity evidence with report metadata. JSON contains the complete report. The XERs are minimal synthetic parser fixtures, not certified P6 re-import files.
Ready to analyse your own schedule?
All tools and report exports are free, with no trial expiry or monthly validation quota. No credit card required.