Short answer: SAP and IBM’s Canadian subsidiary LGS were important participants in Quebec’s failed SAAQclic modernization, and the Gallant Commission criticized aspects of their bids, staffing, licensing and delivery decisions. But the commission did not find that vendors alone caused the disaster. It described a wider failure in which SAAQ chose an inadequately tested ERP strategy, weakened procurement neutrality, compressed the schedule, adopted a high-risk “big bang” launch and gave government misleading progress information. The fairest conclusion is shared responsibility, with SAAQ’s governance decisions creating the conditions in which vendor failures became a public-service crisis.
What SAAQclic and CASA were supposed to be
The Société de l’assurance automobile du Québec (SAAQ) administers automobile insurance, driver licensing and vehicle services for Quebec. CASA—Carrefour des solutions d’affaires—was its broad modernization program. SAAQclic was the public-facing portal for licensing, registration and related transactions, connected to a much larger back-office replacement.
This was not simply a website redesign. SAAQ combined SAP enterprise-resource-planning software, internal work and external implementation services from LGS, an IBM subsidiary. The SAP-LGS/IBM alliance was responsible for major integration and delivery work. The program was divided into delivery phases and was intended to replace aging systems while changing many underlying business processes.
The original 2011 sustainability plan contemplated an 11-year modernization costing C$364 million. By launch, the scope, estimates and accounting treatment had changed substantially.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
What happened when the portal launched
SAAQclic opened to all customers on February 20, 2023. The portal was unavailable or very slow for periods, transactions failed, and some users could not complete routine work. Businesses redirected customers to physical offices. People who expected online service instead arrived at branches, producing severe queues; police were called at some locations. The federal briefing summary also described consequences for police access to information. Government of Canada briefing
The failure reflected more than one software defect. Readiness, performance, data and integration work, operational procedures, training, staffing and governance all mattered. Treating the episode as a single outage hides why the program was so difficult to recover.
Why the cost figures appear contradictory
Different totals describe different scopes, dates and cost categories. The following figures should not be treated as interchangeable:
| Figure | Meaning |
|---|---|
| C$364 million | 2011 sustainability plan for an 11-year, multi-phase modernization. |
| C$458 million | Initial maximum value of the external alliance contract over its stated term. |
| C$661 million | Launch budget combining C$375 million of implementation investment and C$286 million of recurring costs, including SAAQ internal amounts. |
| C$682 million | Later implementation-cost figure including internal SAAQ and contract-related amounts. |
| Approximately C$955 million | SAAQ’s later 10-year estimate for a reduced-scope solution, including external and internal costs. |
| More than C$1 billion, often about C$1.1 billion | Broader estimates associated with the full digitization effort, depending on included components and recurring costs. |
The commission’s executive summary reports that the launch budget included C$248 million in alliance implementation costs and C$127 million in SAAQ implementation costs, plus C$210 million and C$75 million respectively in recurring costs. The alliance contract itself had a 10-year duration. Gallant Commission executive summary
Free tools Windows power users keep installed
One-click scans. No signup required.
The first pivotal choice: positioning the ERP with SAP
SAAQ began ERP-positioning work in August 2014 and held extensive discussions with SAP in October. Those discussions were conducted exclusively with SAP. SAP received unusually broad access to SAAQ personnel and operational information before the tender and supplied much of the early cost information.
SAP’s early estimate put ERP implementation at approximately C$141 million to C$163 million and suggested a three-year implementation. The eventual program took about six years and became considerably more expensive. The commission concluded that SAAQ did not independently validate whether an ERP was appropriate for all of its needs or whether SAP’s estimates and assumptions were reliable.
This was a procurement problem as well as a technology problem. Quebec’s Autorité des marchés publics (AMP) found that the market analysis focused only on SAP products and services, that SAP had participated in positioning without equivalent access for competitors, and that tender evaluation was not sufficiently independent, impartial or confidential. It also identified unauthorized participation in selection-committee meetings and failures to preserve committee-member anonymity. AMP findings and recommendations
Was SAP actually a fit for SAAQ?
The evidence does not support the blanket statement that SAP software could never serve SAAQ. SAP had products suited to insurance-related operations, and some insurance functions matched well. The problem was the fit with SAAQ’s entire operating model.
Recommended Free Tools
SAP presented a favorable match. SAAQ’s own assessment put the match for certain road-access requirements at about 50%. Experts cited by the commission considered a match below 80% likely to require so much customization that the approach might not be cost-effective. That distinction matters:
- Capability: whether a software module can perform a function.
- Enterprise fit: whether the package meets the organization’s full requirements without excessive customization.
- Feasibility: whether migration, integration and testing can be completed safely on the proposed schedule.
- Fair procurement: whether the buyer evaluated alternatives independently before allowing one vendor to shape the requirements.
How the SAP-LGS/IBM alliance won
Final tenders opened on January 23, 2017. The SAP-LGS/IBM alliance received the highest quality score among the finalists and was selected after negotiations between March and June. Contracts were signed on June 14, 2017.
Rank #3
Its final price was about 25% below that of the competing SAP-Deloitte alliance, largely because it proposed fewer hours. The bid also contained a particularly low contingency allowance. The final tender’s stated program cost was approximately C$375 million, compared with SAAQ’s internal estimate of C$269 million. The commission noted that simulations involving service-outlet staff were missing from the amended tender, reducing evidence about how the proposed solution would work in frontline operations.
Price alone did not prove misconduct, but fewer hours and limited contingency made the plan less resilient. SAAQ later increased its own implementation-labor commitment by approximately C$26 million. It had also spent about C$2.7 million before the final contract was signed.
Where LGS/IBM’s responsibilities arose
LGS/IBM was the implementation integrator, not a synonym for IBM’s entire global organization. The commission identified several issues involving the alliance:
- SAAQ complained about the quality and skills of personnel assigned to the program.
- More than 40% of planned LGS/IBM personnel were to work outside Quebec, contrary to SAAQ’s expectations.
- The alliance expressed significant reservations about the compressed schedule but accepted it during competitive dialogue.
- SAP initially refused to sign SAAQ’s licensing contract; LGS/IBM then acted as reseller of SAP licenses.
- SAP license costs rose by nearly C$11 million between tender stages, although later negotiations reduced the license amount by C$21 million.
- Later disputes concerned program management, schedule extensions and alleged errors or inaccuracies in agreements.
In a 2020 settlement, SAAQ agreed to assume a share of approximately C$231 million. The commission said the financial details were complex and could not fully analyze privileged mediation communications because LGS/IBM did not waive privilege. These findings support criticism of delivery and contracting, not a conclusion that IBM globally committed fraud.
Why the “big bang” approach magnified the risk
SAAQ demanded a shortened implementation timeline and ultimately replaced major systems in a largely single-step launch rather than moving progressively with a reliable legacy fallback. The program also combined modernization with new and experimental concepts.
Rank #4
A safer public-service pattern would have been to pilot one service or region, run old and new systems in parallel where practical, migrate data in stages, load-test under realistic demand, and require measurable exit criteria before expanding. Instead, the compressed plan left little room to learn from a controlled release. The alliance’s reservations were therefore important, but accepting the schedule meant vendor accountability did not disappear.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Delivery 2, reporting and oversight
Major slippage and cost growth occurred during 2019–2023, particularly in Delivery 2. The Gallant Commission found that, for much of the program, SAAQ management lied to the government and members of Quebec’s National Assembly about implementation progress and submitted misleading reports that concealed overruns. That is the commission’s finding about SAAQ management; it is not a criminal verdict against named vendors.
The governance chain was also weakened. SAAQ centralized control, lacked sufficient internal expertise and did not provide an effective independent stop mechanism. The government did not receive reliable information early enough to intervene. The AMP separately found that contract modifications changed scope, value and organization; related contracts addressed needs already covered by the framework contract; and needs were split in a way that kept an amendment just below a 10% threshold for additional publication requirements.
Timeline of the failure
| Date | Event |
|---|---|
| 2011 | SAAQ creates an 11-year, C$364 million sustainability plan. |
| August 2014 | ERP positioning work begins. |
| October 2014 | Extensive pre-tender discussions take place with SAP. |
| January 19, 2015 | SAAQ’s executive committee agrees to acquire an ERP suite. |
| February 26, 2015 | SAAQ’s board approves the acquisition. |
| January 23, 2017 | Final tenders open. |
| March–June 2017 | SAAQ negotiates with the winning SAP-LGS/IBM alliance. |
| June 14, 2017 | Contracts are signed. |
| 2019–2023 | Delivery 2 suffers major slippage and cost growth. |
| February 20, 2023 | SAAQclic opens to all customers. |
| March 24, 2025 | Quebec establishes the Gallant Commission. |
| April 24–October 24, 2025 | Public hearings are held. |
| February 13, 2026 | Final report is submitted. |
| February 16, 2026 | Final report is published. |
UPAC searched SAAQ headquarters in June 2025 in connection with an investigation. A search is an investigative step; no later criminal charge or final UPAC conclusion was published. The commission’s proceedings and the AMP’s procurement orders are separate from criminal, civil and contractual processes. Gallant Commission official site
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What SAP and IBM said at the time
June 2025 coverage reported SAP referring to its ethics and compliance commitments and IBM declining to comment. Those statements predated the Gallant Commission’s February 2026 report and should not be presented as responses to its final findings. CIO’s June 2025 report
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe responsibility matrix
| Actor | What the evidence supports |
|---|---|
| SAAQ leadership | Chose the ERP path, relied on weak validation, compressed the schedule, centralized governance and provided misleading reports. |
| SAAQ board | Approved major strategic decisions without receiving or acting on every warning in time. |
| Quebec government | Permitted reduced oversight and lacked reliable information early enough for effective intervention. |
| SAP | Influenced pre-tender positioning, supplied cost and fit assumptions, participated in the alliance and faced licensing and product-fit criticism. |
| LGS/IBM | Integrated the solution, submitted the winning bid, accepted the compressed plan, supplied disputed staffing levels and became involved in later disputes and settlement. |
| Procurement system | Allowed a complex process in which competition and independent evaluation were weakened. |
| External assurance | Did not provide an effective independent stop mechanism before launch. |
What the Gallant Commission recommended
The commission made 26 recommendations across five themes. The central direction was stronger public-sector digital capability and earlier intervention, including:
- Centralized expertise for digital transformation and major technology programs.
- Higher approval thresholds and stronger board scrutiny for scope and cost changes.
- Formal risk governance with independent quality assurance.
- More disciplined contract management, including clear accountability and exit rights.
- Reliable reporting of external contracts, internal labor, amendments and recurring costs.
Quebec said it would analyze the recommendations rapidly after the report was filed. Government of Quebec announcement
What ERP buyers should do differently
- Own the requirements. Conduct fit-gap work independently across every business domain before selecting a platform.
- Build a buyer-owned cost model. Test vendor estimates against internal labor, customization, integration, migration, testing, training and recurring services.
- Prototype before final commitment. Require realistic demonstrations and frontline simulations, not only vendor presentations.
- Stage delivery. Use pilots, parallel operation where feasible and explicit rollback criteria instead of an automatic big bang.
- Contract for capability. Name key staff, location expectations, substitution rules, service levels and consequences for missing expertise.
- Preserve independence. Separate requirements advice, implementation delivery and assurance so the same commercial incentives do not govern all three.
- Report the whole picture. Publish original contract value, amendments, internal costs, recurring costs and forecast completion cost in one dashboard.
- Create stop rights. Give the board and an independent assurance function authority to pause a release when readiness evidence is inadequate.
- Protect public continuity. Keep a tested fallback for essential services until transaction, performance and operational thresholds are met.
Bottom line: vendor failure, governance failure or procurement failure?
All three—but not in equal or interchangeable ways. The SAP-LGS/IBM alliance was criticized for commercial assumptions, staffing, licensing, schedule acceptance and delivery problems. SAAQ, however, selected the path, allowed SAP to shape the pre-tender process, failed to validate fit and cost independently, accepted a compressed big-bang design, centralized oversight and misled government about progress. Quebec’s procurement controls did not protect competition or confidentiality adequately.
That is why “SAP and IBM caused the SAAQclic fiasco” is too simple, while “the software was fine and SAAQ alone failed” is also unsupported. The official record describes a system-wide accountability failure in which buyer governance and procurement weaknesses made vendor shortcomings far more damaging.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
