Schedule Quality Metrics

Schedule quality metrics describe the broader discipline of assessing whether a programme schedule is fit to be relied upon for forecasting, control and investment decision-making. The DCMA 14-point assessment is the best-known framework, but it is one entry point into a wider set of dimensions that UK major projects routinely assess — including resource feasibility, baseline integrity over time, probabilistic readiness, earned-value compatibility, calendar discipline, and the integrity of the work breakdown structure. Different client organisations apply different combinations of these assessments depending on the contracting framework and the sector convention; a schedule that passes one client's quality bar can fail another's.

On UK infrastructure programmes, schedule quality assessment is often shaped by client-specific frameworks rather than a single standard. Network Rail's project schedule quality requirements (specified within the GRIP and AfA frameworks) extend the DCMA checks with sector-specific tests for possession integrity, route-restriction handling and milestone density. HS2 imposes its own schedule submission criteria covering activity coding, calendar treatment of bank holidays, and constraint use. National Highways' Project Control Framework requires specific WBS conventions and resource-loading patterns. Sellafield's NEC4 schedule requirements layer further checks for time-risk allowance treatment and float distribution. A schedule that passes DCMA can still fail one of these client-specific frameworks, and planners working on multi-client portfolios end up running parallel quality assessments rather than relying on a single standard.

Beyond the structural integrity that DCMA tests, several other dimensions matter for schedule quality and are checked using different tools or manual review. Resource quality covers whether the schedule's resource loading is feasible in light of available crews, plant and supply-chain lead times — a schedule with perfect logic but unachievable resource demand is not a defensible baseline. Probabilistic readiness covers whether the schedule is structured well enough to run a Quantitative Schedule Risk Analysis against it; many otherwise-passing schedules fail this test because they collapse into a single critical path with no preserved parallel work. Baseline integrity over time covers whether the live schedule still resembles the approved baseline — a programme that has drifted into an unrecognisable shape has lost its forecasting reference even if every individual activity passes DCMA. Earned-value compatibility covers whether the WBS aligns with the cost breakdown structure cleanly enough for meaningful EV reporting.

Acumen Fuse remains the most widely-used schedule quality tool on UK programmes, and its scorecard module covers DCMA plus a wider set of metrics including logic density, resource loading quality, plan reliability and change volatility. Deltek Acumen Risk extends this with probabilistic readiness assessment. For organisations not licensed for Acumen, Steelray Project Analyzer and Schedule Inspector cover similar territory at lower cost. Many tier-1 contractor planning teams maintain their own internal schedule quality checklists implemented as Excel macros against Primavera P6 exports, calibrated to the specific client requirements on each contract.

Schedule quality assessment is most commonly invoked at four moments: at baseline submission, where the baseline cannot be accepted without a defensible quality result; at major programme reviews or gateway assessments; when a new party is inheriting a schedule produced by another team, typically at contract handover or after a change of contractor; and ahead of a QSRA, where the Monte Carlo result is only as credible as the schedule structure underneath it. SOMA applies multi-framework schedule quality assessments routinely on independent assurance engagements, layering DCMA as the structural baseline with client-specific dimensions and probabilistic-readiness tests on top. The honest position is that no single framework catches everything; a layered approach catches more.