Infrastructure for Shift Bidding & Schedule Optimization

Shift bidding and schedule optimization requires explicit, findable documentation of union contract rules (seniority ordering for shift bids), fair scheduling requirements (maximum consecutive shifts, mandatory rest periods), and skill requirements by shift type (RN-to-patient ratios, charge nurse requirements). These rules must be current and queryable — when the AI auto-approves a shift swap, an auditor must be able to verify which documented rule authorized it.

Staff availability preferences, shift bid submissions, and historical assignment patterns must be captured through systematic workflows. Template-driven preference submission ensures the AI receives structured inputs — preferred shifts, unavailable dates, skill qualifications — rather than email requests to managers. Systematic capture of historical fairness data (who worked last holiday, weekend distribution over the past quarter) enables the optimization algorithm to enforce equitable distribution.

Shift optimization requires consistent schema across all records: Staff entities linked to Qualification records (role, certifications, union seniority), Shift records (unit, time, skill requirements, minimum staffing levels), and Assignment records (who worked when, overtime hours, holiday assignments). Consistent fields across these entities enable constraint checking — the AI can verify 'Staff.RestHoursAfterLastShift >= 8' because every assignment record contains a standard ShiftEndTime field.

Shift bidding operates within the scheduling platform and HRIS — the AI needs access to staff qualification records and open shift postings, which current point integrations partially support. The baseline confirms scheduling systems exist but are separate from HRIS, requiring some manual data transfer. At L2, the scheduling platform can surface open shifts and accept bids, but real-time access to payroll-calculated overtime thresholds or credentialing status requires manual coordination, constraining fully automated compliance checking.

Union contract rules change upon contract renewal. State fair scheduling laws update. Staff qualifications change when certifications expire or new competencies are gained. Schedule optimization rules must update when these events occur — not on a quarterly calendar. When a nurse's ACLS certification lapses, the system must immediately remove them from shifts requiring that certification. Event-triggered maintenance prevents the AI from assigning unqualified staff.

At L2, the shift bidding platform integrates with time-and-attendance (to track hours worked and overtime thresholds) and partially with HRIS (for role and department data). This point-to-point level supports basic shift optimization within the scheduling domain. Full HRIS-credentialing-payroll integration isn't required for shift bidding to function, as the baseline confirms scheduling operates as a dedicated system with core data flows to payroll established.