CS-038failure
Government of Canada (Public Services and Procurement Canada)
Transformation of Pay Administration and the Phoenix pay system (2009 onward; live from 2016)
- Region
- North America
- Country
- Canada
- Industry
- Public Sector and Government (Other (cross-industry))
- Functions
- HR & Workforce, IT, ERP & Digital, Finance & FP&A, Operations & Service Delivery, Risk, Compliance & Internal Audit
- Topics
- Legacy ERP and fragmented systems block execution; Cross-functional processes are slow and broken; Service delivery is too slow, unreliable or expensive; Technology spending is growing without business returns; Workforce costs and capacity no longer match demand
- Starting situation
- New initiative
- Period
- 2009
- Last verified
- 1 November 2026
Executive summary
In 2009 the Government of Canada set out to modernise pay for about 290,000 public servants by centralising pay advisors in Miramichi, New Brunswick, and replacing a 40-year-old system with Phoenix, delivered under an IBM contract on PeopleSoft software [C02, C03, C04]. The initiative was budgeted at $310m and expected to save about $70m a year [C01].
Phoenix went live in two waves in February and April 2016 [C16]. A year and a half later about 500,000 pay requests were outstanding and pay errors exceeded half a billion dollars [C19]. The Auditor General called the project 'an incomprehensible failure of project management and oversight' [C17].
The three numbers that matter: more than 100 important pay functions deferred or removed to fit a $155m build budget that IBM had estimated would need $274m [C07]; $937.5m of Phoenix-related spending in the single year 2024-25 [C32]; and a successor system estimated at more than $4.2bn, while 233,653 transactions remained in the backlog in September 2025 [C33, C34].
The one lesson (KB inference): a savings target booked in headcount before the system works turns a go-live date into a point of no return; the gate must test whether people will be paid correctly, not whether the project is on budget [C03, C13, C14].
Outcome: failure
The initiative was abandoned, exited or written down, or an official finding called it a failure.
Basis of the outcome
The Auditor General of Canada called the Phoenix project 'an incomprehensible failure of project management and oversight' and concluded that the decision to implement it was unreasonable on the information available at the time. A year and a half after launch, about 500,000 pay requests were outstanding; the government has since spent heavily on stabilisation (Phoenix-related spending of $937.5m in 2024-25 alone) and is replacing the system, with a preliminary estimate of more than $4.2bn for the successor. The backlog still stood at 233,653 transactions in September 2025.
Key figures
| Phase | Figure | Value | When | Verification |
|---|---|---|---|---|
| Before | Employees in scope | about 290,000 | 2009 | official_finding |
| Before | Initiative budget / expected annual saving | $310m / about $70m | 2009-2012 | official_finding |
| Before | Phoenix build budget vs IBM estimate | $155m vs $274m | 2009 onward | official_finding |
| Before | Pay functions deferred or removed | more than 100 | pre-2016 | official_finding |
| Before | Miramichi capacity shortfall | 23,000 fewer files than expected | Jul 2015 | official_finding |
| During | Go-live waves | 34 organisations (24 Feb 2016); 67 (21 Apr 2016) | 2016 | official_finding |
| During | Outstanding pay requests | about 500,000 for 150,000+ employees | mid-2017 | official_finding |
| During | Outstanding pay errors | more than half a billion dollars | Jun 2017 | official_finding |
| During | IBM contract value | $407.5m after 47 amendments | 2019 | official_statement |
| After | Backlog beyond normal workload | 384,000 (Jan 2018 peak) to 98,000 | Apr 2021 | official_statement |
| After | Phoenix-related expenditures in one year | $937.5m | 2024-25 | official_statement |
| After | Backlog (OAG measure) | 233,653 transactions; 133,619 employees | Sep 2025 | official_finding |
| After | Successor (Dayforce) preliminary estimate | more than $4.2bn | Mar 2026 | official_finding |
- official_finding
- A finding of an inquiry, court or regulator.
- official_statement
- A government or ministerial statement. It is official, but political, and is not a finding.
Practices this case bears on
- SupportsGate every go-live on measured readiness, not on the calendar BP-001
- SupportsTie every benefit to the financial statements, bank it before counting it, and keep tracking after the programme ends BP-010
- SupportsSimplify what you sell and the rules you run before you automate or scale them BP-011
- SupportsBudget the whole-life cost of a core programme, treat budget rises as new decisions, and retire legacy on a dated plan BP-013
- SupportsMake a business executive, not IT, the owner of a technology-led transformation BP-015
- SupportsMake bad news safe and fast to reach the top, and act on it BP-022
Sources
- S01 Opening statement to the Standing Committee on Public Accounts: Phoenix Pay Problems (2017 Fall Reports, Report 1) · Michael Ferguson, Auditor General of Canada, Office of the Auditor General of Canada, 2017-11-28 · accessed 2026-11-01
- S02 Report 1—Building and Implementing the Phoenix Pay System (2018 Spring Reports of the Auditor General of Canada) · Auditor General of Canada, Office of the Auditor General of Canada, 2018-05-29 · accessed 2026-11-01
- S03 Opening statement to the Standing Senate Committee on National Finance: Building and Implementing the Phoenix Pay System · Michael Ferguson, Auditor General of Canada, Office of the Auditor General of Canada, 2018-06-12 · accessed 2026-11-01
- S04 Lessons Learned from the Transformation of Pay Administration Initiative · Goss Gilroy Inc., Treasury Board of Canada Secretariat, 2017 · accessed 2026-11-01
- S05 Phoenix: Standing Committee on Public Accounts—May 27, 2021 (briefing material) · Public Services and Procurement Canada, Public Services and Procurement Canada, 2021-05-27 · accessed 2026-11-01
- S06 An 'incomprehensible failure' · Sheila Brawn, Canadian HR Reporter, 2018-07-01 · accessed 2026-11-01
- S07 Replacing Phoenix pay system cheaper than fixing its mess will be, PBO reports · Terry Pedwell, Global News (The Canadian Press), 2019-05-16 · accessed 2026-11-01
- S08 Government of Canada and public service unions finalize agreement to compensate federal employees impacted by the Phoenix pay system · Treasury Board of Canada Secretariat, Treasury Board of Canada Secretariat, 2019-06-13 · accessed 2026-11-01
- S09 Question period note: Phoenix IBM and systems upgrades · Public Services and Procurement Canada, Public Services and Procurement Canada, 2019 (late) · accessed 2026-11-01
- S10 Phoenix pay system expenditures, 2024–25 ($ millions) · Treasury Board of Canada Secretariat, Treasury Board of Canada Secretariat, 2025 · accessed 2026-11-01
- S11 Opportunity to address risks before launching the government's new pay system (2026 Reports of the Auditor General, Modernizing the pay system) · Auditor General of Canada, Office of the Auditor General of Canada, 2026-03-23 · accessed 2026-11-01
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026 · Last verified 1 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

