• What - Administrators can now directly edit call shift rankings by entering position numbers, providing an alternative to the drag-and-drop interface. This enhancement streamlines ranking management for large organizations by allowing precise numerical positioning without manual dragging through multiple positions while maintaining full compatibility with existing drag-and-drop functionality.
• Why - This enhancement was implemented due to customer request to provide a more efficient method for managing rankings in large organizations where dragging users through multiple positions was time-consuming and cumbersome.
• How - To use this feature:
• Use Case - A scheduling administrator managing a department with 150 employees needs to move an employee from position 145 to position 5 in the call shift ranking due to a recent certification. Instead of dragging the employee through 140 positions, the administrator simply clicks the pencil icon, types "5" in the position field, and saves the change, instantly repositioning the employee while the system automatically adjusts all affected rankings.
• What - This feature enables administrators to manually conclude call shifts before their scheduled deadline while maintaining the standard award process. It provides greater flexibility in shift management when suitable candidates are already available, eliminating the need to wait for automatic deadline-based awards while preserving all existing award logic and candidate evaluation criteria.
• Why - This enhancement was developed due to customer request to provide administrators with the ability to expedite the award process when qualified candidates have already responded, reducing unnecessary wait times and improving operational efficiency.
• How - To execute an early award:
• Use Case - An administrator creates a call shift for an emergency overtime position with a 4-hour deadline, but within 30 minutes, three qualified candidates have already responded and accepted. Rather than waiting the full 4 hours for the automatic award process, the administrator uses the "Stop and Award" feature to immediately close the call shift and award it to the best-qualified respondent based on the system's evaluation criteria, getting the position filled quickly.
• What - New rotation rules have been introduced to the scheduling system, offering more flexibility in shift assignments with multiple complex patterns including Windsor rotations and various on/off configurations. These patterns support diverse scheduling needs from simple alternating schedules to complex multi-week rotations that can accommodate various operational requirements.
• Why - These new rotation patterns were added due to customer request to support more diverse scheduling requirements and provide greater flexibility in creating rotation schedules that match specific operational needs.
• How - To implement new rotation patterns:
• Use Case - A fire department needs to implement a Windsor rotation pattern for their specialized hazmat team that requires a complex 56-day cycle with varying on/off patterns. The administrator enables the Windsor rotation rule in the system settings, creates a new rotation using this pattern, and assigns it to the hazmat team members, automatically generating their schedule for the entire year based on the complex pattern without manual entry.
• What - This enhancement adds visibility for accepted call shifts directly within the My Shifts interface, ensuring users can track their commitments even when shifts haven't been formally assigned yet. This addresses a critical gap where users could accept call shifts but forget about them due to lack of calendar integration until official assignment, providing complete shift information and maintaining all existing work shift functionality.
• Why - This feature was implemented due to customer request to improve visibility of accepted call shifts and prevent users from forgetting about shifts they've committed to but haven't been formally assigned yet.
• How - The feature works automatically:
• Use Case - A paramedic accepts a call shift for next Saturday's overnight coverage but the shift won't be formally assigned until Friday when all responses are collected. The accepted shift immediately appears in their My Shifts calendar view, allowing them to see their commitment alongside their regular shifts, add availability preferences if needed, and plan their week accordingly without risk of double-booking or forgetting about the accepted shift.
• What - A new launch button has been added to the time clock history page to provide administrators with direct access to kiosk mode functionality. This enhancement eliminates the need for administrators to manually navigate to or remember specific URLs, streamlining the process of setting up shared clocking stations for employee use with one-click access from the history page.
• Why - This feature was added due to customer request to simplify the process of accessing kiosk mode for administrators who frequently need to set up shared time clock stations for employees.
• How - To access kiosk mode:
• Use Case - A shift supervisor needs to set up a shared time clock station at the beginning of each shift for firefighters to clock in and out. Instead of bookmarking URLs or navigating through multiple menus, the supervisor simply goes to the time clock history page and clicks the launch kiosk button, instantly opening the kiosk interface on the station's iPad for employee use throughout the shift.
• What - Agencies can now filter call shifts by district to ensure they contact the appropriate personnel groups when staffing assignments. This enhancement streamlines the call process by allowing organizations to target specific geographic or organizational districts with multi-select capability, integrating seamlessly with existing field management district data and maintaining consistency with current shift and rank filters.
• Why - This feature was implemented due to customer request to improve call shift targeting by allowing organizations to limit calls to specific districts, reducing unnecessary notifications to personnel outside the relevant geographic or organizational areas.
• How - To filter call shifts by district:
• Use Case - A large county fire department with five distinct districts needs to fill an overtime shift at the North District station. When creating the call shift, the administrator selects only "North District" from the district filter, ensuring that only personnel assigned to the North District receive the call shift notification, preventing unnecessary calls to firefighters in the South, East, West, and Central districts who would be unlikely to accept due to distance.
• What - This fix resolves incorrect warning messages that were displaying when assigning users to rotation partial shifts on AWT (Assignment Without Time). The system was incorrectly calculating consecutive hours for users with gaps in their schedule, triggering false warnings about exceeding maximum consecutive hours limits even when assignments were well within configured thresholds, now ensuring accurate consecutive hour tracking across different time periods.
• Why - This fix was implemented due to customer request after users reported receiving false warning messages when making valid assignments that were incorrectly calculated as exceeding consecutive hour limits.
• How - The fix works automatically:
• Use Case - A scheduler assigns an employee to work Monday through Thursday from 08:30 to 16:30 (8 hours per day, 32 hours total) with a configured 48-hour consecutive limit. Previously, the system would incorrectly warn about exceeding the limit despite the 32 hours being well under the 48-hour threshold. With this fix, the assignment proceeds without false warnings, correctly recognizing the actual working hours.
• What - This release addresses an issue where unassigned shifts resulting from trade requests were incorrectly inheriting the system default work type instead of the work type configured in Trade Settings. The fix ensures consistent work type application across all trade scenarios, with both assigned and unassigned shifts now following the same work type logic, improving scheduling accuracy and reducing manual corrections.
• Why - This fix was implemented due to customer request after organizations reported that traded shifts were not maintaining the correct work type, requiring manual corrections and causing confusion in scheduling.
• How - To ensure proper work type application:
• Use Case - An unassigned employee requests to trade into a shift that should be designated as "Overtime" work type per the Trade Settings configuration. Previously, the system would incorrectly apply the default "Regular" work type, requiring manual correction. Now, when the trade is approved, the shift automatically maintains the "Overtime" designation throughout the entire process, from initial request through final scheduling on the Shift Board.
• What - This fix resolves an issue where users were unable to update assignment end dates even when no validated assignments existed after the requested end date. The system now correctly allows end date modifications when there's no risk to data integrity, while maintaining protection against validated data loss and providing clear error messaging when updates cannot proceed due to validated data conflicts.
• Why - This fix was implemented due to customer request after users reported being unnecessarily blocked from updating assignment end dates when no validated data would be affected by the change.
• How - To update assignment end dates:
• Use Case - An administrator needs to end an employee's temporary assignment on March 15th instead of March 31st due to the employee returning to their regular position early. Since no validated shifts exist between March 16th and March 31st, the system now allows the administrator to update the end date to March 15th immediately, whereas previously this would have been blocked unnecessarily even without any validated data at risk.