DCMA-14 · Check 9 of 14
Invalid forecast dates
Dates that don't line up with the schedule's own data date.
What it measures
Whether actual and forecast dates are consistent with the date the schedule was updated to.
How Claims Digger calculates it
Flags four things: an active or completed activity whose actual start is after the data date, a completed activity whose actual finish is after the data date, and an active or not-started activity whose early start or early finish is already before the data date (a forecast that should have been updated). Each of the four is counted separately; the check passes only when all four are zero.
Why it matters
Actual dates in the future, or forecasts left in the past, mean the update wasn't finished properly. Every calculation downstream of those dates inherits the error.
How to fix a failure
- Correct actual dates that fall after the data date.
- Reschedule the schedule to the current data date so stale forecasts move forward.
Claims Digger runs all 14 checks on any schedule you upload, and lists the exact activities behind every failure. See how the health check works.