9. Invalid dates
Actual dates after the data date, or forecasts before it.
- Default threshold
- None
- On the demo programme
- Pass0 of 362
Definition
Actual dates can't be in the future, and work that hasn't happened can't be forecast to start or finish in the past.
How the app counts it
- Actual start or finish after the data date, and an actual finish before its actual start.
- A forecast start or finish before the data date on open work. Forecasts are P6's early dates from the last schedule run; planned dates are never used.
- A minute's grace keeps a forecast exactly at the data date from reading as before it.
Thresholds, the counting basis and whether the check counts towards the score can all be changed. See settings.
Why it matters
Invalid dates mean the progress or the schedule run is wrong, so every date, float value and index built on them is suspect.
How to fix it in P6
- Correct actual dates entered in the future.
- If forecasts are in the past, the file wasn't rescheduled after statusing. Set the data date, press F9 and export again.