The DCMA 14 point assessment is a set of schedule metrics used to examine the structure, status and execution performance of an Integrated Master Schedule (IMS). It checks areas such as missing logic, leads, lags, constraints, excessive duration, unreasonable float, missed baseline dates and critical path integrity.
However, the assessment is a diagnostic framework, not an automatic pass-or-fail contractual test. The U.S. Government Accountability Office (GAO) explains that its thresholds serve as starting points for objective analysis rather than compliance triggers. In addition, the contract, applicable data item description, approved Earned Value Management System (EVMS) description and customer direction determine the actual requirements for each program.
The assessment works best when analysts use it to find conditions that weaken the schedule model. A green score does not prove that the plan is executable. Likewise, a threshold exceedance does not prove that every flagged activity is wrong.
What the DCMA 14 Point Assessment Measures
The 14 metrics evaluate two related aspects of schedule quality. First, structural metrics test whether the network can calculate reliable dates and float. Second, execution metrics compare actual performance with the baseline plan.
The GAO Schedule Assessment Guide describes the assessment as a collection of measures for evaluating both the technical structure of a schedule and the contractor’s ability to plan and execute work. The DoD Risk, Issue, and Opportunity Management Guide also presents the metrics as a schedule health assessment tool.
These tests apply naturally to an Integrated Master Schedule for a DoD program. Still, proposal teams and non-EVMS programs can use the same concepts to evaluate schedule credibility before baseline approval or customer delivery.
Standard DCMA 14-Point Metrics and Thresholds
The commonly published tripwires appear below. Before comparing results across tools or organizations, confirm the filters, denominators, calendars and baseline fields used in each calculation.
- Logic: less than 5%. Measures eligible incomplete tasks that lack a predecessor, successor or both.
- Leads: zero. Identifies negative lag applied to a relationship.
- Lags: less than 5%. Identifies relationships with positive lag.
- Relationship types: less than 10% non-Finish-to-Start. Measures Finish-to-Finish, Start-to-Start and Start-to-Finish relationships.
- Hard constraints: less than 5%. Identifies constraints that can override or restrict logic-driven dates.
- High float: less than 5%. Identifies incomplete tasks with more than 44 working days of total float.
- Negative float: zero. Identifies incomplete tasks with total float below zero.
- High duration: less than 5%. Identifies unfinished tasks with baseline durations greater than 44 working days.
- Invalid dates: zero. Finds actual dates after the status date and forecast dates before it.
- Resources: zero improper assignments. Evaluates resource assignment quality when resource loading applies.
- Missed tasks: less than 5%. Measures tasks that did not finish as planned.
- Critical path test: zero-day variance. Tests whether a large delay inserted into the critical path produces an equivalent movement in the completion milestone.
- Critical Path Length Index: at least 0.95. Compares the remaining critical path with available float.
- Baseline Execution Index: at least 0.95. Measures completed tasks against tasks planned for completion.
How to Interpret the Structural Metrics
1. Missing Logic
A valid network needs enough predecessor and successor logic to model how work flows from the status date to completion. Open-ended tasks can create artificial float, broken paths and dates that do not respond to upstream changes.
Review the details rather than stopping at the percentage. Legitimate start and finish milestones may have only one logical direction. Summary tasks, level-of-effort activities and external interfaces may also require special treatment based on the assessment rules.
2. Leads
A lead creates an overlap by applying negative lag to a relationship. For example, a Finish-to-Start relationship with a five-day lead allows the successor to begin five days before its predecessor finishes.
Leads hide the event that permits the overlap and therefore make the schedule harder to status and defend. Replace them with explicit activities or measurable handoff milestones. See why leads can damage schedule quality for a detailed example.
3. Lags
A positive lag inserts waiting time between two linked tasks. Some lags model legitimate elapsed time, such as a curing or review period. However, the lag has no activity owner, status method or visible work scope.
Therefore, convert substantial or management-significant delays into activities. A short technical delay may remain appropriate when the scheduling procedures permit it and the team documents the basis. The distinction is explained further in when schedule lags are appropriate.
4. Relationship Types
Finish-to-Start logic usually provides the clearest sequence because the successor begins after the predecessor finishes. Excessive Start-to-Start or Finish-to-Finish logic can create dangling starts or finishes, particularly when an activity has no relationship controlling its other end.
Non-Finish-to-Start logic is not automatically defective. Instead, confirm that each relationship represents a real dependency and that the predecessor duration does not become a hidden driver of the successor.
5. Hard Constraints
Hard constraints can force a task to start or finish on a selected date regardless of network logic. As a result, they may distort total float and prevent delayed predecessors from moving downstream work.
Use logic to model the plan whenever possible. Reserve mandatory constraints for genuine external restrictions or contractual dates, then document their basis. The practical difference between date restrictions is covered in hard constraints versus soft constraints.
6–8. High Float, Negative Float and High Duration
High float often points to missing logic, distant constraints or weak integration with downstream milestones. Yet 45 days of float may be reasonable on a ten-year program and suspicious on a six-month effort. The 44-working-day threshold identifies records for investigation; it does not establish a universal limit on acceptable float.
Negative float signals that the calculated network cannot meet a constraint or required date under the current forecast. The scheduler should identify the driving path, quantify the shortfall and determine whether the plan, logic or imposed date requires action.
High-duration tasks can conceal intermediate handoffs, measurable outputs and emerging delays. Break long work into meaningful steps when those steps support management control. Do not split activities merely to improve a score, because arbitrary fragmentation adds maintenance without improving the plan.
How to Interpret the Status and Execution Metrics
9. Invalid Dates
The schedule must use a consistent data date, also called the status date. Actual starts and finishes should not occur after that date. Likewise, unfinished work should not retain forecast dates in the past.
Invalid dates often result from incomplete status collection, incorrect update procedures or manual date manipulation. Before running any health assessment, verify the IMS status date and update cutoff.
10. Resources
The resource metric requires careful interpretation. GAO notes that DCMA assesses proper resource loading when the contract requires a resource-loaded schedule. Therefore, do not treat the 14-point list by itself as authority to require labor hours, costs or named resources in every IMS.
When resource loading applies, check for assignments on inappropriate records, unrealistic units, overloaded resources and inconsistencies with the cost system. Also verify whether milestones, summary tasks or level-of-effort activities have received improper assignments.
11. Missed Tasks
The missed-task metric evaluates whether activities completed according to their baseline finish dates. A high result shows weak baseline execution, but the root cause may involve technical performance, late material, resource shortages, optimistic planning or poor baseline control.
Confirm how the analysis tool defines the measurement window. Also confirm its treatment of deleted tasks, replanned work, baseline changes and activities that finished after their baseline dates.
12. Critical Path Test
The critical path test checks whether the network responds dynamically. The analyst increases the duration of an incomplete activity on the critical path by a large test amount. The program completion milestone should move by the same amount, assuming no available float absorbs the delay.
If the finish date moves less than expected, inspect constraints, open ends, calendars, invalid relationships and alternate paths. The test does not identify every defect, but it quickly exposes a network that cannot transmit delay correctly.
13. Critical Path Length Index
The Critical Path Length Index (CPLI) estimates whether the remaining critical path can fit within the time available to the required completion date:
CPLI = (critical path length + total float) ÷ critical path length
A CPLI of 1.00 indicates that the remaining path fits exactly within the available time. A value below 1.00 indicates schedule compression or negative float. The standard tripwire is 0.95, although management should investigate any value that reflects a meaningful threat to a required milestone.
The calculation only helps when the underlying path is valid. First verify the driving sequence through a disciplined IMS critical path analysis.
14. Baseline Execution Index
The Baseline Execution Index (BEI) measures completion efficiency against the baseline:
BEI = completed tasks ÷ tasks planned to complete by the status date
For example, if the baseline called for 80 tasks to finish and 72 finished, the BEI equals 0.90. That result falls below the standard 0.95 tripwire.
BEI does not show the size or criticality of each miss. Ten late administrative activities may matter less than one late qualification test. Therefore, analyze missed tasks by Work Breakdown Structure (WBS), control account, responsible organization, milestone path and float band.
Fictional Example: Interpreting the Results Together
Consider a fictional sensor-development program preparing its monthly customer submission. Its IMS passes the lead, invalid-date and critical path tests. However, 8% of incomplete tasks lack logic, 7% have high float, the CPLI equals 0.92 and the BEI equals 0.88.
The program should not treat these as four unrelated failures. Missing logic may have created artificial high float. Meanwhile, genuine delay on the driving integration path may have produced negative float and reduced the CPLI. The low BEI confirms that the team has also completed fewer baseline tasks than planned.
The scheduler first traces the completion path and repairs valid logic gaps with the Control Account Managers (CAMs). Next, the team separates artificial float from genuine schedule flexibility. Finally, management reviews the missed integration and test activities, assigns recovery actions and updates the forecast. Simply adding relationships until each percentage turns green would not solve the execution problem.
A Practical Assessment Workflow
- Freeze the input file. Record the schedule version, status date, calendar assumptions and baseline used for the analysis.
- Define the population. Document exclusions for completed work, summaries, milestones, level of effort and planning packages.
- Run all 14 metrics. Retain both summary percentages and activity-level exceptions.
- Validate the critical path. Trace the driving sequence and perform the critical path test before trusting float-based results.
- Analyze by WBS and owner. A contract-level percentage can hide concentrated problems within one control account.
- Review exceptions with CAMs. Determine whether each condition is valid, defective or caused by a documented program constraint.
- Correct root causes. Repair logic, status, planning detail or baseline-control issues rather than manipulating metric scores.
- Trend the results. Compare reporting periods to determine whether schedule quality and execution are improving.
Contractual Requirements Versus Recommended Practice
The 14-point thresholds do not independently create a contractual requirement. Current Defense Federal Acquisition Regulation Supplement EVMS policy addresses when DoD applies EVMS and identifies DCMA’s role when DoD serves as the cognizant federal agency. The contract then establishes the applicable clauses, reporting deliverables and tailored requirements.
In addition, DCMA maintains current EVMS business practices and compliance metric templates on its EVMS compliance page. Those materials should govern formal compliance work when applicable. The traditional 14-point assessment remains useful as a schedule diagnostic, but teams should not substitute it for current contract direction or the complete EVMS surveillance process.
Common Ways Teams Misuse the Assessment
- Managing only to the threshold. Teams may ignore serious defects because the contract-level percentage remains green.
- Changing valid logic to improve a score. Replacing justified relationships with Finish-to-Start links can make the model less accurate.
- Removing constraints without understanding them. A constraint may represent an external need date that still requires visibility and management.
- Splitting activities arbitrarily. Shorter durations do not improve control unless the new tasks have clear scope, ownership and completion criteria.
- Ignoring tool settings. Different calendars, float options and baseline fields can produce different results from the same schedule.
- Submitting percentages without analysis. Management needs affected milestones, root causes, trends and corrective actions.
Final Takeaway
The DCMA 14 point assessment provides a fast, repeatable way to identify weaknesses in an IMS. Its real value comes from the investigation that follows each result.
Use the thresholds as tripwires. Then examine the activity details, driving paths, baseline history and program context. A credible assessment should explain not only which metrics exceed their thresholds, but also why they failed, which milestones they threaten and what the program will do next.