What a planning & scheduling engagement looks like — methodology walkthrough

How this piece is framed

This is not a write-up of a specific past project. Schedule assurance work typically sits inside live commercial relationships — contractor versus client, or main contractor versus subcontract — and naming the programme would identify the parties to anyone who knows the sector. Rather than thread that needle, we have written this as a methodology walkthrough: what a planning engagement looks like in shape, what we do at each stage, what the evidence has to survive, and what we explicitly do not do.

For the underlying technique — logic density, float discipline, the DCMA 14 metrics and what each one actually tells you — see our guide to reading a DCMA 14 result properly, which sits inside the wider infrastructure topic hub. This piece is the operational counterpart: what an engagement actually involves week-by-week, not what the metrics are.

Engagement shape

A typical planning and scheduling engagement falls into one of four scopes, often in combination. Baseline review — independent assessment of a proposed baseline schedule ahead of contract award or gate approval, focused on whether the network can actually carry the activity it is being asked to carry. DCMA 14-point assessment — a structured health check against the Defense Contract Management Agency’s 14 schedule integrity metrics, with each fail or borderline result interpreted in the context of the specific schedule rather than treated as an abstract scorecard. Schedule integrity audit — a deeper diagnostic on a live schedule that is producing reports the project team no longer trusts, looking at logic completeness, float behaviour, constraint use, progress discipline and forecast reliability. Primavera P6 implementation support — standing up the tool properly on a programme that is either new to P6 or has inherited a P6 environment that has drifted, with the global data, enterprise structure, layouts and reporting cadence set up to support the project rather than to fight it.

Most engagements blend two or three of these. A pre-award baseline review will typically include a DCMA 14 run; a schedule integrity audit on a struggling programme will often surface P6 implementation problems that need fixing alongside the logic issues.

What we do at each stage

A planning engagement runs in five recognisable stages. Each one produces a specific deliverable; skipping one is how a planning review ends up producing a report nobody can act on.

• Kickoff and scoping — short workshop with the project director, planning lead and (where relevant) the contractor’s planner to confirm scope, audience, the contractual context (NEC4, FIDIC, JCT, MOD ASCEND), the schedule files available, and the decisions the work is supporting. The output is a one-page scoping brief. Most arguments later in the engagement trace back to a missing line in this brief.
• Data gathering — schedule files (XER, XML, native MSP), contract programme, baseline submission, progress updates, change log, risk register, basis of schedule, and prior assurance reports if any. We read the schedule before we open the tool — the basis of schedule and the activity coding rationale tell you more about the credibility of the network than any metric does.
• Diagnostic — the DCMA 14 metrics run, plus the qualitative checks that the metrics do not capture: critical path realism, calendar discipline, constraint use, progress override behaviour, float distribution shape, and the relationship between the logic network and the WBS. A schedule can pass 13 of the DCMA 14 metrics and still be unfit for purpose if the critical path is an artefact of a hard-coded milestone.
• Reporting — a written assessment with each finding ranked by impact on the delivery confidence position. Findings are separated into structural issues (the network cannot do what it is being asked to do), discipline issues (the network could be fit for purpose but is not being maintained that way) and presentational issues (the schedule produces reports that obscure rather than reveal). The recommendations are sized to the gap, not to the available budget.
• Remediation support — where the engagement extends past the diagnostic, supported re-baselining, logic clean-up, P6 environment fixes, or coaching with the in-house planner. We do this alongside the project team rather than instead of them — a remediated schedule that nobody on the project understands is worse than the original.

What good evidence looks like

A defensible planning assurance product satisfies three audiences. The project director needs to know whether the schedule is telling the truth about delivery — and if not, where the gap is. The contractual reviewer (NEC4 supervisor, FIDIC engineer, IPA gateway team) needs structured evidence that the schedule meets the contractual integrity standard — logic-driven critical path, sub-clause-compliant progress mechanism, traceable change history. The planner who built the schedule needs to recognise the assessment as fair — a planning review the in-house team rejects stops being useful as a governance tool.

In practice that means running the DCMA 14-point assessment to its actual specification — logic density, leads, lags, relationship types, hard constraints, high float, negative float, high duration, invalid dates, resource loading, missed tasks, critical path test, critical path length index, baseline execution index — with each metric reported as a number and a narrative. A schedule with 9% open ends is not the same problem as one with 22%, and a planning report that just lists colour codes against thresholds is doing only half the work.

Where the work supports a contract action (acceleration claim, extension of time, compensation event challenge, gateway review), the report is structured so that the headline finding, the methodology, the schedule extract and the metric run are each self-contained and traceable. That way a contractual reader can audit the chain from a single sub-clause back to a specific activity in the network without taking a guided tour.

What we don’t do

It is worth being explicit about scope limits. We do not act as the contractor’s programme manager — we work alongside the planning function on the client side, or as an independent reviewer; we do not own the delivery commitment. We do not sign off the schedule as fit for purpose if our diagnostic shows it is not — we tell the client what would have to change, but the sign-off remains with the accountable party. We do not draft contract notices on behalf of a client or contractor — a delay analysis can inform a notice, but the notice itself is a commercial document that sits with the appropriate authority. And we do not perform forensic delay analysis for litigation as an expert witness role unless that is the scope explicitly agreed at engagement — the discipline and reporting requirements are different and conflating them weakens both products.

This matters because the failure mode in independent planning assurance is drift. A reviewer who starts rebuilding the schedule on their own laptop, or whose DCMA 14 commentary turns into a critique of the contractor’s strategy, has stopped being independent — and the assessment stops being usable at contractual challenge. Staying inside the planning remit is what makes the independence credible.

How engagements typically run

A planning engagement runs in one of three sizes. A four-week engagement — single schedule assessment, DCMA 14 run, written report, working-session debrief. Right-sized for a focused decision point: a pre-award baseline check, a gateway readiness assessment, or a sanity check on a contractor schedule that has just become contentious. A four-week run is enough to produce a credible independent assessment; it is not enough to rebuild a schedule from scratch on a programme where the planning maturity is low.

An eight-week engagement — the typical shape for a more substantial piece of work. Baseline review plus DCMA 14 plus a P6 environment assessment, plus a structured remediation plan and a coaching pass with the in-house planner. This is the shape that suits programmes coming out of a gateway with planning recommendations attached, or contractors preparing a re-baseline submission they need to defend.

Ongoing retainer — monthly or quarterly schedule reviews against a live programme, with the planning lead supported through update cycles, change cycles and reporting cycles. The assurance stops being a one-off document and becomes a maintained discipline that tracks schedule integrity as the programme moves. This is where planning assurance earns its keep on a multi-year programme — a frozen baseline review from sanction loses value within six months; a maintained discipline continues to inform governance throughout delivery.

Most engagements that produce real change are a defined Phase 1 (four or eight weeks) plus a Phase 2 retainer at a lower cadence. Engagements that stop at the report typically see the discipline drift back within two quarters, because the operating model after the report is unchanged.