Critical Path Checks
Category weight: 15% of overall score
Checks in this category: 2
Critical path checks verify that the critical path is reasonable and can be validated through the schedule logic. A well-defined critical path is essential for accurate forecasting, earned value analysis, and management reporting.
Critical Path Length Index (CPLI)
| Field | Value |
|---|---|
| Check ID | critical-path-length |
| DCMA Reference | — |
| Default Threshold | 5–10% of activities should be critical; total span ≤ 1,825 days; CPLI ≥ 0.95 |
| Severity | Major |
Verifies that the critical path is reasonable in length and proportion. A schedule where all activities are critical suggests missing logic or excessive constraints. A schedule with no critical activities may have a disconnected network.
The Critical Path Length Index (CPLI) compares the remaining critical path duration to the time remaining before the project finish date:
CPLI = (Critical Path Length + Total Float on CP) / Critical Path Length
A CPLI ≥ 0.95 indicates the schedule can achieve the required finish date. A CPLI < 0.95 suggests the project is at risk of overrunning.
What triggers a finding:
- Fewer than 5% or more than 10% of activities are on the critical path
- Critical path span exceeds 1,825 days (5 years)
- CPLI falls below 0.95
Critical Path Test (BEI)
| Field | Value |
|---|---|
| Check ID | critical-path-test |
| DCMA Reference | Point 8 |
| Default Threshold | Critical path must form a continuous chain |
| Severity | Info |
Validates that the critical path forms a continuous, unbroken chain from the project start to the project finish. This is sometimes called the Baseline Execution Index (BEI) test.
What triggers a finding: The critical path contains gaps — there are critical activities that are not connected to other critical activities through predecessor/successor logic.
Why it matters: A fragmented critical path means the scheduling engine is using constraints rather than logic to determine critical activities. This undermines the integrity of the entire schedule analysis.
How to fix: Ensure every critical activity has at least one critical predecessor and one critical successor, forming a continuous logical chain through the schedule.
Next Steps
- Resource Checks — Validate resource assignments
- Progress Checks — Validate progress and status data
- Quality Overview — Return to the quality overview