The gateway review process is a key assurance mechanism designed to provide an objective view of the ability of a programme or project to deliver on time and to budget. It is not part of the programme or project management process. Gateway reviews are managed in NI by the Centre of Expertise for Programme and Project Management (CoE) within Construction and Procurement Delivery (CPD), the local authorised hub.
Risk Potential Assessments (RPAs) must be completed for all programmes and projects. These should be validated by CoE or the head of the departmental programme office and should be sent to the departmental assurance co-ordinator (DAC) at least 12 weeks ahead of an expected review.
Departments may decide on a de minimis cut off point, below which an RPA may not be required, but must do so on the basis of a full understanding of the implications and be accountable for their action. De minimis limits should be approved by the departmental accounting officer in consultation with the head of the appropriate centre of procurement expertise. Where a programme or project is above the de minimis limits an RPA should be completed and forwarded to the DAC for agreement.
RPA forms should be refreshed and resubmitted to CPD at each gateway milestone.
If a risk level of medium or high is indicated in the RPA, the DAC will make arrangements, on behalf of the senior responsible owner (SRO) for a gateway review to take place. The first step will be for the DAC to meet with the SRO and members of the programme or project team. This assessment meeting, typically lasting between one and two hours, will:
- agree the risk assessment as detailed on the RPA
- determine the readiness of the programme or project for a review
- identify necessary skills for potential reviewers
- establish suitable dates for the planning meeting and the actual review
Following the assessment meeting, the DAC will appoint an independent and impartial review team to carry out the review.
The planning meeting is an opportunity for the review team and the programme or project team to meet for the first time. The review team will agree a code of conduct for the review and then agree this with the SRO. The key outputs from the planning meeting are:
- the list of stakeholders to be interviewed
- the list of documents to be made available to the review team
The DAC (or an appointed representative) will attend the planning meeting to ensure compliance with gateway principles and to support both the review team and programme or project team through the process.
A review typically lasts three days. Some high risk reviews will last four days and, where the stakeholder list is unusually short, a two day review may suffice.
For a project, reviews take place at:
- gateway 1 - business justification
- gateway 2 - delivery strategy
- gateway 3 - investment decision
- gateway 4 - readiness for service
- gateway 5 - operations review and benefits realisation
For a programme a series of gateway 0s will be carried out. These typically reflect the programme start, programme delivery and programme close but may vary depending on circumstances. Workbooks are provided for gateway review team members to inform questioning, highlighting areas to probe during each review.
The review is evidence-based and involves interviews with key stakeholders culminating in a report, delivered to the SRO on the final day of the review. This report is confidential to the SRO, containing recommendations based on the review team’s findings. In light of the recommendations, a delivery confidence assessment (DCA) is awarded, indicating the potential for successful delivery.
Delivery confidence assessment
The DCA will range from green to red, defined as:
- green; successful delivery of the programme or project to time, cost and quality appears highly likely and there are no major outstanding issues that, at this stage, appear to threaten delivery significantly
- amber/green; successful delivery appears probable, however, constant attention will be needed to ensure risks do not materialise into major issues threatening delivery
- amber; successful delivery appears feasible but significant issues already exist requiring management attention; these appear resolvable at this stage and if addressed promptly, should not present a cost or schedule overrun
- amber/red; successful delivery of the programme or project is in doubt with major risks or issues apparent in a number of key areas; urgent action is needed to ensure these are addressed, and whether resolution is feasible
- red; successful delivery appears to be unachievable; there are major issues on programme or project definition, schedule, budget required, quality or benefits delivery, which at this stage do not appear to be manageable or resolvable
A gateway review is designed to provide the SRO with real time information so that action can be taken to address live issues and redirect the programme or project towards successful delivery.
Roles and responsibilities
The main roles and responsibilities associated with gateway reviews are:
Senior responsible owner
The programme or project SRO is responsible for initiating the gateway review process, making contact with the DAC and for submitting a completed RPA. They are also responsible for overseeing the provision of all relevant documentation to the review team.
Departmental assurance co-ordinator
The DAC is responsible for administering and arranging gateway reviews and for managing the NICS pool of gateway reviewers.
Gateway review team leader
The RTL will lead an independent team, typically accompanied by two review team members, and is responsible for carrying out the gateway review.
Gateway style healthchecks may also be carried out. Healthchecks are supplementary to formal gateway reviews. They provide additional assurance to SROs where, for example, a programme or project is between key stages or where engagement with the gateway process has occurred late.
Where the RPA for a programme or project is designated low risk and where this is agreed by the DAC, an internal peer review should be undertaken. This should be in line with gateway principles and conducted by an independent team appointed by the department.
It is important to note that an internal peer review is not a gateway review and an IPR team must not be described as having carried out a gateway review under these circumstances.
Further information on the gateway review process is available from the departmental assurance co-ordinator in the Centre of Expertise for Programme and Project Management.