> 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/command-centre-client/quick-tips-for-configuring-the-report-date-and-time-filter.md).

# Quick Tips for configuring the 'Report Date and Time' filter

* When creating a Time Report, by default the **Report Date and Time** filter is already added. You can edit this instance of this filter condition, but will not be able to add another instance of it.
* This filter allows an operator to select the time period for the report. The time control mimics the 'Event Occurrence Time' filter regards the Report Period and Start and End Dates.
* **Report Period:**

The ‘Report Period’ controls allow you 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. Only events that occurred within this period are included in the report.

* **Filter Days:**

The 'Filter Days' control can be used to report on specific days of the week. Selecting a specific day restricts the report by determining time on site to be bound by 00:00 to 24:00 for that day.

* **Time Filter Options:**

This filter includes three ways of handling entry or exit events that fall outside of expected times: Daily Time Ranges, Ignore Midnight Boundary, and Use Shifts (requires licence).

* **Daily Time Ranges:** An 'Earliest Daily Entry Time (EDET)' control which defaults to 00:00 (midnight), and a 'Latest Daily Exit Time (LDET)' control which defaults to the following midnight; 24:00. If an entry event occurred before the EDET, it is reported as having occurred at the EDET. Similarly, if an exit event occurred after the LDET, it is reported as having occurred at the LDET. If the working period crosses midnight, you can set the EDET to be later (e.g. 22:00) than the LDET (e.g. 06:00).
* **Ignore Midnight Boundary:** With this option selected, there are no ‘Daily Time Ranges’. That is, the report will not “assume” that any entry or exit event occurred at midnight or the EDET/LDET time. If an event is missing, other exceptions (e.g. EE, XX, E\_START, E\_END) are used to “assume” the event time.
* **Use Shifts:** This option only displays if you are licensed for the ‘Shifts’ feature. If ‘Use Shifts’ is selected, specific Shifts can be added. The Report will only include events for Cardholders who were, for all or part of the Report Period, assigned to one of the added Shifts. If no Shifts are added, events for Cardholders who were assigned to any Shift are included.

  For any entry event that is missing or occurred outside the Report Period, the entry time is reported as the Start Time of the Cardholder’s Shift, with an ENF\_SS exception. For any exit event that is missing or occurred outside the Report Period, the exit time is reported as the End Time of the Cardholder’s Shift, with an XNF\_SF exception.

  **Record early entry at shift start time:** If selected, where an entry event occurs before the start of the Shift (but still within the Report Period), the Cardholder is reported as having entered at the ‘Start Time’ of their Shift, with an E\_SS exception. If not selected, the true (early) entry time is reported.

  **Record late exit at shift end time:** If selected, where an exit event occurs after the end of the Shift (but still within the Report Period), the Cardholder is reported as having exited at the ‘End Time’ of their Shift, with an X\_SF exception. If not selected, the true (late) exit time is reported. Note: This option can result in exit events being reported as much earlier than they really were.
* **Maximum Time on Site:**

  The 'Maximum Time on Site' control (default is 12:00, unchecked) allows you to set a maximum reportable ‘Time on Site’ time. If set, the report will display the hours worked at this maximum time for any Cardholder that is in the zone for any time at or exceeding this limit.

When ‘Maximum Time on Site’ is set, and the ‘Display only First Entry and Last Exit’ (on the ‘Entry and Exit Readers’ filter) is not set, the maximum time will relate to each entry/exit pair (detailed).

When Maximum Time on Site is set with Display only First Entry and Last Exit also set, the maximum time will relate to the sum of the entry/exit pairs (summary).

* Checking the **Allow change when report is run** checkbox allows the filter to be edited at runtime.


---

# 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/command-centre-client/quick-tips-for-configuring-the-report-date-and-time-filter.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.
