DCMA 14-Point Schedule Check: What It Catches and What It Misses

The DCMA 14-point schedule assessment — originally a US Defense Contract Management Agency checklist, now a de facto industry health check — is the most widely cited mechanical test of a construction programme. Teams wave a "pass" like a certificate of buildability. It is not. A programme audit that stops at fourteen points has measured the spreadsheet, not the job.

What the fourteen points actually test

In plain language, the classic suite looks for structural hygiene in the logic network:

• Missing logic and dangling activities (open ends that never push on anything)
• High leads/lags and excessive relationship types that hide duration in arrows
• Hard constraints that pin dates regardless of logic
• Negative and high total float distributions that signal manufactured flexibility
• Invalid dates, incomplete status, and out-of-sequence progress patterns
• Resource and duration reasonableness at a mechanical level

Done honestly, these tests catch programmes that cannot be analysed — files so broken that any critical path they display is optional. On Primavera P6 files especially, a clean mechanical pass is a useful floor before anyone argues about entitlement or recovery.

What a pass does not prove

Passing DCMA does not mean the programme is buildable, commercially honest, or aligned with how the site will actually work. We routinely see files that clear every mechanical gate and still fail the questions that matter to a project director:

Does the driving path match field reality? A programme can have perfect successor coverage and still put fit-out on the critical path while the site is losing sleep over switchgear delivery. The checklist does not know which room is empty.

Is float honest or sequestered? Preferential logic, calendar games, and well-placed "start no earlier than" constraints can keep float metrics inside DCMA bands while parking negotiating position where the client cannot see it. The audit techniques that expose float manipulation sit outside the fourteen points.

Do durations survive a labour histogram? DCMA will not tell you that week 47 implies a peak workforce the site cannot induct or park. Parallel fronts that look fine activity-by-activity become obvious only when you sum them.

Is long-lead equipment a milestone or a chain? Compressing an 18-month transformer pipeline into a delivery diamond will often sail through mechanical checks. The risk is entirely in the chain nobody modelled.

How we use DCMA in practice

Treat the fourteen points as gate zero, not the audit. Workflow that works:

1. Run the mechanical suite (or an equivalent integrity pack) and fix the file until it is analysable. Do not debate commercial findings on a broken network.
2. Re-run the schedule after cleaning constraints and suspect lags in a working copy. The delta between submitted and cleaned completion is often the first honest conversation.
3. Test the narrative against the site — interviews, area tours, procurement status — before accepting the critical path as evidence.
4. Write findings for decisions, not for compliance theatre: which constraints move the contractual date, which packages are fiction, what to fix before baseline acceptance.

On operator-scrutinised programmes, that sequence has mattered more than any percentage score. A Microsoft or Stack baseline review does not grade you on DCMA aesthetics; it grades you on whether the plan will survive contact with procurement and commissioning.

When DCMA is the wrong tool to lead with

Lead with the checklist when the file is obviously broken and you need a neutral language to get repairs funded. Do not lead with it when the dispute is about delay causation, EOT entitlement, or recovery probability — those need logic forensics and contemporaneous records, not a green dashboard. And never use a "passed 14-point" stamp as the reason to skip an independent programme audit before you accept a baseline or pay against a progress claim.

The posture that works

Mechanical health is necessary. It is never sufficient. The shortest useful sentence we give clients: DCMA tells you whether the programme can be analysed; an audit tells you whether it should be believed. If your team only reports the first answer, you are still flying the job on hope.

Nomad SPS runs independent programme audits and schedule health checks across Australia — DCMA-style integrity as the floor, buildability and commercial honesty as the ceiling. If time is your number one factor, talk to us.