Claims Digger
← All 14 checks

DCMA-14 · Check 6 of 14

High float

Tasks with more than 44 days of total float.

Threshold< 5% (over 44 days)

What it measures

How many tasks appear to have far more slack than a real schedule should.

How Claims Digger calculates it

Counts tasks whose total float exceeds 44 days, converted using each activity's own calendar, divided by the tasks evaluated. The check passes below 5%.

Why it matters

Very high float usually points to missing successor logic rather than genuine slack: the activity isn't really constrained by anything after it.

How to fix a failure

  • Look for missing successors on the flagged tasks and tie them to the work that actually depends on them.
  • Check whether the activity is simply not needed until much later and belongs further along the network.

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.

Go deeper

Terms used here