We wish Alex Benay well and thank him for his years of public service. During his time in this role, important work did move forward, including efforts to reduce parts of the backlog of unresolved Phoenix pay transactions and advance a replacement system.
His departure, however, raises questions that deserve clear and prompt answers.
Two days ago, the Auditor General confirmed that Phoenix remains in crisis. Now, the senior executive leading its replacement has stepped down.
That sequence calls for more than a routine transition – especially as the Phoenix pay system is about to experience a surge of work with WFAs, transfers and early retirement requests.
Earlier this month, Benay expressed confidence that the system could handle a surge of complex pay transactions tied to workforce adjustment – while also acknowledging that public servants were “right to be worried” about whether they would be paid correctly and on time.
That is not a contradiction. It is a reflection of where this file has stood for nearly a decade.
The Auditor General’s report sets out the reality. More than 233,000 pay transactions remain in a backlog, affecting over 133,000 federal employees, many outstanding for more than a year.
At the same time, the government is moving ahead with a replacement system expected to cost more than $4.2 billion, without first resolving the conditions that led to the Phoenix disaster. The report warns that unresolved errors could be carried into the new system and undermine it from the start.
Federal public service workers have waited long enough. They deserve a credible plan grounded in expertise and accountability, one that fixes the underlying problems before moving forward.
That means eliminating the backlog before any transition, completing pay rule simplifications in partnership with unions, being transparent about the full cost of the new system and how success will be measured, and ensuring the public service has the internal expertise and capacity needed to get this right.
We hope this moment prompts the serious reset it requires.
Published on 27 March 2026