Part 1: Project Management, Infrastructure Risk & Transparency - 11/09/2023
- PECConnect
- Nov 9, 2023
- 4 min read
The audit committee meeting was formally called to order and livestreamed. The agenda was approved, there were no pecuniary interests declared, and the previous meeting minutes were adopted. The chair noted an unusually large number of senior staff attending, signaling the importance of the topics being discussed.
View the entire PEC Council meeting, or continue to speaker comments and councillor votes>
Project Management 101 presentation
Senior staff delivered a detailed overview of how municipal projects are planned, costed, approved, delivered, and closed. The presentation covered everything from small operational projects to major multi-million-dollar infrastructure projects.
The core goal of project management was emphasized as delivering projects on scope, on schedule, and within budget, while complying with legislation, procurement rules, and environmental requirements.
Long-term planning and budgeting
Staff explained how projects originate through asset management planning, road needs studies, infrastructure assessments, and multi-year capital plans tied to council’s strategic goals. Projects are funded through a mix of taxes, user rates, grants, development charges, reserves, and long-term debt.
Before projects reach council, staff prepare pre-budget cost estimates that account for design, construction, inspections, engineering, excess soil management, and contingencies. These estimates become more accurate as projects move closer to tender.
Environmental assessment and public engagement
Large infrastructure projects must go through a municipal class environmental assessment, which includes structured public engagement and review of alternatives. Different project sizes follow different schedules, from smaller Schedule B projects to major Schedule C projects and master plans.
Staff stressed that this process is highly technical, time-consuming, and designed to protect the environment while documenting public input.
Design, procurement, and construction oversight
Once approved, projects move into detailed design, tendering, and construction. Consultants are used for specialized engineering work, while contractors deliver the construction. Municipal project managers oversee schedules, budgets, quality control, change orders, and communications.
Procurement rules were outlined clearly, including thresholds that determine whether quotes, tenders, or RFPs are required.
Project closeout and accountability
Staff described project closeout as including inspections, commissioning, as-built drawings, warranty periods, and internal evaluations. These evaluations inform future procurement decisions but are not public documents.
Committee members raised concerns about how lessons learned are tracked, whether recurring issues are identified, and how council and the public understand why some projects go over budget or face delays.
Committee discussion on transparency and oversight
The committee debated the need for greater transparency around project outcomes, especially for large, high-risk projects. Members emphasized that the public often only hears about failures, not successful projects that came in on budget.
There was strong interest in understanding root causes of cost overruns, whether they stem from design assumptions, unknown site conditions, inflation, or contractor behavior.
Public delegation on Wellington infrastructure
A member of the public raised serious concerns about water and wastewater infrastructure projects in Wellington, including rising costs, reliance on front-end development charge agreements, debt risk to ratepayers, and compliance with provincial financial planning regulations.
The delegation asked the audit committee to urgently examine the funding model, financial risks, and accountability mechanisms tied to these projects.
Committee response and next steps
After discussion, the committee decided not to proceed immediately with a detailed audit review due to timing, legal complexity, and lack of advance notice. It was agreed that these concerns would be more appropriately raised at full council, potentially through a notice of motion.
The committee did approve a separate motion requesting a staff meeting with select committee members to discuss infrastructure oversight and efficient use of resources.
Comparator municipalities discussion
The committee clarified confusion around which municipalities are used as comparators in reports. It was confirmed that four approved comparator municipalities are used consistently and were selected based on size, structure, economy, and governance model.
Staff committed to reinforcing consistent use of these comparators across departments, while allowing flexibility for additional aspirational comparisons when appropriate.
Key Takeaways
Large infrastructure projects carry financial risk. Even with planning and oversight, costs can rise due to market conditions, design changes, or unexpected issues, which can impact taxpayers and ratepayers.
Transparency gaps can create confusion. The process behind projects is detailed but not always clearly communicated, so residents often hear more about problems than successes.
Oversight is becoming a bigger focus. The audit committee is looking for better ways to track performance and explain outcomes, aiming to improve accountability without slowing projects down.
Disclaimer: This article is based on a meeting with an approximate duration of 2:09:29. Due to the length of the meeting, our team was not able to independently review the full recording in its entirety. As a result, we relied on software-generated transcription, automated summarization, and automated recognition of speakers and participants, which may not be entirely accurate. All transcriptions, summaries, and related content are prepared by our team in good faith and on a reasonable best-efforts basis. The content is provided for general informational purposes only and is intended to support public understanding of the topics discussed. While reasonable efforts have been made to present the information accurately, automated processes may result in errors, omissions, or unintended misinterpretations. This article does not constitute an official, certified, or verbatim record of the meeting, and it should not be relied upon as such. Readers are encouraged to consult original source materials, official minutes, or recordings where available for confirmation or clarification. Questions, requests for clarification, or suggested corrections may be submitted to hello@pecconnect.ca for review and consideration.
Comments