Sovereign capability is most often discussed in the language of acquisition — platforms, facilities, and the transfer of technology and intellectual property onshore. That language is not wrong, but it describes the inputs to sovereignty rather than the condition itself. Sovereignty is not a state achieved at the point of materiel acceptance. It is the enduring capacity to operate, govern, assure, and evolve a complex system through life, under operational conditions and resourcing constraint, without dependence on intervention that the Commonwealth does not control.
This distinction is not academic. It determines whether the investment set out in the Integrated Investment Program converts into deployable, supportable capability — or into delivered materiel that the enterprise cannot independently sustain at the required rate of effort.
Capability is realised in sustainment, not at acceptance
Across Defence and comparable complex programs, a consistent pattern holds. Capability is not sovereign at the point of acceptance into service. It becomes sovereign only where operational control, engineering and capability assurance, and the supporting industrial and workforce structures are established deeply enough to outlast the delivery milestone and the prime’s mobilisation.
This has direct consequences for how a program is structured from first principles. A program optimised to achieve Initial Operational Capability against schedule is not necessarily a program that has built the sustainment system, the technical workforce, and the configuration baseline on which sovereign control depends. The two objectives are related, but they are not the same objective; and where delivery pressure forces a choice between them, sustainment is the one routinely deferred — with the cost surfacing years later, in availability, in obsolescence, and in a dependence on the original equipment manufacturer that is no longer merely a commercial position but a strategic one.
The gap is rarely the technology
In most distressed capability environments, the binding constraint is not technical. The technology has been delivered, or can be. The constraint is the underdeveloped institutional capacity to retain knowledge as personnel rotate, to govern engineering and configuration complexity across the enterprise and its supply chain, and to maintain operational effectiveness without recourse to external parties whose priorities and availability the Commonwealth does not direct.
That capacity is not acquired. It is deliberately built, and it is readily eroded — by workforce turnover, by the dilution of technical authority under schedule pressure, by configuration drift, and by the quiet migration of decision-making toward those who hold the knowledge by default rather than those who hold the accountability by design.
What building sovereign capability actually requires
Treated as an enterprise discipline rather than a delivery output, building sovereign capability requires:
- Integrated engineering, sustainment, and acquisition planning from inception — not sustainment introduced as a transition activity once the design is fixed;
- Resilient industry and supply-chain ecosystems structured for continuity of support, including the deliberate management of single points of dependence;
- Governance structures aligned to enduring operational ownership, not solely to project delivery and milestone closure;
- Deliberate workforce development and knowledge-retention strategies that treat technical mastery as a capability asset to be managed, not an overhead to be minimised;
- Robust configuration management and assurance frameworks that preserve the integrity of the baseline through life; and
- Structured approaches to stabilising and recovering distressed capability environments before degradation becomes irreversible.
In this framing, sustainment is not a downstream support activity to be costed and scheduled after the capability decision. It is a constituent element of sovereignty itself, and it warrants the governance attention and technical authority that the enterprise reserves for acquisition.
The measure of sovereignty
True sovereign capability is demonstrated not by what can be delivered, but by what can be independently sustained, governed, and evolved under real operational conditions and constraint. The acquisition proves what the enterprise can field. Sovereignty is proven by what it can hold — through workforce turnover, through obsolescence, through a contested environment, and through the withdrawal of the support on which the program was originally stood up.
That is the harder test, and it is the one that matters. For those of us accountable for capability through life, it reframes the central question of program governance:
Are we building a program that will pass acceptance — or an enterprise that can still operate, sustain, and evolve this capability once the prime has demobilised, the original workforce has rotated, and the support we assumed is no longer available on our terms?
Chris Lindemann is the developer of the Program Integrity Method: a predictive systems-assurance methodology designed to identify the systemic conditions that historically precede delivery and sustainment failure in complex Defence and infrastructure programs.
Looking back on programs you've worked on, where have you seen the greatest gap between acceptance into service and true sovereign capability—and what caused it?