Skip to main content

Workforce Scheduling Business Overview

Summary​

The implemented business capability defines working windows and associates employees with a working-time policy. It supports attendance calculation and payroll inputs, but it does not plan workforce demand or publish rosters.

Audience​

Business owners, HR and payroll administrators, managers, implementation partners, QA and architecture reviewers.

Reference Content​

Business purpose​

  • Define a tenant’s named working windows, including start/end time, grace, standard hours and overtime threshold.
  • Define tenant weekly-off days.
  • Associate an employee with one active shift for an effective date range through the extracted foundation.
  • Resolve the effective shift, tenant attendance policy and employee profile for attendance calculation.
  • Carry calculated attendance measures into payroll.

Actors and responsibilities​

ActorVerified involvement
HR administratorOpens Shift Management, maintains shifts and attendance policies, and maintains weekly offs through holiday settings
HR managerCan see Shift Management navigation in the client; mutation authorization differs by routed implementation
Employee administratorSelects a fixed shift on employee profile forms in the compatibility UI
EmployeeSees assigned shift timing in the attendance-punch experience; no scheduling mutation is exposed
Attendance processorUses effective shift/policy values to calculate attendance, overtime, deduction and paid units
Payroll administratorConsumes approved attendance summaries, overtime and shortfall effects

Business process​

Maturity​

The monolith and extracted Attendance Service both expose compatibility-shaped shift behavior behind gateway routing. Direct Attendance Service assignment and policy capabilities exist, but the current React Shift Management page does not administer effective-dated assignments. This is Transitional.

Requires confirmation​

Production routing, adopted tenant rules, legal review, operational ownership, staffing coverage practices and any external time-clock integration require confirmation.

Business Evidence Checklist​

  • Business purpose: Convert shift and work-calendar configuration into attendance/payroll inputs.
  • Actors: HR, managers, employees, attendance processors and payroll administrators.
  • Business process: Define, assign, resolve, calculate and consume.
  • Status transitions: Active/inactive configuration is implemented; schedule publication states are not.
  • Responsibilities: Each actor owns the boundary described above.
  • Business rules: Tenant, validity, effective-date and overlap rules constrain the process.
  • Integrations: Employee identity, Attendance, Leave and Payroll are verified; organizational scheduling is not.
  • Limitations: The capability is not a demand, coverage or roster-planning engine.
  • Requires confirmation: Live routing, business policy and production practice require confirmation.

Source References​

  • microservices/src/attendance-service/Domain/TimeOffice/Shift.cs
  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • Models/Shift.cs
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx

See Also​

Keywords​

  • Business capability
  • Working window
  • Time Office

Revision Information​

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