Passing DCMA vs Having a Good Schedule: They're Not the Same Thing

Yes, a schedule can pass DCMA and still be a bad schedule. The checks test structure (logic, constraints, float, dates), not whether durations, scope, sequence or resources are realistic, and DCMA itself calls the metrics a framework for asking questions. A DCMA compliant schedule can meet every threshold and still be unachievable.

This article sits in the DCMA-14 schedule assessment series and covers where the checks stop being useful, how they get gamed, and what to add.

What does DCMA say about its own metrics?

The pamphlet is less rigid than the way it is often used. It describes the metrics as giving the analyst a framework for asking educated questions and performing follow-up research. A red metric, it says, is not in and of itself synonymous with failure, and correction of the metric is not necessarily required but it should be understood (DCMA-EA PAM 200.1).

That is a smoke detector, not an inspection certificate. The alarm tells you to look. A quiet alarm does not mean the building is sound.

DCMA's scope matters too. The checks come from Section 4 of a 2012 pamphlet written to help analysts review a contractor's integrated master schedule. A 2022 industry presentation, with a DCMA co-author, states that the 14-point list is "still evident in contract CDRLs" but is "no longer used by DCMA (EVMS Center)," and that certain analytics are still used to confirm schedule quality (NDIA IPMD Clearinghouse slides). Whatever the agency's current practice, the 14 checks live on mostly because contracts keep citing them.

What do the 14 DCMA checks not test?

The checks look at the shape of the network and a few performance ratios. Nothing in them asks whether the plan is right.

Mosaic Projects makes the point directly: conforming to the checks does not of itself indicate the schedule is sensible, realistic and achievable, and correlation is not the same as causation (Mosaic WP1088). A schedule with short, linked, well-statused activities can still be built on a wrong sequence or a missing scope item.

How do people game the DCMA metrics?

Every metric has a cheap way to clear it. The following are common patterns, and experienced reviewers know them.

SmartPM also notes that a binary pass/fail reading can hide the root cause behind a score (SmartPM). A schedule that moves from 7% to 4.9% in one update should prompt the question of what changed in the field, not applause.

None of this implies bad faith. Many of these edits are made to satisfy a specification that says "must pass DCMA-14." That is a specification problem, and it is why owners should state what they want, as covered in the guide for the owner's representative.

Why do two tools give different DCMA scores?

The pamphlet gives definitions and thresholds, and each software vendor turns them into rules. Mosaic notes that these implementations are not certified by DCMA or any other body, and that the biggest variance is which tasks count in the denominator (Mosaic WP1088). Handling of paired start-to-start and finish-to-finish links also differs between MS Project and P6.

For the same schedule, one tool can report 4.2% missing logic and another 5.6%. Neither is necessarily wrong. When you report a result, name the tool, the version, the population rules and the baseline. When you review a result, ask for the same.

What does a good schedule add beyond DCMA compliance?

GAO's Schedule Assessment Guide (GAO-16-89G, December 2015) is a broader frame. Its ten best practices cover capturing all activities, sequencing them, assigning resources, establishing durations, traceability, a valid critical path, reasonable total float, a schedule risk analysis, updating with actual progress and logic, and maintaining the baseline (GAO-16-89G).

Compare that list to the 14 checks and the gap is visible. Duration basis, scope capture, traceability and risk analysis are all outside the DCMA metrics. A practical review therefore adds:

• Duration basis. Quantity, crew and productivity assumptions behind the longest or most uncertain activities.
• Scope check. A trace from contract scope or the WBS to schedule activities.
• Calendar review. Weather, holiday, shift and work-restriction calendars.
• Sequence walk-through. The superintendent reads the logic and says whether the work could really be built that way.
• Risk analysis. A quantitative or at least qualitative look at what could move the finish.
• Narrative. A written description of the plan, assumptions and changes since the last update.

Resources are one area where the DCMA-14 is optional while GAO is explicit; see resources in a construction schedule.

What does a compliant but bad schedule look like?

Illustrative example: assume a 14-month building schedule with 500 activities. It scores 0 leads, 2% lags, 96% finish-to-start links, 1% hard constraints, 3% missing logic, 0 negative float, 0 invalid dates, and a BEI of 0.97. Every threshold is met. A superintendent reading it finds four problems.

Fixing these would probably move the finish date and could introduce negative float. The compliant version of the schedule is the one that looked best, and the corrected version is the one that tells the truth. That is why a clean scorecard should open a conversation, not end one.

The reverse also happens. A schedule with 7% of activities missing a successor might be an honest early-stage plan whose open ends are all in a work package scheduled to be detailed later. Reading the flag, finding the explanation, and moving on is exactly what the pamphlet's wording invites.

How should you treat DCMA compliance in practice?

Use the metrics as a screen at each update, trend them, and explain every red result. Then do the review the metrics cannot do. Three habits help:

1. Trend, don't snapshot. A metric that worsens for three updates in a row says more than one bad number. The BEI and CPLI trend is a good example.
2. Explain flags in writing. DCMA's own tone is "understand," not "pass." A paragraph per red metric does more than editing the data until it turns green.
3. Review the plan with the builders. A schedule is a model of how the work will be done, and the people doing the work can test it faster than any metric.

A DCMA compliant schedule is a reasonable starting point. It is not evidence that the project will finish on time.