> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report.md).

# Time and Attendance Report

### Introduction

The Time and Attendance Report provides the ability to track hours worked by individual Cardholders. Door entry and exit events are used in the system to calculate hours worked by individual Cardholders. In general, a Door entry event is equated to a Cardholder clocking in or starting work, while a Door exit event equates to a Cardholder clocking out or ending work.

Operators must have the "View Cardholders", "Edit Report Descriptions" and "View Site" privileges to create, save, edit and delete Time and Attendance Reports. "View Site" privilege is required to see the readers used for the Time and Attendance Report.

**Note:** In a multi-server environment, for any given server where event aggregation is enabled, an operator can run a Time and Attendance Report which incorporates events from remote readers. The Time and Attendance Report can be filtered by remote readers.

***

### Report Wizard

The Time and Attendance Report wizard contains a number of pages which prompt you to enter certain information to create a report.

**Follow the instructions displayed**.

<details>

<summary>Report Style page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7ca33026d2c86a00f89b05b139d1d9ba0454cf82%2Ft%26a1.png?alt=media)

This is the first page of the Time and Attendance Report wizard. It allows the operator to choose between a **Detail** or **Summary** Time and Attendance Report, an **Exception Report** or an **Absentee Report**.

**Detail Reports** show the hours worked by selected Cardholders over the time period defined. They show every time a Cardholder clocked in or out during the reporting period, with a total of hours worked between each pair of clock in and out events.

**Summary Reports** also show the hours worked by each Cardholder, but summarises this information on a daily basis. They show the first time a Cardholder clocked in for work and the last time they clocked out at the end of the day, with a total of actual hours worked between these times.

Detail Reports can have two entries for the one day - one that has insufficient data and one that is real, (e.g. a Cardholder badged their card at an entry reader and opened the door, but then decided not to enter. Ten minutes later the same Cardholder enters again at the same entry reader and exits eight hours later). In the Detail Report the time would all be added up correctly, but in a Summary Report it would note that day as having insufficient data.

If you run a Summary Report and get insufficient data for a Cardholder, run a Detail Report for that Cardholder.

**Note:**

It is recommended that if you run a Summary Report, you should also run an Exception Report. This is due to a Summary Report output giving no indication as to whether or not the report contains unusable events, whereas an Exception Report identifies any unusable events.

**Exception Reports** provide analysis of events that affect accurate time and attendance reporting, (e.g. a Cardholder may forget to clock out at the end of the day or present their card more than once when starting or leaving work). Accurate event information is critical to calculating hours worked for each Cardholder, and this allows you to identify incorrect events when a Cardholder's worked hours cannot be calculated or are excessive.

**Absentee Reports** provide information regarding days that a Cardholder did not work. They determine that a Cardholder was absent on a particular day if there were no clock in or out events.

**Note:**

You need to configure an absentee report to exclude weekends and/or other days that a Cardholder is not expected to work.

</details>

<details>

<summary>Report Format and Filter page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c35e9a7adc788d071e531594229aae37b80c3bf5%2Ft%26a2.png?alt=media)

This page allows the operator to set two options as follows:

* A string or numeric **Personal Data Field** can be selected for display in the report.
* The operator can sort the report by **Cardholder** name or **Personal Data Field**, with an optional top level sort by **Division**.

</details>

<details>

<summary>Select Cardholders and Operators page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-495568be1d2159a09cc99a09011474f19d48fee6%2Ft%26a3.png?alt=media)

This page provides a list of Cardholders that an operator may include in the report. Cardholders shown here are restricted to those under the Division of the operator.

The Find Tool may be used to locate Cardholders, which can then be dragged and dropped onto this page. Alternatively, you can open the **Access Group** List Window and drag and drop those Access Groups you require onto this page.

**Note:**

Only cardholders that are currently active within an Access Group will be reported on. Therefore, if you want the report to include 'expired' Access Group members, you need to select cardholders rather than Access Groups.

The "Automatic removal of expired members" from Access Groups will alter the information in the report depending on when the report is run.

If an operator selects the **All Cardholders** option, then the report is run for all Cardholders under the current operator's Division.

Should you wish to delete a Cardholder from your list on the right, **right click** on the Cardholder and click **Remove from List**.

</details>

<details>

<summary>Time Clocks page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6159c259102f0f2aeb29bda543ca34767b98b17c%2Ft%26a4.png?alt=media)

This page provides a list of available Time Clocks or readers, from which an operator can select those to include in the report. The operator must also indicate if they are using combined or separate entry and exit Time Clocks (see explanations below), and adjust the Grace Time for duplicate events if required.

**Separate entry and exit time clocks:** One reader/clock for entry and another reader/clock for exit.

**Combined entry and exit time clocks:** A cardholder can swipe their card at any reader (entry or exit), and the FIRST read/badge is taken as the "Entry" read and the NEXT read/badge is taken as the "Exit" read for that cardholder. The system also does not check that the entry or exit was actually taken, as some sites just use the readers as time clocks, so they are not attached to doors at all.

</details>

<details>

<summary>Reporting Dates and Times page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-06fe9a08df72d6e4244b37c32e7a7c4a53b22988%2Ft%26a5.png?alt=media)

This page allows an operator to enter a start and end time for the report. Pre-defined periods are provided for simplicity, or custom start and end times can be entered.

</details>

<details>

<summary>Shift Pattern Options page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a47b1f5071634f8a26aec592a21430b3058d6b9b%2Ft%26a7.png?alt=media)

This page provides an operator options for determining what rules will be applied when calculating Attendance records for the report. It only displays if **Detail**, **Summary** or **Exception Report** was selected on the first page of the wizard, (i.e. the 'Report Style' page). It will not display if **Absentee Report** is selected.

If you click the **Define Day Boundaries to match Shift Pattern** radio button, and then the **Next** button, the 'Day of Week' page displays.

If you click the **Ignore Shift Patterns** radio button, and then the **Next** button, the 'Report Generation and Saving' page displays (skipping the 'Day of Week' page). The Ignore Shift Patterns option determines the appropriate report output using the Flexible Shift Pattern rules, and when selected also enables the **Maximum In-Zone time** field which is used by the Flexible Shift Pattern rules. The figure entered in this field determines the time span after which a cardholder has exited without badging their card. See [Flexible Shift Pattern rules](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report/flexible-shift-pattern-rules.md) for a full explanation of these rules, and [Working Examples](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report/working-examples.md) to help explain how this option works.

</details>

<details>

<summary>Day of Week page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5e1c33a4c5bba7057dca9fe3584414e78855dd7f%2Ft%26a6.png?alt=media)

This page allows time restrictions to be applied within the overall reporting period. It only displays if **Absentee Report** was selected on the first page of the wizard, (i.e. the 'Report Style' page), or if the **Define Day Boundaries to match Shift Pattern** radio button was selected on the 'Shift Pattern Options' page.

Individual days of the week can be excluded from the report, or alternatively the report may be restricted to a specific time slice in specific days of the week. The operator can also adjust the day start time to accommodate night shift workers, (i.e. move the concept of midnight).

</details>

<details>

<summary>Report Generation and Saving page</summary>

This wizard page is the same for all report types, and provides the same options. Refer to [Report Generation and Saving](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md) in the *Creating a new report* procedure for further detail.

</details>

### In This Section

* [Flexible Shift Pattern rules](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report/flexible-shift-pattern-rules.md)
* [Working Examples](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report/working-examples.md)


---

# 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.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/time-and-attendance-report.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.
