INFRASTRUCTURE
could be adjudicated quarterly, with a stable annual baseline for business-case and procurement planning. Each release should include machine-readable requirements, human-readable change notes, and an impact statement for schemes at different stages. Where evidence is preliminary, the standard should say so. Where schemes cannot adopt a later version without disproportionate redesign, the decision should be explicit rather than hidden in correspondence. This is how a programme remains both configurable and governable: everyone knows which version applies, which local choices are permitted, and what new evidence may change the next one. This would protect the programme from two familiar
Three-layer governance model.
route; measures and review date; observed result; and an assessment of whether the finding is transferable. That is not a lessons-learned library. Libraries accumulate documents. A compact creates an obligation: if a scheme chooses differently, it must say what it expects to improve and how that expectation will be tested. If the result is material, the national owner must decide whether to adopt it, reject it, commission more evidence, or permit it as a bounded option. The decision then appears in the release note for the next version of the standard. The compact must work at three speeds. Fast learning
comes from prototypes, mock-ups, hazard reviews, digital simulations, supply-chain tests, and construction sequencing, while design choices can still move. Operational learning comes from commissioning, staff simulation, defects, energy use, workflow, and early occupancy. Outcome learning follows after sufficient clinical and operational exposure. The programme’s planned 12-to-24-month summative evaluation is necessary, but it is too slow to be the only feedback mechanism when several wave 1 schemes are developing concurrently. Leading indicators should inform live change control; later evaluation should confirm, reverse, or qualify those early decisions. Materiality is essential. Requiring a full record for
Varun Sharma
Varun Sharma is founder and CEO of NEUVIOR, which has led UK-government- funded medicines and technology innovation projects. His work focuses on medicines operations, evidence governance, and accountable data- enabled systems across healthcare and regulated industries.
every minor adjustment would create bureaucracy and encourage formulaic compliance. Thresholds should focus effort on variation that affects safety, clinical function, interfaces, repeatability, cost, carbon, workforce, schedule, or benefits. The record should reuse existing business-case, risk, benefits, and design-assurance data rather than create a parallel reporting industry. Commercial confidentiality is a constraint, not a veto. Detailed supplier information may need protection, but the existence of a variation, its safety and whole-life consequences, its evidence status, and the resulting standard change can usually be reported at an appropriate level. The Construction Playbook’s collaborative model only compounds value when performance information moves across the portfolio. A programme buying at national scale should also buy
the right to reuse learning. The governance body receiving these records should include national technical owners, Trust clinical and estates representation, safety, digital, commercial, workforce, and carbon expertise, with independent challenge for high-consequence changes. Its output should be short and visible: accepted into the core; retained as a bounded option; local exception only; further evidence required; or rejected, with reasons.
A predictable release cadence would make the compact usable. Urgent safety changes should move immediately through controlled notices. Routine evidence
56 Health Estate Journal November 2026
pathologies. The first is frozen standardisation, where early assumptions harden before real hospitals test them. The second is perpetual customisation, where every scheme claims difference and the national platform never matures. A compulsory compact allows the standard to be firm at any given moment and revisable when evidence earns the change.
From slogan to operating model The 11 partnerships are an opportunity to make this architecture real. A signed alliance agreement is an enabling mechanism, not evidence that main works have started or benefits have been realised. The annual report’s March 2026 status data placed Airedale and Frimley at strategic-outline-case assurance and the other nine partnership schemes in outline-business-case development. That is precisely when decision rights, assumptions, and learning obligations should be made explicit – before choices become expensive to reverse. Five deliverables would turn the three-layer model into an auditable system: n a versioned national technical core, with evidence, owners, and change notes;
n a Trust-owned decision charter aligned to business- case gateways;
n a material-variation record using common cost, carbon, safety, workforce, and outcome fields;
n a programme change decision that converts evidence into a new standard, a bounded option, or a rejected exception; and
n published, independent post-occupancy findings connected back to the requirements they test.
None requires abandoning the programme’s present direction. Hospital 2.0 already has standard products, national and local demand assumptions, change control, clinical engagement, an alliance, a Standard Operating Model in development, and a learning framework. The proposal is to join those parts with a public decision-rights and version-control spine. That spine matters because repeatability alone is not learning. Local autonomy alone is not accountability. Evaluation alone is not improvement unless it changes the next decision. The aim is not to prevent variation. It is to stop accidental variation and make useful variation travel. Hospital 2.0 can then be national where sameness creates safety and scale, local where context determines care, and relentlessly programmatic about turning experience into a better next version. Standardise the substrate. Federate the judgement. Mandate the learning.
Disclaimer n The author has no role in the New Hospital Programme, Hospital 2.0 Alliance, NHS England, or any participating NHS Trust.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72
