Forum Replies Created
-
Posts
-
From a public sector procurement perspective, these are very relevant concerns because they challenge some of the core principles procurement has operated under for years, particularly open competition, non-discrimination, and best value.
The increasing shift toward “Buy Canadian” and regional preference policies suggests that governments are placing greater weight on supply chain resilience, economic security, and domestic capacity building. While trade agreements such as CETA and CUSMA remain in place, we are seeing growing pressure to interpret procurement decisions through a strategic and economic lens rather than strictly through lowest compliant cost.
This creates a difficult balance for procurement professionals. On one hand, public entities still have obligations around fairness, transparency, and treaty compliance. On the other hand, there is increasing political and public expectation to support local industry, reduce foreign dependency, and strengthen domestic supply chains, especially in critical sectors.
I also agree that affordability will become a major issue for social procurement and sustainability initiatives. These priorities have gained traction because they deliver broader public value, but under continued inflationary pressure and fiscal constraints, organizations will likely face greater scrutiny on measurable outcomes and return on investment. Going forward, social procurement initiatives may need to demonstrate not only social impact, but also economic and operational value to remain sustainable.
In many ways, procurement is evolving from a transactional function into a strategic risk management function, where policy alignment, market resilience, supplier diversification, and long-term sustainability all need to be balanced within a defensible procurement framework.
This article was a helpful reminder of why it’s important to distinguish between mandatory response requirements and mandatory performance requirements when drafting a solicitation. A mandatory response requirement is something bidders must provide at the time of bidding to be considered compliant. A mandatory performance requirement, on the other hand, is something the successful contractor must meet during the delivery of the contract.
The Tantramar case shows how mixing these two can create unnecessary risk. The Town expected a transfer station as part of contract performance, but it wasn’t a mandatory condition for bid submission. Because of that, PBS was still considered compliant even though the transfer station wasn’t immediately available. The court made it clear that owners must avoid treating performance obligations as if they were bidding requirements.
The key takeaway for me is that clear drafting matters. Before releasing a tender, we need to review the requirements carefully, identify which items are truly mandatory at the bidding stage, and ensure performance expectations are written in the right place. Keeping that separation clean helps avoid disputes, protects fairness, and reduces the chance of litigation
You’ve covered this really well, especially how all four areas connect.
On economic volatility and geopolitics, I agree the key shift will be toward more flexible and risk-aware contracting. Things like shorter pricing validity, escalation clauses, and deeper market analysis will likely become standard.
Your point on AI is important. It’s not just adopting it, but actually understanding how vendors are using it and making sure there’s transparency and accountability built into contracts.
On social procurement, I think you’re right that measurement is the hard part. Clear metrics and consistent monitoring will be critical, otherwise it risks becoming more of a checkbox than real impact.
In the end, it really points to procurement becoming more structured, data-driven, and focused on managing risk across the full supplier lifecycle.
You make a good point, especially on tariffs. Even when we’re not directly affected, the impact flows through vendors, and that price volatility makes planning and contract stability a real challenge.
I also agree on the social side. Balancing local sourcing with getting the best value won’t be easy, and it’ll likely require clearer policies and trade-offs so decisions stay fair and defensible.
You’ve covered the key issues well. I’d just add that it’s not only about having backup suppliers, but building more resilient supply chains through diversification and stronger vendor relationships.
On inflation and budgets, it’ll go beyond tough negotiations. Teams will need to focus more on total cost of ownership and smarter contract strategies.
And on transparency, digital tools and data will play a bigger role in making decisions clearer and easier to defend.
Over the next five years, public sector procurement will be shaped by supply chain disruptions, rising costs, and growing demands for transparency. At the same time, the introduction of AI will change how procurement is done, speeding up bid evaluations, improving market analysis, and helping manage contracts more efficiently.
The challenge will be balancing these benefits with accountability. AI can introduce risks like bias and lack of transparency, so decisions still need to be clear, fair, and easy to justify. Alongside this, teams will also face pressure to meet sustainability goals and adopt new digital tools, all while staying compliant. The real test will be using AI and technology to improve outcomes without compromising trust or fairness
Michael, That’s a solid idea. Adding an independent review checkpoint before the RFP is issued and again before contract award would help catch inconsistencies early, especially around key details like quantities, pricing formulas, and evaluation steps. Having a fresh set of eyes who was not involved in the original setup or evaluation reduces the chance of errors being overlooked.
It’s also practical because it doesn’t slow things down much, but it adds a layer of accountability. In a case like this, a simple review could have caught the mismatch in quantities before it affected the evaluation. Overall, it helps strengthen trust in the process and shows bidders that the procurement is being handled carefully and fairly.
Anny, I agree with your analysis. Under the Contract A framework, procurement teams are required to follow the evaluation criteria exactly as stated in the RFP. Any deviation from those terms undermines fairness, transparency, and equal treatment of bidders, even if the final outcome would not have changed.
In the Mantario Housing case, using 900 units instead of the 475 inspections set out in the RFP and confirmed at the site visit is a clear breach of the procurement process. The appropriate response is to correct the error and re-evaluate using the proper methodology. If the ranking changes, the award should be cancelled and reissued. If it remains the same, the contract may stand, but accountability and potential remedies under the CFTA are still necessary to protect the integrity of the process.
I agree with your point. In procurement, the RFP sets the rules, and bidders rely on those rules when preparing their pricing. When the procurement team does not follow the stated evaluation method, it undermines fairness and the credibility of the process, even if the final ranking of bidders would not change.
That said, the consequence is not always to cancel the award. If a proper re-evaluation using the correct method still produces the same result, the contract may stand. However, the procurement team should still be required to correct the error, document what happened, and strengthen internal controls to prevent similar issues in future RFP evaluations.
If the procurement team does not follow the evaluation method set out in the RFP, the process is already compromised, even if the final ranking of bidders would not change.
In this case, the procurement team used incorrect quantities when calculating the evaluated price, which means the proposals were not assessed in line with what was clearly stated in the RFP. That undermines fairness, transparency, and the integrity of the procurement process.
The proper consequence is that the evaluation should be corrected and the RFP re-evaluated according to its original terms. If the outcome remains the same after a proper evaluation, the contract may still stand, but the procurement team should still be held accountable for the procedural error and the impact it has on trust in the RFP process.
I understand your reasoning, and it makes sense given the level of control the general contractor had over the project.
They weren’t just coordinating the work, they were actively making the key decisions on how it should be done, even after being warned about the fire risks. Once those concerns were raised and still overridden for cost and time reasons, it does place a lot of weight on their side.
That said, the subcontractor’s role isn’t completely passive. Even though they operate within a defined scope, they still have a responsibility to avoid proceeding in situations they know could be dangerous. That’s where some shared responsibility can still come into play, depending on how much authority they actually had to refuse or stop the work.
In the end, your main point stands: the party making the final call on how to proceed, especially after being warned, carries the heavier share of liability.
I see your point, and I think you’re right to frame it that way.
The GC had overall control of the site and ultimately decided to proceed despite safer alternatives being raised, so their share of responsibility is clearly heavier.
At the same time, the subcontractor isn’t completely off the hook either. Once they were aware of the risks, continuing the work does create some level of shared responsibility, even if they were operating under direction.
So it really comes down to control versus awareness, and how each party responded once the safety concerns were on the table.
I think you explained the balance really well. I agree that both parties share responsibility, but the GC carries more since they ignored clear warnings and directed the work.
Your point about not fully excusing the SC is important too. Even under pressure, there’s still a duty to refuse unsafe work, so some level of shared liability makes sense.
I think the general contractor carries most of the liability because they were clearly warned about the risks more than once and still chose to proceed. They even rejected a safer method and assured they would take responsibility, which shows they knowingly accepted the risk.
That said, Vasco isn’t completely free of responsibility. As the expert, he had a duty to refuse unsafe work, especially after identifying flammable material. By continuing, he contributed to the outcome.
So realistically, this looks like shared liability, but with greater responsibility on the general contractor for directing the unsafe approach.
