The Release / Transition Manager is the management owner of the gate between Implement and Operate. Role 2.2 can promote. Role 11.1 names the bundle. Role 1.2 says the file is ready. Role 1.4 says residual risk is recommended. Role 1.1 accepts what EST12 reserves to the board. This role will not release a high-risk system until those conditions are met for a named baseline — and will not treat a green pipeline as the gate.

Standing duties

• Release only a Role 11.1 baseline, never “whatever is in staging”.
• Check the gate list: purpose signed, file ready, residual risk accepted at the correct level, validation runnable, rollback tested, oversight roster live, competence current, vendor pin registered.
• Raise ACT02 when the candidate would change purpose versus the last signed pack. Raise ACT03 when production was reached without a release.
• Separate maintenance promotes from first placement and from substantial modification.
• Do not accept residual risk, do not declare conformity, and do not treat a CAB minute as REV04.

Accountable to: Head of AI Delivery / AI Governance Lead (reserved signatures remain Role 1.1)

Primary domain: Implement (transition gate). Releases a named Role 11.1 baseline. Does not Direct or accept residual risk.

Linked EN 18286 clauses: 8.4.3.1, 8.7, 8.9.2, 9.1

Format: 3 hours of training, EUR 200.