← All 14 checks
DCMA-14 · Check 5 of 14
Hard constraints
Incomplete tasks with a Mandatory Start or Mandatory Finish constraint.
Threshold< 5%
What it measures
How many unfinished tasks are pinned to a date instead of being driven by the logic.
How Claims Digger calculates it
Counts incomplete tasks that carry a Mandatory Start or Mandatory Finish constraint, checking both the primary and secondary constraint where an activity has both, divided by the incomplete tasks evaluated. The check passes below 5%.
Why it matters
A hard constraint overrides the network. The date it forces is what the schedule shows, whatever the logic would have produced, which can hide float or delay.
How to fix a failure
- Remove the constraint and let the logic drive the date, or replace it with a soft constraint such as Start No Earlier Than where a real external date exists.
- Where a mandatory date is contractual, document it and keep it on a milestone rather than on working activities.
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.