> 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/shift-roster/whats-new-in-this-release.md).

# What's New in This Release

**Available on:** Desktop · Web · Phone

This release adds a **shift roster** to Payroll: each employee can now follow a shift, or a rotation of shifts, with their own week-offs, worked out day by day. Around it come an **organisation structure**, the HR screens of the **attendance app**, a [Change Log Viewer](/logic-erp-learning-hub-tutorials-and-best-practices/user-access/change-log-viewer.md), and improvements to both **attendance registers**. Every one of these screens also runs in the **web browser** and on a **phone**.

Your existing shifts, holidays, attendance and payroll are untouched. Employees you do not give a roster carry on exactly as before, with the branch's holidays and weekly-offs.

## New screens

### **Shift roster**

| Screen                  | Menu           | What it does                                                                                                                            |
| ----------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Setup Week-off Patterns | Payroll Setups | Rules for which days are off: fixed days every week, days like the 2nd and 4th Saturday, or a cycle such as 6 days on, 1 off            |
| Setup Shift Rotations   | Payroll Setups | A repeating sequence of shifts, for example a week of day shift, then a week of night shift                                             |
| Allocate Roster         | Payroll Entry  | Gives each employee their shift or rotation from a date; many employees at once or one at a time                                        |
| Generate Roster         | Payroll Entry  | Builds the day-by-day roster for many employees at once and shows the result for each                                                   |
| Roster Calendar         | Payroll Entry  | Shows each employee's days for a payroll period; change days by hand — one day or a block — such as a swapped shift or a moved week-off |

> **Example —** Ravi's roster has one line: the day shift, Sundays off. From 1 November he moves to a rotation: one week of day shift, then one week of night shift. HR adds a second line for Ravi in [Allocate Roster](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/allocate-roster.md), from 1 November, and generates. From 1 November his days follow the rotation; the days before it stay on the day shift.

### **Organisation structure — who approves**

| Screen                  | Menu           | What it does                                                                                                           |
| ----------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Setup Designations      | Payroll Setups | The list of designations, with a level (1 = most senior)                                                               |
| Setup Org Units         | Payroll Setups | The organisation tree — company, region or zone, branch, department, team or section — where each unit can have a head |
| Assign Employees to Org | Payroll Setups | Places each employee in a unit with a designation, and shows who they will report to                                   |

### **The attendance app — HR's side**

| Screen                          | Menu           | What it does                                                                                                                                                      |
| ------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Setup Attendance App Branches   | Payroll Setups | Where each branch's staff may punch (sites on a map), its time zone, and automatic absent marking                                                                 |
| Setup Attendance App Users      | Payroll Setups | Who may use the app, the mobile they log in with, what happens when they punch away from a site, and who acts as HR                                               |
| Setup Attendance Approval Rules | Payroll Setups | Who approves leave and missed-punch requests, level by level                                                                                                      |
| Attendance App HR Review        | Payroll Entry  | One daily list of everything from the app that needs a person: punches that could not be written, flagged punches, automatic absents, and requests waiting for HR |

### **Change Log Viewer**

[User Access\Change Log Viewer](/logic-erp-learning-hub-tutorials-and-best-practices/user-access/change-log-viewer.md) shows the changes recorded from every screen above: who made each change, when, from which computer, and every value before and after. It only shows changes; it never alters anything.

## Changes to existing screens

* [Setup Payroll Shifts](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-payroll-shifts.md) has two new columns: **Week-off Pattern**, the shift's usual week-offs, and **Inactive**, for a shift that is no longer used. They appear only once your company has the roster update.
* **Holidays added by the roster are protected:**
  * In **Setup Employee Wise Holidays**, deleting a week-off or holiday the roster added is skipped. The message says how many were kept, and to change them in Allocate Roster.
  * **Setup Multiple Holidays** will not allocate weekly-offs to an employee whose week-offs come from the roster, and names that employee.
  * **Copy Employee Holidays** copies only the holidays entered by hand.
* **Attendance follows the roster:** for a rostered employee, the [Attendance Register](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register.md), **attendance import** and the attendance app use the shift from their roster for that day, instead of the fixed shift on the employee's record. (A gate import keeps the shift recorded at the gate.)
* **Half-day week-offs are charged to leave:** when attendance is saved for a rostered half-day off, the off half is charged to casual or sick leave, in the order set on [Setup Week-off Patterns](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-week-off-patterns.md) (casual leave first, then sick leave, until you change it).
* [Attendance Register Month Wise](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register-month-wise.md) shows grey **W/O**, **HOL** or **H/O** on the empty days of rostered employees — a week-off, a holiday or a half-day off. They are shown only; nothing is saved from them.
* [Attendance Register](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register.md) shows **Update Holiday** on a day that is a roster week-off or holiday too, not only on a branch holiday.
* **Overtime with no minimum hours:** for an employee with no minimum hours per day, the length of the day's shift is now used as the minimum, so only the time worked beyond the shift counts as overtime. Overtime for these employees will be **lower than before — this is intended**. Employees with minimum hours set are not affected.
* **Attendance Register — search:** typing part of a name now matches whatever the capitals, and the list stays narrowed after **Refresh** or a change of **Sort On**. The employee list also fills faster.
* **Both attendance registers** check delete rights before asking whether to delete.

## On the web and on a phone

* Every new screen has a web page. On a phone, the larger screens show one part at a time, chosen with a switch.
* [Attendance Register](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register.md) on a phone has two tabs, **Employees** and **Attendance**. After you save, the next employee opens straight away.
* **Attendance Register Month Wise** on the web can now:
  * mark a whole block of employees and days at once,
  * take an employee's whole month when you click their **S.No.**, or everyone's with **Select all**,
  * open a menu with a right-click (or a long press on a phone).
* Time cells on the web open a list of times in 15-minute steps.

See [Using These Screens on the Web and Phone](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/shift-roster/using-these-screens-on-the-web-and-phone.md) for the full comparison.

## Corrections

These used to go wrong and now work as they should:

* **Attendance Register Month Wise:** a block that started before an employee's joining date marked none of that employee's days. Their days from the joining date on are now marked.
* **Attendance Register Month Wise:** employees who sorted to the same place — for example two with the same name — could have their rows mixed up or left out. Each now keeps their own row.
* **Attendance Register:** with a search typed in, ticked employees hidden by the search were left out when saving or deleting. They are now included with the rest.
* **Attendance Register on the web:** typing in the search box no longer jumps into the time grid.
* **Update Holiday** marked a holiday for employees of every branch on that date. It now marks only employees whose branch has the holiday.

## Before you use it

Your company must have the **roster update** that comes with this release. Ask your Logic ERP support team if you are not sure. Users who are not administrators need rights to the new menus in **User Access**.


---

# 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/shift-roster/whats-new-in-this-release.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.