Author: Aditi Gupta, Senior HCM Consultant, Namos Solutions
Managing a workforce with irregular shifts, complex labour rules, and employees spread across roles and locations is a daily challenge for many organisations. And yet, many Oracle HCM customers are operating with a scheduling setup that has a critical blind spot in the Redwood experience. Here’s what’s happening and what to do about it.
Let’s start with something that often causes confusion. Employees can view their own schedule, their peers’, and their team’s calendar perfectly well in the Oracle Responsive UI, that capability exists and works. The issue is more specific than “you can’t see a calendar.” So, where is the actual gap?
The Redwood Team Schedule page only surfaces schedules that have been set up using Work Pattern Templates (the newer configuration method). If your organisation’s schedules are assigned via Work Schedule Assignment (the traditional approach), those schedules simply do not appear on the Redwood Team Schedule page. Employees and managers using Redwood get an incomplete picture or no picture at all, depending on how schedules are configured.
Why Does This Matter?
Because Redwood is where Oracle is investing. It’s where the modern employee and manager experience lives. It provides cleaner UI, mobile-consistent rendering, absence integration, and team visibility. If your schedule setup method isn’t compatible with it, you’re locked out of that experience.
Here’s a quick comparison between traditional work schedules and new Work Patterns:
| Capability | Work Schedule Assignment (traditional) | Work Pattern Templates (new method) |
| View own schedule in Responsive UI | Works | Works |
| View team calendar in Responsive UI | Works | Works |
| Redwood Team Schedule page visibility | Not shown | Fully visible |
| Alerts/Notifications compatibility | No | Yes |
| Compatible with Workforce Scheduling | No | Yes |
When an organisation adopts Workforce Scheduling, they’re configuring everything through this modern framework from the ground up. Because the Redwood Team Schedule page was built around this same setup method, everything shows up as it should, including shifts, work patterns, and absence details, all rendered in one unified view, on both desktop and mobile.
Some of the latest Oracle releases which enhance the Redwood calendar are –
- Improved View Options (Release 25A)
The Redwood Team Schedule supports both weekly and 4-week views to monitor shifts, absences, and holidays.
- Calendar Extensibility (Release 26A)
Administrators gained the ability to configure the calendar UI using page properties, with the following options:
- Enable or disable Month, Week, Day, and List views on desktop. On mobile in the Redwood interface, only month pull-down and list views are supported.
- Enable page-level journeys for both Desktop Calendar and Mobile Calendar.
- Configure which fields display for colleagues during shifts — Shift Type, Worker Name, Title and Job information, and Shift start and end times.
- Accurate absence rendering (Release 26B)
Single-day absences now display correctly and consistently across all views.
- Full-day absences appear as all-day blocks
- Partial absences with fixed times appear as time-blocked events on the timeline; partial absences measured in duration (elapsed schedules) display with labels such as “Half-day” or “4 hours.”
- Overnight absences that cross midnight appear only on the starting day, preventing duplicate entries from cluttering the following day’s view.
- Configurable starting day of the week (Release 26B)
Administrators can now set which day the calendar week begins on, any day from Sunday through Saturday. The setting applies immediately across Month, Week, Day, and List views on both desktop and mobile for all workers. If no selection is made, the default is Sunday.
Here are some images for you to get a look and feel of Redwood UI calendars vs Responsive UI calendars:
Team Schedule in Redwood UI
Team Schedule in Responsive UI
View Own Calendar in Redwood UI
Own calendar in responsive UI
What Workforce Scheduling Actually Does
For organisations managing workers with irregular shifts, variable patterns, or complex staffing rules, this is where the real capability begins.
Intelligent shift assignment
Workforce Scheduling is built for environments where “everyone works 9 to 5” simply isn’t true. Rather than managers manually checking availability, rules, and eligibility for every shift, the system does the heavy lifting automatically.
Shifts are assigned based on each worker’s work pattern template which means the system already knows their contracted hours, working days, and rest requirements before a single shift is placed. On top of that, assignments respect the worker’s job and position, ensuring only appropriately qualified workers are considered for a given shift.
The system also enforces working time rules throughout, including maximum hours per day or week, minimum rest periods between shifts, and paid and unpaid break requirements. If a proposed assignment would breach any of these, it’s flagged or blocked before it reaches the published schedule, removing the compliance burden from the manager entirely.
For organisations with more complex staffing needs, shifts can also be drawn from float pool departments where workers from designated float teams are automatically considered to fill any remaining open shifts after home workers have been assigned first.
Employee empowerment on mobile
Workforce Scheduling gives employees meaningful control over their own schedule through a mobile-first experience. Once schedules are published, employees can act on them directly from their device without needing desktop access or manager involvement for routine changes. Employees can –
- View all assigned shifts in a clear schedule view, on desktop or mobile
- Claim available open shifts that match their eligibility
- Swap full shifts by equal duration and not just identical times
- Offer just the start or end portion of a shift for a partial swap
- Request shift covers when unexpected absences arise
Is it time to make the move?
If your organisation is using Work Schedule Assignment to manage schedules, you’re not getting a broken experience as the Responsive UI still works. But you are locked out of the Redwood Team Schedule page which comes up with much better details around shifts, absences, holidays, conflicts, etc. and you’re missing the shift management intelligence, automation, and mobile-first employee experience that Workforce Scheduling brings.
The path forward isn’t just about turning on a new module. It requires re-configuring shifts and work patterns using the new method. That’s a considered migration but for organisations dealing with irregular shifts, multi-department staffing, or a workforce that expects modern self-service tools, the investment pays back quickly.
Begin by mapping how your current schedules are set up specifically whether they use Work Schedule Assignment or Work Pattern Templates. That single answer determines how much migration effort is involved and which Redwood capabilities you’re currently missing.
Let’s talk about your scheduling setup!
Whether you’re assessing the gap or ready to plan a move to Workforce Scheduling, get in touch to walk through what a #TeamNamos migration could look like for your organisation.
