The DCMA 14-Point Schedule Assessment Explained

The Defense Contract Management Agency (DCMA) developed the 14-Point Schedule Assessment as a standardised way to evaluate the structural quality of an Integrated Master Schedule (IMS). It was originally designed for US government defence contracts, but its logic applies well beyond that context — it's now widely used in capital projects, infrastructure, energy, and commercial construction to assess whether a schedule is a credible planning tool or an administrative artefact.

The 14 checks cover the most common sources of schedule quality failure: missing logic, unrealistic durations, poor use of constraints, and metrics that can reveal whether a schedule was genuinely maintained or just submitted. Understanding what each check measures — and why the thresholds are set where they are — is more useful than treating the assessment as a compliance exercise.

The 14 Checks and What They Measure

1. Logic (Missing Task Links)

Checks the percentage of activities with no predecessors or no successors (excluding the first and last milestones). Threshold: less than 5%. Activities without successors create artificial float and break the flow of the critical path. Activities without predecessors (other than the project start milestone) can start at any time, which undermines the schedule's predictive value entirely.

2. Leads (Negative Lags)

Checks for relationships with negative lag values (leads). Threshold: 0%. Leads are scheduling shortcuts that pull a successor's early start earlier than the predecessor's finish. They're mathematically valid but logically problematic: they typically represent a dependency that hasn't been properly modelled with real logic, and they can artificially shorten the critical path.

3. Lags

Checks the percentage of relationships that use positive lag. Threshold: less than 5%. Lags represent waiting time between activities. Low usage of lags is preferred because lags often mask activities that should be separately modelled — when work takes time, it should be an activity, not a lag.

4. Relationship Types (Non Finish-to-Start)

Checks the percentage of relationships that are not Finish-to-Start. Threshold: less than 10%. Start-to-Start, Finish-to-Finish, and Start-to-Finish relationships add complexity and can obscure the critical path. Overuse often indicates logic that hasn't been thought through carefully — most real construction sequences can be modelled with FS relationships connected to reasonably decomposed activities.

5. Hard Constraints

Checks the percentage of activities with hard date constraints (Must Start On, Must Finish On). Threshold: less than 5%. Hard constraints override the schedule's calculated logic — they force a date regardless of what the network analysis says. Overuse of hard constraints produces a schedule that doesn't reflect reality: it produces whatever dates the constraints say regardless of whether the work can actually happen then.

6. High Float

Checks the percentage of activities with total float greater than 44 working days (approximately two months). Threshold: less than 5%. High float doesn't mean a schedule has lots of buffer — it usually means the logic is incomplete. Activities float because there's nothing after them to constrain them, not because the project genuinely has eight weeks of margin.

7. Negative Float

Checks the percentage of activities with negative float. Threshold: 0%. Negative float means the schedule cannot deliver to its own constraints — the calculated path takes longer than the dates require. Any negative float is a schedule QA failure: the schedule is claiming it can complete by a date that the underlying logic says is not achievable.

8. High Duration

Checks the percentage of activities with remaining duration greater than 44 working days. Threshold: less than 5%. Long durations reduce schedule granularity and obscure risk. A 120-day activity might actually contain three distinct work phases that have different resource profiles and different risk exposure — collapsing them into one activity makes progress tracking and delay analysis effectively impossible.

9. Invalid Dates

Checks for activities with actual or forecast dates that fall outside the project date range, or activities with actual dates after the data date (i.e., recording future work as completed). Threshold: 0%. Invalid dates indicate data entry errors or a schedule that hasn't been updated honestly.

10. Resources

Checks the percentage of activities that have no resource assigned. Threshold: less than 10% for resource-loaded schedules. Resource loading is what converts a sequence of activities into a statement about the capacity required to execute the plan. A schedule without resources can't tell you whether the durations are achievable with the available workforce or whether the plan has resource conflicts.

11. Missed Activities (BEI — Baseline Execution Index)

The BEI calculates the proportion of activities that should have started or finished by the data date but haven't. BEI below 0.95 (95%) indicates the project isn't performing to plan. A BEI of 0.8, for example, means 20% of the work that should have started hasn't started — that's a significant slip against the baseline.

12. Critical Path Test

Tests whether the critical path is continuous and traces from project start to finish through logical relationships. A broken critical path — one that stops mid-project due to missing logic or hard constraints — means the schedule has no genuine critical path and therefore no way to assess the impact of delays on completion.

13. Critical Path Length Index (CPLI)

CPLI measures schedule efficiency on the critical path: it's the ratio of (critical path length + total float) to critical path length. A CPLI of 1.0 means the critical path and the remaining schedule duration are fully aligned. Below 0.95 indicates a schedule that is behind and will likely not finish on time without recovery. CPLI below 0.95 is a threshold flag.

14. Baseline Execution Index (BEI)

BEI (see #11 above) is listed again as a standalone metric in some DCMA versions. When treated separately: completed task BEI should be at or above 0.95. A low BEI sustained over multiple updates is evidence of a project falling persistently behind its plan — not a one-off data date issue.

How to Use the Assessment Productively

The 14-Point Assessment is most useful as a diagnostic tool at the point of baseline submission and at each programme update. If a schedule passes all 14 checks, it doesn't guarantee the schedule reflects reality — but it does confirm that the structural errors that most commonly undermine schedule analysis are not present. If it fails multiple checks, those failures need to be investigated and resolved, not papered over.

The checks that matter most in practice: missing logic (check 1), negative float (check 7), hard constraints (check 5), and the BEI (check 11/14). These four tell you the most about whether the schedule is being used and maintained as a genuine planning tool.