UKG Pro WFM Scheduling: Patterns, Coverage and Open Shifts

Good schedules in UKG Pro Workforce Management start with three layers: repeating schedule patterns for predictable work, coverage targets that say how many people with which skills you need each hour, and rules for open shifts and swaps that fill the gaps. Fair workweek laws then decide how late you can change any of it.

Key takeaways

• Use patterns for the stable core of the schedule and open shifts for the variable edge.
• Define coverage by job, skill and time block before anyone builds a schedule. Without a target, nobody can tell whether a schedule is good.
• Swap and pickup rules need the same overtime, certification and rest checks as manager-built schedules.
• In predictive scheduling jurisdictions, the posting date and every later change carry a cost. Configure lead times before go-live.

What scheduling tools does UKG Pro WFM provide?

UKG's employee scheduling page describes forecasting that predicts workload demand in 15-minute intervals, auto-assigning shifts based on skills, preferences and availability, mobile self-service where employees swap shifts and submit preferences, the ability for employees to pick up open shifts, and built-in support for fair workweek laws, certifications and fatigue rules. The UKG Pro Scheduling product profile adds real-time views of staffing coverage and rule checking in Advanced Scheduling.

Which of these you have depends on your licensed modules. Confirm with your UKG team whether forecasting and advanced scheduling are in scope before designing around them. This guide assumes the core scheduling capability and calls out where advanced modules change the approach.

How do schedule patterns work, and when should you use them?

UKG's help topic on how to create a schedule pattern describes patterns as a way to fill out a schedule quickly. You open the pattern for an employee, a schedule group or employment terms, set a start date and optional end date, define a repeating cycle in days or weeks, and add shifts, availability and pay codes to each day. Saving the schedule rolls the pattern out for its full length. An option lets a new pattern override shifts and pay codes from earlier patterns.

Patterns work well for

• Fixed rotations such as four on, four off, or a two-week cycle in a plant.
• Office and support roles with stable hours.
• Recurring days off that should appear months ahead.

Patterns work poorly for

• Retail and hospitality hours that move with demand week to week.
• New stores or units with no history.
• Employees with frequently changing availability.

A common mistake is stacking patterns at the employee level and the group level without a rule for which wins. Pick one level as the default (usually the schedule group) and document when an employee level pattern is allowed.

How do you define coverage and staffing needs?

Coverage is the target your schedule is measured against. Build it before building schedules, and keep it in a table the operations leader signs.

Element	Decision	Example
Location and department	Where coverage is measured	Store 14, front end
Job or skill	Who counts toward coverage	Cashier, certified forklift operator
Time block	Granularity of the target	Hourly, or 15-minute blocks if forecasting is used
Minimum	Floor for safety or service	Two cashiers whenever open
Target	Number you schedule to	Driven by forecast volume
Maximum	Point where cost outweighs service	Set by budget

With forecasting, the target comes from predicted volume. Without it, start from historical traffic or units processed by hour and revise monthly. Either way, check the real-time coverage view during the first weeks and compare scheduled against needed by block. Gaps that repeat in the same block point to a pattern problem, not a staffing problem.

How should open shifts and swaps be configured?

Open shifts and swaps let employees fill gaps without a manager rebuilding the schedule. They also let employees accidentally create overtime, schedule themselves without a required certification, or break a rest rule. Write the rules first.

• Eligibility: which jobs, locations and certifications can claim each open shift.
• Overtime: whether a pickup that pushes someone into overtime is blocked, flagged or allowed.
• Rest: minimum hours between shifts, especially where the law sets one.
• Approval: automatic for like-for-like swaps between qualified employees, manager approval for everything else.
• Cutoff: how close to the shift a swap or pickup is still allowed.
• Fairness: first come first served, seniority or rotation when several people want the same shift.

Shift premiums and overtime calculations sit in your pay rules, so changes here should be tested with payroll. Our UKG Pro WFM pay rule and work rule checklist covers that side.

What do predictive scheduling laws change in your setup?

Fair workweek laws vary by city and state, so treat the following as an example rather than a rule for every location. Oregon's Bureau of Labor and Industries explains on its predictive scheduling page that the state law covers retail, hospitality and food service employers with at least 500 employees worldwide. Covered employers must post written schedules at least 14 calendar days in advance, give a good faith estimate of hours at hire, and avoid scheduling workers within 10 hours after the end of the previous day's shift unless the worker requests or agrees, with time-and-a-half for hours worked in that window. Changes without required notice can trigger predictability pay, and employers may keep a voluntary standby list with written consent.

Law requirement	Scheduling setup to review
Advance posting	Schedule generation and posting calendar per location
Rest between shifts	Rule checks on manager edits, swaps and pickups
Predictability pay	Pay codes and how late changes are flagged to payroll
Voluntary standby list	Who receives open shift offers, and consent records
Good faith estimate	Onboarding documents, not the schedule itself

For the payroll side, see our guide to calculating fair workweek predictability pay. For the broader legal picture by jurisdiction, our guide to employee scheduling rights in the US is a useful starting point. Have employment counsel confirm which laws apply at each location.

Frequently Asked Questions

Should every employee have a schedule pattern?

No. Patterns suit stable rotations and fixed hours. In demand-driven operations, patterns can create more editing work than they save, because managers override them every week. A common approach is patterns for full-time core staff and open shifts or generated schedules for part-time and flexible staff, with coverage targets guiding both.

How far ahead should schedules be posted?

As far ahead as the law requires at each location and your operation can forecast reliably. Oregon's law requires 14 calendar days for covered employers, and other jurisdictions set their own periods. Where no law applies, posting two weeks out is a reasonable baseline that gives employees time to arrange child care and swaps.

Can employees swap shifts without a manager?

UKG describes mobile self-service where employees swap shifts with coworkers. Whether a swap needs approval is your policy choice. Automatic approval works for like-for-like swaps between qualified employees that do not create overtime or rest violations. Everything else should route to a manager with the reason shown.

What is the most common scheduling setup mistake?

Launching self-service before writing eligibility and overtime rules. Employees then pick up shifts they are not certified for or that push them into overtime, and managers lose trust in the tool. Configure rules first, test them with real scenarios, and turn on open shifts by location once each one passes.

Next steps for your scheduling build

• Write a coverage table for one pilot location and have operations sign it.
• Decide which employee groups get patterns and at which level.
• Write open shift and swap rules, including overtime and rest checks.
• List every fair workweek jurisdiction you operate in and map each requirement to a setting or pay code.
• Pilot for four schedule cycles before rolling out.

For accrual, pay rule and payroll close topics, see our UKG guides.

Last reviewed: October 2026.

Sources

• Employee Scheduling Software for Smarter Planning, UKG
• UKG Pro Scheduling Product Profile, UKG
• Create a schedule pattern, UKG Help
• Predictive Scheduling, Oregon Bureau of Labor and Industries