Manitoba's June 9, 2026 hailstorm exposed critical weaknesses in the province's repair system, including capacity limitations, communication gaps, and coordination challenges that affect how quickly vehicles can be repaired and customers served during catastrophic events.
- The June 9 hailstorm generated over 8,000 claims within hours, revealing that Manitoba's repair system lacks predetermined catastrophe response plans and surge capacity.
- Repair timelines could extend two years or more, creating additional complexity as vehicles accumulate damage, claims overlap, and documentation becomes outdated.
- Communication breakdowns forced repair shops to become information desks while customers sought answers from multiple sources, highlighting the need for coordinated messaging.
- Capacity constraints rippled across the entire ecosystem, affecting estimators, call centers, adjusters, repair facilities, glass shops, and rental providers simultaneously.
- A systems-based approach to hail preparedness—including predetermined triggers, expanded capacity, and consistent service standards—could significantly improve future catastrophe response.
The hailstorm that swept across Manitoba on June 9, 2026, was a reminder that hail is not a surprise in our province. Southern Manitoba sits within one of Canada’s major hail corridors, making damaging hailstorms a predictable part of Prairie life. The question is not whether another major hailstorm will occur, but whether our repair system is prepared when it does.
When hail falls, the damage happens fast. In a matter of minutes, thousands of vehicles can be dented, windows shattered, leaving thousands of Manitobans wondering what to do next.
The lesson from June 9 is bigger than hail. It is about systems. Systems theory teaches us that the whole is greater than the sum of its parts.
Manitoba’s repair system is interconnected, but those connections often become visible only when the system is under strain. Hail does not create problems in the system — it reveals them. It exposes bottlenecks, communication gaps, capacity constraints and unintended consequences that may remain hidden during normal operations.
That is what makes hail more than a weather event. It provides an opportunity to examine how the repair system actually performs when tested by real-world conditions, not just how it was designed to work on paper.
Manitoba’s repair industry has an opportunity to learn from these events in a way that benefits everyone moving through the system. The goal is not simply to prepare for the next storm, but to build a repair system that is more resilient, more responsive and better able to meet customer needs when demand suddenly spikes.
Hail doesn’t create problems – it reveals them
Most days, the collision repair system works quietly in the background. Claims arrive at a manageable pace, estimates are completed, repairs are scheduled and customers move through the process with little awareness of the complexity behind it.
Catastrophe readiness
The volume of notices to trade issued after the storm suggests the response was evolving in real time. Procedures changed repeatedly as claim volumes became clearer, estimating authority was expanded, new hail response centres were opened and temporary measures were repeatedly extended. While this demonstrated adaptability, it also raised questions about whether the industry was executing a predefined catastrophe plan or developing solutions as events unfolded.
Capacity limitations
The storm revealed limitations across the entire repair ecosystem. Estimators, call centres, adjusters, repair facilities, PDR technicians, glass shops, suppliers and rental providers were all required to handle demand far beyond normal operating volumes. Delays that typically measured in hours stretched into days as resources were redirected to manage the catastrophe.
Overlapping claims and technical complexity
The event exposed the complexity of managing vehicles with pre-existing claims, in-progress repairs or damage that approached total-loss thresholds. Existing estimating standards for overlapping claims and marginal repairs required additional review, documentation, approvals and coordination at the same time workload was increasing dramatically. What appeared to be a simple hail claim often became a complex technical and administrative exercise.
Industry coordination
Effective catastrophe response depends on alignment among MPI, repair facilities, PDR providers, glass shops, suppliers, rental companies, industry associations and customers. The numerous process updates, emergency measures and ongoing discussions between MPI and the Automotive Trades Association demonstrated how dependent the system is on coordination among all stakeholders during a large-scale event.
Communication challenges
Customers needed immediate answers regarding claims, estimates, repairs, rental vehicles and total-loss decisions. As procedures evolved and multiple notices to trade were issued, maintaining clear and consistent communication became increasingly difficult. This highlighted the importance of having a well-defined communication strategy before a catastrophe occurs.
Administrative and approval bottlenecks
The storm also revealed that paperwork, approvals and administrative processes can become just as significant a constraint as repair capacity. Additional documentation requirements, delayed estimate approvals, payment processing concerns and rental authorization issues all contributed to slower claim progression despite repair facilities being ready to perform work.
More than individual policies – what happens when there is no systems approach?
The day after the June 9 hailstorm, customers wanted answers.
• Should I report my claim today?
• Can I still drive my vehicle?
• Is the damage getting worse?
• How long will repairs take?
• Who do I call?
The problem was simple: the hail arrived faster than the information.
As MPI worked to understand the size of the catastrophe and develop its response, customers turned to repair shops, friends, neighbours, news reports and social media looking for answers. MPI reported more than 8,000 claims within hours and advised that additional processes were still being developed. Repair shops quickly became the industry’s information desk. Shops were answering questions about claims, estimates, timelines, glass damage, rentals and next steps — often while looking for the same answers themselves.
The ATA’s June 10 bulletin reflected the same situation, advising members that MPI was still developing procedures and that additional direction would follow.
This is what happens when there is no coordinated systems approach.
• Customers become confused.
• Shops become call centres.
• Information comes from multiple sources.
• Everyone works hard, but not everyone is working from the same playbook.
The storm also revealed a second systems challenge: capacity.
What happens when capacity becomes the limiting factor?
Industry forecasts suggest it could take up to two years for hail claims from the June 9 event to work through Manitoba’s repair system. The storm happened in a single evening, but its effects may be felt for years.
A vehicle damaged on June 9, 2026, may not be repaired until 2027 or 2028. During that time, damage may evolve, additional collisions or weather events may occur, documentation becomes older and questions become more complicated:
• Which damage belongs to which event?
• Which claim pays?
• Which procedures apply?
• What changed between the date of loss and the date of repair?
The hail date never changes. The repair date might.
The same challenge affects repair facilities. A hail claim that might have been straightforward in July 2026 may look very different in 2027 or 2028. Estimates become older, vehicles accumulate additional damage, overlapping claims become more common and documentation becomes harder to validate.
Shops spend more time investigating, documenting, explaining and reconciling what happened between the date of loss and the date of repair.
As delays increase, a simple repair can gradually become a more complex technical and administrative file. In that sense, capacity affects more than repair timelines — it influences workload, claim complexity, customer expectations and the resources required to bring a claim to completion.
Viewed through a systems lens, the storm demonstrated that capacity is not simply a repair issue. It affects communication, customer experience, claims administration, estimating accuracy, repair planning and decision-making across the entire repair ecosystem.
The longer the gap between the date of loss and the date of repair, the more likely it becomes that customers, repair facilities and insurers are managing challenges created by time rather than by the original hail event.
What can we learn from Manitoba’s hail storm?
Hail is not a rare event in Manitoba.
We live in one of Canada’s most active hail regions. As weather patterns continue to evolve, severe storms may become larger, more frequent and more disruptive. The question is not whether another major hail event will occur. The question is whether we will be better prepared when it does.
The June 9 storm did more than generate claims. It exposed how the different parts of Manitoba’s repair ecosystem interact when demand suddenly exceeds capacity.
Systems theory teaches that a system is more than the sum of its individual parts. Customers, MPI, repair facilities, glass shops, PDR providers, suppliers, rental companies, industry associations, technology, policies and procedures do not operate independently. They influence one another.
When one part of the system comes under pressure, the effects ripple throughout the entire system.
Viewed through a systems lens, many of the challenges revealed after June 9 were not isolated failures. They were symptoms of a highly interconnected system operating under extraordinary pressure.
This presents an opportunity.
Manitoba has experience responding to environmental catastrophes. Floods, wildfires and other large-scale emergencies have demonstrated the value of preparedness, surge capacity, predefined response plans and coordinated communication. The goal is not to prevent the event. The goal is to ensure the system is ready when the event occurs.
The same thinking could be applied to hail.
What would a hail catastrophe framework look like if it were designed as a complete system rather than a collection of individual policies and procedures?
Areas worth exploring include:
• Predetermined catastrophe triggers that activate surge-response measures.
• Expanded assessment and repair capacity that can be deployed quickly.
• Clear principles for managing claims when repairs extend over multiple years.
• Consistent service standards for customers, insurers, and repair facilities.
• Communication frameworks that ensure information moves through the system as quickly as claims do.
The specific solutions are open for debate. The lesson is not.
The June 9 storm revealed that communication, capacity, estimating, repair planning, customer service, administration and claims management are interconnected. When one area struggles, every area feels the effect.
Perhaps the most important lesson is this: hail readiness is not an MPI issue, a repairer issue or a customer issue. It is a system issue.
And systems perform exactly as they are designed to perform.
If Manitoba’s repair system is to become more resilient, the next conversation may need to be less about the individual parts and more about how those parts work together.
The opportunity created by the June 9 storm is not simply to repair damaged vehicles. It is to learn from the stress test. To understand where the system bends, where it breaks, where it succeeds and where it can improve.
Because hail doesn’t create problems in the system. It reveals them.
