By Darian Macey, March 24 2026
By Toby George and Darian MaceyĀ
Executive summary
Defence is trying to modernise and rationalise a large, ageing estate while also delivering new capability enabling works. The independent Defence Estate Audit described the estate as large and costly, fast decaying, increasingly irrelevant, and not fit for purpose, with a need to move urgently. [1]
At the same time, Defence is tightening expectations around responsible use of artificial intelligence, including lawfulness, values-based principles (including accountability and explainability), and proportionate controls and oversight across the full AI lifecycle. [2] In plain terms, if Defence is going to use AI to help forecast cashflow, estimate-at-completion (EAC), or portfolio delivery risk, the underlying schedule data needs to be consistent, auditable, and defensible.
A Defence Estate Schedule Specification (DESS) is a practical, delivery-model-agnostic way to standardise the minimum acceptable schedule structure, coding, update discipline, and delay method rules across capital facilities projects, so schedule data can be trusted for contract administration and portfolio decisions. This mirrors what parts of the US Department of Defense have already done through Unified Facilities Guide Specifications and USACE regulations that make an acceptable baseline schedule a precondition for work and progress payments, and require consistent data exchange formats and schedule governance. [3]
The evidence is not theoretical. Public audits show how weak or inconsistent program discipline drives real delay costs, disputes, and settlements. In one Defence facilities case, scope and schedule disputes escalated into claims up to $155 million and repeated deed renegotiations. [4] In another Commonwealth build, the project ran 61 months versus an expected 34 months, and the facility budget increased by 60 per cent. [5] These outcomes are exactly what a schedule specification is designed to reduce.
Why a schedule specification is now a Defence estate issue
Capital facilities schedules are doing two jobs. The first is operational: planning, sequencing, coordinating interfaces, and controlling delivery. The second is governance: supporting payment certification, extensions of time, delay analysis, and portfolio reporting. US DoD schedule specifications explicitly treat the CPM schedule as a management tool for both contractor and government activities, a basis for progress reporting, time extensions, and progress payments. [6]
If the estate is to be reshaped at pace, Defence needs āportfolio-gradeā schedule data. The Estate Auditās premise is urgency and resource reallocation. That only works if Defence can compare projects and make trade-offs using consistent, credible time and cost forecasts. [1]
The responsible AI policy settings add a second pressure: explainability, accountability, traceability, and risk controls. [2] Portfolio analytics that cannot explain why a forecast moved (logic change, scope change, constraint abuse, out-of-sequence progress, missing links) are not suitable inputs to high-consequence decisions.
The DESS concept is aimed at solving this at the root, by standardising schedule logic, updates, and data fields so decisions are auditable and AI-ready across delivery models. īfileciteīturn0file0ī
What a DESS should contain
A DESS is not āmore paperworkā. It is the minimum set of schedule rules that make a CPM schedule usable for contract administration and portfolio forecasting.
USACE policy is blunt: a contractor-prepared schedule must be detailed enough for both contractor management and government administration, must be updated, and failure to enforce schedule requirements is āhighly detrimentalā. USACE also links schedule acceptance to progress payments, and mandates a standard data exchange format to transfer schedule data between systems. [7]
US DoD schedule specifications also make baseline acceptance a condition precedent to starting key work and to processing invoices, and require structured deliverables and update cycles. [6]
A Defence Estate Schedule Specification should adopt the same practical spine, adapted to Australian Defence estate conditions:
A baseline and update regime that is enforceable. For example: baseline submission within a defined period, explicit accept/reject criteria, and consequences for non-compliance that matter commercially (payment hold, re-submission windows). This mirrors UFGS language where baseline acceptance gates demolition or construction start and invoice processing. [6]
A standard coding dictionary and data schema. USACE requires use of a Standard Data Exchange Format coding structure, and UFGS details mandatory coding and structured exports. [8] For Defence, this is where āportfolio comparabilityā is built: WBS, location/precinct tags, asset type, delivery model, and critical government hold points, plus consistent milestone naming.
Defined rules for schedule quality and automated checks. GAO describes why a reliable schedule is foundational and why schedule variance typically precedes cost variance. [9] GAO also documents the DCMA 14-point assessment measures (logic, leads/lags, constraints, float, invalid dates, high duration, resources, critical path tests, and indices such as CPLI and BEI) as a structured way to assess schedule technical quality. [10] A DESS can require a minimum schedule health score at submission and each update, with exceptions explained in the narrative.
Clear delay and change integration rules. A DESS should state what method is used for time impacts (for example, prospective time impact analysis requirements and minimum fragnets), and what is expected for retrospective analysis if matters become disputed. US DoD schedule specifications include explicit clauses for time impact analysis and forensic schedule analysis. [11] Industry guidance such as the Society of Construction Law Delay and Disruption Protocol and AACE forensic scheduling recommended practice can be referenced to frame method selection and evidence discipline, without pretending any one method is universally ācorrectā. [12]
Defined roles and capability uplift. USACE runs training specifically to enforce schedule clauses and technical provisions across thousands of projects. [13] If Defence wants DESS to work, contract managers and third-party project managers will need practical schedule review competence, not just software access.
Case studies showing the cost of inconsistent scheduling and the upside of doing it well
The pattern across public inquiries is consistent: when scope, design, and schedule disciplines are not held together tightly, delays turn into claims, settlements, and ongoing operating costs.
Case study comparison table
| Project | Issue linked to weak schedule disciplineĀ | Impact (time, cost, claims)Ā | Primary sourceĀ |
|---|---|---|---|
| Mulwala Redevelopment Project (Defence propellant facility, Mulwala) | Scope and schedule disputes, slow design progress, repeated deed renegotiations, difficulty establishing enduring solutions to technical and schedule issues | Construction started late; ongoing schedule loss during commissioning; each month of delay estimated at ~$1 million; Defence imposed liquidated damages; contractor claims escalated, eventually seeking up to $155 million; multiple deeds extended deadlines and changed scope | ANAO performance audit on Mulwala [4] |
| Christmas Island Immigration Detention Centre (CIIDC) facility build | Over-ambitious timetable, design not completed before main works tender, abandonment of āhold pointā discipline, extensions of time and adviser contract variations | Practical completion expected in 34 months but elapsed time was 61 months (27 months longer); facility budget increased 60 per cent (from $197.7m to $317.0m), plus multiple EOTs and settlement arrangements | ANAO performance audit on CIIDC [5] |
| EASTROC (Eastern Region Operations Centre), RAAF Base Williamtown (Defence estate project case study) | Users not aware of contractual timetable; late changes after agreed date triggered paid delay and rework | Commonwealth had to pay additional amounts for delay and work caused by late changes, highlighting the transaction cost of weak change control against the time baseline | ANAO Defence Estate Project Delivery report [14] |
| Russell Hill Redevelopment Project (Defence HQ office redevelopment, Canberra) | Program and space planning optimisation supported by managed delivery method and disciplined āmaster cost-plan and programā administration | Construction program reported as 15 months shorter than the original; improved space use avoided a lease requirement and reduced leasing costs by ~ $3 million per year | ANAO Defence Estate Project Delivery report [15] |
Two points matter for DESS.
First, these failures are not just ābad luckā. They show predictable failure modes: missing or unstable baselines, weak hold point discipline, unclear integration of changes into the programme, and insufficiently comparable reporting. [16]
Second, the Russell example shows a realistic upside: better program and scope integration can shorten delivery time materially and reduce recurring costs, in that case via avoided leases. [15]
Quantifying benefits in time, cost, and EAC confidence
EAC confidence is not a vibe. It is the degree to which the forecast āestimate at completionā is supportable by performance to date, commitments, and a credible remaining work plan. In earned value management intent guidance, a properly maintained EAC explicitly depends on visibility into cost and schedule, and integration through WBS and organisational structures, with the schedule providing forecast dates and supporting the estimate to complete. [17]
GAO makes the linkage explicit: cost estimates are not credible if they do not account for schedule slippage, and schedule variances are typically followed by cost variances. [9]
A DESS therefore drives EAC confidence through mechanics, not slogans:
Less time wasted arguing about the schedule itself. DCMA-style structural checks and standard narratives make it faster to see whether a reported slip is real or an artefact of poor logic and constraint abuse. [10]
Earlier detection of delay paths and recovery options. If updated schedules are required and usable, management actions can be targeted, rather than arriving after the critical path has already shifted and the only lever left is acceleration cost. [9]
Reduced claim exposure and settlement costs. Mulwala demonstrates what happens when schedule and scope issues compound and negotiations become deed-driven: delay costs of ~$1 million per month and claims up to $155 million are the scale of downside. [4]
Reduced budget volatility from timetable collapse. CIIDC shows a 27-month schedule blowout and a 60 per cent facility budget increase, with explicit commentary on how the project departed from its own risk strategy due to time pressure and design delay. [5]
The pragmatic claim is not that DESS eliminates overruns. It is that it reduces self-inflicted uncertainty, which is the part Defence can actually control.
A practical two to three project DESS pilot
Defence already manages construction procurements through SEGās infrastructure function, and the CFI branch relies heavily on third-party contract management. [18] That reality makes a pilot more important, not less: the standard has to work when project managers and delivery partners vary.
A pilot should select two to three live CFI projects that deliberately span delivery models and risk profiles, for example: one refurbishment in an operating base environment, one new-build with complex services and commissioning, and one civil or airfield project with weather and access constraints. The pilot should run DESS as a contract annex plus a portfolio reporting extract, not as an optional ānice to haveā.
Success metrics should be specific and measurable:
- Schedule acceptance cycle time: median days from submission to acceptance for baselineĀ and forĀ monthly updates.Ā
- Schedule health trend: DCMA 14-point results (or DESS-defined equivalent) at baseline and each update, plus the rate of unresolved critical failures.Ā [10]Ā
- Forecast stability: variance between forecast completion at each update and actual completion, tracked as a rolling measure (accuracy improves if the schedule is credible and updated honestly).Ā [9]Ā
- Delay governance: proportion of EOT submissions supported by compliant time impact analysis artefacts and accepted without escalation.Ā [19]Ā
- Portfolio extract usability: ability to roll-up standard milestones, critical paths, andĀ cashflowĀ timing consistently across all pilot projects.Ā
Stakeholder engagement needs to be gated, not open-ended. SEG and CFI must co-own the template. Estate service delivery stakeholders must specify what portfolio questions the schedule data must answer. Contractors and head contractors must validate that the spec is buildable and not just written for clause neatness. This is aligned with the broader shift toward documented accountability and explainability in Defenceās responsible AI controls. [20]
Next stepsĀ
If Defence wants schedule data that can support explainable, auditable decisions, it needs to standardise the schedule inputs. A DESS pilot is a low-regret move: small number of projects, defined metrics, and a clear decision point on scale-up. The alternative is to keep paying the hidden tax of non-comparable schedules: slower approvals, noisier forecasts, and higher dispute risk.
ReferencesĀ
[1]Ā Delivering the Future Estate,Ā DefenceĀ Estate Audit ReportĀ
https://newscop.com.au/wp-content/uploads/2026/02/Defence-Estate-Audit-Report-WEB.pdf
[2]Ā [20]Ā Policy Settings for Responsible Use of Artificial Intelligence inĀ DefenceĀ (PDF)Ā
https://www.defence.gov.au/sites/default/files/2026-03/Policy-Settings-for-Responsible-Use-of-Artificial-Intelligence-in-Defence-%5BOFFICIAL%5D.pdf
[3]Ā [6]Ā UFGS 01 32 17.00 20 Cost-Loaded Network Analysis Schedules (NAS)Ā
https://www.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2032%2017.00%2020.pdf
[4]Ā Defence’sĀ Management of theĀ MulwalaĀ Propellant Facility | Australian National Audit Office (ANAO)Ā
https://www.anao.gov.au/work/performance-audit/defences-management-mulwala-propellant-facility
[5]Ā [16]Ā Construction of the Christmas Island Immigration Detention Centre | Australian National Audit Office (ANAO)Ā
https://www.anao.gov.au/work/performance-audit/construction-the-christmas-island-immigration-detention-centre
[7]Ā [8]Ā USACE Engineer Regulation ER 1-1-11 Project Schedules (PDF)Ā
https://www.publications.usace.army.mil/Portals/76/Publications/EngineerRegulations/ER_1-1-11.pdf
[9]Ā GAO-16-89G, Schedule Assessment Guide: Best Practices for Project SchedulesĀ (December 2015)
https://www.gao.gov/assets/gao-16-89g.pdf
[10]Ā GAO-16-89G, Accessible Version, Schedule Assessment Guide, Best Practices for Project SchedulesĀ
https://www.gao.gov/assets/690/687052.pdf
[11]Ā [19]Ā UFGS 01 32 01.00 10 Project Schedule (PDF)Ā
https://www.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2032%2001.00%2010.pdf
[12]Ā Society of Construction Law, Delay and Disruption Protocol 2nd Edition (PDF)Ā
https://www.scl.org.uk/sites/default/files/documents/SCL_Delay_Protocol_2nd_Edition_Final.pdf
[13]Ā USACE Learning Center, PROSPECT course description (Construction Schedule Performance Management)
https://ulc.usace.army.mil/CourseListDetail?CtrlNbr=80
[14]Ā [15]Ā ANAO,Ā DefenceĀ Estate Project Delivery (Report No. 37 1999ā2000) (PDF)Ā
https://www.anao.gov.au/sites/default/files/anao_report_1999-00_37.pdf
[17]Ā NDIA IPMD EIA-748 EVMS Intent GuideĀ
https://www.ndia.org/-/media/sites/ndia/divisions/ipmd/division-guides-and-resources/ndia_ipmd_intent_guide_ver_d_aug282018
[18]Ā MaximisingĀ Australian Industry Participation throughĀ DefenceĀ Contracting | Australian National Audit Office (ANAO)Ā
https://www.anao.gov.au/work/performance-audit/maximising-australian-industry-participation-through-defence-contracting
AACE International, Recommended Practice 29R-03 Forensic Schedule Analysis (TOC/guide PDF)Ā
https://web.aacei.org/docs/default-source/toc/toc_29r-03.pdfĀ
Author: Darian Macey
Darian is a former Engineering Officer with the RAE with tertiary qualifications in Engineering and Project Management. He is a leading practitioner within Australia's NSI sector with previous employment in Government, project management and building contractor organisations.
