The DCMA 14-point assessment and the GAO Schedule Assessment Guide both judge whether a schedule can be trusted, but they work at different depths. The DCMA 14-point assessment is a set of 14 numerical checks with pass thresholds, run on the schedule file. The GAO Schedule Assessment Guide (GAO-16-89G) sets out 10 best practices, grouped into four characteristics of a reliable schedule: comprehensive, well-constructed, credible and controlled.
In short, DCMA tells you whether the network is built soundly. GAO tells you whether the schedule, and the way it is managed, can be relied on for decisions. This guide explains what each framework covers, where they overlap, where they differ, and when to use each.
What is the DCMA 14-point assessment?
The DCMA 14-point assessment was developed by the US Defense Contract Management Agency to give a quick, repeatable health check of contractor schedules on defence programmes. It applies 14 metrics to the schedule data, most of them with a numerical threshold, and reports a pass or fail for each. It does not depend on any particular software: it can be run on a Primavera P6 schedule, a Microsoft Project file or any other critical path schedule, either with a schedule-checking tool or with P6 reports and filters.
The 14 checks and their usual thresholds are:
| No. | Check | What it tests | Threshold |
|---|---|---|---|
| 1 | Logic | Incomplete activities missing a predecessor or a successor (open ends) | Less than 5% |
| 2 | Leads | Relationships with a negative lag | 0 |
| 3 | Lags | Relationships with a positive lag | Less than 5% |
| 4 | Relationship types | Share of Finish-to-Start relationships | At least 90% |
| 5 | Hard constraints | Activities with constraints that override logic | Less than 5% |
| 6 | High float | Activities with total float above 44 working days | Less than 5% |
| 7 | Negative float | Activities with total float below zero | 0 |
| 8 | High duration | Activities with a remaining duration above 44 working days | Less than 5% |
| 9 | Invalid dates | Forecast dates before the data date, or actual dates after it | 0 |
| 10 | Resources | Activities with duration but no resources or cost assigned (where the schedule is resource-loaded) | All activities with duration loaded |
| 11 | Missed tasks | Activities that should have finished by the data date under the baseline but did not | Less than 5% |
| 12 | Critical path test | Whether a delay added to a critical activity moves the project finish by the same amount | Pass |
| 13 | Critical Path Length Index (CPLI) | Whether the remaining critical path can achieve the required finish | 0.95 or more |
| 14 | Baseline Execution Index (BEI) | Activities finished against activities planned to finish by the data date | 0.95 or more |
For a fuller explanation of each check and how to fix a failure, see DCMA 14-point assessment explained.
What is the GAO Schedule Assessment Guide?
The GAO Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G) was published by the US Government Accountability Office in December 2015. GAO uses it when auditing the schedules of major federal programmes, and agencies and contractors use it as a reference for building and maintaining schedules. It is a best-practice guide, not a regulation or a software check.
The guide sets out 10 best practices and groups them into the four characteristics of a reliable schedule:
| Characteristic | No. | Best practice |
|---|---|---|
| Comprehensive | 1 | Capturing all activities |
| Comprehensive | 3 | Assigning resources to all activities |
| Comprehensive | 4 | Establishing the duration of all activities |
| Well-constructed | 2 | Sequencing all activities |
| Well-constructed | 6 | Confirming that the critical path is valid |
| Well-constructed | 7 | Ensuring reasonable total float |
| Credible | 5 | Verifying that the schedule can be traced horizontally and vertically |
| Credible | 8 | Conducting a schedule risk analysis |
| Controlled | 9 | Updating the schedule using actual progress and logic |
| Controlled | 10 | Maintaining a baseline schedule |
In a GAO-style assessment, each best practice is scored on a five-point scale (fully met, substantially met, partially met, minimally met or not met), and the scores roll up into a rating for each characteristic. The evidence goes well beyond the schedule file: the work breakdown structure, the schedule basis or narrative, how durations were estimated, how updates are made, how the baseline is controlled, and whether a schedule risk analysis supports the forecast dates.
Where do DCMA and GAO overlap?
Both frameworks want a schedule that is logically sound, realistic and usable for management. Several DCMA checks give direct evidence for GAO best practices:
- Logic: DCMA checks missing predecessors and successors, leads, lags and relationship types. GAO's sequencing practice expects every activity to be linked, apart from the start and finish milestones, with sparing use of lags and constraints.
- Critical path: DCMA runs the critical path test and CPLI. GAO expects a valid, continuous critical path driven by logic rather than constraints, and attention to near-critical paths.
- Float: DCMA flags high float and negative float. GAO expects total float to be reasonable and explained, with high values usually pointing to missing logic.
- Durations and resources: DCMA flags long durations and unloaded activities. GAO expects durations to be estimated from the work and the resources assigned to it.
- Baseline and progress: DCMA's invalid dates, missed tasks and BEI checks test performance against the baseline. GAO's controlled characteristic covers how the baseline is kept and how progress is recorded.
In practice, a schedule that fails DCMA will struggle to rate well under GAO's well-constructed characteristic. A schedule that passes DCMA has cleared a useful bar, but it can still fall short on GAO practices that the 14 checks do not test.
What are the key differences between DCMA and GAO?
| Aspect | DCMA 14-point assessment | GAO Schedule Assessment Guide |
|---|---|---|
| Purpose | Quick, repeatable health check of the schedule data | Comprehensive assessment of schedule quality and schedule management |
| Structure | 14 metrics, most with numerical thresholds | 10 best practices grouped into four characteristics |
| Evidence | The schedule file | The schedule file plus the WBS, schedule narrative, estimating basis, update records, baseline control and risk analysis, often with interviews |
| Method | Largely automated, pass or fail per metric | Analyst judgement against criteria, scored from not met to fully met |
| Output | Scorecard of 14 results | Rating per best practice and characteristic, with findings explained in a report |
| Resources | Checks that activities with duration carry resources or cost | Expects resources to be assigned and their availability and effect on dates to be understood |
| Baseline | Measures performance against it (missed tasks, BEI) | Covers how the baseline is set, controlled and changed |
| Schedule risk | Not covered | Schedule risk analysis is a best practice in its own right |
| Traceability | Not covered | Horizontal and vertical traceability is a best practice in its own right |
| Time to run | Minutes to hours | Days to weeks |
The DCMA checks are objective and fast, but they test structure, not judgement. A schedule can pass all 14 and still have durations nobody believes, a WBS that does not match the scope, or a finish date with no risk analysis behind it. The GAO guide asks those harder questions, at the cost of time and evidence.
Which framework should you apply on your project?
- Use the DCMA 14-point checks for routine quality control: on every monthly update, on each contractor submission, and before a baseline is accepted. They catch missing logic, hard constraints, leads and lags, float problems and invalid dates quickly and consistently.
- Use the GAO best practices when the schedule must be defensible: when a baseline is being set on a major programme, at stage gates, for a funding or board decision, or when a forecast is under challenge. They are also a good structure for building a new schedule and its basis memo.
- Use both together: DCMA as the regular health check and GAO as the periodic deep review. Many teams fix their DCMA failures first, because they are mechanical, then work on the GAO gaps such as traceability, resource realism and schedule risk.
Outside US government work, neither framework is mandatory unless the contract or the client's planning specification calls for it. Both are widely used as reference benchmarks by owners, project management consultants and independent reviewers. An independent schedule review by Project Assure's project planning team typically starts with the DCMA metrics and then tests the schedule against the GAO characteristics, so the client sees both the mechanical faults and the judgement calls.
DCMA is the tactical check on how the network is built. GAO is the strategic framework for whether the schedule, and the process behind it, can be relied on. Knowing which question you are answering tells you which to apply.
