Reporting functions of P3O
The reporting role is a key component of an effective P3O. The purpose is to provide a reporting service within the organisation that hosts the P3O, and outwards to wider stakeholders, including the ‘Hub’, as apart of a ‘Hub and Spoke’ P3O implementation model. The P3O also acts as a single, authoritative point of base data collation, and generates reports to multiple audiences with the appropriate levels of data aggregation.
Responsibilities
The specific responsibilities associated with the P3O reporting role may include:
- Providing regular reports to Boards, including a commentary on performance, coordinating upward aggregation of data/information and reports eg Highlight, Dashboard
- Ensuring integrity of reports including consistent RAG (Red, Amber, Green) status
- Identifying and reporting deviations and triggering excepting reporting when appropriate
- Developing processes to fulfil internal reporting needs of programmes/projects including any contractual reporting
- Ensuring that data collection and reporting deadlines are adhered to
- Documenting the weekly/monthly/quarterly reporting cycle and make available to all relevant stakeholders, with built in reminders
- Building and maintaining an information/knowledge base of trend data to aid emerging issues, reasons for delay and capture of lessons learned
The DoF P3O (Hub) is responsible for collating departmental P3O (Spoke) data and reporting to the NICS Board twice a year on the Major Projects Portfolio (MPP). This is a list of high-risk programmes/projects over £5m that are engaged with the Gateway Assurance Review process.
Departmental P3Os should develop and maintain a regular reporting cycle for their own oversight body (eg Departmental Board). The criteria should match internal governance and programme/project delivery requirements. This should be broadly aligned with the DoF P3O reporting cycle to streamline data collection and collation processes and minimise the ‘ask’ from departmental programme/project teams.