> For the complete documentation index, see [llms.txt](https://docs.pockethrms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pockethrms.com/ess-portal/employee/leave-and-attendance/breakshift-attendance-regularization.md).

# Breakshift Attendance Regularization

### **Breakshift Attendance Regularization**

### **How To Request Breakshift Attendance Regularization?**

**Path:** ESS Portal > Leave > Request > Breakshift Attendance Regularization

This screen shows your punches for each day and lets you add any that are missing. Adding them keeps your working hours accurate on days when Breakshift is turned on for your shift.

**Step 1:** Log in to the **ESS Portal**, open **Leave**, then **Request**.

<img src="/files/2d900ad71a89c26bdac91465ad160fd23d6b424d" alt="" width="188">

**Step 2:** Click on **More, From** the dropdown, choose **Breakshift Attendance Regularization**.

![](/files/da685468c6a1040c5317a4a5039de3c28a339107)

<img src="/files/4daaab3e0c21ea8445ed921d52378f65386efc6c" alt="" width="188">

**Step 3:** Each Entry in the list shows:

* First punch
* Last punch
* Permitted shift hours
* Actual working hours
* Shortfall hours
* Additional hours
* A Regularize button

<figure><img src="/files/625b3eeea2ad77d9a68a75e38807d45176246e66" alt=""><figcaption></figcaption></figure>

**Step 4:** Click **Regularize** on the entry you want to fix.

<figure><img src="/files/846f56fb96be8ce178c2602d97d477483b559dfa" alt=""><figcaption></figcaption></figure>

A pop-up opens showing that day's raw punches, along with three figures:

* Captured Actual Working Hours
* Regularized Working Hours
* Total Working Hours (the first two added together)

<img src="/files/c7e4d48e31d30f8d8b12a0b53c3932a7cf09e379" alt="" width="375">

How the punches are laid out depends on your shift's Pattern Type:

* **Consecutive Punches**: All of that day's punches appear together in a single list, one after another.
* **Dedicated In/Out Punches**: punches are split into separate In and Out columns instead.

**Step 4:** **Add** any missing punches. How this works also depends on the Pattern Type:

* **Consecutive Punches:** you add the missing punch yourself, and it's highlighted in **blue**. The system places it in the correct order automatically.

<figure><img src="/files/7d4f28dd0a2cf4387a951ea4ec8345d82eb8217b" alt="" width="375"><figcaption></figcaption></figure>

<img src="/files/320da8e3e4e8d93146d2202bce7d98b5afad3f53" alt="" width="375">

* **Dedicated In/Out Punches:** the system already fills in a suggested missing punch for you, highlighted with a red border. You can edit that value directly, or add more punches if needed.

**Step 5:** Click **Save.**

<figure><img src="/files/d7d04c6d5434b70bcb26f0e60189a54cffec0af1" alt="" width="375"><figcaption></figcaption></figure>

Once you save, the request goes to the prioritized **manager** **or** **manager’s** **OR** to **Admin/HR** for approval. Both get notified automatically. Afterward,

click **View** **Details** to check the approval status and see what you submitted.

<figure><img src="/files/e0c254cef92dacb6e1d7a1d39dfb4a86c1090947" alt="" width="375"><figcaption></figcaption></figure>

**Important Note:** With Consecutive Punches, your total punches for the day (old plus new) must add up to an even number, since punches are paired two at a time. If the count is odd, Save is blocked and shows this message: "Punches shall be in even count."

**Path Link:** [**https://ess.pockethrms.com/Leave/Transaction/LeaveRequest?Menu=leave**](https://ess.pockethrms.com/Leave/Transaction/LeaveRequest?Menu=leave%20)

**For any queries, contact** [**support@pockethrms.com**](mailto:support@pockethrms.com)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pockethrms.com/ess-portal/employee/leave-and-attendance/breakshift-attendance-regularization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.