Forum Replies Created
-
Posts
-
I like the clarity of your argument, especially how you emphasize the repeated warnings and the decision to proceed despite them. The distinction you make between primary and secondary responsibility is clear and easy to follow. It also highlights an important point: even when instructions are given, professionals still have limits on what they should accept in unsafe conditions.
In this situation, liability should be viewed less as a simple split of fault and more as an issue of who had the authority to control and override safety decisions on site.
The general contractor ultimately made the key decisions that created the risk exposure. They were explicitly warned multiple times, rejected a safer method, and chose to proceed with a mitigation approach that was clearly insufficient given the known hazards. Most importantly, they directed the subcontractor to continue and effectively assumed responsibility for the outcome. This places the GC in a position of primary accountability from a governance and decision-making standpoint.
At the same time, the subcontractor is not entirely without responsibility. Even when instructed by a GC, a professional contractor has a duty to exercise independent judgment, particularly where there is an obvious and serious safety risk such as flammable materials being present. Continuing work under those conditions raises questions about whether that standard of care was fully met.
Overall, the case highlights that liability in construction risk scenarios is strongly tied to who controlled the decision to proceed in unsafe conditions, even when operational execution is carried out by another party.
Even if the final result would have been the same, there should still be consequences when an evaluation is not conducted according to the solicitation.
In this scenario, using incorrect quantities (900 instead of 475) means the evaluation did not follow the clearly defined methodology. The issue is less about who won, and more about the loss of process credibility and defensibility. Suppliers rely on those rules to structure their pricing, so any deviation introduces risk and uncertainty.
In my view, the appropriate consequence is a mandatory re-evaluation using the correct criteria, along with internal review of how the error occurred. Even if the outcome does not change, documenting and correcting the issue is important to maintain transparency and support auditability.
Ultimately, procurement decisions must be both correct and demonstrably fair, because if the process cannot be defended, the outcome cannot be fully trusted.
I really like how you connected operational controls with longer-term contract decisions, especially your point on renewal reviews. That’s often where organizations miss an opportunity to correct course.
Your emphasis on formalizing workflow and sign-off also stands out, it not only supports invoice accuracy but creates a clear audit trail if issues arise later. One thing your post highlights well is that controls shouldn’t work in isolation; when inspections, sign-offs, and performance reviews are aligned, they reinforce each other and make it much harder for discrepancies to go unnoticed.You’ve taken a very structured approach by focusing on strengthening the tender upfront, which is key. What stands out to me is how your requirements create clear accountability at each stage, from pre-approval to invoicing and ongoing performance. That end-to-end alignment really reduces the likelihood of gaps being exploited.
One aspect I find particularly valuable is the link between documentation and enforceability. By defining not just what is required, but also how discrepancies are handled and escalated, you’re essentially making the contract more defensible if issues arise.
It also highlights an important point, strong contract outcomes often depend less on pricing and more on how well expectations, controls, and consequences are built into the process from the start.
You did a great job highlighting the importance of invoice verification and tying it back to work orders. One thing I’d add is that even with strong documentation, there should also be some level of independent validation (like spot checks or audits) to ensure the data itself is reliable. Your point really reinforces how critical that connection between scope and payment is.
In addition to strong operational controls, I would focus on three broader measures to prevent situations like the OCHC–Argos case.
First, establish clear audit and data retention rights in the contract. The owner should have the right to request supporting documentation (e.g., measurements, internal worksheets, or supplier records) at any time. This creates a deterrent effect and allows issues like inflated quantities to be identified earlier.
Second, implement segregation of duties in contract management. The same individual should not be responsible for approving work, verifying performance, and processing payments. Separating these roles reduces the risk of oversight gaps and ensures more objective validation of invoices.
Third, strengthen supplier accountability through consequences and incentives. This includes defined penalties for inaccurate billing, but also mechanisms like holdbacks or performance-based payments tied to verified outcomes. When financial incentives are aligned with accuracy and compliance, the risk of overbilling is reduced.
Instructor Note – Using this post to address several comments in this Forum.
About #1 point – Asking for supporting documentation from a Vendor and ensuring it is provided AND reviewed properly are two different things.
This case represent an organizational failure of the OCHC to properly manage both its people and their processes.
Housing is a tough subject to manage with dozens of daily problems that distract from primary tasks. Organizations need proper systems and resources to manage their business properly.
#2- Good job identifying the potential for fraud here. Most of the case details are about inaccurate invoicing or overcharging. With a system this weak, OCHC is lucky they were not paying for “ghost” invoices that represent no work being performed.
#3- While your points are correct, think about not making things more complicated. Basic due diligence is not being performed and if it was, most of the issue would not exist. What you propose is inserting ANOTHER layer of administration. Deliberate overbilling is fraud and unacceptable period. Tying up payments in excessive checking or lengthy holdbacks can starve legitimate vendors of liquidity so be careful not to overcompensate.What stands out in your post is the idea of “shaping rather than setting” requirements through the early stages. In the E-COMM case, the RFQ vendor discussions basically functioned as a structured feedback loop, allowing requirements to be refined without breaking fairness under Contract A.
Your mention of competitive dialogue is also interesting, because it highlights that E-COMM achieved some of the same benefits (like collaboration and clarification) without formally leaving the traditional Canadian procurement model. That balance between flexibility in practice and rigidity in structure is really what makes this case notable.Your discussion of reducing Contract A risks through early engagement is key. I’d add that E-COMM didn’t really eliminate Contract A risks, they shifted where those risks were managed. Instead of dealing with ambiguity during evaluation or contract award, they pushed it into structured market engagement phases, which is arguably where it can be managed more safely and iteratively.
Hello Chris,
Please find attached my assignment #1, I’m Looking forward to your feedback.
Thanks,
Imane Bey zekkoub
One thing I’d add is that in repair and maintenance contracts, the shift to outcome-based delivery also changes how risk is allocated between the organization and the vendor. While it creates space for innovation and preventative strategies, it also requires careful definition of what falls under “routine maintenance” versus larger capital-type repairs, so expectations stay clear on both sides. That balance is often what determines whether the model works smoothly in practice.
Cleaning in healthcare is a strong fit for this model, especially because it links directly to infection control rather than just task completion.
One thing I’d add is that the success of this approach would really depend on how clearly those “cleanliness standards” are defined and measured in practice. In healthcare environments, outcomes can be influenced by multiple factors, so having strong governance and agreed-upon performance metrics becomes just as important as the incentive structure itself.What stands out here is how this model changes the role of procurement from price negotiation to performance design. Instead of managing transactions, the focus shifts to defining outcomes and governance structures that support continuous improvement over time.
I like your point about freeing up internal resources. One thing I’d add is that in practice, the “win-win” depends a lot on how well demand is defined and monitored. If the outcome metrics aren’t carefully designed, you can end up shifting inefficiencies to the supplier rather than actually eliminating them. So the structure of what “efficient use” means becomes just as important as the outsourcing itself.
Good observation on the “slow down to speed up” idea! what stands out to me in the E-COMM case is that they didn’t just slow down informally, they actually built a structured mechanism (working groups, PoC, RFQ feedback loops) to ensure that the time invested in planning translated into actionable, converged requirements rather than open-ended discussion. In that sense, the process wasn’t just longer, it was deliberately engineered to reduce ambiguity before procurement risk peaked at the RFP stage.
