> 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-3-missing-entry-or-exit-events-detail-report.md).

# Example 3: Missing Entry or Exit events (Detail Report)

In this example, the raw data contains multiple consecutive Entry Events as well as multiple consecutive Exit Events. On Monday the Cardholder has tailgated out to lunch. On Tuesday the Cardholder has tailgated back in after lunch.

### Raw Data

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fe29c7aa054c20d3b475861b7ae339f161912764%2Frawdata3.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 first Entry Event is unusable because its subsequent event is not an Exit Event, so no Attendance Record is created. The event is displayed showing “Insufficient Data”.

Similarly, the last Exit Event is unusable because its previous event is not an Entry Event, so no Attendance Record is created. The event is displayed showing “Insufficient Data”.

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

### Comments

In this example, extending the Report Time-Frame to start earlier and/or end later, will not affect the output of the report because the Report Start and End Date-Times are not being used to create any Attendance Records.


---

# 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-3-missing-entry-or-exit-events-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.
