DCMA 14-Point Schedule Assessment: Complete Guide

What Is the DCMA 14-Point Assessment?

The DCMA 14-Point Schedule Assessment is a standardized framework developed by the Defense Contract Management Agency for evaluating the quality and reliability of project schedules. Originally created for defense acquisition programs, it has been widely adopted across the construction industry as a benchmark for schedule quality. The assessment evaluates 14 specific metrics that together indicate whether a schedule is well-constructed, logically sound, and suitable for project management purposes.

Each of the 14 points examines a different aspect of schedule quality — from logic completeness and constraint usage to critical path integrity and resource loading. A schedule that passes all 14 checks is considered "healthy" and reliable for decision-making. Schedules that fail multiple checks may produce unreliable dates, misleading float values, and an inaccurate critical path.

While the DCMA thresholds provide useful benchmarks, they should be applied with professional judgment. Some projects may have legitimate reasons for exceeding certain thresholds, and passing all 14 checks does not guarantee a perfect schedule. The assessment is a screening tool that identifies potential issues for further investigation, not a definitive quality certification.

The 14 Assessment Points

1. Logic (Missing Predecessors/Successors)

This check identifies activities without predecessors or successors (open-ended activities). The threshold is less than 5% of incomplete activities should be open-ended. Open-ended activities are not properly connected to the schedule network, meaning their dates are not logic-driven and they cannot drive other activities. Every activity except the project start and finish milestones should have at least one predecessor and one successor.

2. Leads (Negative Lag)

Negative lags (leads) allow successor activities to start before their predecessors reach the defined relationship point. The threshold is zero — no negative lags should exist. Leads create scheduling anomalies where activities can start before their logical prerequisites are met, producing unreliable date calculations.

3. Lags

This check measures the percentage of relationships with positive lags. The threshold is less than 5% of relationships should have lags. While some lags are legitimate (curing time, review periods), excessive lag usage often indicates that activities are being used as substitutes for proper logic or that work is being hidden within lag durations.

4. Relationship Types

This metric examines the distribution of relationship types. The threshold is less than 5% of relationships should be Start-to-Finish (SF) or Finish-to-Finish (FF) types. Finish-to-Start relationships are preferred because they are the most intuitive and easiest to validate. Excessive use of other relationship types can obscure the driving logic.

5. Hard Constraints

Hard constraints override CPM logic by forcing activities to specific dates. The threshold is less than 5% of incomplete activities should have hard constraints. Excessive constraints undermine the schedule's ability to respond dynamically to changes and can mask the true critical path.

6. High Float

Activities with excessively high total float (typically greater than 44 working days) may indicate missing logic or disconnected paths. The threshold is less than 5% of incomplete activities should have high float. While some activities legitimately have high float, a large percentage suggests logic gaps that need investigation.

7. Negative Float

Negative float indicates the schedule cannot meet its constraints or completion date without acceleration. The threshold is zero — no activities should have negative float in a viable schedule. Negative float means the project is already behind its required dates and corrective action is needed.

8. High Duration

Activities with durations exceeding 44 working days (approximately 2 months) may be too large for effective management. The threshold is less than 5% of incomplete activities should have high durations. Long-duration activities should typically be broken into smaller, more manageable pieces that allow better progress tracking.

9. Invalid Dates

This check identifies activities with actual dates that are inconsistent — for example, an actual finish date without an actual start date, or forecast dates in the past. The threshold is zero invalid date combinations. Invalid dates indicate data entry errors or update inconsistencies that undermine schedule reliability.

10. Resources

This metric checks whether activities are resource-loaded. The threshold varies, but generally all incomplete activities should have resource assignments. Resource loading enables earned value analysis, resource histogram generation, and workforce planning.

11. Missed Tasks

Missed tasks are activities with baseline finish dates in the past that are not yet complete. A high percentage of missed tasks indicates the schedule is not being maintained or the project is significantly behind plan. This metric helps assess whether the schedule reflects current reality.

12. Critical Path Test

This check verifies that the critical path is valid and logic-driven. It tests whether extending a critical activity's duration by a defined amount (typically the project's remaining duration) causes the project end date to extend by the same amount. If not, the critical path may be constraint-driven rather than logic-driven.

13. Critical Path Length Index (CPLI)

CPLI measures the efficiency needed to complete the project on time. It is calculated as (Critical Path Length + Total Float) / Critical Path Length. A CPLI of 1.0 or greater indicates the project can finish on time; below 1.0 indicates acceleration is needed. This metric provides a single number that communicates schedule feasibility.

14. Baseline Execution Index (BEI)

BEI measures how well the project is executing against its baseline plan. It is calculated as the number of completed tasks divided by the number of tasks that should have been completed per the baseline. A BEI of 1.0 indicates on-plan execution; below 1.0 indicates the project is completing fewer tasks than planned.

Implementing DCMA Assessments

DCMA assessments should be performed at key project milestones: baseline approval, monthly updates, and whenever significant schedule changes occur. Automated tools make this practical — manually checking 14 metrics across thousands of activities is impractical for regular use.

Float Master's DCMA assessment feature runs all 14 checks automatically against any uploaded XER file, providing instant results with detailed breakdowns of which activities fail each check. This enables rapid identification and resolution of schedule quality issues.

When a schedule fails DCMA checks, prioritize corrections based on impact. Logic issues (missing predecessors/successors) and negative float typically have the most significant impact on schedule reliability and should be addressed first. Cosmetic issues (high duration activities, lag usage) are important but less urgent.

Key Takeaways

The DCMA 14-point assessment provides a standardized, objective framework for evaluating schedule quality. While originally developed for defense programs, its principles apply universally to construction scheduling. Regular DCMA assessments catch quality issues early, ensure schedule reliability, and demonstrate professional scheduling practices to project stakeholders.

Use the assessment as a diagnostic tool, not a pass/fail gate. Investigate failures to understand their root causes, prioritize corrections based on impact, and track improvement over time. A schedule that consistently passes DCMA checks is one you can trust for decision-making.