← Blog
Field Model·13 Jun 2026·15 min read

The anatomy of schedule quality: what the DCMA check reveals across a portfolio

Run the DCMA 14-point check across enough programmes and a striking thing emerges: bad schedules don't fail at random. They fail in a recognisable shape — the same handful of checks, in the same order — and those structural failures quietly predict which projects will slip months later. This is a model of that shape, and what the best schedules look like instead.

About this analysis. This is an analytical field model, not a survey of named projects. The figures below are indicative — synthesised from published DCMA / GAO schedule-assessment findings, the long-standing patterns reported across the planning literature, and our own experience scoring programmes. They describe the shape of schedule quality you should expect, not exact percentages from a specific dataset. Where a number is illustrative, we say so. Run the 14-point check on your own file and you'll see your programme's own version of these curves.

The uncomfortable baseline: most schedules fail

Start with the headline every reviewer learns early and every contractor hates to hear: the typical first-submission CPM schedule fails several of the 14 checks. Not because planners are careless, but because the checks measure something most schedules were never built to satisfy — structural integrity strong enough that the CPM engine can calculate honest dates. A schedule built to look right on a wall chart and a schedule built to survive forensic scrutiny are different artefacts, and the gap between them is what the 14 points measure.

The distribution of quality scores across a mixed portfolio is not a bell curve centred on "good". It's a lump sitting low, with a long thin tail reaching up toward excellence that very few schedules occupy.

Where schedule-quality scores actually sit (indicative distribution) 0–20 30–40 50–60 70 85 95+ schedule quality score → share of schedules the lump: 45–65 the rare top decile
Fig 1. Quality scores cluster in the 45–65 band — passable-looking schedules with real structural weaknesses — with only a thin tail reaching the 80+ territory a reviewer trusts on sight. Indicative shape, not a measured sample.

The failure fingerprint

Here is the part that genuinely surprises people the first time they see it laid out. The fourteen checks do not fail with equal frequency. A small number fail constantly; others almost never do. And the order is remarkably stable from one programme to the next, across sectors. This is the "fingerprint" of schedule failure — and because it's consistent, it tells you where to look first on any file you're handed.

The failure fingerprint — how often each check trips (indicative) Missing logic · ≤5% Lags · ≤5% High duration · ≤5% Relationship types · ≥90% FS Hard constraints · ≤5% High float · ≤5% BEI / missed tasks · ≥0.95 Negative float · 0 CPLI · ≥0.95 Leads · 0 Invalid dates · 0 ~66% ~58% ~52% ~44% ~38% ~32% ~28% ~21% ~17% ~10% ~6% Share of programmes exceeding each threshold on a representative submission. Indicative — your portfolio's order may shift, but the top three rarely move.
Fig 2. Missing logic, lag abuse and over-long activities dominate; invalid dates and leads are rare. The structure checks (top) fail far more than the zero-tolerance hygiene checks (bottom) — which is exactly backwards from where most planners spend their effort.

Three things fall out of this fingerprint. First, the top of the list is all structure — missing logic, lags, durations, relationship types, constraints. These are the checks that determine whether the network can compute honest dates at all. Second, the zero-tolerance hygiene checks (leads, invalid dates) are near the bottom — easy to keep clean once you know they exist. Third, and most usefully: if you only have ten minutes with an unfamiliar schedule, you now know the order to look in. Missing predecessors and successors first, every time.

The insight that should change how you review: structure predicts slippage

Now the part that elevates this from a checklist to a forecast. It is tempting to treat the 14 points as a tidiness audit — a way to make a schedule "neat". But the structural checks are leading indicators of delivery performance. Plot a portfolio with structural quality on one axis and actual on-time delivery on the other, and the schedules don't scatter randomly. They fall into two families.

Structural quality vs. delivery — schedules fall into two families (indicative) structural quality (DCMA structure checks) → finished on time → good structure, still late — bad luck or scope on time despite weak structure — got lucky weak structure · finished on time (rare) strong structure · finished late (rare)
Fig 3. The diagonal is the story: weak-structure schedules cluster bottom-left (late), strong-structure schedules cluster top-right (on time). The off-diagonal cases are the exceptions that prove the rule. Indicative — the correlation isn't destiny, but it's strong enough to act on.

Why would the tidiness of a network predict whether the project finishes on time? Because the structural failures aren't cosmetic — each one is a small lie the schedule tells about how the work connects. An activity with no successor can slip without moving the finish date, so the slip goes unmanaged. A lag hides a real duration nobody owns or updates. A hard constraint forces a date the logic can't support, masking negative float. Individually small; collectively, they blind the team to the very slippage the schedule exists to surface. A structurally weak schedule isn't just untidy — it's an early-warning system with the wires cut. The project doesn't slip because the schedule is messy; it slips because nobody could see the slip coming.

The correlation trap. This does not mean a high score guarantees delivery, or that a low score dooms a project — read Fig 3's outliers. A pretty network can still be wrong about the work (see quality vs. accuracy), and a shambolic one can finish on time through heroics. The claim is narrower and more useful: structural quality is the cheapest available leading indicator of schedule risk, available on day one, long before any slippage shows in the dates.

Quality is a trend, not a snapshot

The single most diagnostic thing you can do with the score is not measure it once — it's watch it across revisions. Healthy programmes hold their quality roughly steady update to update; the planner maintains the logic as the work evolves. Troubled programmes show a quietly declining score: open ends creep in, constraints get added to force dates, durations balloon as detail is abandoned. The score decays months before the completion date moves — which is precisely why the trend is worth more than any single reading.

Quality score across monthly updates (indicative) 90 75 60 45 monthly revision → healthy troubled first reported finish slip quality fell here… …the date moved here
Fig 4. On the troubled programme, the quality score starts sliding two to three updates before the completion date is admitted to have moved. The score is the leading indicator; the date is the lagging one. Indicative.

What good actually looks like

It's easy to dwell on failure, so here is the other end. A top-decile schedule — the thin tail of Fig 1 — has a recognisable profile, and none of it is exotic. Logic is complete (open ends only on the genuine start and finish). Lags are rare and named; leads are absent. Over 90% of relationships are finish-to-start. Hard constraints are counted on one hand and each has a documented reason. Activity durations sit comfortably under the two-month line, so progress can be measured honestly. The critical path responds when you test it. And — the tell that separates the genuinely good from the merely tidy — the score holds steady across updates, because someone is maintaining it.

None of that requires talent, only discipline and the habit of checking. Which is the quietly hopeful conclusion buried in all this: schedule quality is almost entirely a maintained property, not an innate one. The portfolios that score well aren't staffed by better planners — they're staffed by planners who run the check every period and fix what it flags.

TraitTypical schedule (the lump)Top-decile schedule
Missing logic10–25% open ends< 5%, only start/finish
Lags & leadsLags common, some leadsLags rare & named, zero leads
Hard constraintsoften > 10%< 5%, each justified
Long durationsMany multi-month bars< 5% over 44 days
Critical-path testOften fails (date won't move)Passes — network responds
Score across updatesQuietly decliningHeld steady, maintained

Methodology — so you can argue with it

In the spirit of the schedules this site exists to scrutinise, here is how the model was built, openly. The failure fingerprint (Fig 2) follows the long-reported pattern in the DCMA 14-point assessment and the GAO Schedule Assessment Guide, in which logic, lag and duration checks fail far more often than the zero-tolerance hygiene checks — the ordering shown is representative, not measured from a named sample. The distribution (Fig 1) reflects the widely-observed reality that first-submission schedules cluster below the threshold most reviewers trust. The structure-vs-delivery relationship (Fig 3) is directional: the GAO guide and NDIA's Planning & Scheduling Excellence Guide both treat structural soundness as a precondition for a schedule being a usable forecast, and the diagonal expresses correlation, not a fitted regression. The decay curve (Fig 4) illustrates the well-known lead/lag between quality erosion and date movement. Every figure is labelled indicative for exactly this reason: the shapes are robust and worth acting on; the specific percentages are illustrative. The most honest thing about schedule quality is that you can measure your own in seconds and stop relying on anyone's model — including this one.

Sources & further reading

  1. U.S. Government Accountability Office — Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G, Dec 2015). The ten best practices behind a reliable schedule; the basis for treating structural integrity as the foundation of a trustworthy forecast. gao.gov/products/gao-16-89g · full PDF
  2. Defense Contract Management Agency — 14-Point Schedule Assessment. Developed from 2005 to standardise DCMA review of contractor Integrated Master Schedules after the IMS mandate for contracts over $20m; the origin of the 14 structural checks used throughout this site. Background: The evolution of the DCMA 14-point assessment (Mosaic Projects).
  3. NDIA Integrated Program Management Division — Planning & Scheduling Excellence Guide (PASEG). Industry best-practice for building and maintaining an IMS, including the Generally Accepted Scheduling Principles (GASP). ndia.org — Planning & Scheduling.
  4. Our own reference: the DCMA 14-point assessment, properly explained — every check, threshold and how to fix it, and the basis for the metrics modelled above.

Key takeaways

See your schedule's own version of these curves

Drop a P6 XER or MS Project file in your browser and get the full 14-point fingerprint, your quality score, and — across revisions — your own decay curve. Nothing is uploaded.

← PreviousThe DCMA 14-point assessment, properly explained