> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/users-and-access/labour-management/scheduled-vs-worked-report.md).
# Scheduled vs Worked Report
The Scheduled vs Worked Report displays information on who have clocked in and out within the selected week.
In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Workfoce > Scheduled vs Worked reports**.
Use the **arrows** beside the date range to move between weeks. Each column represents a day of the week, and each row shows a staff member’s recorded hours.
## Shift Duration
The report displays staff shift information such as:
* Scheduled hours
* Discrepancy between scheduled and total hours worked
* Total hours worked
{% hint style="info" %}
Shift data comes directly from:
* Shift schedule - [Roster](/users-and-access/labour-management/roster.md)
* Staff clock in/out and break records - [Staff Clock In and Clock Out](/pos/staff-clock-in-and-clock-out.md)
{% endhint %}
## Total Hours
The rightmost column displays each staff member's total hours for the selected week. A Total row at the bottom shows the combined hours for all staff for the day.
---
# 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://docs.bossithq.com/users-and-access/labour-management/scheduled-vs-worked-report.md?ask=&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.
