Part 2: Infrastructure Oversight, Costs & Accountability - 11/09/2023
- PECConnect
- Nov 9, 2023
- 3 min read
This part of the meeting looks at who asked the big questions, how staff responded, and where things are heading next. A lot of the conversation focused on project costs, accountability, and how major infrastructure projects are managed behind the scenes.
No final budget decisions were made here, but it’s clear that concerns about rising costs and oversight are being taken seriously. It also shows that many of these bigger issues are now moving to council, where the final calls will be made in a more public setting.

View the entire PEC Council Meeting; or view our recap.
Project management explanation
David MacPherson led the presentation, explaining that inflation, market volatility, and unknown site conditions have made accurate budgeting more difficult. He emphasized that contingencies are not failures, but necessary tools for managing risk.
Questions on accountability and Risk Discussion
Ben Thornton asked who is accountable when projects exceed budgets. Staff responded that procurement is tightly regulated and that market conditions often drive cost increases beyond municipal control.
Jane Lesslie pressed on whether project closeout reports identify recurring issues and whether lessons learned are tracked across projects. She emphasized the need for continuous improvement, not blame.
Wilma Vreeswijk focused on contingencies, asking how often they are exceeded and whether council is notified when costs rise significantly. Staff explained that council approves a maximum project value and additional approvals are required if that ceiling is exceeded.
Staff response on learning and improvement
Peter Moyer, speaking on behalf of engineering and procurement, explained that staff regularly adjust practices based on past issues. Examples included better surveys, more geotechnical work, and tighter tender documents to reduce change orders.
Motion on infrastructure oversight
The committee passed a motion directing development services staff to meet with John Hirsch, Wilma Vrieswick, and Jane Leslie to discuss oversight of infrastructure project management and efficient use of resources.
Public delegation on Wellington projects
Dorothy Bothwell raised detailed concerns about Wellington water and wastewater projects, including escalating costs, reliance on developer funding, debt exposure, and compliance with provincial regulations.
Her comments directly reflected resident anxiety about rate increases and long-term debt.
Committee and staff response

Amanda Carter, the finance director, clarified that front-end agreements are already in place, backed by secured letters of credit. She explained that updated financial models cannot be produced quickly because they rely on proprietary consultant models and finalized tender costs.
Councillor Engelsdorfer agreed to withdraw his motion and instead bring the matter forward as a notice of motion at council, where broader authority exists.
This affects locals because the debate will move to the full council table, where binding decisions are made.
Comparator municipalities clarification
Staff and Amanda confirmed that Norfolk County, Brant County, West Nipissing, and Grey County are the official comparators used by KPMG and staff. The committee passed a motion encouraging consistent use across departments.
Overall impact on the community
This meeting did not change project budgets or stop infrastructure work. What it did do was open the door to deeper scrutiny, clarify misconceptions, and shift major financial risk discussions to council where they belong.
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