> 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/working-examples/example-1-maximum-in-zone-time-detail-report.md).

# Example 1: Maximum In-Zone Time (Detail Report)

In this example, the raw data contains an Entry Event and Exit Event that would result in an invalid Attendance Record. The Cardholder has tailgated out after work on Monday and tailgated back in on Tuesday morning.

### Raw Data

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

### Report Scenario 1

In this scenario we use the above raw data and set the following values when running the report.

| **Report Start Date-Time:** | Monday, 22 Jan 2007 00:00:00  |
| --------------------------- | ----------------------------- |
| **Report End Date-Time:**   | Tuesday, 23 Jan 2007 23:59:59 |
| **Maximum In-Zone Time:**   | 24hrs                         |

### Report Output

The Entry Event at 1:00pm on Monday is matched with the Exit Event at 12:30pm on Tuesday and an Attendance Record is created for 23.5hrs. This is treated as a valid record because its length is less than the Maximum In-Zone Time setting of 24hrs.

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

### Report Scenario 2

In this scenario we use the same raw data but reduce the Maximum In-Zone Time setting to 20hrs.

| **Report Start Date-Time:** | Monday, 22 Jan 2007 00:00:00  |
| --------------------------- | ----------------------------- |
| **Report End Date-Time:**   | Tuesday, 23 Jan 2007 23:59:59 |
| **Maximum In-Zone Time:**   | 20hrs                         |

### Report Output

Now the Entry Event at 1:00pm on Monday is not matched with the Exit Event at 12:30pm on Tuesday because the resulting Attendance Record would be invalid because its length (23.5hrs) would exceed the Maximum In-Zone Time setting of 20hrs. Instead, these events are displayed showing “Insufficient Data”.

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


---

# 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/working-examples/example-1-maximum-in-zone-time-detail-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.
