> 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/hr-and-admin-portal/cloud-configuration/setting/attendance/breakshift-configuration.md).
# Breakshift Configuration
### **BreakShift Configuration**
**Break Shift Configuration** defines a work schedule in which an employee’s working day is divided into multiple work periods by pairing the received raw punches. It considers all punches recorded during the day and provides an accurate view of total working hours, break duration, and additional hours worked.
**Path:** Cloud Portal > Settings > Attendance > Attendance Setting > Breakshift Configuration
**Step 1:** Log in to the **Cloud Portal**, open **Settings**, go to **Attendance**,
select **Attendance** **Setting**, and under it, select **Breakshift** **Configuration**.
**Step 2:** Turn on the **Enable Breakshift** toggle. This calculates working hours using every punch made in the day, instead of only the first-in and last-out punch, which is the default method.
**Step 3:** In **Select shifts**, choose the Created shift or shifts this configuration applies to. Shifts that already have a Breakshift setting saved appear highlighted in the list.
**Step 4:** In **Skip Punch within**, enter a **duration** in **minutes** and **seconds**. If two punches in a pair fall within this duration of each other, one of them is skipped so it isn't counted twice.
**Step 5:** Choose a **Pattern Type**.
**Consecutive Punches** treats any two punches that fall close together in time as a pair.
**Dedicated In/Out Punches** The system automatically treats the punches as per **In Flag and** and **Out Flag** received against punches.
* **Consecutive Punches:** choose First Punch or Second Punch — which one of two quick, consecutive punches should count.
* **Dedicated In/Out Punches:** The system automatically treats the punches as per **In Flag and** and **Out Flag** received against punches.
**Step 7:** Click **Save.**
**When to Use:**
Turn this on for employees whose schedules include flexible timing or multiple breaks in a day, so their working hours are tracked accurately.
**How It Works:**
All punches, in and out, are recorded through the day. If the skip duration is set to, say, 2 minutes, any two punches that fall within 2 minutes of each other are treated as a pair, and one of them is skipped. The example below assumes a "Consider First Punch" rule, so the earlier punch in a skipped pair is the one that's kept. Employees can also regularize and add any unpaired or missed punches from the ESS side.
For a day with these punches — 10:00:00, 10:01:00, 10:03:00, 10:30:00, and 18:20:10 — and a 2-minute skip duration:
**Important Note:** Set the skip duration carefully. Any pair of punches that falls within it has one punch removed, so setting it too wide can drop punches you actually want counted.
**Path Link:** [**https://cloud.pockethrms.com/Settings/Employee/Index?module=attendance\&submodule=BreakShiftConfiguration**](https://cloud.pockethrms.com/Settings/Employee/Index?module=attendance\&submodule=BreakShiftConfiguration)
**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/hr-and-admin-portal/cloud-configuration/setting/attendance/breakshift-configuration.md?ask=&goal=
```
`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.