Progress integrity: trust the update before the forecast
Check status, actual dates and sequence before interpreting a completion date.
A polished forecast is only as useful as the status behind it. Use the reporting cut-off as the reference, then reconcile activity status and actual dates with the records accepted for that period.
Confirm the cut-off
Record the XER data date and the reporting period. Verify that the latest recalculation date represents the intended cut-off. Identify missing dates and ambiguous date formats before treating a clean validation score as evidence of a reliable update.
Reconcile status with records
Inspect completed activities without an actual finish, not-started activities with an actual start, and any finish entered without a start. Compare each entry with agreed site records, inspection releases or handover evidence. Correct the source record rather than concealing the discrepancy with a constraint.
Investigate sequence in context
A started successor with an incomplete predecessor needs explanation. Review whether the relationship is FS, SS, FF or SF, whether a lag applies and whether the status is complete. Discuss the chosen scheduling options in P6. An intentional SS overlap must not be treated as an automatic error.
Separate the kinds of progress
Check what each percentage represents. Oracle distinguishes duration, units and physical percent complete; a physical percentage can be manually entered or based on activity steps. Keep quantity acceptance and consumed hours visible instead of replacing one with the other.
A140 starts after the data date
| Field | Sample value | Interpretation |
|---|---|---|
| Data date | 1 September 2026 | Reporting reference |
| A140 actual start | 12 September 2026 | PP-703: actual is later than the cut-off |
| Predecessor A130 | Incomplete | PP-502: review the sequence and source status |
Do not just move the data date to clear the warning. First establish which date and status are supported by the reporting records.
Take this checklist into the review
- Data date agrees with the reporting cut-off
- Actual starts and finishes are supported by records
- Future actuals resolved or the reporting date corrected with approval
- Sequence warnings reviewed by relationship type
- Resource consumption kept separate from physical completion
Inspect the progress-integrity demonstration
Follow A140 from its future actual to the specific PP-502 and PP-703 evidence.
Open the free demonstration →Further reading
These guides describe PlanProof’s current implementation and a suggested review workflow. External references provide broader scheduling context; they do not endorse or certify this tool.
- Oracle P6 Help · Percent Complete Columns (2024) ↗
- GAO Schedule Assessment Guide · GAO-16-89G (2015) ↗
References checked 6 October 2026. PlanProof methodology · Scoring model