Integrated strategy for human resources and pay
Progress update session, January 2025
Since the launch of the Phoenix Pay System in 2016, work to stabilize Pay Operations has been ongoing. Despite significant efforts by the Office of the Chief Human Resources Officer (OCHRO) at the Treasury Board of Canada Secretariat (TBS) and Public Services and Procurement Canada (PSPC), public servants continue to feel the impacts of its roll out eight years later.
The session informed public servants of the continued work being done to stabilize operations and the current status of the transformation project to integrate pay and human resources into a central system.
A commitment has been made to move forward transparently on this file through regular updates, a revitalized webpage and user engagement. This was the third of a series of quarterly updates that will be organized in the coming year.
This video is the recording of the event which held on January 22, 2025. Both an English and a French session took place separately. Most topics were covered equally during both sessions, except for the question-and-answer period at the end, which took questions from the different audience members. Below the video, you will find the list of all questions and answers addressed during the French session.
Transcript of the video: Progress update session, January 2025
Start of video
(Text on screen: Public Services and Procurement Canada)
[Video opens with Mitos San Diego on a stage and talking from podium.]
Welcome to the third quarterly update for HR and Pay for the Government of Canada. This is the English event for all public servants.
(Text on screen: Mitos San Diego, Senior Director, Strategy and Integration Branch, Human Capital Management portfolio, Public Services and Procurement Canada)
For those of you tuning in for the first time, I’m Mitos San Diego, Senior Director in the Strategy and Integration Branch within the Human Capital Management portfolio at PSPC, and I will be moderating today’s session.
Before we begin, I would like to acknowledge that since I’m in Ottawa, I’m on the unceded traditional territory of the Anishinaabe and Algonquin Nations. We are grateful to meet on this land and acknowledge the ongoing contributions with Indigenous communities across Canada.
As we all work in different places, I invite you to reflect on the Indigenous territory where you are joining us today.
[Moment of silence]
You can participate in today’s session using Slido. We’ll be launching a few polls and using this platform for the Q&A at the end. To join, scan the QR code on the screen or go to Slido.com and enter the code #GCHRPAY3. Alternatively, you can also click on the Slido button on the top menu of your screen.
To get us started, we have two questions for you:
- Overall, how worried are you about how the HR and Pay transformation will affect you?
- Which topics would you most like to hear about during the future sessions?
While you are connecting to Slido, here are a few housekeeping items.
This session is recorded and will be posted on Canada.ca.
There is sign language interpretation available. To access, click the button on the top right of this video. Closed captioning is also available.
If you’re experiencing technical difficulties, try disconnecting from your VPN.
So without further ado, let me introduce our panel:
[The video goes full screen where you see Mitos San Diego talking at the podium and Francis Trudel and Alex Benay sitting at a table on the stage.]
Christiane Fox, Deputy Clerk of the Privy Council and Associate Secretary to the Cabinet, joining us virtually; Francis Trudel, Associate Chief Human Resources Officer at the Treasury Board of Canada Secretariat; and Alex Benay, Associate Deputy Minister of Public Services and Procurement Canada, Human Capital Management.
I will now turn it over to Deputy Clerk to begin.
[Video changes to Christiane Fox talking from her office virtually.]
(Text on screen: Christiane Fox, Deputy Clerk of the Privy Council and Associate Secretary to the Cabinet)
Thank you very much, Mitos, and nice to see you Francis and Alex. Sorry I could not be there in person. We were just coming off a call with the premiers across the country on all things Canada-U.S., so I apologize that I can’t be here but very happy to be online, and Happy New Year to all of you. I think I can still say that in January especially given this is our first update of 2025.
And I guess off the starting gate, I do want to just kind of recognize that, you know, it continues to be a super busy time with so many of you and lots of change, obviously, as we navigate what’s happening in the House and Can-U.S. and a lot of this impacts our day-to-day. So I just want to take a moment just to thank all of you for your continued work. And like I said, I think it’s really important and I’m very happy to be here for the third quarterly update on HR and Pay.
These sessions are key opportunities for us to share progress, but most importantly for us to listen to your feedback and keep moving forward together. Your input absolutely matters, and it will and it does continue to guide the work that, you know, the three of us do, but even more broadly across departments and deputy community as well as HR teams in each department and agency.
Everything that we’re doing around testing, around transparency, around engagement is about rebuilding trust in public service management in our institution, in our protest—in our processes, sorry, and it’s easy to lose that trust. So we’re kind of very cognizant of that and want to be kind of working very closely with you.
So HR and Pay is at the front and centre of this and it’s driving our efforts in terms of the conversations that we’re having to make improvements, to be more service-oriented, and be aware of the very real impacts that it has on all of you. And I just want to reiterate that advancing this work remains a priority for the leadership across the public service: myself, the Clerk; and every leader across departments and agencies.
So, during our October update, many of you raised concerns about pay issues, around AI, around employee support and communication.
[A graphic takes up 80% of the screen and a small square still reminds of Christiane Fox on video in the bottom right corner.]
(Title text on graphic: Recap: What We Said Last Time)
(Text on graphic;
On October 2, 2024, we updated employees, unions, and the media on the HR and Pay.
- “This is what transparency is all about – good or bad, letting the numbers tell the story”
- Launched commitment tracker to show progress for FY2024-25
- Work to simplify rules and standardize systems and processes:
- Simplification efforts to include acting administration; liquidation of leave; retroactive payments; allowances; general definitions; annual rates of pay; extra duty pay, and union dues.
- TBS issued Directive on the Stewardship of Human Resources Management Systems.
- MyGCHR as interim GC enterprise HR system standard.
- “This journey is not solely a question of which IT solution we use – it is about changing the culture of HR and Pay to make it more efficient and human.”
- Transparency by Design engagements: Published What We Heard Report from engagements held with key stakeholders in Summer/Fall 2024.
- First release of 50 documents and datasets about HR and Pay on the Open Government Portal.)
A recurring frustration was not knowing what’s happening with your pay or what actions were needed. So, I do want to reassure you that we’re making it a priority to share more information and create opportunities for you to engage directly, because I know that we can’t address every single question, especially when it comes to kind of, you know, very personal context and we want to make sure that we are engaging directly.
And today is part of that. You can obviously ask questions during the live Q&A or answer the polls in Slido, and we are paying close attention to that. But there is also kind of surveys that we’re going to send that you can, you know, respond to particular questions or share particular things after this event. There’s, as Alex mentioned last time, like the Facebook page.
There is the GC and Pay Benefits page that you can actually go on and get some support. We’ve engaged with our client contact centres to help you with specific scenarios, and of course, you can sign up for new HR and Pay newsletter. And that’s just kind of ways that we are attempting to create different paths for all of you should you have particular questions.
In October, we also introduced a commitment tracker and it outlined 11 goals for this fiscal year. So, it’s not just about tracking progress. It’s really about a real conversation with all of you, and we can sort of tackle some of these challenge together. And I think it is important that we are tracking these 11 goals and how we’re measuring our outcomes against it.
We released the first wave of HR and Pay documents in our Open Government Portal. This kind of transparency means it’s an attempt from us and the leadership structure and the DM Governance Committee to demystify our work, to make sure that everyone internally and externally has access to the information they need around HR and Pay. And lastly, we discussed how we’re simplifying our HR rules and processes.
So, what have we done since October? I am happy to report that since October 2024, we have made significant progress. So, the sponsorship group, which I refer to which myself, Francis, Alex and others are part of, it’s got departments like the Treasury Board and the Secretary is part of that, the SSC, PCO, and PSPC Finance. We meet bi-weekly, and we drive challenge and shape the project that we’re all sort of focused on.
And so what have we been able to achieve as a result of these bi-weekly meetings that we continue to have? Launching the internal AI operational ethics review board in October and the external AI advisory board in December, to really ensure that we’re using AI responsibly, we’ve engaged thousands of public servants through Dayforce user awareness sessions and I’m sure that Alex would talk a little bit about the National Lobby Roadshow that we really tested out to make sure the platform works for those who are, you know, working in it every day and those who are being served by it.
As I said, we’re adding—I think we’ve added over 100 documents on Open Government Portal to really be transparent around the decisions that we’re making.
The first checkpoint for the feasibility analysis project in November was approved and so the next one is scheduled for February and that really assesses kind of what is our system, enterprise, departmental readiness for this big shift.
And then finally, we’ve reviewed the unified actions for pay and departmental surcharge initiatives really to ensure that departments are prepared for transition while they are improving the current operations of the pay system. And we’re not going to stop there, obviously.
In the first quarter of this fiscal year, we’re going to talk about privacy, security, the streamlining of Pay and HR information, which I know can be really tough to access clear information, so single, easy access service for employees.
So, in closing, just before I turn it to Francis, I do want to thank the Pay and HR teams for their hard work, and thank you all for your engagement, I am proud of the progress that we’re making. I know that sometimes it can feel like it’s not fast enough, but I think that taking the time to engage in conversation, taking the time to hear directly from you all about your experiences will help us at the end of day get a better product that will have results for all of us. And I think that’s what we’re really pushing towards.
So Francis, with that I will turn it over to you to update us on the simplification of HR rules and processes, which you started at a conversation back in October. So over to you.
[The graphic changes and the small video of Christiane Fox changes to Francis Trudel sitting at the table talking.]
(Text on screen: Francis Trudel, Associate Chief Human Resources Officer at the Treasury Board of Canada Secretariat)
[Graphic on screen.]
(Title text on graphic: Strategic Alignment)
(Text on graphic;
PSPC and TBS
- Working cohesively towards the same HR and pay outcomes
- Continuing collaborative work on each initiative
- Stakeholder engagement at many levels
HR & Pay Simplification
- Ongoing engagement sessions with bargaining agents
- Classification simplification
HR & Pay Standardization
- HR transformation culture moving towards consolidation of HR systems
- Departments and agencies onboarding to MyGCHR
- HR and pay training for employees)
Thank you, Chris. Thank you for the great overview. Hi everyone, a great pleasure for me to be here again with you for a quick update on the HR to Pay and the role that TBS OCHRO is doing in that space.
I think the best way for me to do a short summary of an update is maybe probably to start where I left at the last session, which is to talk about the two pillars of work that the TBS OCHRO, one being the simplification agenda and the other being the standardization agenda.
Just maybe before I do, I would just reiterate the point that I mentioned last time, which I think is very important that we all understand in all of this work that we’re doing is agnostic to the fact that we’re moving to something else or we’re staying with the current environment. The actions that we’re doing are equally important in both scenarios, so important that we push through.
So, on the simplification you’ll remember that what we talked about last time was the starting point was the complexity of the environment in which we were working. I won’t repeat it here, but you’ll remember the size of our organization, the numbers of classification categories that we have, the number of collective agreements we have to manage. All of this kind of results in a very large amount of conditions of employment that we have to manage and equally result into a lot of business rules and pay rule that we have to operate.
So in large part, not the only way, but the biggest agenda item we have on this is actually a partnership and collaboration with our unions, colleagues, who have you’ll remember, have signed with us in the last round of collective agreements, MOU that would allow us to reopen collective agreements and make some changes to those conditions of employment, if we agree on certain areas of simplification that could result in helping our pay system.
Very happy to report that since the last session, last update that we had, we have engaged with our bargaining agent partners for initial meetings. Other meetings are being planned in January, in February, to engage into the actual negotiation of what actually could be done. I would qualify the receptivity being very positive on both ends. I think looking at short-term actings, looking at allowances, looking at establishment of rates of pay and liquidation of leaves, those are the five areas in which we will be focusing our attention with our bargaining agent colleagues. So more to come in our next update as the meetings are continuing with our union partner.
Of course, I said mostly through our unions negotiation specifics that we’re initiating, but I would just like to say that simplification if now at Treasury Board, something top-of-mind for any initiative that we’re doing, including the next round of bargaining negotiations. I will add on simplification that we’re also going to work on the classification system, specifically undertaking efforts with the alliance at PSAC, on the PA conversion agenda that touches more than 70 departments and almost half of the public service in trying to reduce the number of classifications that we have.
A quick word on standardization, we continue to engage with departments on the numbers of systems. We’re now down to 30 systems that feeds into the Phoenix Pay, still way too much. We are working with heads of HR, CIOs and departments to try to consolidate systems and rationalize efforts and spending.
The next round will include onboarding 15 other departments into MyGCHR, which is significant. This will bring us by the fall, when we’re having 73 different organizations on the same system. 73 out of 101, I believe that we have 155,000 users and moving from 30 systems to 24 systems by the fall, so efforts are continuing along those lines.
The last thing I’ll say, a little pitch on the training aspect of things, which is also something we’re responsible for, we’re preparing to launch an HR to Pay training update for employees. This will compliment what we have done last March for managers. This will include concrete scenarios and life events and work events that people go through both for employees and for managers, and how do you manage those into the pay system in a concrete way. We’re also going to push very much as part of that, leveraging the self-service both on MyGCHR and in Phoenix, which is also part of what we’re looking to change in our way to interact with the systems.
So I think I’ll stop here and I’ll turn it to you, Alex, for the update on your end.
[The graphic changes and the small video of Francis Trudel changes to Alex Benay sitting at the table talking.]
[Graphic on screen.]
(Title text on graphic: Commitments: Tracking our progress. Progress against 2024-25 commitments*)
(Text on graphic;
Current operations (2024-25)
- Reduce Net Backlog – 49,000 Cases, at 27% and up 13%
- Process Backlog Cases with Financial Impact – 19,000 Cases, at 68% and up 25%
- Eliminate SSC Priority and Backlog cases – 12,000 Cases, at 77% and up 17%
- Process Backlog Cases During Routine Processing – 81,000 Cases, at 62% and up 23%
- Introduce New Pay Measures (Unified Actions for Pay)- 7 Measures in Effect, at 57%
- Onboard 9 New Depts. To MyGCHR as Interim GC HR System – Completed – 100%
Transformation (2024-25)
- Data Hub Procurement – Vendor recommended, at 64% and up 26%
- Data Hub Pilot – Pilot Environment Ready – 100%, and up 56%
- AI Virtual Assistant – 3 Case Types Tested and Implemented, at 64% and up 29%
- Build and Validate Dayforce System (Year 1) – Feasibility Report Completed, at 72%, and up 22%
- PSPC and SSC Data Migration Pilot to Dayforce – Pilot Completed, at 62%, and up 7%
*Data as of December 31, 2024
**Data compared to September 26, 2024)
(Text on screen: Alex Benay, Associate Deputy Minister of Public Service and Procurement Canada for Human Capital Management)
Merci beaucoup, Francis. Thank you. So great. As Chris mentioned, I’m going to focus on the tracker that you have in front of you on the screen. We launched it in October, and we introduced the tracker to provide a better view of the direction that we’re heading into over the course of the fiscal year, and some of key projects. We have 11 commitments that have a whole bunch of milestones and goals on our project tracker, which is available online and you can get more details there.
So, if you did miss our update in October, no worries, the recording is on our website. As Chris mentioned, there’s a lot of resources on our website now and there will be more. So feel free to browse there quite often.
So, I’m not going to dive into every commitment that’s on the slide here today. I’m going to focus on where we’ve made good progress, but I’m also going to talk about some areas that we clearly need to continue improving.
So when we start on the left with current operations, well let’s talk about backlog, obviously. So, I mean that’s probably the first thing that we’re going to want to tackle in this conversation. We’ve made good progress on the backlog and let me explain that.
So between processing backlog cases that have financial impact, so these are cases that are the most financially impactful to employees, we also wanted to by the end of the fiscal year, eliminate SSCs cases and continue to close routine backlog cases. So, these are the kind of cases that are attached to a major case. You might have a couple ancillary cases that are attached to a major case.
So all of things, we’ve been able to close about 25,000 backlog cases over the last three months, so in the last quarter.
This is a great effort. It’s good progress. It’s unfortunately just chipping away at the backlog problem, and here’s the reason why is while our agents at the Pay Centre are processing these cases, new ones continue to come in.
So for example, last quarter, our intake for the Pay Centre was close to 300,000 cases. So that means that the pay centre has to process those and then some in order to be able to chip away at the backlog. So, I’m sad to report that the net backlog reduction still sits at roughly 27%. We had a goal to reach 49,000 cases this year. We’re about 27% of our goal. We’ve moved up 13% since October, so we are making progress, but high likelihood that we do not reach the net backlog reduction because we just do not control the intake. It’s, as I mentioned, we do need to do better on that front.
So how do you control intake is probably your next question or how do you do better? So that’s why we’re going to talk about AI in a minute. We have new AI tools that we’ve actually deployed, and I’ll talk about some updates there.
Our new AI agent is going to be able to process cases automatically in bulk. So, that means that we’ll be able to increase our production rate dramatically, and I’ll talk about that in a moment. We also are really reliant on departments increasing some of their HR practices, the consistency in their HR practices, through our unified actions for pay, which is also on our website.
But this is frankly where we need your help, because we don’t control intake at the Pay Centre. This comes from departments. It comes from you. So for example, if you ever receive a letter of offer that has you start on any other day other Thursday after a pay day, I would highly recommend you go back to your HR department and ask them to change the date because that could create manual intervention requirements on the Pay Centre, which means we could be in a situation where this is going to have an impact on your pay. Hiring on a Thursday is one of those unified actions for pay measures that we’re asking all HR departments to put in place in order to avoid manual intervention at the Pay Centre so that we receive the information in a timely, accurate manner to make sure that you’re on the payroll.
So while it’s a manager’s responsibility, highly encourage the employees to request that change in order to avoid pay disruptions when you see your letters of offer. This is just one way you can help.
We’re also launching two new pay measures by the end of this fiscal year. One of them is going to be Treasury Board Secretariat guidance to ensure that we have consistent application of some of our rules for short-term EX actings for non-EX employees, right now that is an entirely manual process and it comes at us in 40 to 50 different mechanisms. So getting that consistency from TBS and in the departments will help manage our intake issue.
The other measure is going to focus on ensuring that employees have accurate contact information. It sounds silly, I know. I realize that it does, but when cases are pending or we need answers and emails keep bouncing back or the mail address is the wrong address, it means that we get into a communication problem with you, so we want to make sure that your emails and your addresses are accurate as much as possible so that we can introduce more measures next year to notify you of changes more rapidly when changes are required or actions are required to make sure your pay is accurate and on time.
Now on the transformation side of our program, by the end of this fiscal year we’re going to recommend whether or not Dayforce can meet the Government of Canada’s HR and Pay needs. Currently, we are about three quarters of the way through our feasibility activities. And so for us, we are right on track.
In December, we validated and tested 50 different scenarios with roughly 1,000 different HR and Pay steps alongside employees from PSPC and SSC so that we could compare Dayforce against our current system, and I’m happy to say that for a first pass, 88% of the scenarios passed without a problem. Other scenarios needed some tweaking but eventually were passed as well.
So for us, that means that we are very much on the right path with our basic Dayforce system that we’re developing. Lots of work to do to build 140 different integration points next year should we proceed with the project, but as a baseline, this is highly encouraging for us because it already surpasses some of the accuracies we’ve had with our current pay system over the last eight years.
So on the other hand, as I mentioned with AI, our virtual assistant tool is also making quite a few strides. We committed this year to testing three case types: actings, leave without pay, and EX actings.
So since we launched the tool in the fall, this tool has by the way only been used by 30 compensation agents. It’s helped to process 4,000 acting cases as we’re building it.
So, that’s about half of the acting case backlogs that were processed during that timeframe have been processed by our new AI agent, with the help of humans. Obviously, we’re not eliminating the humans from the loop, because I’m sure that will be one of the questions we get on Slido. That said we’re not stopping there.
We’re also looking at ways this tool can help process cases automatically in bulk. So with a launch set for April, this will be a game changer for us on how quickly we can process cases. This means that our AI virtual assistant will be able to automatically process cases in large masses, again, with human intervention.
So progress on the topic of human intervention, obviously progress doesn’t mean a heck of a lot without trust. So that’s why we launched our two AI governance boards that Chris mentioned, and any third-party reviews, and we plan to have a few, will be released publicly every step of the way so you can see what third-parties are saying about the tools that we’re using and that’ll be accessible to you as well.
So, as Deputy Clerk mentioned, transparency is a priority that we’re committed to. We’re here today as our third session for transparency by design and we want to lead by example. So we’ve actually released hundreds of HR and Pay documents and datasets, but some of the things that we’re going to release moving forward will include testing results because that was something that last time wasn’t maybe done as well as it could have been when we launched Phoenix.
[Graphic disappears and Alex Benay’s video goes full screen.]
You will see the testing results. That’ll be available on our portal. You will see the architectures that we want to put in place. I would actually encourage you and frankly, you see anything that seems out of the ordinary to you, to please reach out to the team and tell us.
This is a project that has to succeed. So we will continue to release different document types over the course of the next few months, and as we look ahead to ’25, ’26, where we’re going to be shaping the next kind of series of commitments on our tracker and we’re going to want your input.
So what HR and Pay areas do you want more visibility into? So for example, we’re going to be launching next year, HR and Pay Concierge, which will give you access to see where your ticket is, so you can ask it questions on the process and the progress of your tickets with the Pay Centre and give you visibility. What else do you want to see?
So you can share your thoughts on Slido poll that we’re going to be launching just now. You can send us an email. You can find some of the team members on social media. So, we’ll introduce these new commitments in April, so stay tuned.
So for us, your input is hugely important and we live transparency. It’s more than just a buzz word. It’s about making sure we’re working on this program and fixing this issue with you.
So, with that, I’m going to turn it over to Annie Therriault, who is our Senior Director for the future state of HR, to take us through a Dayforce demo as it stands today. I should underline and italicize in bold, there’s still 18 months’ worth of design left, and tell us how you can actually help shape that design.
Annie, over to you.
[Annie Therriault begins to talk from podium.]
Thank you, Alex. So hello, everyone. I’m very happy to be here today to give you a sneak peek into the next generation of HR and Pay.
(Text on screen: Annie Therriault – Senior Director Future State of HR, Human Capital Management, Public Service and Procurement Canada)
So today, you’ll get a behind the scenes look at Dayforce, a platform we’re currently testing to meet the needs of the Government of Canada.
[Animation takes over the screen while Annie Therriault talks.]
[Animation opens with white background, at the top is the Dayforce logo in blue and below is a login area, a mouse moves over it and clicks on the login button.]
This platform is designed to make managing your HR and Pay easier, faster, and more accessible.
[It brings us to the homepage of Dayforce, the page is all white and at the top is a fictitious name and photo of an employee, and a blue bar with six icons along across the bar.]
(Text on screen: The six icons say, Earnings, Benefits, Calendar, Time Away, Employee Timesheet and Profile.)
[Below the blue bar on white there are four icons.]
(Text on screen; The four icons say, Actions, Balances, Earnings, and Events.)
(Text on screen: Pending Actions.)
[A mouse moves around and clicks on the Time Away icon, which brings us to the Time Away page, the page shows 3 different vacation requests the employee has taken, two have been approved and one is pending. The cursor then moves to a create a new request tab.]
But what you’re seeing on screen is the out of the box solution. It’s just the starting point, the beginning of something much bigger.
[The next screen is titled “Create Time Off Request“, the cursor moves around showing you the features to request time off, moving from one page to another.]
Dayforce is mobile first, user-friendly, and accessible from anywhere, whether you’re in the office, working remotely or on the go.
[The animation continues to show you different pages within the earnings icon, show you your past pay, and pay stubs.]
So as you watch the demo, notice how much smoother and more intuitive the platform is. Everything you need will be in one place, from managing personal information, to submitting leave requests, checking pay stubs, and more, all accessible from your phone or computer.
[Animation fades to several shots of women and men sitting at workstations and looking at their monitors. The last shot is of a women looking at her monitor and it has the words “User Awareness Session” on it.]
It’s designed to save you time and it’s easy to use. But again, this isn’t the final version you’re seeing today. It’s really just a start. We’ve been working closely with you, gathering feedback and testing, to ensure Dayforce works for everyone. It’s not just about accessing the platform’s technical feasibility.
[The video continues with several shots of people talking in lobby settings, behind them are the Human Capital Management paraposts.]
It’s about making sure it meets the real needs of public servants now and into the future.
[The video returns the same people who were looking at their monitors, and they are taking the User Awareness Session, working in the Dayforce program and providing feedback to each other over teams.]
To do this, we’ve been engaging with thousands of employees across the country over the past few months through user awareness sessions, one-on-one chats, and the National Lobby Road Show. All your feedback is already helping improve the platform.
To date, we have held over 85 sessions and spoken to more than 2,000 employees in 10 cities. Through these sessions, you have the chance to try Dayforce for yourself, and tell us what’s working and what’s not. We’ve already had great ideas about simplifying the language, improving the navigation, and making the experience even more intuitive.
And we’ve listened. Your feedback is driving the change you see today and in the future. In fact, your input has already made a huge difference. Over 90% of you have said the platform is accessible and easy to use, but we’re still working on refining it further based on what you’ve told us.
During our sessions, you complete tasks; you leave comments, and tell us exactly how Dayforce can work better. And the changes you suggest, whether it’s clearer terminology or better design, help us make it better for everyone.
[The video transitions into the new Dayforce homepage, it is not a plain white page with a blue bar and icons, it now has images, and links to sites that can help you with different aspects of your career. At the bottom you can see your last pay and quick links to all your pay details.]
So take a good look now because what you’re seeing is the next iteration of the platform, the one that’s inspired directly by your feedback. And as you watch these new visuals, we hope you’ll see how the system is evolving right before your eyes.
[Video returns to the women and men we saw before sitting at the desks and taking the Awareness Session, followed by the people in the lobby talking with Dayforce representatives.]
So, as we wrap up today’s demonstration, I just want to leave you with this: your feedback isn’t just heard, it’s really what’s driving the change. The next version of Dayforce is already in the works as you can see on screen.
You’ll get to test it, see the improvements over the next few months, and then in April, we’ll be back with the next progress update, with a more polished version of the platform. We’ll walk you through a full demo, showing exactly how an employee can use the platform to complete a task from start to finish. It’s your chance to see how much smoother and easier it’s becoming, thanks to your input.
So keep sharing your feedback. The more you participate, the better Dayforce will get. We want to make sure this platform works for everyone, and that can only happen with your continued input. If you haven’t yet, sign up for user awareness sessions or join us for our National Lobby Road Show.
[The video then tuns back to an animated slide with text and a QR Code.]
(Text on screen: Register now! canada.ca/gc-hr-pay)
These sessions are your chance to shape the future of the platform. Just head over to our website at canada.ca/gc-hr-pay to sign up and stay involved.
Thanks again for being part of this process. Together we’re building a solution that will make a real difference for public servants across Canada. We can’t wait to show you what’s next.
[Animation ends and video returns to Annie talking at the podium]
And with that, I’ll pass it back over to Mitos.
[Mitos San Diego talking at the podium.]
Thank you, Annie. Now it’s time for our Q&A, and as a reminder, this event is recorded and will be posted on our website so please do not share any personal information in your questions. So to ask questions, connect to Slido using the QR code and type in the code #GCHRPAY3, or you can simply press the Slido button at the top of your screen.
Do not forget to upvote questions from your colleagues. So even if we don’t get to your questions today, don’t worry. Your input is still incredibly valuable. It helps us understand what you want to hear for next time and how we might better meet your needs with new resources or different guidance.
So just don’t hold back. Ask away. We’ve got a dedicated team that will go through all of your questions and after the event to find actionable ways to address them in future progress updates.
So, just looking for question #1. Okay. So first question we have: What will happen to this new pay system if a new government comes in? Turn it over to the deputies.
[Alex Benay talking from table.]
I think I saw Chris with her finger up, so I’m happy to pass it over to Chris.
[Christiane Fox returns to the screen while talking in her office virtually.]
Well you may want to add, but I think we have been reflecting on this a lot.
So first, I think it’s really important to highlight to all of you that there has been a ton of work done by PSPC and Treasury Board to build in, you know, the needs for, I would say kind of the two systems: run the current system and make sure that we’ve got dedicated resources to do that successfully and so that as we kind of show your slides on the backlogs and improvements there that we’ve got the right authorities and resources to run the current system, while at the same time investing in the transformation and into Dayforce and how we’re kind of designing that and testing that, and getting departments kind of ready for that transition.
And what I would say in the context of a transition is I think we’ve got a great foundation now with this kind of long-term plan for run and transform that it positions us well as public servants in the context of our advice to a new government should we face that, you know, in the weeks, months, or October of 2025, that I think we’ve got a good basis for a strong brief to a transition team and eventually a new government around the very significant improvements that we have made, the process that we have followed and a transparent approach, I think, helps us in that advice that we would give.
And I think this is one of the big projects that has gotten a lot of attention, not just from all public servants but from media and from parliamentarians, and so some may have a better understanding of some of the challenges that have plagued our pay system, and so we will have to really describe the shift that we have taken.
So, I think what I would say is as public servants, the best thing that we can do in a transition environment, is be prepared with a solid plan, and that’s what we are doing on pay and that’s what we will be prepared to do in the context of a new government.
And I think that is the responsible thing to do to kind of position the new pay system in this transformation exercise as why do we think that this is different? Why do we think that this new system has the factors of success? And how we are treating individual employees in the context of, you know, running the current system that we have and making as many improvements as we can to deal with that.
And I think that over the coming weeks, we’ll have to continue to reflect on those briefings, but I think we’re well-positioned with the authorities and the resources that we have now for both to go into that conversation.
[Alex Benay talking from table.]
Okay, maybe I will actually jump in a little bit and just support maybe by providing details to what Chris has referred to. Like I would think that regardless of government coming in, we’re going to always want to continue simplifying our HR and standardizing our HR, for example, and that’s platform independent, right, whatever system we choose.
The current platform is increasingly considered legacy. So at some point, one way or another, we’re going to have to look, again, regardless of government because the legacy part of this equation won’t really care about our governance or anything like that. The technology will become obsolete at some point, so we have to look at that. And I think we’re on to Chris’ point, the right track to have done their investigation responsibly this time.
The other thing that has to get fixed is our HR and Pay are separated right now and that is the root cause of what is causing us all these problems. So that’s something that whether it’s on current platform or future platform, we have to rectify it. So there’s a lot of these issues that are I’d say, platform agnostic and new government agnostic. Like these are all things that us as the civil service are going to have to continue to work on to make the current and future environments better.
[Mitos San Diego talking from the podium.]
Thank you for that. So the next question: Can the pay system handle all the WFA actions happening across departments or will this impact the backlog?
[Alex Benay talking from table.]
Yep. I’ll take maybe a first pass at this one. We are currently looking at all ways of optimizing our current platform. Never mind WFA, I mean any opportunity to optimize how we process the platform.
So when we talk about the AI Virtual Agent—and we’ll be able to deal with about 70% of case types by the end of next fiscal year—so the reason we’re doing that, again to Chris’ earlier point is if for some reason we don’t decide to go with Dayforce, we still need new technology in our backlog and our operational management to be able to adjust to any circumstance, whether it’s WFA or departments merging, or you name it.
Like there’s a whole but of different things that can happen in the next 10 to 15 years that we need to make sure that our backlog management and our backlogs operations have more modern tools than what we’ve been equipped with, because simply hiring more humans we cannot keep up. It takes four years to train a compensation advisor at a senior level, so it has to be done with technology.
So when you hear about all of our AI Virtual Agent updates, it’s really important for this year and next year to manage current backlog, but frankly, any future actions that could happen on the HR front. Francis.
[Francis Trudel talking from table.]
Yeah, just—I actually like the question because it goes to one of the myths that people have is when we are in periods of reductions, there’s actually less transactions than when we are—that’s actually a myth.
Quite often, reduction periods of time generate even more transactions because people have the tendency to do things in a very short period of time and just do short-term transactions and all of this ends up with additional efforts not necessarily the backlog but the actual update that Alex was talking about earlier.
So, I mean, the question relates to WFA, but I think WFA is one transition in multiple types of transactions that HR actually that management actually generates with HR.
Does it affect the backlog? You’ve heard Alex answer that. I would just add to this to say it all depends how we do these actions. You know, if you get the right human resources hygiene in the transactions, you’re doing it in a timely manner; you’re doing it in a way that is respecting all the best practices that we have suggested.
If we’re doing it in a standardized business process and a standardized system, all of these things actually have reduced the possibility of this actually ending up in a backlog situation, so not all HR transactions in numbers ends up with adding backlog. I think the hygiene in how we’re doing it is actually probably more important.
[Mitos San Diego talking from the podium.]
Thank you Alex and Francis for that. So the next question is the backlog is outrageous. How are you addressing this in assisting EE, who call the Pay Centre for an update on their files and told it hasn’t been assigned?
[Alex Benay talking from table.]
Yeah, maybe a couple ways of answering this. I agree the backlog is outrageous. This is a direct result of having separated our HR system and our pay system, number one. Number two, our intake is also outrageous. And what I mean by that is, you know, we have people that changed departments and the transaction is in process for 18 months, and then the Pay Centre receives it and then has to process it.
And then there’s just human error that can happen at the Pay Centre as well. Like there are a series of individual failure points along this process of ours, from a manager forgetting to press a button when an employee leaves the Government of Canada, to a human error that increases the backlog.
So, I mean I’d be hard pressed to stay up here today and tell you that I don’t think it’s outrageous, but we have done it to ourselves, unfortunately as a civil service, and so we have to address a series of things. The data that we receive sometimes is a year old to process a transaction. Sometimes it’s not in the right format, so departments have a role to play; HR has a role to play.
Your manager has a role to play and you have a role to play.
On the Pay Centre front, we can’t continue to hire employees and think that we’re going to be able to manage this onslaught of information that’s coming at the Pay Centre, because the Pay Centre is a clean-up centre and then it’s a pay centre. So we have to clear that as well.
Okay, so my little rant’s over. Some of the things we’re actually doing to fix it is I mentioned really briefly in my opening remarks, we’re going to be launching early next fiscal year our HR and Pay Concierge. This is the beginning. Please do not assume that it’s going to solve all the problems immediately, but we will release a new version on a monthly basis. But our HR and Pay Concierge is going to be able to help you track your tickets, for example, where is your ticket? Has it been assigned?
Has it not been assigned? The goal for us is going to be to increase the transparency into the Pay Centre operations for employees next fiscal year, so you know where your ticket is being processed, by who. That’s step one.
Step two is we’re going to be looking to, once SSC’s backlog has been cleared, to change the service model. Do you need to go through 10 steps to call a compensation advisor? So maybe you’re going a little bit further back to the days before we decided to consolidate that service.
Could once your backlog as a department is processed, have you call the compensation advisor directly like you did when you used to call John or Jane for a service. Those are things that we’re going to look at as well, so that it gives it a more human touch, I would say on the service. The way that things have been designed that you have lived over the last eight years was designed for a reason. We needed to design different things just to be able to get pay out the door.
We’re at a 98.1% accuracy on pay right now. We’re shooting for 99%+. So we’re not quite there, but it is getting better with our current system. But now, next year’s focus is going to be on adding empathy into things like overpayments, for example.
So stay tuned because I think that’ll be part of the tracker for next year, but just know that we are working on the human element of this as we speak.
[Mitos San Diego talking from the podium.]
Okay. Thank you, Alex. This next question is for Francis. Is there a mandate for departments to clean up their HR data, or is it just at their speed and any consequences for non-compliance?
[Francis Trudel talking from table.]
Yeah. I think I would say partially, we have—I think that was part of the last session, or maybe the first session, we talked about the delegation environment that HR operates and so each department are very independent in how they’re operating their business, which comes with a lot of benefits, but also comes with some challenges.
Some of the challenges sometimes, is the ability to bring all of us into an enterprise approach and dealing with issues in the same standardized way. It also, and I think that gets to the core of the question, that also allows a little bit for some to decide not to follow the enterprise approach to what we’re asking them to do.
I think this is kind of slowly, slowly being resolved in the sense that there is more and more of a public service approach to things, which includes, you know, receptivity to some of the directions we’ve been giving them on the UAP, the Unified Action Plan, for example, where we’re actually guiding people to do things in a certain way.
We need to create report cards for some of this and I believe, and Alex you can correct me, but I think some of this will actually be part of some of the release documentation we will do this time around.
So again, in spirit of transparency, you’ll see that some are doing actually better than others. But what I actually encourage about is that is that there is kind of an acceptance that we need move as an enterprise in moving some of these things, like we should not underestimate the small things. When you look at these unified action plan items, Alex gave an example of the date of hiring, for example, which sounds maybe futile or minor.
You just have to think of the multiplicity of onboarding we’re doing in an enterprise of the size of 400,000, and you can realize how quickly these things kind of funnel into a system and create a problem down the road.
Now consequences, we’ve started to touch a little bit on that, but actually we need to refine our data to be sure that we’re assessing things properly.
But I think we’ve talked about some of those consequences as having a department to be on the hook eventually, to actually pay for the additional transaction that they’re creating in the systems if you’re not following the rules that we expect them to do: paying meeting, paying the costs of the transactions here.
I’m not talking giving tickets for people for having been delinquent. I’m talking about if you’re going to create more work to our system, that’s actually going to cost down the road and have a cost to the overall enterprise, then maybe there is a case to be made for charging departments for this.
So working with deputy heads who are delegated. Working with human resources, who are guides of that process and working with managers who are the actual delegated managers for the transactions that are generating all these actions.
[Alex Benay talking from table.]
Maybe just one quick comment, too. I think everything Francis has said is so important because should we make the move to Dayforce, the consequence for non-compliance will be the employee doesn’t get paid. I think but the big difference is we’ll have full transparency in the audit log to show where the process broke down, which is not something we have right now.
[Mitos San Diego talking from the podium.]
Perfect. Thank you. So this one is for the group. Can we get an update on the budget regarding extensions?
[Alex Benay talking from table.]
Sure. I mean, I’ll take a first step at this. As Chris mentioned, like we’ve gotten a lot of positive pieces in place, including some good indications of some of our financial needs over the next period of time for the program to continue that includes the extensions.
On the extension front, we had identified 12 initially. So these are things that Dayforce was going to build for us. They’re not customizations, they were going to become part of the code and maintained by Dayforce as well. And we’re down to 11, because as we’re going through the process there are things that we can standardize that you heard Francis speak about.
The goal will be to bring it lower than 11. But we have, this year, committed to three and a half extensions, so we’ll have 3.5 done. The goal is to have them done between now and the end of March and then complete the rest next fiscal year. Just to be clear, we cannot launch this project into testing until we have all these extensions done, either addressed through simplification and standardization from OCHRO or a technical solution on our side. So it’s super critical that we land these on time.
[Francis Trudel talking from table.]
And you can’t associate…
[Christiane Fox returns to the screen while talking in her office virtually.]
[Cross talk] Oh, sorry.
[Francis Trudel talking from table.]
Go ahead, Chris. Sorry.
[Christiane Fox returns to the screen while talking in her office virtually.]
No, I was just to say I think, you know, some of the work that’s been done to put our case forward in terms of getting the investments that we need over time, to move forward on these projects, like we did get the decisions that we needed to both run and transform, which is enormously helpful for the project, including the extension. So I was just going to add that point, but go over to you, Francis.
[Francis Trudel talking from table.]
Yeah, I was just going to complement to say, like you can’t associate the budget and the efforts on the extension to the actual simplification agenda and the negotiation we’re doing with unions. So if we’re not successful in simplifying our condition of employment, we need technology to help us navigate the complexity.
So Alex’s team has actually worked on that, to identify and see what that would look like. I needed that information walking in to the discussions with our bargaining agents to find solutions because of course, at the core of this will also be costs.
So I need to—well, we need to come up with unions finding solutions that actually fit within a frame of acceptable costs because there is a technical solution called extensions. So that was very important that we were doing this in the right sequence, so just wanted to make the link between the two.
[Mitos San Diego talking from the podium.]
Okay. Thank you. So this one is directly for Alex. Can you speak on the potential conflict of interest regarding Benay’s post CIO employment? He was on the board for an AI company and worked for Microsoft.
[Alex Benay talking from table.]
Yes, heaven forbid we would leave the public service and come back. So listen, I mean, we promised you transparency. I see this has been up-voted quite a few times so let me answer the question upfront.
Everything that I have done personally has been run through the Ethics Commissioner and including everything having to do with employment.
We have the Departmental Oversight Branch at PSPC that is confirming the following statement, which is I’ve never had a personal contract or a contract to one of the companies I’ve been employed with while I was gone from the government. So everything’s been managed with the Ethics Commissioner at this point.
[Christiane Fox returns to the screen while talking in her office virtually.]
And maybe just to add to that, I think that process that Alex described is important, right? I think that we all have a responsibility as, you know, deputy ministers and associate deputy ministers, clerks, deputy clerks, to actually signal to the Ethics Commissioner through a very transparent and regular process of declaring our conflicts, of checking in.
And it’s part of, I think, a very healthy part of our system, to ensure that we need to recuse ourselves from various decisions that we do, and that we have the things in place and when the Ethics Commissioner does not see a conflict, that’s important for us to know as well. So I just, I think, you know, we’ve got to address these questions head on, but there is a very rigorous process by which deputies abide by that help us guide our work in sometimes what can be difficult to navigate.
And I think it is healthy for a public service to have, you know, porous talent coming in and out. And I think we all bring different experiences. Some of us have spent a big part of our career in the Public Service.
Others have come in from other levels of government or private sector and can enrich the work that we do. But having a healthy way for us to have kind of a porous public service makes us stronger, and I think that’s part of the talent conversation that we need to be having more and more.
So I just wanted to add a little bit of my reflections on that question. Thank you very much.
[Mitos San Diego talking from the podium.]
No, that’s very good. Thank you very much. This one is for Chris Fox. So, will RTO be looked at again instead of three or four days mandate, two days is a better option, isn’t it?
[Christiane Fox returns to the screen while talking in her office virtually.]
Thank you for that question. And I think, you know, it’s—this conversation is obviously top of mind for many public servants. It has been for me as I navigate the role that I’m in, and I think that as I had explained back in the fall, you know, we feel as a government that it’s really important for public servants to spend time together, to learn from each other, to tackle really hard challenges together, and we landed at three days a week to try to maximize those experiences working as a team, to deliver for Canadians.
I think that’s still important, and, you know, I appreciate the different perspectives that exist out there. I appreciate the continued reflections on it.
So I don’t mind the question at all. I think it’s healthy for us to talk about this and to reflect, and I think that where we landed, that is the guidance that continues. And I think that, you know, if I reflect on the workplace I’m in, which is here at the Privy Council Office and some of the challenges in the work that we’ve done over the last few months, being together with my team, whether it’s Intergovernmental Affairs or the broader PCO team, has really helped us get through tough challenges or tough issues that surface on a day-to-day basis.
And so I continue to believe the importance of teamwork, but I welcome these conversations and I welcome the questions. So thank you.
[Mitos San Diego talking from the podium.]
Thank you for that answer. Okay, so this one is directed for Francis. Some retirees do not receive their back severance payouts for two to four days after retirement. Is this [an] expected timeframe? Only complaints to their MP help.
[Francis Trudel talking from table.]
I’ll just—I’ll just turn it to Alex because that actually is in operation, but I think we’re talking two to four years here, not two to four days.
[Alex Benay talking from table.]
Nice try, Mitos. Thank you. No, listen this is not the timeframe that we’re expecting so I do fully appreciate that going to your MP is part of the process. It relates a little bit to what we want to do with the HR and Pay Concierge next year. We want to provide transparency into what happens when your request goes into the Pay Centre.
Maybe you require—maybe it does require a contact with your MP, but maybe it doesn’t. So that’s going to be part of our efforts next year, is to make sure that we can bring all of these processes, which at times may not meet service standards, often even, may not meet service standards and bring them closer to the service standards that we want to put, but in order to do that we need to take the first step on our side and that’s increase the transparency into our operations.
So I know that’s not probably the answer you were looking for specifically on this particular use case, but they do kind of—I’d say there’s about half a dozen of these kinds of examples that kind of are the same thread, which is increase the transparency, work with you on your cases, try to see if we can’t put some of the experiments that I talked about, about changing the service model a little bit and making some experiments. Now that we have pay accuracy up to 98.1%, like now is the time to maybe try tweaking a model to see how we can avoid some of these cases, and I’m sorry you’re going through that.
[Mitos San Diego talking from the podium.]
Okay. Thank you for that. And this is for Alex as well. It takes months for employees’ files to be transferred from one department to another, when will this be fixed so that files are transferred in a timely fashion?
[Alex Benay talking from table.]
Yeah, no. So great question. So listen, this could be a multitude of things. It could be the outgoing department not processing the transaction. It could be the incoming department not processing the transaction. It could be the Pay Centre not processing the transaction. It could be you as an employee not completing a transaction. Like, it’s a little bit ludicrous to me that in 2025 with the internet that we still have to transfer our files from one department to another like we’re in the 1990s.
So, part of what we’re doing as part of this year is looking to secure the purchasing of a central data management toolset that’ll the able to have Government of Canada employee information in I say one location. It’s not one location, but for simplicity let’s call it that, where you don’t have to transfer your files from one department to the next anymore.
So we’re on track. You can see some of the commitments on the tracker. We already have the pilot environment ready, so as soon as we’ve identified a solution, we’ll be able to start some of the piloting and probably start it again with SSC and PSPC over the course of the next year or two, but the goal is to eliminate file transfer. The systems should be able to talk to a central data repository. Entire countries have architected their economy this way. There’s no reason we can’t do this for HR and Pay.
So we have blueprints that are a little bit more complex than ours, but we’ll be looking to pull some more information together on the central information repository over the course of the next few months as we go into next year. The same kind of user engagement that you’ve seen for Dayforce, our plan is to have that kind of user engagement data hub, moving forward as well because this should be a place where you get to see your information, where maybe—I know I always get in trouble for suggesting things, but maybe you can go change your own address, as opposed to having to go through a 10-step process with someone else. But you should be able to see your own information as well. So these are all the kinds of services we’ll be able to, I guess, to add to our arsenal, starting next year.
[Mitos San Diego talking from the podium.]
Thank you, that’s very good. So, this is the last question for the group. Why are we relying on an untested technology, AI, to assess our pay files?
[Alex Benay talking from table.]
Maybe I’ll start there, since I seem to say the words a lot. I guess first of all, maybe I’ll refute the question a little bit by saying it’s untested. A lot of the things we do have a lot of machine learning in it already. If you’ve taken a flight, the software on your phone, your cars, right?
So I just want to challenge the untested a little bit, so that’s thing one. What we’re doing is about financial reconciliation of information as it relates to a pay file. It’s moving information around and it’s making a calculation. Machines have already done that better than humans, faster for the last two decades.
So what we are doing, though, because I realize that it’s new and untested and let’s say from a public service perspective on how we’re using it for pay so I fully appreciate the concern. But what we’re doing—what we’re going to be doing is running it by our two advisory groups that Chris mentioned earlier in her speech, and we’re also going to be releasing all of our test results publicly, so if it’s not working you’ll see it.
We’ll also be hiring a third-party company to come in and review all of our governance, all of our test results, all of our algorithms, and you’ll get to see the third-party review of that. And then finally, we will also be releasing—it might already be done, so check our website—the actual algorithm itself that we’ve built. I mean, I’m not sure you’re going to be able to read it. If you can, by the way, we’re hiring. But if you cannot, like it’s normal. It’s a lot of zeroes and ones, but the algorithm itself is released publicly.
So I want this to be the most transparent AI project on the planet by the time we’re launching this and deciding to actually turn it on so that it helps us process pay.
[Christiane Fox returns to the screen while talking in her office virtually.]
And maybe if I can just jump in on that. I think Alex has described it exceptionally well. And I think it’s about sort of ensuring that we’re deploying it when we’ve done the right amounts of, you know, checks and balances in place that we have a reliability that is at the highest standard in order to deploy.
And then even as we deploy, a constant monitoring to ensure that the tool is giving us our results from, you know, its efficiency, but also in terms of security and privacy.
So I think these bodies that we’ve put in place and the measures to kind of track and monitor, you know, I think will help us make the decision around when to deploy, where to deploy, how to deploy, and I think being transparent with everybody about that is key. And I think privacy and security has to be at the front end of that.
[Mitos San Diego talking from the podium.]
That’s very good. Thank you for that. So that concludes our Q&A session. Thank you all for your active participation today. Before we close, I am going to be sharing a few ways to stay updated on HR and Pay, and get involved in our future engagements.
(Title text on graphic: Thank You!)
(Text on screen: Email us your comments, questions, feedback, and suggestions: spac.gcrhpaye-gchrpay.pspc@tpsgc-pwgsc.gc.ca
Learn more at https://www.canada.ca/gc-hr-pay
Sign-up for the HR & Pay newsletter!)
First one, visit Canada.ca/GC-HR-Pay for today’s updates and our third quarterly progress report along with quick links to documents on the Open Government Portal.
Follow our Facebook page: facebook.com/GCEmployeePayBenefits for the latest news in HR and Pay advice. And we’ll soon launch a new Reddit account to answer questions, so stay tuned. And for future engagement opportunities, register for the HR and Pay Employee Consultation Pool to be contacted for user consultations. And you can also sign up for user awareness sessions to help refine the HR and Pay solution demoed today.
If you haven’t already, please fill out today’s Slido polls and the post-event survey which will be sent shortly.
And lastly, we’re launching an HR and Pay newsletter soon, so sign up on our website to receive updates directly in your inbox.
Thank you again for joining us today, and a special thanks to our speakers and the event management team for ensuring this session ran smoothly. We’ll see you for our next update in April. Enjoy the rest of your day.
[The same graphic takes over the screen.]
(Text on screen: Check us out: Web: canada.ca/gc-hr-pay, Facebook: /GCEmployeePayBenefits, Reddit: u/GCPay_PayeGC)
(Text on screen: ISBN 978-0-660-75539-7, Catalogue P4-164/2025E-MP4)
(Public Services and Procurement Canada signature)
(Canada Wordmark)
End of video
Questions and answers addressed during the French session
Everyone talks about Dayforce as though it has already been selected to replace Phoenix. But elsewhere it says the decision has not yet been made. What’s the story?
Alex Benay: Okay. Francis just told me my question would be the first. So, here it goes. You are right. Sometimes I think we get carried away with our wording. I think our teams are so wrapped up in it and want to see the project succeed. I want to say ultimately. That said, the decision has not yet been made. Until the end of the current fiscal year, we intend to make a recommendation to the Deputy Minister’s Sponsorship Group, Chris and Bill Matthews chairing. Then, at that point, we will have more, we will make a decision. I just want to point out that making a decision in March does not mean the system comes online at that time. There will be a further 18 to 24 months of configuration and testing to be done before we start rolling it out, I would say, more globally, throughout the federal department. I don’t know, Chris, if you had any comments about the role of the DMSG?
Christiane Fox: Yes, perfect! I was just about to say that in fact, even if the final decision has not yet been made, decisions did need to be made to do the necessary testing, to see whether a platform would be ready and for the decision. So, a decision was made about Dayforce in terms of a platform that we would continue testing, that we would definitely demonstrate and take back to the Deputy Ministers’ Group and say, okay, here it is. We had all these criteria that went into making that choice. And now, with the information we’ve been able to collect and the subsequent testing, we are making this recommendation. Then the group will make the ultimate decision, but I think what we can tell you is that we are very encouraged by the performance to date. I think we really received some excellent input from people working on the matter that will inform that ultimate decision. I think the platform and testing are essential to allow us to make the final decision.
What is frustrating is the lack of accountability when there are delays and errors in our pay file. It’s never anybody’s fault. What can be done about it?
Francis Trudel: Maybe I can start. I have a lot of empathy for this question, because it is in fact a complex process—more than complex—it’s the human resources process that is the culmination of a series of transactions that lead to the success or failure of a pay file. It’s called an end-to-end process. It’s hard to identify where, in each of the files—each file has its own merits. Each file is specific. The need for accountability? I would say that I’ve been in this business a long time, in human resources and pay, and I would say that if I see anything that is changing, it’s certainly that no one is playing the ostrich and sticking their head in the sand about whose fault it is. I see—and I say this sincerely—I see deputy ministers who at this moment are taking responsibility, accountability for rationalizing their investments and the decisions they make about their systems. It would create problems if those decisions were not made. I see a community of human resources professionals who understand that they have an advisory role that must be appropriate and timely in terms of the transactions that need to be made. Here again, there has to also be accountability taken. I see communities of managers who increasingly—and thanks to you, the employees, for bringing your pay issues to the attention of your managers, because they too need to, need to identify transactions and, as they say, move the file to the top of the pile and say: this has to be done right away, these actions, because this is affecting my employees’ pay. So accountability is being taken. Each file is particular. What I would say is that we are often wrong—and here, Alex, I don’t want to speak for your team—but we are often wrong to get to the end of the process and point our finger as though the error was made by the person doing the pay transaction.
Alex Benay: You can certainly say that. That’s right.
Francis Trudel: I have a lot of empathy for the people working to resolve these cases, particularly cases they have inherited. These are not cases they have created. So, in looking for accountability, we have to be careful not to jump to the sometimes too-simple conclusions, but I have seen some improvement in this area.
Christiane Fox: Yes, I just wanted to add—I think Francis’s answer was excellent—that despite the fact that it has been frustrating, and despite the fact that the system did not perform well, public servants, one thing I find comfort in, is that we are looking at these cases, these experiences. And when we develop the new platform with necessary transformation, we try to look at those challenges and see how they could be avoided. It may not be comforting in terms of the experiences you have had, but know that those challenges are on the table. We check, and we test the system with these in mind, to avoid a repeat of past scenarios. Thank you.
Alex Benay: It’s more fun answering questions when you have time to think. So, going third is great! Perhaps an observation, and plans for next year. Next fiscal year, to try to give you some reassurance. One, the reason why we are where we are is that we made a choice; we made the wrong decisions in 2016-2017. Poor business decisions. We have departments that control their decentralized human resources systems. That is essentially okay, but we have a centralized pay system. So throughout a transaction, to Francis’s point, there are lots of things that can go wrong. And it’s not always obvious what those things are. It’s almost a whole investigation every time a case is created at the Pay Centre. Did the department fail to transfer the file during the file transfer? Was there a delay at the Pay Centre? Did the employee fail to fill something out? We have to simplify this. That’s for sure. That’s the problem in a nutshell. We have a business model that isn’t working. On a new platform, if we move ahead with Dayforce, there will be transparency with every transaction. Does the problem lie with your manager? With you? If the transaction was not done, your manager will receive an email. The manager’s manager will receive an email. And we will continue on up the food chain to the deputy minister, until the transaction gets done! There will be a level of transparency integrated into the new platform that we don’t have at the moment. Okay! You’re going to say: That will take years! So, what are we doing soon? Next year, in April, we will be putting in place a pilot project with a new human resources and pay concierge. That will be a start—I want to stress the word start—on incorporating transparency into our operations. So, what I mean to say is that you will be able to ask the officer, where is my ticket, or is my ticket with the Pay Centre, has it been assigned? Where are we at in the process? The goal will be to use this platform with monthly updates. So there will be new features that will be added every month to enhance the level of transparency within the process, to at least see where the problem lies in the current process and help you see where you stand with the steps taken.
Is there a plan to decentralize compensation and move back to internal compensation advisors?
Alex Benay: Francis indicated it was my turn to go first. So, here goes. I would say, immediately, no. Potentially, in some cases, yes. Let me explain a bit more. The reason why we want to focus on Shared Services to reduce the backlog to zero is that one, they will be one of the first departments to implement Dayforce, if we proceed with that decision in March. That’s one. But two, we also want to do testing to see whether the department can contact compensation officers directly, like in the pre-Phoenix era. So that would mean that we would have John or Jean, the compensation officer who could be in contact with a branch, like back in the day, and have more direct service. We will start our testing. The intention is to do it next year. Then we will share the results with everyone. That may help. There is a chance that it won’t help either. So we really want to see the results with data. And then, like with everything we are doing in the program, we will base these results on the Internet and share them with you as we begin our testing of changes to the service model.
Francis Trudel: I don’t have much to add on this issue. What I would say is, there are decisions to be made, and the sequence in which they are made is important. All decisions are important, but the order is important too. I have managed human resources in a context where I had pay services that reported to my team directly. I know what that looks like. I was also part of the transition, when we moved to the Miramichi operational model, and I understand the reasoning behind it. The reason why both work, at least intellectually, is that there was a well defined business model. So we adjusted our service model based on the business model. I think there are decisions to be made now, such as, which system are we going with? How will it work? Once that thinking has been done, we can decide which service model will be the most appropriate to support the departments. Not really much to add, except to say that the questions are valid, but the sequence is important. We need to define the trajectory of the next step, the next system, in order to provide a full answer.
Artificial intelligence promises savings by reducing the number of employees needed to fulfill a mandate. How many positions do you plan to abolish, once Dayforce is launched?
Christiane Fox: I can start. Maybe you can jump in afterwards, Alex. I think it’s still a bit—it’s a question that is a bit premature in the current context. We introduced artificial intelligence to see how we could maximize technology, to manage. At this time, we are doing testing on the simplest cases. Obviously, we will take, we will see how it unfolds, but today, we can’t define the future employees that will be needed to manage the pay system. Yes, we can use technology to improve our service, to improve the system, to maximize the tools we have. There will always be a need for public servants, human resources experts and payroll experts going forward, with the Dayforce platform or some other. So, we can’t give a definitive number as an answer today. I think we also have to be careful not to adopt AI too quickly, before we truly understand it and understand the required security, limitations and human input to address areas where AI can’t do the job. So I would say we’re studying this closely. I think it’s important for the public service. We’re looking at artificial intelligence and responsible adoption, but we can’t give you numbers today, at this point.
Alex Benay: Yes, I’m 100% in agreement with Chris. I can tell you we don’t know the cost; none of the data at the moment. That’s why we’ve taken an approach—yes, we’re planning currently, but we also have our hands in the tool, to be able to start deciphering it. Beyond a PowerPoint presentation, in the real world, how will it operate? I can tell you that the only thing we know right now is the cost of not doing things that way. That’s what we did in 2017. We had a business case that said that 500 employees were needed. We hadn’t tested anything. So we pulled a number out of thin air, I’d say. And the cost to PSPC, at this point, we know what it was. Everyone paid the price in a very personal way. So we definitely want to avoid making the same mistake this time around. Pulling numbers out of thin air, from basically anywhere, without testing everything, I would say, when we go, for example, into a department and will be implementing the solution, if that’s the direction we’re going with Dayforce, that will be six months of testing. So I want to say that we will be taking the time needed to make the decision.
With the possibility, with the possible upcoming change of government, the fear is that everything will go up in smoke. Is there anything in place to prevent this?
Christiane Fox: Thank you for the question. So, in fact, questions about transition, public service councils, are something that my attention and my work have been focused on recently, with all the scenarios we are dealing with. I think I would like to say something to answer the question. First, I think it is very important that we put in place all the authorities needed two advance both elements of our system. To ensure that we can manage the current pay system and improve on the current system, at the same time that we have the investments and the authorities required to move forward with the new system, the new platform and the transformation needed to arrive at a new pay system. So we have the funding authorities needed for both. I think it will be really important, as a public service, to present to a new government, sooner or later, around October 2025, the work we have done, the transparency we demonstrated as a public service. Being humble about the challenges we experienced and honest about what we learned from them to put in place these new systems. So what gives me confidence is that we did the work needed to build a business case that is truly based on work, on facts, on lessons learned, on a system that will allow us, as public servants, to provide our best advice. So that is what we must do in the end. That’s our job. It comes from the ethical value of public servants and the public service. So what gives me confidence is that we’ve done the work. And we can present a solid business case. So, will we have questions? Absolutely! Will we have to make adjustments? Maybe, but I think that what is important is the work we are doing right now to put ourselves in the best possible position, to give our best advice. Thank you.
Francis Trudel: I’m not sure I have much to add to what you said, Chris, but I don’t think it’s too much of a stretch to say that regardless of the incoming government, we will have the same objective, which is to pay our people correctly. I think we absolutely all have that same goal, regardless of the colour of government that will be in place. We will have questions that will be asked, such as how to get to that stage, how fast and with what type of tool. We are doing our homework. We are studying. We have lessons learned since 2016 up the yin yang. I think we can share. And we will play our role of direct advisors. However, there are also things, in my opinion, that are inevitable, that will be decisions to be made, again, regardless of the government in place. That’s that there is a platform that is not sustainable. So we have a platform that needs, that we will need to make changes to. So there are decisions that will have to be made at that time—that aspect is inevitable. So I don’t see—I see a lot of questions, but I don’t have a lot of concerns about what comes after.
Why can the call centre almost never settle a file or get it moving? You should give call centre agents more authority.
Alex Benay: I think Francis will be taking . . . No, it’s mine. Listen, that is an excellent suggestion, and I would tell you we are in the process of giving the Call Centre more authority to resolve cases. For the moment, that does not mean all cases. You heard me say earlier that we will be looking into whether Shared Services, for example, once their backlog is cleared, that there will be direct talks between Pay Centre employees and the Department. That would be one example. We are looking at, I would say, six to 12 different types of cases that the Pay Centre could also resolve directly. So we’re in the thick of it. Your suggestion, I would say we’re right on target. Thank you very much. And I would also say, feel free to contact me if you would like to help out, because we are 100% in agreement with your recommendation.
Will budget cuts cause a reduction in resources assigned to the HR and pay project?
Christiane Fox: I could start, Alex. I think that when we draw up the budget, obviously, the last budget included representations regarding cuts. I think it was indicated in the budget: 5,000 employees. The majority of the departments are managing the situation, but others will be making different decisions. I think that collectively, across the public service, we will absolutely have to prioritize existing priorities. The human resources pay system is one of them. I think we need to have a good system in place for our employees. I think we will have to dedicate the necessary resources to do it. So I think each department will look at its specific context, programs, etc. I would say that within the public service, with the committee I chair and in conversation with the clerk, it is essential that we dedicate the necessary resources to the pay system and ensure that it runs smoothly so our employees get paid. As Francis said, that’s our objective. It’s an objective we will be keeping. So I think that what I can say in terms of priorities is that emphasis will be placed on the pay system.
Alex Benay: Absolutely nothing to add. I just want to say, perhaps briefly, that our teams and Francis’s teams are working very closely with our central agencies, the departments. I want to say there is positive momentum. That’s basically what I am trying to communicate. And we fully intend to make it to the end of the fiscal year with clarity that we will be able to communicate more readily. Soon, we hope.