The Legacy Annuity.

In December 2025 the Provincial Auditor of Saskatchewan released the 2025 Report — Volume 2. Two findings, in different chapters, together describe one operation.1

The first finding is on the Saskatchewan Health Authority's Administrative Information Management System: approximately two hundred and fifty million dollars spent, three failed rollouts across three years, the scheduling component cancelled and the system reverted to its legacy predecessor on ministerial order. The full breakdown is the subject of Case 10 in this volume.

The second finding is on the Enterprise Business Modernization Project — EBMP — managed not by the Saskatchewan Health Authority but by the Ministry of SaskBuilds and Procurement itself. EBMP is the Government of Saskatchewan's parallel attempt to overhaul provincial administrative systems and modernise the back-office operations of its ministries. The Auditor reports EBMP is projected at two hundred and sixty million dollars to fully implement, following a one hundred and thirty million dollar budget overrun and a two-and-a-half-year delay as of 31 March 2025.

Approximately half a billion dollars of attempted back-office IT modernisation, run through two parallel projects in two adjacent corners of the same provincial procurement architecture. Both projects produced the same outcome at different speeds. The official framings of each have stressed that the projects are difficult, the technology is complex, the integration challenges are substantial. Both framings, taken individually, are unfalsifiable. Taken together, with the same architecture producing the same outcome in two locations, they describe a property of the architecture rather than of the projects.

The Saskatchewan editorial reporter Tammy Robert paired the two projects publicly in January 2026 under the name EBMP-AIMS.10 The pairing is structurally correct.

The Provincial Auditor's 2025 examination of the central IT-project monitoring function — the part of SaskBuilds and Procurement that monitors IT projects across most of the Government of Saskatchewan — produced a finding the modernisation vocabulary cannot absorb.

Between April 2024 and March 2025, the ministry monitored twenty IT projects with a combined forecast of approximately forty million dollars. Eight of those twenty projects ended over budget. Twelve of the twenty were delivered late. One unnamed client spent more than four million dollars on a project before it was cancelled, in the Auditor's own carefully neutral phrasing, "due to the vendor's inability to meet the client's requirements."1

Forty per cent over budget. Sixty per cent late. One in twenty cancelled outright after seven figures of spending. These are not the figures of an institution whose IT delivery is occasionally challenged by particularly complex projects. These are the figures of an institution whose IT delivery is, as a baseline, not functional. The Auditor's five recommendations focus on improvements to monitoring — formal reporting requirements, percentage-on-time-and-budget tracking, completeness assessment of client-reported risks. The recommendations address what the central ministry can see and act on. They do not address what the underlying institutional capability deficit is or where it came from.

Forty per cent over budget. Sixty per cent late. The pattern is the case.

This is appropriate: that is not the Provincial Auditor's job. It is the job of the responsible ministers and senior public-service leadership, who have had the data on this pattern for years — in successive Auditor cycles, in successive parliamentary questioning, in the cumulative documentary record of each failed project after the next — and who have continued to characterise each new failure as a difficult particular case rather than as a property of the system the cases are emerging from.

The current cycle is the visible part of a much older pattern. To see it, return to twelve years ago, at SaskEnergy.

In its 2013 Report — Volume 1, the Provincial Auditor of Saskatchewan published Chapter 19, "Securing SaskEnergy's SCADA System."2 SCADA — Supervisory Control and Data Acquisition — is the system SaskEnergy uses to monitor and control compressor stations, pipelines, and related equipment across its natural-gas distribution network. That network serves approximately three hundred and fifty-eight thousand customers in ninety-two per cent of Saskatchewan communities. SCADA is, in operational terms, the system that runs the pipelines.

For the audit period of September 2012 to February 2013, the Provincial Auditor found that SaskEnergy did not have effective processes to secure its SCADA system verified. The audit identified gaps across threat-and-risk assessment, policies and procedures, and the confidentiality, integrity, and availability of the system. The audit also recorded, in its own framing, that critical-infrastructure providers like SaskEnergy and SaskPower "are interdependent, such that a failure to provide services by one of the providers could lead to the failure of services provided by [another]." The Auditor's own statement of the systemic-risk implication of one Crown's capability gap is twelve years old.

The audit function works. The follow-up rates are documented and respectable — seventy-six per cent of recommendations fully implemented after first follow-up, eighty-seven per cent after subsequent.1 What the audit function is doing, however, is identifying point gaps and securing point remediations. What it is not doing — because it cannot, structurally — is preventing the next gap from emerging in the adjacent system, or addressing the upstream institutional condition that produces gap after gap across two decades.

The audit reports are the visible record of the drift. They are not a brake on it.

The structural question the public record leaves open — and the question this case is specifically about — is what fills the institutional capability gaps the Auditor documents.

The Provincial Auditor's 2025 example of the client who spent more than four million dollars before cancelling a project "due to the vendor's inability to meet the client's requirements" is the case study in microcosm. The client institution did not have the internal capability to recognise, before signing the contract, that the vendor could not deliver. The client institution did not have the internal capability to recognise, during the four-million-dollar spend, that the project was failing. The client institution discovered the vendor's inability only at the point of cancellation. The vendor, meanwhile, was paid for the work delivered up to the cancellation, regardless of whether that work met the requirement.

This is the structural shape of the vendor annuity. An institution that has hollowed out its own technical and managerial capability cannot, by definition, oversee a vendor competently. It cannot specify requirements precisely, cannot evaluate proposals critically, cannot manage execution actively, cannot recognise failure early, cannot conduct meaningful audit, cannot conduct a replacement procurement competently when the current vendor's contract ends. Each of these incapacities translates directly into vendor leverage. The vendor's continued engagement becomes the institution's only continuity of operation. The annual contract becomes a permanent retainer. The "modernisation" never finishes, because the institution that cannot oversee the current vendor cannot complete the replacement that would end the vendor's engagement either.

Saskatchewan's Crown corporations and provincial ministries have spent two decades in this condition, with the documented capability deficits stretching back at least to the 2002 Provincial Auditor report on Government IT systems generally. The legacy stacks that maintain Crown-corp operations are not merely old. They are maintained by external vendors whose business model is the continued maintenance, who have no commercial incentive to retire the legacy in a way that would end their own engagement, and whose understanding of the systems exceeds, in many cases, the understanding of any current employee of the client institution. The institution pays for the maintenance in perpetuity because the institution can no longer do the maintenance itself specific contractor count: not carried.

When a new modernisation project is initiated — AIMS, EBMP, the others — the same dynamic governs. The new project's vendor is selected by an institution that lacks the internal capability to evaluate the proposal critically. The new project's execution is overseen by an institution that lacks the internal capability to recognise early failure. The new project's success criteria are negotiated by an institution that lacks the internal capability to articulate precise requirements. The new project, predictably, joins the eight-of-twenty-over-budget cohort and the twelve-of-twenty-late cohort. The "transformation journey" has produced not a transformation but the next layer of the same annuity. The vendor changes; the annuity continues.

The § 04 argument describes the annuity's existence. The mechanism by which it is renewed — at each procurement cycle, in each individual tender — is observable in the procurement process itself, and the most relevant receipts are in the Saskatchewan public record.

The architecture, in its public description, is open. SaskTenders.ca, administered by the Ministry of SaskBuilds and Procurement, posts opportunities for goods, services, construction, and IT work.11 Any qualified business may register on the portal, may receive bid-matching notifications, and may submit proposals. The Government of Saskatchewan has, since at least 2016, maintained a public lobbyist registry that requires paid lobbyists to disclose their activities targeting elected officials and civil servants.24 On its own description, this is a transparent, competitive, accountable system for the supply of services to the provincial state.

The architecture, in its operation, contains six mechanisms by which the set of effective bidders for a given competition is reduced from "any qualified business in Canada" to a small, mutually-known cohort. Each mechanism is, in isolation, defensible on its own terms. The aggregate effect is the annuity.

The first mechanism is the threshold barrier. Above the open-tender thresholds, suppliers must satisfy prequalification, security clearance, bonding, insurance, and trade-agreement-related requirements before they can bid.12 A firm that has never previously won government work cannot easily clear these barriers; a firm that has cleared them once tends to retain that status across competitions. The mechanism rewards incumbency at the firm level, regardless of which firm wins a specific competition. The set of firms eligible to bid on large Saskatchewan IT contracts is, on the structural evidence, in the range of five to ten at any given time specific cohort: reserved for dedicated Case.

The second mechanism is the time barrier. The Provincial Auditor of Saskatchewan documented this directly. In a 2019 special audit of eHealth Saskatchewan's procurement practices, Auditor Judy Ferguson tested three procurement requests and found that eHealth gave vendors only 5 to 10 days to respond verified.13 The Auditor's own characterisation: this short response window "could increase the likelihood that some may not see the request or choose not to respond because of the short time frame. Fewer responses result in fewer options to acquire goods or services at the best price." This is the Provincial Auditor of Saskatchewan, in her own audit, naming the time-based barrier-to-entry mechanism in Saskatchewan public-sector IT procurement, in 2019. A firm with no prior relationship with the issuing institution — no monitoring of internal communications, no existing client contact, no in-place proposal team — cannot meaningfully respond to a 5-to-10-day window. A firm with those relationships and that infrastructure can. The window is, on the Auditor's own framing, a filter.

The third mechanism is the biased-specification problem, documented by the Canadian International Trade Tribunal — the federal body that adjudicates procurement complaints. In Re MTS Allstream Inc. in August 2005, the CITT examined a federal procurement and found that specific mandatory technical requirements — including a transition timeframe of impossible compactness — "biased the technical specifications" in favour of the incumbent vendor.23 The Tribunal distinguished between "legitimate requirements that favoured a natural incumbent advantage" and "requirements that unfairly biased the competitive process by establishing standards that were impossible to meet by other bidders." The drafting of tender documents is performed by client institutions that, as Case 10 establishes, have hollowed out their internal technical and managerial capability. Without that capability, the client institution consults — formally or informally — with vendors familiar with the operational environment. The vendor consulted is, predictably, the incumbent. The tender that results reflects the incumbent's particular product and methodology choices. The procurement is, technically, fair. The upstream process that produced the tender is, structurally, captured.

The fourth mechanism is the vendor-hospitality problem, and the Provincial Auditor of Saskatchewan documented this directly as well — in the same 2019 eHealth audit.13 The Auditor found eight instances of vendor-sponsored travel where vendors covered additional costs without specific contractual provisions, including a trip to the PGA Championship and a trip to the Indianapolis 500. Two of these trips involved travel that resulted in the vendor receiving a contract. The Auditor further noted that two of the three eHealth employees subsequently disciplined or dismissed had decision-making responsibilities over eHealth's procurement of goods and services. The eHealth audit also identified ten contracts that had been sole-sourced without written justification. The vendor in the 2017 PGA Championship case — Lexmark — had received approximately $2.6 million in eHealth contracts since 2015 verified.16 The contractual relationship between the institution and the vendor pre-dated the trip, encompassed the trip, and continued after the trip. The institution's response, in a September 2018 email subsequently obtained by CBC: "All contracts with the companies involved have been reviewed and it was determined that no follow-up action was required."14 The Auditor's findings, eight months later, said otherwise.

The trip happened. The contracts followed. The institution reviewed the contracts and reported no follow-up required. The Provincial Auditor reviewed the same record and reached a different conclusion.

The fifth mechanism — and the one operating now, in current SaskBuilds data — is the definitional one. In June 2025, the Saskatchewan NDP Opposition released documents obtained through a Freedom of Information request showing that SaskBuilds and Procurement had awarded 666 contracts in fiscal year 2024–25 verified.17 The government had publicly stated that approximately 90 per cent of contract value went to Saskatchewan-based companies.19 The NDP's analysis of the same FOI documents showed that only approximately 51 per cent of contracts and 58 per cent of contract dollars actually went to firms headquartered in Saskatchewan.20 The gap between 51 per cent and 90 per cent is the entire mechanism. Companies the government classified as "Saskatchewan-based" in the data included Crumb Rubber Manufacturing of Newport Beach, California, and Mitsubishi of Canada, headquartered in Ontario. Both sides confirmed the definition: a "Saskatchewan-based" business is any firm with a place of business in Saskatchewan, employing Saskatchewan residents, registered with the Information Services Corporation. The definition is drawn from the Canadian Free Trade Agreement and is legally defensible. It is also, on the SaskBuilds data, sufficiently elastic that a California rubber manufacturer and an Ontario automotive distributor are classified as Saskatchewan businesses. The 90 per cent figure used in the government's procurement statements is, in NDP characterisation, "bogus." The definition that produced the figure is, in government characterisation, replication of Canadian-trade-agreement language. Both characterisations are accurate in their own terms. The structural fact is the gap between the headline and the underlying composition. The headline is the laundering. The composition is what the laundering covers.

The sixth mechanism is the broker-and-sub-hire model, and its cleanest public-record demonstration is, for the moment, federal. Between 2020 and 2024, the federal procurement system permitted GC Strategies — a two-person firm with no in-house IT delivery capability — to win contracts including approximately $19.1 million related to the ArriveCAN application.21 The work was performed not by GC Strategies but by sub-contracted firms; GC Strategies' role was as broker and prime contractor, retaining a margin on the sub-contracted work. In June 2025, the federal government determined GC Strategies ineligible to enter government contracts for seven years under the Ineligibility and Suspension Policy.22 The Auditor General's Performance Audit characterised the case as "in line with previous internal and external audits and reviews relating to professional services contracts." That phrase, in this context, is the structural finding: GC Strategies is the visible part of a federal procurement market in which broker-and-sub-hire is the operating model. The same mechanism necessarily operates in any jurisdiction whose procurement architecture admits the same three preconditions — prequalification barriers excluding individual practitioners, mandatory-clause filters favouring incumbents, and the absence of internal client capability sufficient to oversee delivery directly. Saskatchewan satisfies all three preconditions. The Provincial Auditor's eHealth findings demonstrate that the mechanism operated in Saskatchewan in at least one documented case. The SaskBuilds FOI demonstrates the aggregate outcome — six hundred and sixty-six contracts, with the definitional laundering of who counts as a local bidder running across the entire portfolio.

Six mechanisms. Each one defensible in isolation. The aggregate is the annuity, renewed at each procurement cycle, in each individual tender, across the entire portfolio. The cohort that benefits does not need to coordinate formally to behave like a cartel. The structural barriers ensure that no individual project produces unexpected competition, and the institutional incentives ensure that no individual procurement officer can credibly correct the pattern at the level of one decision. The mechanism is the architecture. The architecture is the case.

Read together with the surrounding cases, the laundering pattern becomes one operation seen from multiple angles.

The three Cases together — 10, 11, 12 — describe one operation in three movements. Hiring practices produce institutional incapacity; institutional incapacity produces vendor dependency; vendor dependency is brokered through the access layer; the access layer's credentials are themselves produced by the same public-service architecture; the loop closes. The annuity continues. Each "modernisation" feeds the next cycle. The public account treats each cycle as a discrete project with discrete challenges. The structural reality is one architecture, observable in the public record across at least two decades.

The laundering operation this case describes is not primarily about money — although the money is real. It is about capability. What is being laundered is the absence of internal institutional capability, which is rendered in public discourse as a "transformation journey," a "modernisation initiative," a "complex undertaking requiring partners with deep expertise." Each of these phrases is technically accurate. None of them names the underlying condition: that the institution speaking the phrase no longer possesses the capability to do what it is contracting external partners to do, and has not possessed that capability for long enough that no one in the institution now alive remembers when it did.

This is the capability layer of the laundering — a layer not previously named in the volume's laundering taxonomy and identified here for the first time. Reputation laundering works because the institution borrows another entity's reputation to cover its own. Capability laundering works because the institution borrows another entity's capability and describes the borrowing as its own modernisation. The vendor delivers; the institution puts its name on the deliverable; the public account describes the institution as having modernised, when what has actually occurred is the institution has paid a vendor to do work the institution no longer knows how to do.

The vendor delivers. The institution puts its name on the deliverable. The public account describes the institution as having modernised.

The Provincial Auditor's audit reports are, in this frame, doing exactly what audit reports do: assessing whether institutional processes are effective, identifying gaps, recommending improvements. What the audit function cannot do, structurally, is observe that the underlying condition — the institutional capability deficit — is being laundered into the modernisation vocabulary. That would require an audit of the institutional self-description, not of institutional processes. Such an audit is not within the Auditor's mandate, and would not be welcome from any external party undertaking it.

The cost is paid in two distinct ways. The taxpayer pays in cash, through the cumulative cost of decades of contractor retainers and serial modernisation overruns — by the most conservative reading of the public record, well into the billions over the two decades the pattern is documented to have run. The institution's own workforce pays in the second currency: in the absence of internal advancement opportunities for senior technical staff, in the loss of professional respect within the institution as the work is described by managers who cannot do it, in the steady migration of capable people to private-sector employers who pay more and treat them as professionals. Each cohort of workers who leaves takes a piece of the institution's residual capability with them. The vendors hire some of them, completing the loop in personnel terms — the people who used to work for the Crown corp now bill the Crown corp through the vendor that employs them.

It does not claim that all external-vendor engagement is laundering. Many specific vendor relationships are appropriate, well-managed, and produce value commensurate with their cost. The structural pattern observed here is about the aggregate condition of institutional capability across multiple Crowns and ministries over two decades, not about any single contract.

It does not claim that the Provincial Auditor of Saskatchewan has failed to do its job. The audit function has, on the contrary, done what it is structurally designed to do: surfaced point gaps, issued recommendations, tracked implementation, and produced a continuing public record across decades. The structural critique the case offers is precisely about what audit cannot address, not about audit failing to address things within its mandate.

It does not claim that any specific named senior official at any specific Crown corporation or ministry is responsible for the institutional capability deficit. The deficit is the inheritance of two decades of incremental decisions made by many people across multiple administrations and many institutions. The structural argument operates at the level of the aggregate condition, not at the level of individual conduct.

It does not claim that named vendors operating in Saskatchewan are exploiting client institutions in bad faith. The vendor that "was unable to meet the client's requirements" in the Auditor's 2025 example may well have been operating in entirely good faith and produced the four-million-dollar non-deliverable through circumstances neither side anticipated. The structural argument is about the dependency relationship, not about vendor conduct.

It does not claim a specific contractor count for SaskEnergy's legacy portfolio. The Case characterises the contractor footprint structurally and reserves the specific number for a Rev 02 if and when a sourceable disclosure is in hand.

It claims this: the Provincial Auditor of Saskatchewan has documented, across at least two decades of audit cycles, a recurring pattern of institutional capability gaps at Crown corporations and provincial ministries in Saskatchewan; the 2025 portfolio-level finding confirms the pattern is operating at the level of routine institutional delivery, not at the level of unusually difficult particular projects; the half-billion-dollar EBMP-AIMS pair is the headline-grade instance of a much broader baseline rate; the structural consequence of institutional capability deficit is permanent vendor dependency, which converts the public payroll for institutional staff into a permanent contractor annuity over time; and the modernisation vocabulary launders the underlying capability condition as a "transformation journey," concealing the structural reality of the dependency relationship.

The strongest version refuses to indict individuals, refuses to dismiss legitimate vendor work, and refuses to soften the institutional indictment.

The pattern is sourced to the Provincial Auditor. The pattern operates across decades. The pattern is recognisable in any organisation that has ever attempted institutional self-description in modernisation language while paying external vendors for the underlying capability. The pattern is the case.

The Provincial Auditor identified SaskEnergy SCADA capability gaps in 2013.
The Provincial Auditor identified the central IT-project monitoring pattern — 8 of 20 over, 12 of 20 late — in 2025.
AIMS spent ~$250M across three failed rollouts; EBMP is ~$260M projected with $130M overrun and 2.5 years late.
The audit function works at point-gap remediation and cannot, structurally, address the upstream capability deficit.
The deficit becomes a permanent vendor annuity.
The modernisation vocabulary launders the deficit as a "transformation journey."
All six statements are true.
Their relationship is the case.