§07bGate AssurancePart 1 of 3
§07bThe gate model
Illustrative model · every programme’s gates differ
Your phases. Your gates. Our engine reads them
A programme advances an asset through phases, each phase through stages, and each stage ends at a gate. The governance is written down. The evidence that a gate was earned is not: it is distributed across months of correspondence, and on a programme of scale a gate releases money.
The model below is illustrative. We do not publish any client’s gate model, and we do not assume yours: it is configured from your own governance.
The anatomy of one gate
- 01Deliverables producedAcross design, cost, programme, risk, and consents.
- 02Reviews and commentsCirculated, answered, and closed out in correspondence.
- 03ValidationThe submission checked for consistency against itself.
- 04ApprovalThe panel decides. The evidence must already be there.
Deliverables
- Mandate and brief
- Options appraisal
- Order-of-cost estimate
Approved by
- Programme board
- Investment committee
Validated against
- Brief traceable to the mandate
- Estimate reconciles to the funding envelope
Configuration
We take in your gate manual, your deliverable schedules, and your delegation of authority, and map them to a gate schema your own team reviews and signs. Revisions are versioned, and a question is answered against the version of the model that was in force at the date in question.
No gate is passed by a machine. The panel decides; the engine’s job is to put the record in front of it. Your record stays yours: held in your own tenancy, and not pooled with any other client’s.