DCMA-14 · Check 1 of 14
Logic (missing predecessors and successors)
The share of incomplete tasks with no predecessor or no successor.
What it measures
Whether every unfinished task is tied into the network. A task with no predecessor has nothing driving its start; a task with no successor drives nothing after it.
How Claims Digger calculates it
Every incomplete task is checked twice: does it have a predecessor, and does it have a successor. The result is failed checks divided by total checks (incomplete tasks x 2). Milestones are listed separately and don't count toward the percentage. The check passes below 5%.
Why it matters
The critical path calculation only means something if the network is connected. An activity with no successor gets a late date from the project finish, so it looks like it has plenty of float whether or not it really does.
How to fix a failure
- Add the missing predecessor or successor for each flagged task, based on what really has to happen before or after it.
- Where a task genuinely starts or ends the job, tie it to the project start or finish milestone rather than leaving it open.
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.