This topic describes the information that’s available when you load the appropriate period in Work > Calendar during an active vacation bidding session and select the Bidding Calendar View. It outlines how you can review your vacation bidding session limits and plan your vacation based on availability, your rank in the bidding order, and session type.
Role feature access: Work > Calendar > Bidding Calendar
Dayforce shows eligible dates for vacation bidding on the calendar and the number of available vacation slots on each date. Vacation slots are the number of spaces that are available for vacation on a day (in other words, the total number of employees who can take vacation at the same time). Each calendar cell in the period that’s eligible for bidding shows the number of available slots:
In concurrent vacation bidding sessions, Dayforce updates the available slots count dynamically. Depending on your rank in the bidding order and the number of bids made by other employees, Dayforce shows a different availability value.
Consider an example where three vacation slots are available for March 27, and nine employees are included in a session to bid on vacation for the month. Employee 1 is ranked first in the bidding order, Employee 2 is ranked second in the bidding order, and so on. Employees 4 through 6 submit bids for March 27 first, claiming all three available slots. After they submit their bids, the available slots value updates to “0” on March 27 for Employees 7 through 9 because they’re ranked lower in the bidding order than the employees who placed the bids. However, for Employees 1 through 3, the available slots value for March 27 is still marked as “3” because each bid was placed by employees with lower rankings in the bidding order. If Employee 1 bids on March 27, the available slots value changes to “2” for Employees 2 and 3, representing the only bid made by an employee higher than them in the bidding order hierarchy.
Available slot values update dynamically in sequential vacation bidding sessions as well. However, because these sessions require that employees bid in a scheduled sequence, it’s easier for the employees to determine the likelihood that their bid will be approved. In some cases, the available slots value might increase if employees remove bids.
Dayforce marks calendar dates with an icon when a site is temporarily closed. Depending on how a vacation bidding session is configured, this icon might indicate that you shouldn’t bid on a date for vacation time because the site won’t be operational:
Dayforce also marks calendar dates with the low probability for bid win icon (
) when you’re unlikely to win a vacation bid. The application shows this icon on the cells of eligible dates that no longer contain vacation slots or already contain multiple bids.
Before You Begin: Depending on your Dayforce configuration, the wait list for vacation bids might be unavailable. You also might be unable to bid on dates with no available vacation slots.
While it’s unlikely that you’ll be granted vacation when you bid on dates that are marked with the low probability for bid win icon, you can still bid on these dates. When an eligible date in the bidding period has no more slots, Dayforce places any subsequent bids in a wait list. The wait list follows the same ranking logic as the session’s bidding order. If a date’s slot availability is exceeded and an employee with a higher rank bids on the same date before you, they’re ranked higher than you in the wait list. After you bid on an eligible date with no slots available, Dayforce shows your rank in the wait list on the date in the calendar:
In the screenshot above, each eligible date in the bidding period contains one vacation slot, and three employees have placed bids on the same date. Because only one slot is available, Lyndon Brandt and Macon Burke are placed in the wait list for the vacation date. Macon Burke is ranked second in the wait list after Lyndon Brandt because Macon’s rank is lower.
In concurrent vacation bidding sessions, a bid that you placed that was originally within the available slot limit can sometimes be pushed to the wait list. When employees that are ranked above you in the bidding order bid on the same date and exceed the slot availability limit, Dayforce lowers your position in the bid hierarchy and places your bid in the wait list.
Continuing the example outlined above: Employees 1 through 9 all plan on bidding for vacation on March 27, which has three vacation slots available. Employee 1 is ranked first in the bidding order, Employee 2 is ranked second in the bidding order, and so on. Employees 4 through 6 submit bids for March 27 first, claiming all three available slots. Employee 1 submits a bid for March 27 after Employees 4 through 6. After Employee 1 submits their bid, Employees 4 through 6 all move down one spot in the bidding hierarchy. Employees 4 and 5 still have valid bids but Employee 6’s bid is no longer within the available slot limit, so their bid is placed in the wait list.
If any eligible bids ahead of you in the bid hierarchy (in both the wait list and within the default availability limit) are canceled or removed, your rank in the wait list increases. Also, depending on your position in the wait list, your pending bid might be approved after another employee’s bid is canceled or removed.
Dayforce shows your bidding information in the top-right section of the Bidding Calendar View. Depending on the type of session you’re participating in, Dayforce shows different bidding information.
| Session Type | Information Shown |
|---|---|
| Concurrent |
Dayforce shows your rank in the bidding order:
|
| Sequential |
Dayforce shows your bidding window start date and time when your bidding window is in the future:
When your bidding window is active or in the past, Dayforce shows your bidding window end date and time:
|
Note: Dayforce shows bidding window start and end times based on your time zone.