The DCMA 14-Point Schedule Assessment, Explained for 2026

What the DCMA 14-Point Assessment Actually Measures

The DCMA 14 point assessment is the most widely used schedule health check in construction, and understanding it in 2026 is essential for anyone who builds, reviews, or litigates a critical path method (CPM) schedule. Rather than judging whether a project is on time, the assessment grades schedule quality: how sound the logic is, how realistic the durations are, and whether the network can be trusted to forecast anything at all.

The framework originated in government program controls but has become a common language across owners, contractors, project controls teams, and claims professionals. A schedule that passes signals a defensible, well-built network. A schedule that fails is a warning that forecasts and delay analyses resting on it may be unreliable.

Why Schedule Quality Comes First

A delay claim, a time impact analysis, or an earned-value forecast is only as good as the schedule underneath it. If the logic is broken, no amount of downstream analysis will fix the answer. That is why a schedule health check is the first step in any serious review, and why the fourteen checks are worth learning individually.

The Fourteen Checks, One at a Time

Twelve of the checks flag structural problems in the network. The final two are performance indices that measure realism and progress. Here is what each one looks for and why it matters.

• Open ends (logic): Activities missing a predecessor or successor float freely and distort the critical path. A healthy network ties nearly every task into the logic on both sides.
• Leads (negative lag): Negative lag lets a successor start before its predecessor finishes, masking true sequence. Best practice treats any lead as a red flag to remove.
• Lags: Excessive positive lag hides real work or arbitrary waiting time inside relationships. A high count suggests durations that should be modeled as activities instead.
• Relationship types: A robust schedule is built mostly on finish-to-start links. An over-reliance on start-to-start or finish-to-finish relationships can signal logic that was forced to fit a date.
• Hard constraints: "Must finish on" and similar constraints override calculated logic and can create artificial dates. Too many of them mean the schedule is being driven by constraints, not by the network.
• High float: Activities with very large total float (commonly flagged above roughly 44 working days) often point to missing successor logic rather than genuine scheduling slack.
• Negative float: Negative float indicates the schedule cannot meet a required date as currently logic-linked. It demands explanation, whether from constraints, missed progress, or an aggressive completion date.
• High duration: Very long activities (typically flagged above about 44 working days) are hard to status accurately and hide progress detail. They usually should be broken into smaller, measurable steps.
• Invalid dates: Actual dates in the future or forecast dates in the past reveal statusing errors that corrupt the data date and every calculation flowing from it.
• Resources: If the schedule is resource- or cost-loaded, this check confirms activities carry the expected assignments, which matters for earned-value and cash-flow reporting.
• Missed tasks: This compares actual progress against the baseline to see how many activities slipped past their planned finish, giving an early read on schedule performance.
• Critical path test: A deliberate large delay is inserted on a critical activity to confirm the delay flows through to project completion. If it does not, the critical path is broken.

CPLI and BEI: The Two Performance Indices

The final two checks move from structure to performance, and together CPLI and BEI are the quickest way to read whether a schedule is realistic and progressing.

Critical Path Length Index (CPLI) measures the efficiency the remaining critical path requires to finish on time. A value of 1.0 means the plan is exactly on track. Below 1.0 means the team must work faster than planned to hit the date, an early signal of an at-risk completion.

Baseline Execution Index (BEI) measures how many activities have actually been completed against how many were baselined to be complete by now. A BEI of 1.0 means the project is finishing work as planned; below 1.0 means tasks are falling behind the baseline rate.

How to Read the Results

No single failing metric condemns a schedule, and no perfect score guarantees a good one. Read the results as a pattern. A cluster of open ends, high float, and a failed critical path test usually points to the same root cause: incomplete logic. A wave of hard constraints paired with negative float often means a schedule squeezed to fit a date it cannot support.

Context matters, too. A resource check is irrelevant on a schedule that was never resource-loaded, and some long durations are legitimate for procurement or curing activities. The goal of a schedule health check is not a flawless scorecard but a clear-eyed understanding of where the network can and cannot be trusted, so that any forecast or claim built on it stands up to scrutiny.

Turning the Checks Into a Routine

The most durable value of the DCMA framework is repeatability. Running the same fourteen checks on every baseline and every monthly update turns schedule quality into a trend you can watch, catching drift before it becomes a dispute.

If you would like to see where a schedule stands, Fragnet runs a full DCMA 14-point assessment automatically from an uploaded .xer, so you can read the results in minutes.