> 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-4-summary-report.md).

# Example 4: Summary Report

In this example, the raw data contains matched Entry and Exit Events that cross over midnight. The Cardholder works a morning shift on Monday, a night shift on Tuesday, an afternoon shift on Wednesday and Thursday, and has Friday off.

### Raw Data

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ca816480969da72858922ffe9c0826046b9eccd4%2Frawdata4.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:**   | Friday, 26 Jan 2007 23:59:59 |
| **Maximum In-Zone Time:**   | 20hrs                        |

### Report Output

The Cardholder has worked a total of 8 hours on Monday (lunch breaks are excluded).

On Tuesday the Cardholder starts a night shift at 11:00pm and clocks out for a break at 3:00 Wednesday morning, so the report shows this as a total of 4 hours for Tuesday.

The second half of the Tuesday night shift (Wednesday morning) is combined with the first half of the Wednesday night shift to give a total of 8 hours for Wednesday.

The second half of the Wednesday night shift (Thursday morning) is combined with the Thursday afternoon shift to give a total of 12 hours for Thursday.

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

### Comments

Because the Cardholder clocks out for mid-shift breaks, night shift hours are spread across different days – the first half of the shift being shown on one day and the second half of the shift being shown on the next. To get the entire Tuesday night shift to be included in Tuesday’s total, the Cardholder must not clock out between midnight and the end of the shift.

Note that if the Report End Date-Time had been set to Wednesday, 24 Jan 2007 00:00:00, then Tuesday’s Time Worked would only show 1 hour because the report would assume an exit at the Report End Date-Time.


---

# 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-4-summary-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.
