What Is the DCMA 14-Point Schedule Assessment? A Plain-English Guide

If you work in government construction, federal contracting, or any project environment where schedule quality is formally evaluated, you have almost certainly encountered the DCMA 14-point assessment. It is the most widely used framework for evaluating whether a construction schedule is well-built and reliable — and it has become a standard reference point even on projects that are not formally subject to DCMA review.

This post explains what the 14-point assessment is, what each check measures, what the standard thresholds are, and why the checks matter in practice.

What Is DCMA and Why Does the Assessment Exist?

DCMA stands for the Defense Contract Management Agency — a United States federal agency that oversees contractor performance on defense contracts. The 14-point schedule assessment was developed by DCMA as a standardized method for evaluating whether a contractor's Integrated Master Schedule (IMS) is a credible, logic-driven model of the project.

The 14 checks are a systematic way to identify the most common schedule quality problems before they cause real harm. The assessment has been widely adopted beyond defense contracting. Commercial GCs, owners, and construction managers use it as a general-purpose schedule quality checklist, and many project-specific scheduling specifications now reference it explicitly.

The 14 Checks — What Each One Measures

Check 1: Missing Logic

What it measures: Activities that have no predecessor, no successor, or both.

Standard threshold: Fewer than 5% of activities.

Why it matters: Every activity in a well-built schedule should be connected to the network through logic relationships. An activity with no predecessor can start at any time — it is floating free of the plan. An activity with no successor has no downstream consequences modeled. Both conditions mean the schedule is not a true network model.

Start and finish milestones are excluded from this check because they legitimately anchor the beginning and end of the schedule.

What to look for: Activities deep in the WBS with no predecessor are often data entry oversights. Activities with no successor near the end of the project may need to connect to a project completion milestone.

Check 2: Leads (Negative Lag)

What it measures: Relationships where the lag value is negative — meaning the successor can start before the predecessor finishes.

Standard threshold: Zero leads allowed.

Why it matters: Negative lags are a schedule modeling shortcut that can hide real logic. They create time travel in the schedule — allowing work to begin before its predecessor is done. This makes the critical path analysis unreliable and creates date calculations that do not reflect real construction sequencing.

In most scheduling specifications, leads are explicitly prohibited. If a lead appears in a schedule, it typically indicates that the correct logic sequence has not been modeled.

Check 3: Lags

What it measures: Relationships where the lag value is positive — meaning there is a waiting period between the end of the predecessor and the start of the successor.

Standard threshold: Fewer than 5% of relationships.

Why it matters: Lags are not necessarily wrong — a concrete cure time, a submittal review period — but excessive use of lags can mask missing activities. A 10-day lag between two activities might mean "we have not bothered to model what happens in those 10 days." Well-built schedules minimize lags and instead model the actual work.

Check 4: Non-Finish-to-Start Relationships

What it measures: Relationships that are not Finish-to-Start (FS) — including Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF).

Standard threshold: Fewer than 5% of relationships.

Why it matters: SS and FF relationships, especially when combined with lags, can create complex schedule logic that is difficult to validate and may not survive out-of-sequence progress. The DCMA position is that most work sequences should be modeled as simple FS relationships. Non-FS relationships require additional scrutiny to confirm they represent genuine construction logic.

Check 5: Hard Constraints

What it measures: Activities with constraint types that override CPM logic — specifically Must Start On, Must Finish On, Mandatory Start, and Mandatory Finish.

Standard threshold: Fewer than 5% of activities.

Why it matters: Hard constraints force an activity to a specific date regardless of what the logic network is telling you. Used sparingly for contractual milestones, they are legitimate. Used broadly, they prevent the CPM engine from doing its job — the schedule is no longer a dynamic model, it is a list of forced dates.

Soft constraints (Start No Earlier Than, Finish No Later Than) are not flagged because they allow the CPM to override them when the logic dictates an earlier or later date.

Check 6: High Float

What it measures: Activities with total float above the threshold — default 44 working days.

Standard threshold: Fewer than 5% of activities exceeding the threshold.

Why it matters: Very high float on a non-critical activity usually means one of two things: the activity is missing a downstream logic link (so the CPM engine sees no urgency to complete it), or the activity was added to the schedule without being properly integrated into the network. Legitimate activities rarely have months of float.

The 44-day threshold is adjustable in Change Inspector to match your contract's specific float requirements.

Check 7: Negative Float

What it measures: Incomplete activities with total float below zero.

Standard threshold: Zero — no negative float allowed.

Why it matters: Negative float means the schedule cannot be executed as planned within the contractual end date. The project is mathematically behind. This is the most urgent signal in the DCMA assessment and is always treated as a critical finding. The cause of negative float needs to be understood — it may be a modeling error, or it may reflect genuine schedule risk.

Check 8: High Duration

What it measures: Activities with planned duration exceeding the threshold — default 44 working days.

Standard threshold: Fewer than 5% of activities exceeding the threshold.

Why it matters: Activities with very long durations are difficult to manage and track. A 90-day activity provides almost no visibility into what is actually happening on the ground. DCMA's guidance is that activities should generally be broken into smaller, trackable units. Milestones are excluded from this check.

Check 9: Invalid Dates

What it measures: Date entries that do not make logical sense — future actual dates, past planned dates for not-started activities, actual starts without a corresponding status, or complete activities with no actual finish recorded.

Standard threshold: Zero — no invalid dates allowed.

Why it matters: Invalid dates indicate data entry errors or P6 status update problems. They corrupt the CPM calculation and make progress reporting unreliable. This is fundamentally a data quality check.

Check 10: Missing Resources

What it measures: Activities that should have resource assignments but do not.

Standard threshold: Fewer than 10% of activities missing resources.

Why it matters: A resource-loaded schedule is a more reliable planning tool than an unloaded one. Resource loading reveals capacity conflicts, allows cost-loading, and provides the basis for earned value calculations. Activities with no resources are cost-invisible and cannot support Earned Value Management. Milestones and Level of Effort activities are excluded.

Check 11: Missed Activities

What it measures: Activities that were planned to finish before the data date but are not yet complete.

Standard threshold: Zero — no missed activities.

Why it matters: This is the most direct measure of schedule execution. An activity whose baseline finish date is in the past should be done. If it is not, the schedule has been missed — and that needs to be reflected, explained, and addressed.

Check 12: Critical Path Length

What it measures: The percentage of schedule activities that are on the critical path (total float ≤ 0).

Standard threshold: Informational — reported but not a pass/fail check.

Why it matters: A schedule where 80% of activities are critical is not a credible model — it suggests the logic network is over-constrained or that float is being artificially suppressed. Conversely, a schedule with very few critical activities may have missing logic that is inflating float across the board. There is no single right number, but outliers warrant investigation.

Check 13: CPLI — Critical Path Length Index

What it measures: CPLI = (Critical Path Duration + Total Float of Critical Activities) ÷ Critical Path Duration. A measure of schedule efficiency on the critical path.

Standard threshold: CPLI ≥ 1.0.

Why it matters: CPLI below 1.0 indicates the project is behind on its critical path — the amount of remaining work exceeds the available time. It is a leading indicator of schedule slippage risk.

Check 14: BEI — Baseline Execution Index

What it measures: BEI = Activities Completed ÷ Activities That Should Have Been Completed by the Data Date. A measure of whether the project is completing work at the planned rate.

Standard threshold: BEI ≥ 0.95.

Why it matters: A BEI below 0.95 means the project is completing activities more slowly than planned. This is an early warning of execution problems that will compound over time. A BEI of 0.80, for example, means the project has only completed 80% of the work it should have by this point in the schedule.

Thresholds Are a Starting Point, Not a Fixed Rule

The DCMA default thresholds — 5% for most checks, 44 days for high float and high duration, ≥0.95 for BEI — are widely recognized standards. But specific contracts, project types, and owner requirements often call for different values.

A simple infrastructure project with a handful of logic relationships might tolerate a higher percentage of lags than a complex multi-prime hospital project. A resource-light schedule might have a different missing resources standard than a fully resource-loaded integrated project schedule.

Change Inspector uses the DCMA default thresholds out of the box, and lets you adjust any of the 11 configurable threshold values to match your contract requirements. The reset button restores DCMA defaults instantly.

Using the Assessment Practically

The DCMA 14-point assessment is most useful when run at every schedule update — not just at baseline submission. Running it monthly gives you a running picture of schedule quality over time. Are violations increasing or decreasing? Which checks are consistently failing? Are new activities being added with proper logic, or are they floating free?

Change Inspector runs the full 14-point assessment on any loaded XER or XML file, with an overall score (0–100), color-coded pass/warning/fail cards for each check, and drill-down violation tables that show exactly which activities are failing and why. The Excel export produces a formatted scorecard with one violation detail sheet per failing check — ready for submission or internal review.