> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/faq/time-and-attendance.md).

# Time and Attendance

Time and attendance FAQs: give overtime without the full budgeted hours (working hour adjustment), what an extended day is, and why night shifts with a break around midnight stay one shift.

## How can I assign overtime to an employee without designating the entire budgeted hours?

Overtime refers to hours worked beyond the initially budgeted hours. In the scenario where an employee's standard daily work time is 9 hours, overtime hours are only assigned if the employee works beyond the 9-hour mark on that specific day. Overtime on a day depends on the total hours against the budget hours, not on the time of day the hours were worked. The one exception is flex on a **Start & End Times** shift, which can ignore a few minutes before the shift starts or after it ends. See [Normal hours, overtime and short time](https://help.allwage.com/modules/time-and-attendance/how-hours-are-calculated.md#normal-hours-overtime-and-short-time).

To allocate overtime for the employee while not necessitating the full budgeted hours, you can implement a working hour adjustment to reduce the total budgeted hours. For instance, if the employee's standard workday is set at 9 hours (budgeted hours = 9), but you wish to allocate 7 regular hours and 2 overtime hours, you can apply a working hour adjustment to shorten the duration of the shift.

## What is an extended day?

In AllWage, each day runs from midnight to midnight, which makes it easy to spot issues like missed clock-ins or clock-outs. The challenge is shifts that cross over into a new day — for example a night shift.

When an employee clocks in before midnight and works straight through into the next morning (for example, clocking in at 18:00 and clocking out at 05:00 the next day), AllWage keeps the whole stretch together as one shift on the day it started. This is called an **extended day**. Instead of showing an error, the system calculates the total hours across the two calendar days, and flags the shift as "Extended Day" on both the Employee Overview report and the dashboard.

For the full explanation — including how the day boundary works, why we don't shift the day for night-shift workers, and how breaks around midnight are handled — see [Night Shifts & Extended Days](https://help.allwage.com/modules/time-and-attendance/night-shifts-and-extended-days.md).

## Why is my employee's night shift no longer split into two days?

If a night-shift employee clocks out and back in for a short break around midnight, AllWage now keeps the whole night together as **one shift on the day it started**, rather than splitting it into two separate days.

This applies whether the break is taken after midnight, or straddles midnight (the employee clocks out before 00:00 and back in after 00:00 — common for teams working to an overseas time zone). As long as the employee clocks back in within 120 minutes, it's treated as a break in the same shift, with the break time excluded from worked hours. A longer gap still ends the shift and starts a new day.

For details and examples, see [Night Shifts & Extended Days](https://help.allwage.com/modules/time-and-attendance/night-shifts-and-extended-days.md#night-shift-breaks-around-midnight).


---

# 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://help.allwage.com/faq/time-and-attendance.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.
