Skip to main content

Employee Scheduling Self-Service

Summary​

Employee self-service is Partial. An attendance-punch experience can display the selected employee’s shift timing, but employees cannot browse a roster or request scheduling changes.

Audience​

Employees, managers, HR administrators, product, QA and support.

Reference Content​

Business purpose and process​

The punch page loads employee attendance-profile data and displays the employee name, shift timing when present, and attendance mode. The employee can use attendance self-service according to permissions, while holidays, weekly offs and approved leave constrain date handling in attendance views.

Employee responsibilities​

  • Use the assigned attendance/punch surface within authorized scope.
  • Review displayed shift timing where available.
  • Escalate an incorrect or missing shift through an external HR/support process; no in-product correction workflow is verified.

Status and actions​

No scheduling status is shown. Employees cannot accept, decline, swap, bid for, request, edit or acknowledge a shift. No preferred availability, unavailability or roster calendar is captured.

Integrations​

Shift display depends on the employee/attendance data returned to the UI. Attendance records and leave/holiday/weekly-off status are integrated with employee views, but this does not create a scheduling self-service domain.

Limitations and requires confirmation​

The inspected route includes a temporary/demo punch page and a separate ESS attendance experience; exact production exposure requires confirmation. Employee communication and correction service levels are not defined in source.

Business Evidence Checklist​

  • Business purpose: Let employees see shift context while recording/viewing attendance.
  • Actors: Employees, managers and HR/support administrators.
  • Business process: Load employee profile, display available shift timing and continue attendance self-service.
  • Status transitions: No employee scheduling transition or acknowledgement exists.
  • Responsibilities: Employees report discrepancies; HR/support correct through supported administration.
  • Business rules: Employee visibility remains permission- and data-dependent.
  • Integrations: Employee profile, assigned shift, Attendance, holidays, weekly offs and Leave.
  • Limitations: No roster, preference, availability, swap or change request.
  • Requires confirmation: Production page exposure and correction process require confirmation.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/TemporaryAttendancePunchPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • microservices/src/attendance-service/Application/Services/AttendanceQueries.cs

See Also​

Keywords​

  • Employee visibility
  • Attendance punch
  • No shift swap

Revision Information​

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