IPEXIQ · LEARN
DCMA 14-Point · Acumen Fuse · AACE 78R-13 / 38R-06 / 48R-06 · GAO-16-89G

Schedule Quality

Most schedule quality reviews stop at structure: logic, lags, constraints, float. Those checks matter, but a schedule can score perfectly on every DCMA metric and still miss half the scope, ignore the contracting strategy and finish at a date nobody believes. Real quality has three layers - the structure, the content, and the process that built it.

Understanding what the purpose of the schedule is critical in knowing what type of review should apply. The way an EPC Master Schedule is built is drastically different for a Oil and Gas project vs a Built Environment Building project. A client side Level 2 schedule will be much different than a contractor schedule. Again, each of these can't simply be pushed through a formula and recieve an answer to quality

Start reading

Three layers of schedule quality

1 · Structure
Is the network mechanically sound? DCMA 14, Fuse metrics, logic checks. Automated, fast, necessary - but the lowest bar.
2 · Content
Does the schedule represent the scope, strategy and reality of the project? Needs people who know the work.
3 · Process
Was the schedule built to a plan, documented in a basis, and reviewed? Determines whether anyone can trust or maintain it.

Layer 1 · Structural checks

The DCMA 14-Point Assessment is the de-facto structural standard. Thresholds are guidelines, not laws - a schedule failing a metric needs an explanation, not necessarily a fix.

#CheckTypical threshold
1Logic≤5% of incomplete activities missing a predecessor or successor
2Leads0% negative lags
3Lags≤5% of relationships carry a positive lag
4Relationship types≥90% Finish-to-Start
5Hard constraints≤5% of activities with hard constraints
6High float≤5% with total float > 44 working days
7Negative float0% with total float < 0
8High duration≤5% with remaining duration > 44 working days
9Invalid datesNo forecasts before, or actuals after, the data date
10ResourcesAll activities with duration carry resources / cost
11Missed tasks≤5% of baseline-due activities finished late
12Critical path testDelay injected on the CP flows through to project finish
13CPLICritical Path Length Index ≥ 0.95
14BEIBaseline Execution Index ≥ 0.95

A Layer 1 critique - an EPCM schedule is not an erection schedule

The DCMA thresholds were written for short-cycle, site-observable work. Apply them unedited to an EPCM schedule and they start flagging good practice as defects: procurement, contracting, engineering and mobilisation durations are supposed to be long, and contract-anchored milestones are supposed to exist. A pragmatic Layer 1 review therefore reads every failure against what the schedule is for - is it telling the right reality, or is it mechanically tidy and wrong?

Check 8 · High duration ≤ 44 days
Long durations are often the truth
The 44-day limit assumes erection-style work you can stand on site and watch progress on. EPCM schedules are full of work where that logic inverts: procurement from requisition through vendor fabrication to required-on-site, contracting from bid through award to mobilisation, engineering man-hours and vendor data cycles. These legitimately run months, and splitting them into 20-day slices does not add control - it manufactures false progress. What matters is whether the duration is defensible against the estimate or a vendor commitment, not whether it is short.
Checks 1 & 5 · Logic / hard constraints
Milestones sitting on contract dates
EPCM schedules routinely add a milestone as a successor to the critical chain to showcase a contractual completion date, give it no successor of its own, and hold it on a contract constraint. DCMA flags missing logic or a hard constraint - but in an EPCM schedule this is deliberate and often correct practice: it is how the contractual obligation is represented. The review question is not 'remove the constraint', it is 'is this date genuinely fixed, and is the chain driving into it the right one?'
Checks 1-14 · origin
Built for defence IMS, not plant construction
DCMA 14 was developed for US DoD Integrated Master Schedules - work-package discipline, EVMS reporting, short deliverable cycles [4](https://rockstarconsultant.substack.com/p/beyond-the-dcma-14-point-assessment). The buildability, access, authority interfaces, temporary works and trade-sequencing issues that dominate engineering and construction sit largely outside what the framework was shaped for - which is why it works best as a first-pass screen, not a full judgement [2](https://www.somaprojectcontrols.com/resources/guides/reading-a-dcma-14-result-properly/).
Overall · correlation ≠ causation
Passing says nothing about being right
Conforming to the checks does not of itself indicate the schedule is sensible, realistic and achievable - the analyst still has to look at it from a common-sense perspective [5](https://www.mosaicprojects.com.au/WhitePapers/WP1088_DCMA-14-Point.pdf). It was never designed to replace proper schedule QA, and it offers no validation of scope at all [3](https://edwps.com/wp-content/uploads/2016/03/DCMA-14-point.pdf). A failure is a question to investigate; a pass is not a clearance.
Checks 1 & 8 · procurement modelling
Procurement hides in the structure
Deliveries are typically modelled as single-point milestones or fixed-lag activities, which conceals delivery uncertainty and weakens DCMA compliance - the fix is modelling (level-of-effort spans, SS/FF logic), not deleting the durations to game the score [6](https://exa.ai/library/publication/jlmzdgf4fj1). A clean 'high duration' report achieved by shaving fabrication durations makes procurement less integrated, not more.
Checks 1-14 · blind spots
It can only measure what exists
Every metric counts activities that are already in the file. Missing scope, tidy-but-wrong logic between real activities, durations that were guessed, an execution strategy that never made it into the WBS - none of it is visible to any of the 14 checks. The metrics are designed to prompt educated questions, not to answer them [5](https://www.mosaicprojects.com.au/WhitePapers/WP1088_DCMA-14-Point.pdf).

Why layers 2 and 3 exist: there is no native way of looking at a schedule and knowing it accurately reflects the scope and the execution plan - you have to read those documents too, and that is exactly what a content review does. Structure tells you the schedule is well-formed; content and process tell you whether it is the right, honestly-built schedule.

Acumen Fuse & typical logic checks

Tools such as Acumen Fuse extend DCMA with their own metric libraries and a single quality score. They are excellent at finding mechanical defects quickly - and at giving false comfort when used as a pass mark.

Schedule Quality Index
Fuse's weighted roll-up of logic, float, duration and constraint metrics into a single score - useful for trending, dangerous as a pass mark.
Logic density & merge hotspots
Average links per activity, and activities with many predecessors converging - merge points concentrate risk and are under-represented in deterministic dates.
Dangling activities
Start not driven by a predecessor (open start) or finish not driving a successor (open finish), even when the activity has 'a' link of the wrong type.
Out-of-sequence progress
Successors started before predecessors finished - a signal the logic no longer reflects how the work is being done.
Riding the data date
Remaining work stacked against the data date period after period - the classic sign of an un-statused or unrealistic plan.
Calendar & float anomalies
Mixed calendars distorting float, 7-day vs 5-day paths, and float that changes only because of calendar choice.

The limit of structure: every structural metric examines the activities that exist. None of them can tell you about the work that is missing, the logic that is tidy but wrong, or the duration that was guessed. That is the job of a content review.

Layer 2 · Schedule content reviews

Content reviews ask whether the schedule is the right schedule for this project. They cannot be automated - they need planners, discipline leads, construction and commissioning people reading the schedule against the scope, the estimate and the execution plan.

01Does the schedule adequately represent the scope?
Trace the WBS, the scope of work and the estimate line by line to the schedule. Every scope item with budget should have an owning activity or summary; anything missing is invisible to the critical path. A logic check can never find scope that isn't there.
02Is the execution strategy visible?
Contracting strategy, modularisation, construction sequence, area release and commissioning by system should be legible in the WBS and logic. If the contracting plan has five packages and the schedule reads as one, the schedule is not the plan.
03Are the durations defensible?
Durations should tie to quantities and productivity in the estimate, or to benchmarked analogues. Look for round-number durations (20d, 40d, 60d) and identical durations repeated across very different scope - the fingerprints of guessed values.
04Is the logic physically and contractually true?
Clean logic metrics say nothing about whether pipe really follows steel, or whether the vendor data really drives the IFC drawing. Walk the critical and near-critical paths with discipline leads and ask 'is this actually how it will be built?'.
05Are interfaces and third parties represented?
Owner-furnished equipment, permits, approvals, shutdown windows, utility connections, other contractors and the operator's readiness. These are where real delays come from and where schedules are thinnest.
06Is procurement integrated, not appended?
Requisition, bid, award, vendor data, fabrication, FAT, shipping and required-on-site dates tied to the install activities. A procurement schedule held separately hides the most common driver of construction delay.
07Does completion reflect commissioning and handover?
Mechanical completion by system, pre-commissioning, commissioning, start-up and handover sequencing. Schedules built in area / discipline structure often stop at 'construction complete' and miss the system turnover that actually defines finish.
08Are resources and cost credible over time?
Peak manpower vs camp and site capacity, crane and laydown limits, labour availability and the resulting S-curve shape compared with benchmarks. A front-loaded or impossible peak is a content problem no structural metric flags.
09Is the critical path the one the team expects?
If the calculated critical path surprises the project manager, either the logic or the team's understanding is wrong. Either way, it needs a conversation.
10Are risk and contingency treated explicitly?
Weather, productivity and known risks either modelled in schedule risk analysis or held as visible schedule contingency - not buried in padded durations.

Layer 3 · The schedule development process

How the schedule was built is a quality attribute in its own right. A schedule with no development plan and no basis document is a black box: it may be right, but nobody can prove it, maintain it or defend it in a claim. The two documents bookend the build - the plan says how it will be built, the basis records what actually went in.

Schedule Development Plan (before)

Defines how the schedule will be built: purpose and class, level of detail, WBS / CBS alignment, coding structure, calendars, activity identification rules, duration sources, who provides input, review and approval steps, and how contractor schedules integrate. Written before activities are built.

  • Was there a plan at all?
  • Was it agreed by the people who must supply input?
  • Was the schedule actually built to it?
Basis of Schedule (after)

Documents what actually went into the schedule: scope included and excluded, key assumptions, execution strategy, duration and productivity sources, calendars, constraints and why they exist, critical path narrative, risks, contingency, and deviations from the development plan.

  • Can a new planner rebuild the reasoning from it?
  • Is every hard constraint explained?
  • Are exclusions stated - not discovered later?
Review & validation

Structural checks (DCMA / Fuse), a content review by discipline leads and an independent reviewer, a constructability review, and schedule risk analysis - each recorded with findings closed out before the baseline is approved.

  • Who reviewed it, and when?
  • Were findings tracked to closure?
  • Was the baseline formally approved?

Standards & references

Guidance on content review is thin compared with structural metrics. The references below are the ones that go beyond structure - AACE 78R-13 and 48R-06 and the GAO guide's "comprehensive" and "credible" criteria are the closest the industry has to a content standard.

AACE RP 78R-13
Original Baseline Schedule Review - Educational Guideline
The closest AACE comes to a content review: reviews the baseline against scope, contract, execution approach and reasonableness - not just structure.
AACE RP 48R-06
Schedule Constructability Review
A structured review of whether the schedule can physically be executed as drawn - sequence, access, resources and site constraints.
AACE RP 38R-06
Documenting the Schedule Basis
Defines the content of a Basis of Schedule: scope, assumptions, exclusions, constraints, calendars, critical path narrative and risks.
AACE RP 91R-16
Schedule Development
Sets out the schedule development process end to end - effectively the content of a schedule development plan.
AACE RP 27R-03
Schedule Classification System
Ties expected schedule maturity and content to project phase (Class 5 to Class 1).
AACE RP 53R-06
Schedule Update Review
Extends review to each update: progress validity, logic changes and forecast reasonableness.
GAO-16-89G
Schedule Assessment Guide
Ten best practices grouped as comprehensive, well-constructed, credible and controlled. 'Comprehensive' (capturing all work) and 'credible' (risk analysis, horizontal/vertical traceability) are content tests.
NDIA PASEG
Planning & Scheduling Excellence Guide
Practitioner guidance including schedule health and the qualitative checks that sit behind the metrics.
PMI Practice Standard for Scheduling
Schedule model assessment
Assessment checklist covering both required components and good-practice behaviour of the schedule model.
DCMA 14-Point Assessment
Earned Value Management System Program Analysis Pamphlet
The structural baseline every schedule tool reports against. Originally a defence procurement screen (DCMA-EA PAM 200.1, 2012) - a first pass that flags questions, never a full quality judgement.
SOMA Project Controls (2026)
Reading a DCMA 14 Result Properly
Practitioner critique: what each metric actually catches, which metrics mislead more than they help, and how to write a credible review report instead of pasting the dashboard.
Bob Panic (2026)
Beyond the DCMA 14-Point Assessment
Whitepaper on the application limits of DCMA 14 in engineering and construction projects: completeness, logic quality, traceability, critical-path validity, risk and schedule governance.
CII PDRI
Project Definition Rating Index
Not a schedule spec, but scores the definition of the project schedule, execution approach and contracting - the upstream inputs a content review relies on.