Different Workforces, Different Rules: What to Know Before You Plan Your Global Workday Scheduling Deployment
Ask a frontline manager how they spend their week and scheduling usually makes the list. Building the schedule, reworking it when someone calls out, checking that nobody slips into overtime and filling last-minute gaps can take hours that would be better spent with their teams and customers.
Workday Scheduling and Labor Optimization are designed to take much of that work off managers’ plates. Labor Optimization forecasts business volume, converts that forecast into labor demand and can generate schedules that account for worker availability, preferences, qualifications, labor rules and cost. For global organizations, that offers something many have never had: one consistent approach to scheduling across sites and countries.
How well those schedules work, though, depends on decisions the organization makes long before deploying Workday. Made early, those decisions give the technology something solid to work from. Left until configuration, they can lead a project to rebuild the old spreadsheet inside a new system. The sections below walk through the decisions that matter most.
Scheduling Is Only One Part of Workforce Management
When deploying Workday, Scheduling is often scoped as a standalone project, but it is closely tied to everything around it. A schedule sets the expected hours that Time Tracking compares against actual time worked to calculate overtime, premiums and rest-period exceptions. Approved absences remove workers from availability. Payroll pays the result. A decision made in one area shows up in all the others.
In a global deployment, those connections multiply. A minimum rest rule may be checked when the schedule is built, flagged again when time is recorded and paid as a premium when it is broken. If Scheduling, Time Tracking, Absence and payroll are designed by separate teams on separate timelines, the same rule can be built differently in each, and the gaps tend to appear in payroll parallel testing or in employees’ paychecks.
Before deployment, decide how these modules will be designed together, which team owns decisions that cross them, and in what order countries and modules will go live.
Start With What Drives Demand
Labor Optimization starts with a forecast. Historical business data, such as transactions, units produced or guests served, is used to predict future volume, which is then translated into staffing needs through labor standards and business rules. That raises questions many organizations haven’t fully answered:
- Which business metrics actually drive staffing at each type of site?
- Is historical data available, reliable and captured at the right level, by location, department and time interval?
- Do labor standards exist, or are staffing levels based on manager experience?
- Who owns the forecast, and who can adjust it?
A global organization may find that demand drivers are consistent across a business line but differ sharply between a distribution center and a retail store. Defining those drivers and standards is business work. It needs operations leaders involved from the start, alongside HR and IT.
Define Who Gets Scheduled, and How
Country is the obvious way to divide a global scheduling design, and often the least useful. Scheduling needs vary by worker population: full-time and part-time, hourly and salaried, union and non-union, permanent and contingent. Some populations will be scheduled by the optimization engine. Others will work fixed patterns or won’t be scheduled at all.
Map the worker populations in each country and decide how each one will be scheduled before deployment begins. Workday assigns schedules, rules and validations based on worker data, so that data has to identify each population reliably.
Know Where Every Scheduling Rule Comes From
Once you know who is being scheduled, the next question is which rules the schedule has to respect. This is where global scheduling gets complicated quickly. Maximum working hours, minimum rest between shifts, break timing, minimum shift lengths, overtime thresholds and qualification requirements vary by country, and often by agreement within a country. In Australia, Modern Awards and Enterprise Agreements can set roster rules, minimum payments and penalty rates. In Germany, works councils can influence how schedules are set and when a rollout can begin.
Not every rule described as a requirement is one. Some come from legislation. Some come from collective agreements. Others are company policy or a site’s long-standing habit. Workday can support all three, but they shouldn’t be treated the same way. A legal requirement has to be built in and tested. A site habit is a choice the organization can keep or retire.
Workday Scheduling supports configurable validations that flag schedules breaking policy or regulatory rules before they are published, and schedule tags can limit shifts to workers with the right skills, certifications, availability, and qualifications. Using them well depends on answers the design team needs before configuration:
- What is the source of each rule, and which worker populations does it cover?
- Should a violation stop a schedule from being published, or warn the scheduler and allow an override?
- Where does certification and qualification data live today, and who keeps it current?
- Which markets involve unions or works councils, and when do they need to review the design?
Decide How Much Control Employees and Managers Have
Scheduling decisions affect employees directly, so the choices made during deployment have to settle how much flexibility the organization wants to offer. Workday supports open shifts, shift swaps, coverage requests and worker availability preferences, with manager approvals where needed. Which of these to turn on, and for whom, is a policy decision as much as a technical one.
In a global deployment, the answers may differ by country. Self-service shift swaps may be welcome in one market and subject to employee representative agreement in another. Set a global baseline for employee self-service, identify where local agreements require something different and plan the change management for managers who are used to building schedules themselves. Moving from building schedules to reviewing system-generated ones is a real change in how managers work, and it needs as much attention as the configuration.
Decide How You’ll Measure Success
Much of the value of Labor Optimization comes from comparing forecasted demand, scheduled labor, actual hours worked and business outcomes. That comparison shows where locations are consistently overstaffed or understaffed and whether labor spend follows demand.
That visibility only works if it is planned for. Demand metrics, time data captured in Time Tracking and the organizational structure used for reporting all have to line up. Before deployment, agree on the measures leaders will use, the level of detail they need and the baseline you’ll compare against. If you don’t know how long managers spend on scheduling today or how often schedules change after they are published, start measuring before go-live.
Questions to Answer Before Your Workday Scheduling Deployment Begins
- Which worker populations in each country will be scheduled, and how will Workday identify them?
- What business metrics drive labor demand at each type of site, and is the historical data reliable?
- Which scheduling rules come from legislation, which from agreements, and which from company policy or local practice?
- Where do unions, works councils or employee representatives need to review the design, and how does that affect the timeline?
- Which rules and processes will be global, and which local differences will you allow?
- How will Scheduling, Time Tracking, Absence and payroll be designed together, and who owns decisions that cross them?
- What self-service will employees have, and which approvals will managers keep?
- Who will own forecasts, labor standards and scheduling rules after go-live?
- How will you measure whether the deployment is working?
Scheduling Is One Decision in a Larger Strategy
Scheduling and Labor Optimization can reduce the time managers spend building schedules and bring labor closer to actual demand. In a global organization, they are also one part of a larger workforce management deployment that includes Time Tracking, Absence and payroll. The organizations that get the most from Workday design these modules together, start with worker populations rather than countries, separate legal requirements from local practice and decide what is global and what is local before configuration begins. Those decisions are what make a global deployment hold up after go-live.
About Helios
Helios has worked in workforce management for more than 20 years, including early design workshops that helped shape Workday Time Tracking. Workday has brought Helios in to advise on workforce management across the United Kingdom, France, Germany and Australia, including where Time Tracking, Absence, Scheduling and Labor Optimization could be strengthened for those markets. Our consultants lead workforce management deployments for large global organizations with union rules, collective agreements and complex shift patterns.
We bring that perspective to every global program. We help clients define worker populations, trace each requirement to its source, decide what should be global and what should be local, and design Scheduling, Time Tracking, Absence and payroll as one connected solution. Our clients go live with a design their teams understand and can maintain as the business grows.
To learn more, read our white paper, Expanding Workforce Management Globally: Seven things leaders need to consider before a global implementation, or contact Helios to talk through your global scheduling and labor optimization plans.
