Skip to main content

Workforce Scheduling Business Limitations

Summary​

The module is a shift-policy and attendance foundation, not a complete workforce scheduler. The following gaps are verified from source.

Audience​

Product, HR/payroll administrators, managers, QA, support, architects and implementation partners.

Reference Content​

Scheduling​

  • No weekly or monthly shift roster builder, schedule calendar, demand forecast, coverage model or publication.
  • No shift templates, patterns, rotations, split shifts, multiple daily shifts, availability or preference model.
  • No department, team, factory, branch or location scheduling.

Assignment​

  • Effective-dated assignment exists in the extracted backend but has no confirmed React administration screen.
  • Compatibility employee UI stores only one optional fixed shift.
  • No bulk assignment, assignment update/end endpoint, history correction UI, swap, bid, acknowledgement or replacement process.

Workflow​

  • No Draft/Published/Confirmed roster lifecycle, approval, delegation, conflict workflow or schedule change request.
  • No overtime preapproval or scheduling exception process.

Reporting​

  • No shift headcount, coverage, variance, assignment history, fairness, cost, compliance exception or schedule report.
  • Attendance/payroll reports describe outcomes, not planned rosters.

Notifications​

  • No shift assigned, changed, cancelled, upcoming, swap or publication event/template/notification is verified.

Integration​

  • Employee-to-Attendance profile synchronization remains transitional.
  • Leave does not use employee shift assignments for duration.
  • Payroll does not calculate shift differentials or direct shift premiums.
  • Organization/factory/department/team/location data is not connected to assignment commands.
  • Gateway routing can change ownership and delete behavior.

UI​

  • Shift Management covers shift CRUD and attendance policies, not roster management.
  • No effective-dated assignment list/form, shift activation control, assignment calendar, employee schedule page or manager scheduler.
  • Client navigation can expose Shift Management to HR managers while monolith mutations remain administrator-only.
  • UI labels mention roster-ready patterns, but no roster function is implemented.

Requires confirmation​

External/manual roster processes, production routing, tenant-specific policy, legal controls, operational reconciliation and roadmap commitments all require confirmation.

Business Evidence Checklist​

  • Business purpose: Prevent foundation features from being mistaken for a complete scheduler.
  • Actors: Product, HR/payroll, managers, QA, support and architects.
  • Business process: Compare requested capability with verified source and classify the gap.
  • Status transitions: No missing workflow state is represented as implemented.
  • Responsibilities: Product owns roadmap decisions; operators use only verified capabilities.
  • Business rules: Unsupported rules are not inferred from labels, plans or placeholders.
  • Integrations: Gaps span Employee, Leave, Payroll, Notification and Organization.
  • Limitations: Scheduling, assignment, workflow, reporting, notification, integration and UI gaps are grouped above.
  • Requires confirmation: External processes and future commitments require confirmation.

Source References​

  • microservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.cs
  • UI/salary-ui/HRMS_FEATURE_GAP_PLAN.md
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx

See Also​

Keywords​

  • Business limitations
  • Roster gaps
  • Scheduling foundation

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly