Why the comparison gets confused
CADMID and PRINCE2 frequently get compared, and the comparison usually goes badly. The two are not direct alternatives. CADMID is the lifecycle the UK Ministry of Defence applies to acquiring military equipment: it sets out the phases an acquisition programme moves through and the investment decisions that govern the transitions between them. PRINCE2 is a generic project-management method: it sets out how to organise, control and assure any individual project, regardless of what is being delivered.
The confusion comes from the word "phase". CADMID has six phases. PRINCE2 has management stages. The words sound interchangeable but they describe different things. CADMID phases are externally enforced and tied to investment approval — a programme cannot pass from Concept to Assessment without a Main Gate decision and, on Major Projects, an IPA Gateway Review. PRINCE2 stages are internally defined by the project board for control purposes; the project itself chooses how many to have and where to put the stage boundaries.
On a real UK defence programme the two often run together. The programme moves through CADMID phases; an individual project inside the programme — say, the integration of a new combat system into a platform — may be managed using PRINCE2. The CADMID lifecycle says when the programme has to be ready for Main Gate; PRINCE2 says how that particular project is being controlled to be ready. They do not compete. They do different jobs.
CADMID in one paragraph
CADMID is the UK MoD's six-phase acquisition lifecycle: Concept (defining the requirement), Assessment (option analysis and full business case), Demonstration (development, integration and test), Manufacture (production and acceptance), In-Service (operational sustainment, often spanning decades), and Disposal (decommissioning and asset disposition). Each transition between phases is governed by a Main Gate decision and, for programmes on the Government Major Projects Portfolio, by an IPA Gateway Review. The framework is owned and operated by Defence Equipment & Support (DE&S) and the Submarine Delivery Agency (SDA) inside the MoD.
PRINCE2 in one paragraph
PRINCE2 (PRojects IN Controlled Environments, version 2) is a project-management method originally developed by the UK government and now owned by PeopleCert (formerly AXELOS). It defines seven principles, seven themes, and seven processes that govern how an individual project is started up, directed, controlled and closed. It is sector-agnostic and is used across government, infrastructure, IT and commercial work. It is explicitly designed to be tailored to project context — the method is a framework, not a rulebook, and the project board chooses how it is applied.
Where they overlap (and where they don't)
The overlap is real but narrow. Both frameworks emphasise stage- or phase-based control with explicit decision points between increments of work. Both expect a documented business case that is revisited at boundaries. Both expect risk to be managed actively with named owners. Both expect change to flow through a controlled process rather than being absorbed silently into the baseline.
The differences matter more. CADMID is externally enforced — a programme does not get to choose whether to comply, and the gateway criteria are owned outside the programme by IPA and the MoD's own assurance machinery. PRINCE2 is internally tailored — the project board decides which themes and processes apply, how heavily, and what gets streamlined. CADMID is whole-life and decades-long; PRINCE2 is project-bounded and finishes when the project closes. CADMID has prescriptive controls expectations at each phase — QRA at Concept and Assessment, EVMS at Demonstration and Manufacture, through-life cost In-Service — that PRINCE2 deliberately leaves to the project to define.
The most useful way to hold the two in the same head is: CADMID describes the lifecycle the MoD applies to its equipment acquisitions; PRINCE2 describes a way of managing any one project inside it. The two are not in tension — they are at different altitudes.
Controls implications under CADMID that PRINCE2 does not set
CADMID is opinionated about what the controls function must produce at each phase. At Concept the requirement is option-level QRA, a Class-5 cost estimate with reference-class comparison, and a risk register structured to support option comparison. At Assessment the requirement steps up to a Class-3 estimate, integrated QCSRA, and a full business case that satisfies HM Treasury Green Book optimism-bias scrutiny. At Demonstration the Performance Measurement Baseline is established and EVMS reporting begins. At Manufacture the EVMS becomes the primary financial reporting framework and SSRO cost-reporting applies on non-competitive contracts above the threshold. In-Service brings through-life cost modelling and reliability-driven sustainment forecasting. Disposal brings its own cost estimating and regulatory risk, particularly on platforms with radiological or environmental legacy.
PRINCE2 is silent on most of this by design. The method tells a project board to manage risk, but it does not specify QRA methodology or confidence-level expectations. It tells a project board to manage cost, but it does not specify an Earned Value framework. It tells the board to assure quality, but it leaves the actual quality regime to the project. That silence is appropriate — PRINCE2 is sector-agnostic — but it is also why PRINCE2 alone is insufficient on a defence programme. The CADMID overlay specifies what the project controls function actually has to deliver; PRINCE2 governance can describe how those deliverables flow through the project board.
How they coexist on a real programme
On a typical UK defence programme the picture looks like this. The programme — say, a new platform acquisition — sits on the CADMID lifecycle. Senior Responsible Owner reports to the MoD Investment Approvals Committee through the Main Gate process. IPA Gateway Reviews provide independent assurance at the major decision points. Inside the programme, there are projects — software integration, supply-chain development, training and support delivery — each of which may be run using PRINCE2 (or any other defensible method). The project boards report into the programme. The programme reports into the CADMID gate.
The interface that matters is at the project-to-programme boundary. Project-level controls have to feed programme-level controls without loss. The schedule from the PRINCE2-managed project has to integrate with the master programme schedule used at gateway. The cost reporting from the project has to feed the integrated EVMS at programme level. The risk register at the project has to feed the QRA at programme level. Getting that interface right is what the controls function on the programme actually does. Getting it wrong is why projects appear green and the programme as a whole is red.
Which one applies to you
If you are running an MoD acquisition programme, CADMID applies whether you want it or not. The lifecycle is externally enforced and the gateway machinery will be applied. The choice you have is how the controls function inside that lifecycle is structured.
If you are running an individual project — including a subcontract delivering into a CADMID programme — PRINCE2 is one of several defensible methods. APM Body of Knowledge, the IPA Project Routemap, or a tailored client-specific method may be the right choice instead. The selection should be made on what the project board and the client actually expect to see, not on what is most familiar.
If you are inheriting a controls function on a defence programme, the question to ask is not "which framework are we using" but "what does the next gateway require, and what does the controls evidence have to show". The frameworks are means; the evidence is the end.
How SOMA helps
SOMA Project Controls works on defence and government programmes through three repeating engagement shapes: independent Quantitative Risk Analysis on Concept and Assessment-stage business cases where the team needs a defensible contingency figure that will withstand IPA and SSRO scrutiny; EVMS implementation reviews on Demonstration and Manufacture contracts where the reporting is technically compliant but operationally disconnected from delivery; and IPA gateway readiness reviews on long-running programmes. The work is delivered by senior practitioners who have led controls on UK infrastructure, water, nuclear and defence programmes, and who treat the controls function as an intelligence function for the Programme Director rather than a reporting overhead. Where PRINCE2 or another method is being applied at project level inside the programme, we work to make the project-to-programme interface produce evidence that survives gateway review.