DCMA 14-Point Schedule Assessment: Complete Construction Scheduling Principles Guide

A clean-looking Gantt chart can hide fatal structural flaws: open-ended tasks, hard-coded dates, and phantom float that shatter your timeline mid-build. The DCMA 14-Point Schedule Assessment is the global benchmark used by owners, lenders, and project controls engineers to verify whether a construction schedule is mathematically sound, claim-defensible, and capable of forecasting true completion dates.

Table of Contents ▾

1. What Is the DCMA 14-Point Schedule Assessment?

Originally created by the U.S. Defense Contract Management Agency to audit large-scale defense and infrastructure programs, the DCMA 14-Point Schedule Assessment has become the gold standard across commercial and civil construction for validating Critical Path Method (CPM) baselines and progress updates.

Its core principle is unambiguous: a construction schedule is a dynamic mathematical network, not a static drawing of bars. Whenever concrete delivery slips or excavation hits rock, the schedule must automatically ripple that impact into downstream trades, the completion milestone, and your Earned Value S-Curve (EVM).

Golden Rule for Tenders & Delay Claims

Passing all 14 DCMA checks doesn’t automatically build the project on time—but failing them guarantees your schedule cannot forecast reliably or stand up in an Extension of Time (EOT) dispute.

2. Complete Matrix of the 14 DCMA Metrics & Official Thresholds

Use this reference table to audit your project baseline before mobilization and during every weekly or monthly update cycle:

# DCMA Metric What It Audits Target Threshold
01 Logic Incomplete tasks missing a predecessor and/or successor (open ends). ≤ 5%
02 Leads Negative lags that distort float and create illogical overlaps. 0% (none)
03 Lags Positive lags (e.g., curing waits) used instead of explicit tasks. ≤ 5%
04 Relationship Types Share of Finish-to-Start (FS) links vs. SS, FF, or SF links. FS ≥ 90%
05 Hard Constraints Fixed dates (Must Start/Finish On, Finish No Later Than). ≤ 5%
06 High Float Incomplete tasks with total float exceeding 44 working days (~2 months). ≤ 5%
07 Negative Float Tasks whose early dates are already later than contractual late dates. 0 tasks
08 High Duration Incomplete tasks longer than 44 working days (insufficient detail). ≤ 5%
09 Invalid Dates Forecast dates in the past or actual dates in the future vs. Data Date. 0 tasks
10 Resources Tasks with duration (> 0) loaded with cost, budget, or labor units. 100%
11 Missed Tasks Tasks completed later than their baseline finish date. ≤ 5%
12 Critical Path Test Adding +600 days to a critical task must push completion by +600 days. Pass
13 CPLI Critical Path Length Index: efficiency required to hit completion date. ≥ 1.00
14 BEI Baseline Execution Index: actual task completion rate vs. baseline. ≥ 0.95

3. The 4 Practical Engineering Pillars Behind DCMA

A. Network Logic Integrity (Points 1–5)

  • No dangling tasks: Only Project Start lacks a predecessor and only Substantial Completion lacks a successor. Every trade in between must drive downstream work.
  • Zero Leads (0%): Instead of forcing overlaps with FS -5d, break work into zones or floors (Floor 1, Floor 2, Floor 3) connected by clean Finish-to-Start (FS) links. This satisfies both Point 2 (0% leads) and Point 4 (≥ 90% FS).
  • Hard Constraints ≤ 5%: Pinning arbitrary dates overrides CPM math and hides emerging slippage until recovery is too expensive.

B. Float Health & Granularity (Points 6–9)

  • Actionable durations (≤ 44 working days): A 120-day block labeled "MEP Rough-In" cannot be managed on site. Breaking it down by zone and system connects physical progress directly to Unit Price Analysis (APU) budgets.
  • Zero invalid dates: Every update must move unfinished work after the Data Date and ensure no actualized activity carries a future timestamp.
  • High float (> 44 days) as a red flag: Almost always signals a forgotten successor link (such as procurement lead times or closeout inspections).

C. Cost-Schedule Integration (Point 10)

DCMA requires 100% resource or cost loading across all tasks with duration. Without cost-loaded tasks, your S-Curve cannot measure Earned Value (EV), CPI, or cash-flow risk accurately.

D. Predictive Reliability & Execution Discipline (Points 11–14)

The Critical Path Test (Point 12) is the ultimate stress test: add a 600-day delay to any critical task—if the finish milestone does not slip by exactly 600 days, a hidden hard constraint or broken tie is corrupting your schedule.

4. The Two Core DCMA Formulas: CPLI & BEI

Critical Path Length Index (CPLI — Point 13)

$$\text{CPLI} = \frac{\text{CPL} + \text{TF}}{\text{CPL}}$$
  • CPL: Remaining working days on the critical path from the Data Date to forecast completion.
  • TF: Total Float to the contractual finish date (negative when behind schedule).
  • Interpretation: CPLI ≥ 1.00 means on time or ahead. A CPLI = 0.85 means crews must sustain 118% daily efficiency on the critical path just to finish on time; anything below 0.95 signals high delay risk.

Baseline Execution Index (BEI — Point 14)

$$\text{BEI} = \frac{\text{Total Tasks Completed up to Data Date}}{\text{Total Tasks Baseline-Scheduled to Finish by Data Date}}$$
  • DCMA Target: BEI ≥ 0.95.
  • Field Example: If 80 tasks were scheduled to finish by Week 12 and your team closed 64, your BEI = 64 / 80 = 0.80—revealing a growing backlog that will choke finishing trades unless corrected immediately.
Don’t Read BEI Without Critical Path Context

Closing dozens of small non-critical tasks can temporarily boost BEI while the structural path stalls. Always pair BEI with CPLI and Lean Construction’s weekly PPC.

5. 5 Schedule Mistakes That Immediately Fail Audits

  1. Building a bar chart with zero dependencies: Without FS logic, field delays never trigger early warnings on the handover date.
  2. Forcing dates with hard constraints to match the contract: Breaks Point 5 and invalidates the Critical Path Test (Point 12).
  3. Hiding real work inside positive lags: A 15-day lag has no owner, no cost, and no accountability in site meetings.
  4. Updating schedules from memory instead of live field data: Produces invalid dates (Point 9) and disconnected S-Curves.
  5. Isolating the schedule from warehouse and subcontractors: A critical activity without materials or verified crews slips regardless of how clean the Gantt looks.

6. Bringing DCMA Discipline to the Jobsite with STRUKTTO

Traditional scheduling software traps DCMA principles inside heavy office files while site engineers and contractors coordinate over scattered chats. STRUKTTO bridges office scheduling rigor with mobile-first execution:

  • Granular workfronts & activities: Structure every project into trackable workfronts with assigned contractors, target dates, and live completion statuses.
  • 100% budget-to-progress integration (Point 10): Link APU budgets directly to physical progress to monitor live S-Curves, CPI, and SPI.
  • ARLE AI bottleneck alerts: Spot contractors concentrating delays before float turns negative and threatens liquidated damages.
  • Forensic offline field logs: Document weather delays, inspections, and milestones with GPS-stamped daily logs ready for owners and claims defense.
STRUKTTO 2026 • Mobile-First + Web App

Audit your schedules and catch delays before they erode margins

Start with 7 days of full Pro AI access—no credit card required. Connect APU budgets, contractors, warehouse, offline logs, and S-Curves in one place.