# Approve or Reject a Regularization

Decide a correction request, and what the final approval writes back to attendance.

Deciding is one press per row. Knowing which of the two stages you are at is what tells you whether the attendance record is about to change.

- Open **Regularizations** and read the **Status** column first. It tells you whether your decision is the first or the last.

  ![The Status and Actions columns of the regularization table. Five rows read Pending in amber and one reads Manager Approved in blue, each beside a green Approve button and an outlined red reject button. The last row reads Approved in green and its actions cell contains only a double dash.](https://www.sorviai.com/help/worklink/regularizations/decide-actions.png)
- Compare the **Requested Times** against the **Reason**. A claimed 17:30 finish with "went straight to a customer site" is a different judgement from the same time with no explanation.
- Select **Approve**, or the red button to reject. The row updates in place.

## What your decision does depends on the stage

| You are deciding a | Approving moves it to | The attendance record |
| --- | --- | --- |
| Pending request | Manager Approved | Does not change yet. |
| Manager Approved request | Approved | Is rewritten with the requested times. |
| Either, rejecting | Closed | Never changes. The day stands as recorded. |

> **Note:**
>
> **The record changes at the second approval, not the first**
>
> This is the single most misread thing about the module. A manager who approves and then checks the attendance list will see the day exactly as it was, and conclude nothing happened. It did; it is waiting on the final sign-off.

## What to check before approving

- **The date** (is it the right day): People routinely raise a correction against the day they noticed rather than the day it happened.
- **The times against the shift** (is it plausible): A claimed finish long after the shift end is an overtime question rather than a clock-out correction.
- **The pattern** (is this the third one this week): Repeated corrections from one team usually point at a broken terminal rather than at forgetfulness.

> **Tip:**
>
> **Several requests with the same cause deserve a different fix**
>
> If a whole shift's worth of people forgot to clock out on the same day, the terminal was down. Approving twenty requests works, but re-importing the period from the Records screen is one action instead of twenty.

## After approval

The corrected times appear on the attendance record and the day's status is recalculated against the shift, so a day that read Late may no longer. The request itself stays in the list as Approved, with no further actions, as the evidence of who agreed to the change.