When putting together your business case, managing a project or maintenance work, there are technical requirements that may be relevant to your work that will need to be considered and included.
To ensure you are completing all steps correctly, follow the table below.
The following table should be read in conjunction with the ESR standard. It outlines in further detail what is expected at each project stage.
| Business case phase | Technical requirements |
| Strategic case |
Identification of key stakeholders/decision makers, and their likely interest in the issue. Investment logic mapping workshop to occur. If working with stakeholders outside the Transport Agency, we should be at Collaborate level. |
| Programme business case |
High level public engagement plan (PEP) to be prepared. The PEP should be scaled to the size of the project. Determine what level of influence the public will have throughout the project lifecycle. In most instances, we should be at Inform/Consult level. |
| Indicative business case |
High level PEP to be prepared. The PEP should be scaled to the size of the project. Undertake engagement. At end of engagement, prepare a consultation report on engagement process, outcomes and next steps. In most instances, we should be at Consult/Involve level. |
| Detailed business case |
Update PEP based on outcomes of the indicative business case. Undertake engagement. At the end of engagement, update previous consultation report on engagement process, outcomes and next steps. In most instances, we should be at Consult/Involve level. |
| Pre-implementation |
Consents and other statutory requirements are applied for in the pre-implementation phase. The consultation report will form part of the assessment of environmental effects supporting the statutory application. Generally speaking, we will be at the Inform level as we go through the statutory process. This is because wider public engagement would have been undertaken as part of option selection and analysis during the indicative and detailed business case phases. However, engagement with individual affected parties and submitters will be at Involve/Collaborate level. |
| Implementation |
Review the PEP for the project and prepare a communications plan/strategy. The size and scale of the communications plan/strategy should be fit for purpose. In most instances, we will be at Inform level for the general public. Directly affected parties, or stakeholders with an interest greater than the general public will require higher levels of engagement. |
| Maintain and operate |
The Network Outcomes Contract (NOC) requires the contractor to prepare a customer and stakeholder communications management plan (CSCMP). The CSCMP should reference all relevant PEP (if available). PEPs will provide the contractor with valuable information about the background to the project/community. The contractor will use this information to develop a strategy for their public engagement through their quality control systems they bring to their work. The CSCMP should be based on the principles in this guideline and show how they are being implemented in the context of the Network Outcomes Contract.
The CSCMP must reference all relevant project PEPs in the NOC area, and factor in commitments to update the CSCMP on a reqular basis. Depending on the work being undertaken, engagement will vary across the spectrum. The focus will in most cases be at the Inform level, with directly affected parties potentially at Consult/Involve. |
For further information contact environment@nzta.govt.nz.
