> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-short-leave-rules.md).

# Setup Short Leave Rules

**Available on:** Desktop · Web

Navigate to **Payroll Setups** and click on "Setup Short Leave Rules".

A **short leave** is a few hours off on a working day - to come in late, leave early or step out for some work. Employees ask for it on the **Logic Workforce** app, it goes through the same approval steps as their other requests, and the day stays a working day. **Setup Short Leave Rules** decides, grade by grade, who may take short leaves, how many are free in a pay period, and what an extra one costs.

## The grid

Every grade is listed, one row each. A grade with no rules yet shows **ALLOWED = No**, and its other columns are blank. When it is set to **Yes**, it starts with 2 free short leaves, 120 minutes, **START OR END OF THE SHIFT**, **EACH EXTRA ONE = A HALF DAY** and **CL, THEN SL, ELSE HD**. Change any of them.

| Column                  | What it means                                                                                                                                                                                                                                                                 |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GRADE**               | The grade. A **\*** after the name means the row has changes not saved yet.                                                                                                                                                                                                   |
| **ALLOWED**             | **Yes** - employees of this grade may ask for short leaves. **No** - the app tells them short leave is not set up for them. The other columns can be changed only when this is **Yes**.                                                                                       |
| **FREE A MONTH**        | How many short leaves are free in each pay period (the calendar month where no pay period is set up), from 0 to 31 - a higher number is changed to 31. On the app, short leaves waiting for approval count too.                                                               |
| **LONGEST (MINUTES)**   | The longest single short leave, from 15 to 480 minutes.                                                                                                                                                                                                                       |
| **WHEN**                | **START OR END OF THE SHIFT** - only to come in late or leave early. **ANYWHERE IN THE SHIFT** - also in the middle of the shift. **START OR END OF THE SHIFT, OR ONE MID-DAY SLOT A MONTH** - the middle of the shift only once in each pay period; a second one is refused. |
| **EXTRA ONE COSTS**     | **EACH EXTRA ONE = A HALF DAY**, or **EVERY TWO EXTRA = A HALF DAY** (a last single extra one is not charged).                                                                                                                                                                |
| **HALF DAY CHARGED TO** | The leave the half day is taken from: **CL, THEN SL, ELSE HD** · **SL, THEN CL, ELSE HD** · **CL, ELSE HD** · **SL, ELSE HD**. When none of these leaves can be taken that day, it becomes **HD**, an unpaid half day.                                                        |

The line under the grid counts the grades, how many have short leave, and how many are changed but not saved. It also reminds you that an extra short leave becomes a half day when **Convert Short Leaves** is run. After a save it shows how many grades were saved.

## Saving

* Press **Save** and answer **Yes**. Every changed grade is saved. Each change is recorded in the Change Log Viewer (User Access) with the old and new values and the user who made it - look for the screen **Setup Short Leave Rules**.
* Closing with changes not saved asks first - **No** keeps the screen open.

## What the rules do

* **On the app** - the employee sees the pay period, how many short leaves are used so far, how many are free, the longest allowed and the day's shift. **Another time** (the middle of the shift) is offered when **WHEN** allows it. When the short leave is over the free ones, the app says it will count as a half day of leave - or, with **EVERY TWO EXTRA = A HALF DAY**, that every two extra count as a half day.
* **In attendance** - an approved short leave at the start of the shift covers coming in late, and one at the end covers leaving early. The covered time is added to the hours worked, so the day can still count as a full day - but never as overtime. A short leave in the middle of the shift is not added. Once a short leave has been turned into a half day, it no longer covers the time.
* **At the end of the pay period** - **Convert Short Leaves** (Payroll Entry) turns the extra ones into half days as set here. It skips an employee until every short leave of that pay period is approved or rejected. Changing a rule later changes how the next run counts them; short leaves already counted as a half day stay as they are until undone there.
* Setting a grade's **ALLOWED** back to **No** stops new requests, but short leaves already approved for that grade are still counted by **Convert Short Leaves**.

> **Example - setting up two grades**
>
> Staff may take 2 free short leaves a pay period, up to 2 hours, at the start or end of the shift; each extra one is a half day, from CL first and then SL. Managers may take 4, up to 3 hours, anywhere in the shift; every two extra make a half day. HR sets **Staff**: ALLOWED Yes, FREE A MONTH 2, LONGEST 120, START OR END OF THE SHIFT, EACH EXTRA ONE = A HALF DAY, CL, THEN SL, ELSE HD. Then **Managers**: ALLOWED Yes, FREE A MONTH 4, LONGEST 180, ANYWHERE IN THE SHIFT, EVERY TWO EXTRA = A HALF DAY (HALF DAY CHARGED TO stays CL, THEN SL, ELSE HD). HR presses **Save** and answers **Yes**.

## Messages you may see

| Message                                                        | Why                                                     | What to do                           |
| -------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------ |
| Save the short leave rules of ... grade(s)?                    | Asked before saving                                     | **Yes** to save                      |
| Nothing to save.                                               | **Save** with no grade changed                          | -                                    |
| ...: the longest short leave must be 15 to 480 minutes.        | **LONGEST (MINUTES)** is out of range for that grade    | Correct it                           |
| ... grade(s) have changes not saved yet. Close without saving? | Closing with changes not saved                          | **No** goes back so you can **Save** |
| Modification rights are not available...                       | **Save** pressed when your user may only view this menu | Ask for modify rights in User Access |

## On the web

The same screen is on the web, with **Save** and **Close**. On a phone the grid scrolls sideways.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-short-leave-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
