Automotive & Embedded
Safety cases and supplier gates run in parallel with the software increments. The release is only as ready as its evidence.
- Automotive SPICE
- ISO 26262
- IATF 16949
- APQP / PPAP
- SAFe
Industries
Every sector governs delivery its own way
The standards below are what a program is actually assessed against in each sector, and what a gate decision turns on.
Energy & Industrial
Capital projects where the contract sets the cadence, long-lead procurement drives the critical path, and handover is a document exercise as much as a physical one.
- FIDIC
- Stage-gate / FEL 1–3
- EPC delivery
- Commissioning & handover
- ISO 55000
Telecom & Digital
Transformation programs where the operating model changes underneath the delivery, and rollout governance has to survive both.
- TM Forum eTOM
- ITIL
- TOGAF
- Agile at scale
Smart Buildings & Government
Fixed go-live dates set by an occupancy or an opening. Systems integration, accreditation, and facilities handover all land in the same window.
- RIBA Plan of Work
- ISO 19650 (BIM)
- Systems commissioning
- Security accreditation
Technology
Portfolios where the plan re-forms every increment, and governance has to inform delivery rather than interrupt it.
- SAFe
- DevOps / DORA
- ISO/IEC 27001
- Product operating model
We do not publish client names or case studies. Program governance means holding a client's cost position, delay analysis and risk register — a firm that publishes those is not one you hand a difficult program to. References are given directly, with the client's consent, when a tender requires them.
Each row is a sector, the reality that governs delivery in it, and the frameworks under which that delivery is assessed.
Bring us the program.
The first conversation costs nothing, and it usually clarifies more than it commits.