The Water Industry Development Project (WIDP) is an illustrative PHC project record informed by publicly available sector programmes, representative of the kind of regulated infrastructure delivery seen across the sector. The programme reflects a major step-up in water and wastewater infrastructure activity, with investment directed toward improving service resilience, protecting rivers and coastal waters, reducing storm overflow impact, upgrading treatment assets, developing new water resources, and strengthening long-term environmental performance.
This PHC project is a structured example showing how the PHC Service could support a large regulated infrastructure programme by improving visibility of risks, issues, actions, evidence, decisions, and delivery status across multiple projects, contractors, disciplines, and stakeholder groups.
The Water Industry Development Project (WIDP) Major Projects Risk Governance record has been created as an illustrative PHC project to support preparation for a Senior Risk Manager interview linked to a water company’s major-projects environment. Initial public-domain information has been reviewed, including the regulated programme context, the job brief, company operating information, and the role emphasis on infrastructure risk, QSRA/QCRA, partner risk integration, mitigation follow-up, and PMO reporting. A first set of project overview narratives, involved-party descriptions, expected outcomes and PHC Questions responses has been prepared to demonstrate how PHC governance routines could strengthen delivery control in this environment.
This illustrative record is deliberately structured so it can be operationalised via either:
The current limitation is that this is an illustrative record based only on public-domain information and interview preparation material. It does not yet use internal risk registers, risk tool configuration (e.g., Riskonnect/ARM), schedules, cost data, partner reports, or established PMO governance routines.
In employment mode, the first step would be to replace illustrative content with controlled internal data, align to company governance standards, and establish a sustainable risk operating rhythm with named owners and regular updates.
In contracted PHC Service mode, the first step would be to agree scope, access protocols, information governance, and interfaces with the PMO—then stand up a blended operating model where the PHC team supports integration, quality control, evidence linkage, and escalation discipline without duplicating existing systems.
The next step is to complete interview preparation, particularly the links between PHC practice and the company’s need for major-project risk visibility, mitigation tracking, partner integration, QSRA/QCRA support, and leadership reporting—framed in a way that is equally credible whether delivered by an embedded employee or an external PHC Service team.
If the interview is successful, the PHC record can be repositioned as a private onboarding and 90-day execution tool, supporting early contribution through rapid baseline, stabilisation of reporting rhythm, and improved follow-through on mitigation and partner updates.
If the interview is not successful, the record can still serve as a portfolio demonstration of how PHC would support a regulated water infrastructure delivery period. It can then be refined into either:
Water Industry Development Project (WIDP) Major Projects Risk Governance is an illustrative project created within PHC Port to provide a realistic governance model for a major regulated water and wastewater infrastructure programme. It does not represent an official company project record and contains no confidential or proprietary information. Its purpose is to act as a structured reference point for exploring how the PHC Service could be applied to a complex, high-scrutiny, multi-stakeholder programme delivery environment.
The model reflects the kinds of challenges typically associated with a major water-sector capital programme: regulatory and environmental obligations, construction and engineering uncertainty, multiple delivery partners, NEC contract interfaces, customer and community impact, significant schedule and cost exposure, and the need for disciplined control of risks, actions, assumptions, issues, opportunities and deliverables. Through this project, PHC tools such as concerns lists, 90-day plans, reports, gap plans, questions and risk maturity records can be developed in a way that mirrors the governance needs of a large, high-consequence infrastructure programme.
The aim is not to simulate engineering detail or claim inside knowledge of the company’s live project portfolio, but to create a practical governance and assurance framework that helps test visibility, accountability, escalation, mitigation follow-up and monitoring routines. In that sense, the project serves as a shadow model for thinking through how robust project health control could support successful delivery in a regulated major-projects programme context.
This illustrative PHC record is structured to be deliverable in two ways: either by embedding PHC discipline through an employed role within the company’s existing PMO and risk function, or by providing the same governance and reporting control layer via a commercially contracted PHC Service team working alongside established systems.
| # | ID | Risk Summary | Mitigation |
|---|---|---|---|
| 1 | 569 | Environmental and regulatory commitments not integrated into project plans could lead to significant delivery challenges. | Integrate all regulatory and environmental commitments into project planning and execution to prevent disruptions. |
| 101 | 562 | Misalignment and communication gaps in integrating external partner risk updates. | Structured communication protocol and risk management software for real-time updates. |
| 101 | 568 | NEC Early Warnings not integrated into risk management processes. | Ensure material Early Warnings drive updates to risk view and QSRA/QCRA inputs. |
| 102 | 563 | Ineffective integration of QSRA/QCRA outputs could lead to unmanaged risks, causing project delays and increased costs. | Ensure QSRA/QCRA outputs are integrated into project management practices and that follow-up actions are tracked. |
| 104 | 570 | Ground conditions and productivity variability pose significant risks to project schedule and cost. | Explicitly address uncertainties by using ranges and discrete risks, and update assumptions with improved evidence. |
Note: Top Risks are selected from the full open Concern set by applying a priority flag. This table therefore shows the risks currently requiring senior focus, while the classification and engagement sections reflect the wider Concern population.
Top Risks are priority-flagged items (not strictly the highest score).
Total Concerns 10 | 10 Open | 0 Closed
|
TECHNICAL T1 Project Scope T2 Design / Eng. T3 Technical Processes T4 Construction T5 Startup T6 Logistics / Warehouse |
COMMERCIAL C1 Feasibility/Business Case C2 Market/Product C3 Finance / Funding (4) C4 Estimate Uncertainties C5 Suppliers / Vendors C6 Legal / Contract Terms C7 Currency/Inflation C8 Tax/Tariff |
|
MANAGEMENT M1 Project Management (6) M2 Project Organisation M3 Communication M4 Project Resourcing M5 Operations / People M6 Operations / Permits M7 Operations / Logistics M8 Project Quality M9 Health / Safety / Environment |
REGIONAL R1 Environment / Weather R2 Security / Language R3 Regulations R4 Infrastructure R5 Utilities R6 Approvals / Permits / Licenses R7 Workforce Availability / Capability R8 Political / Government |
00 gen
Total Engagement Comments 14
| Category | Item Count | Comment Count | Last-7-Days | Comments to Process |
|---|---|---|---|---|
| Concerns | 10 | 12 | 0 | 12 |
| Locations | 1 | 0 | 0 | 0 |
| Actions | 2 | 1 | 0 | 1 |
| Milestones | 1 | 0 | 0 | 0 |
| People | 0 | 0 | 0 | 0 |
| Events | 2 | 1 | 0 | 1 |
| Deliverables | 1 | 0 | 0 | 0 |
This section measures visible engagement with the risk-control process by counting comments and updates against PHC records, especially Concerns. The purpose is not to reward comment volume, but to highlight whether risks are being actively reviewed, challenged and progressed by owners, managers and discipline leads.
Showing 10 Open risks - 4 are Top Risks
Note that in cases where there is no action strategy, the residual will be the same as current. For this illustrative example the current and residual PxI scores are set arbitrarily for illustration purpose.
| ID | Title | Owner | Current Score | Residual Score |
|---|---|---|---|---|
| 568 | NEC Early Warnings Integration into Risk Governance | 1 | 20 (5×4) | 16 (4×4) |
| 570 | Ground Conditions and Productivity Uncertainty Driving Schedule and Cost | - | 20 (5×4) | 16 (4×4) |
| 562 | External Partner Risk Integration | 1 | 16 (4×4) | 9 (3×3) |
| 563 | QSRA/QCRA Process Integration and Data Quality | 1 | 12 (4×3) | 9 (3×3) |
| 565 | Mitigation Actions Not Completed | 1 | 12 (4×3) | 9 (3×3) |
| 567 | P50/P80 Confidence Deterioration Across Key Milestones | - | 12 (3×4) | 8 (2×4) |
| 569 | Regulatory and Environmental Constraints on Project Delivery | - | 12 (3×4) | 8 (2×4) |
| 564 | Risk Register Quality and Consistency | 1 | 9 (3×3) | 6 (2×3) |
| 571 | Contingency Recommendations Misaligned With Current Cost Exposure | 1 | 6 (2×3) | 2 (1×2) |
| 572 | Risk Management System Devolving into a Passive Repository | - | 6 (2×3) | 3 (1×3) |