List attendance corrections

In this article

Before you start

• You are signed in with Harbor Soho selected in the GB demo runtime.
• Your location role includes attendance management permissions for staff shifts.
• The date range covers the staff shifts to review; if no range is supplied, the screen uses the current year.
• At least one staff_shift event in the selected range has start_status or end_status set to correction_requested.

Instructions

1. 1.

   Open the corrections list

   Open attendance/corrections?pending_only=true from Home, a notification, or a direct link. The screen loads pending corrections for the selected Harbor Soho location only.

2. 2.

   Check the pending rows

   Use the Pending corrections table to compare employee, status, entry time, exit time and hours. Rows marked Pending have an entry or exit that is waiting for correction.

3. 3.

   Adjust the date range

   Change the date range if the shift is outside the current period. The app updates from and to in the route, resets corrections_page to 1, and reloads staff-shift events for that range.

4. 4.

   Filter by employee

   Use the employee filter to narrow the visible rows after staff and events have loaded. The route can hold a staff value, but the filtering happens in the app rather than through a staff_id API parameter.

5. 5.

   Move through pages or refresh

   Use pagination when the list has more than 8 rows, or refresh the table manually to reload the latest pending corrections without leaving the screen.

6. 6.

   Open a row for review

   Select a row or its review action only when you are ready to handle the correction. This leaves the list and opens the staff-shift event review surface covered by related actions.

Validations and limits

• Without attendance management permission, the corrections query is not enabled and the app shows the attendance no-access message instead of the table.
• With pending_only=true, only staff_shift events whose flat start_status or end_status equals correction_requested are listed.
• The calendar-events API requires both from and to; invalid route dates are ignored by the app before loading, while a reversed range is rejected by the backend.
• If corrections_page is invalid, the screen uses page 1; if it is too high, the route is corrected to the last valid page.
• On mobile, the Hours column is not shown.
• The list does not approve, reject, edit or delete corrections; resolution belongs to the separate review flow.

Expected result

The manager identifies the pending attendance correction for Harbor Soho and can open the relevant staff-shift review flow, while the listing action itself remains read-only.