Contact us
Skip to the 14 checks
  1. Learning Center
  2. White Papers
  3. DCMA 14-Point Assessment

Free guide and schedule checker

DCMA 14-Point Schedule Assessment

In 2005, the Defense Contract Management Agency (DCMA) first released a set of schedule assessment guidelines known as the DCMA 14 Point Assessment. It was last formally published in 2012, and it is the most widely known and utilized of the schedule-driven guidelines.

What it is
A tool-agnostic, bare minimum assessment for schedule health.
What it measures
The construction and performance of the Integrated Master Schedule (IMS). It does not provide the complete picture of project health.
Why use it
It provides a quantitative assessment of schedule quality based on measurable criteria rooted in industry defined scheduling best practices.

Read the free PDF guide (opens in a new tab) See the 14 checks Check your schedule

This page follows our guide, DCMA 14-Point Assessment for Project Schedule. The checks themselves date from DCMA's 2012 pamphlet, DCMA-EA PAM 200.1.

Informational only. Not an official DCMA or government checklist. Read the full notice.

The 14 checks and their thresholds

Here we dig into each of the 14 points of assessment criteria and how they may serve as indicators to potential problem areas, why they are critical for a healthy project schedule, and where a deeper schedule analysis may be necessary.

  1. 1Logic5% or less missing links
  2. 2LeadsZero
  3. 3Lags5% of relationships
  4. 4Relationship types90% or more finish-to-start
  5. 5Hard constraints5% or less
  6. 6High float5% at 44 days or greater
  7. 7Negative floatIdeally none
  8. 8High duration5% over 44 days
  9. 9Invalid datesZero
  10. 10ResourcesNo threshold given
  11. 11Missed tasks5%
  12. 12Critical path testPass or fail
  13. 13CPLIBelow 0.95: investigate
  14. 14BEIBelow 0.95: investigate

Check 1 of 14

1

Logic

No greater than 5% of incomplete activities should miss a predecessor and/or successor

The logic check looks to ensure all incomplete activities have defined predecessors and successors. Just one missing link can have a significant impact on the project completion date, so it is imperative the team analyze the network logic to ensure they capture all dependencies.

The DCMA threshold for this metric is that no greater than 5% of incomplete activities should miss a predecessor and/or successor. However, it is common for organizations to self-impose a more rigorous policy that all incomplete activities have predecessors and successors, except for milestone, level-of-effort, and summary tasks.

At the very least, it is advisable that tasks without true in scope predecessors or successors be linked to the project start or project finish milestone, respectively. This indicates you considered the dependencies and not simply missed them.

From the Edwards PDF guide

2

Leads

Zero. One of the few metrics where the DCMA threshold is zero

A lead is a negative lag between two tasks in which a task starts some number of days before the finish date of its predecessor. Using leads can have adverse effects on the project total float, therefore impeding the ability to determine the true critical path.

For this reason, this is one of the few metrics where the DCMA threshold is zero. Rather than using leads, it is better to decompose activities to a level of detail in which traditional finish-to-start relationships can be used.

From the Edwards PDF guide

3

Lags

5% of total task relationships

Positive lags between tasks, where a task starts some number of days after the finish date of its predecessor, can also adversely affect analysis of the project critical path. Additionally, lags can be confusing if the reason for them is not immediately clear.

DCMA is more lenient with this metric, setting the threshold at 5% of total task relationships. However, in many cases it is better to represent a lag with an explicitly named task. For instance, rather than adding a 5-day lag to account for shipping time to the customer, represent shipping time with a separate task.

From the Edwards PDF guide

4

Relationship types

At least 90% of all activity relationships should be finish-to-start

The preferred relationship with tasks is the finish-to-start relationship. Ideally, all tasks in the schedule would be sequenced this way to have the clearest understanding of the critical path. There are instances, however, in which alternative relationships are appropriate. DCMA maintains that at least 90% of all activity relationships should be of the finish-to-start variety.

Start-to-start or finish-to-finish relationships may be used in cases where that is the true nature of the dependency. For example, it is reasonable that an audit may not begin until the activity being audited begins. It also makes sense that a Quality Assurance (QA) inspection may not finish until the process or product being inspected is complete. Start-to-start and finish-to-finish relationships should not be used, however, simply to schedule activities in parallel if they do not truly depend on each other. In such instances, it is better to give the two parallel activities the same finish-to-start predecessor(s).

The fourth relationship type, start-to-finish, can unnecessarily complicate the network logic of the schedule and should be used only in extremely rare cases.

From the Edwards PDF guide

5

Hard constraints

No greater than 5% of incomplete activities. Ideally, none

Constraints in general should be used sparingly, allowing task dates to be the natural result of dependencies and activity duration. When necessary, however, soft constraints (Start No Earlier Than and Finish No Earlier Than) are preferable because they allow the schedule to continue to be logic driven.

By contrast, hard constraints (Start No Later Than, Finish No Later Than, Must Start On, and Must Finish On) artificially prevent the schedule from shifting to the right. This has the potentially disastrous effect of obscuring the possibility of late performance before it is too late to take corrective action. Hard constraints can also obscure the schedule's critical path.

The DCMA threshold for hard constraints is that no greater than 5% of incomplete activities in the schedule should use them. However, this is another area where an organization may choose to impose limits that are more restrictive. Ideally, there should be no hard constraints in the schedule. It is more advisable to use deadlines to represent hard dates, allowing the schedule to forecast late delivery early while it is still possible to correct it.

From the Edwards PDF guide

6

High float

5% of total incomplete activities with total float of 44 days or greater

DCMA defines high float as total float of 44 days (approximately 2 working months) or greater. Intuitively, one would assume that activities with high float would be a good thing, a form of schedule margin. However, high float is more often the result of missing dependencies.

It is a rare activity that can slip more than two months without impacting the project completion date. The threshold for this metric is set at 5% of total incomplete activities.

From the Edwards PDF guide

7

Negative float

Ideally, none. DCMA would like to see no negative float at all

Negative float occurs when the project schedule is forecasting a missed deadline, or when a hard constraint is holding a task further to the left than it would otherwise be. In either case, it is indicative that some future date is likely to be missed and that the project team may need to either fast track or crash the schedule to rein it back in.

Ideally, DCMA would like to see no negative float at all. If the negative float is accurate with regards to a critical or contractual date, the project manager may request an explanation and corrective action plan.

From the Edwards PDF guide

8

High duration

5% of incomplete activities with a baseline duration greater than 44 days

Part of the planning process is decomposing work packages to a level where the activities are discrete enough to track and manage. DCMA considers any incomplete activity with a baseline start date within the detailed planning period or rolling wave and a baseline duration of greater than 44 days (about 2 working months) to be in violation of this metric.

Activities beyond this duration make it difficult to objectively estimate resources and assess performance. In cases where an activity cannot be broken down further, the project manager should have an articulable method of performance assessment. The DCMA threshold for high duration is 5% of incomplete activities.

From the Edwards PDF guide

9

Invalid dates

Zero. The threshold for this metric is zero

The invalid date check applies only during execution of the project. This may affectionately be referred to as the DeLorean rule, for those Back to the Future fans. A task is said to have invalid dates if it has forecast start/finish dates in the past or actual start/finish dates in the future, with respect to the project status date.

The threshold for this metric is zero. Tasks which have not yet started or completed must be pushed beyond the status date, and tasks which have started or completed early must be revised with the actual start/finish dates on which they occurred. This is one of the more critical metrics, as tasks that violate this call into question the validity of the rest of the schedule.

From the Edwards PDF guide

10

Resources

No threshold given. One of the more flexible metrics

Ideally, all project schedule activities should have costs or resources assigned to them. In practice, not all organizations resource load their project schedules. Additionally, there are occasions where tasks with durations greater than zero are representative of time but have no work associated with them, such as procurement lead-time or customer review of deliverables.

This is one of the more flexible metrics of the 14-point assessment. In the case of organizations that resource load their schedules, it is still a good metric to evaluate to ensure no activities were missed during the resource estimation process.

From the Edwards PDF guide

11

Missed tasks

5% of the projected complete tasks

The missed tasks metric is indicative of schedule performance against the baseline plan. It is the percentage of tasks which have a baseline finish on or before the project status date, which have actual or forecast finish dates later than their baseline finish dates.

It does not include tasks which are currently forecasting late if those tasks have baseline finish dates after the status date. In that way, it is purely retrospective. The DCMA threshold for missed tasks is 5% of the projected complete tasks, though recovery at a certain point becomes unlikely after a project falls too far behind.

From the Edwards PDF guide

12

Critical path test

Pass or fail. The project finish should slip by a commensurate amount

The critical path test is a Boolean pass/fail metric intended to evaluate the integrity of the network logic in the schedule. This test is performed by first identifying the critical path in the schedule, and then intentionally introducing some amount of schedule slip to the first task on the path.

If a commensurate amount of schedule slip occurs on the project finish milestone, the test has been passed. A failed test is indicative of missed dependencies and requires deeper analysis of the network logic.

From the Edwards PDF guide

13

Critical Path Length Index (CPLI)

Below 0.95 indicates a potential issue requiring further investigation

The Critical Path Length Index (CPLI) is a measure of required schedule efficiency to complete a project or critical milestone. It is something of a schedule counterpart to the To-Completion Performance Index (TCPI).

It is defined as the duration from now to the baseline finish of task/milestone being measured (number of working days on the critical path) and total float, divided by the same duration without float. Total float in this instance is the variance between the current forecast and baseline finish date of the task/milestone projected finish date.

A CPLI of 1.00 indicates that the project must execute exactly to plan to achieve the task/milestone. A CPLI above 1.00 indicates that there is a remaining schedule margin, while a CPLI below 1.00 indicates that the team must overachieve to meet the baseline finish date. DCMA considers a CPLI below 0.95 to be indicative of a potential issue requiring further investigation.

From the Edwards PDF guide

14

Baseline Execution Index (BEI)

Below 0.95 indicates a potential issue requiring further investigation

The final metric, Baseline Execution Index (BEI), is another indicator intended to measure performance against the baseline plan. Put differently, it measures the throughput with which the project team is accomplishing tasks. DCMA defines two calculations, cumulative and hit task.

The cumulative calculation is calculated by dividing the total number of tasks that have completed regardless of baseline by the sum of tasks without a baseline date and tasks with a baseline finish date on or before the current reporting period (status date). A BEI of 1.00 indicates the project team is executing on plan, with greater than 1.00 indicating ahead of schedule and below 1.00 indicating behind schedule. DCMA considers a BEI below 0.95 to be indicative of a potential issue requiring further investigation.

The hit task ratio is the total number of tasks baselined to have been completed in a period or on or before the status date that has been completed. The hit task ratio will never exceed 1.00 but can certainly be lower if baseline performance is not being achieved.

From the Edwards PDF guide

Take note. While satisfying these guidelines doesn't necessarily mean the schedule is feasible, not satisfying them almost certainly means it is not.

Check your schedule

Type in counts from your scheduling tool and see each one next to the thresholds in our guide. Nothing is sent anywhere. Your numbers stay in this browser.

Informational only. Not an official checklist or assessment. For general information only. This page, the checker, and the printouts are not an official DCMA, Department of Defense, or government checklist, tool, or guidance, and are not endorsed by DCMA. Results are not an assessment, certification, or finding of compliance by Edwards or anyone else, and should not be submitted or presented as one. Always follow your contract and your government customer's requirements.

Size of the schedule
Links and constraints
Float, durations, and dates
Performance against the baseline
Critical path

12Critical path test

Your results

Enter your counts to see results.

    Result for each of the 14 checks
    CheckYoursThresholdResult

    For general information only. This page, the checker, and the printouts are not an official DCMA, Department of Defense, or government checklist, tool, or guidance, and are not endorsed by DCMA. Results are not an assessment, certification, or finding of compliance by Edwards or anyone else, and should not be submitted or presented as one. Always follow your contract and your government customer's requirements.

    Managing schedule quality

    A project schedule, when well-constructed and maintained, is an indispensable tool to aid a PM in managing and directing project work.

    Developed in response to the Electronic Industries Alliance (EIA) standard 748 for Earned Value Management Systems (which is maintained by the National Defense Industrial Association (NDIA) and accredited by SAE International), the DCMA 14 Point Assessment was last formally published in 2012 through the Earned Value Management System Program Analysis Pamphlet (PAP) identified as DCMA-EA PAM 200.1.

    The 14 Point Assessment has been decoupled from Earned Value Management, and while it may serve as an enabler of reporting earned value, it is no longer viewed as a part of EVM.

    A well-constructed schedule may still be unachievable or incomplete. It should be used as a first pass, requiring failures to be analyzed in greater detail. It does provide an indication of critical path accuracy and requires continuous workstream governance, but does not offer any sort of validation of scope.

    Does that mean the 14 Point Assessment should be disregarded or ignored? Certainly not. Besides, some checks are better than no checks, and automating as many of these as possible frees up analysts to analyze.

    Other standards

    There are plenty of different best practices and industry standards you can draw from to ensure schedule build quality. Contrary to the 14 Point Assessment, the GAO Schedule Assessment Guide recommends limiting and justifying use of soft constraints, ensuring Schedule Risk Assessments are routinely conducted, and development of a corresponding schedule narrative or basis document. NAVAIR has its own 11 Point Assessment document, which differs from the DCMA 14 Point Assessment.

    Is it still used?

    The U.S. Government Accountability Office's Schedule Assessment Guide (GAO-16-89G) describes DCMA using the 14-Point Assessment and says: "DCMA's 14PA thresholds are not compliance triggers. Rather, they are used as a starting point toward an objective analysis of the schedule." Read GAO's page (opens in a new tab)

    The DCMA 14 Point Assessment does not dictate any hard and fast rules for schedule development, rather, it offers a fantastic way to objectively evaluate schedule quality over the life of the project. It would be in the best interest of all project managers to routinely perform this assessment to maximize the likelihood of on-time project performance.

    Sources

    Notice

    For general information only. This page, the checker, and the printouts are not an official DCMA, Department of Defense, or government checklist, tool, or guidance, and are not endorsed by DCMA. Results are not an assessment, certification, or finding of compliance by Edwards or anyone else, and should not be submitted or presented as one. Always follow your contract and your government customer's requirements. The thresholds and explanations on this page are reproduced from our informational guide for convenience. DCMA's own publications are the authority on the 14-Point Assessment.