> 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/licensable-features/guard-tours/creating-a-guard-tour-report.md).

# Creating a Guard Tour Report

### Introduction

The Guard Tour Report is a tool for reporting events and alarms that occur during each initiated Guard Tour. It shows:

* the time the guard reached each checkpoint,
* times taken between check points,
* any anomalies, (e.g. early or late arrival at a checkpoint, and arriving at a checkpoint out of sequence), and
* alarm acknowledgement and processing of alarms relevant to each Guard Tour.

This procedure describes how to create a Guard Tour Report.

**Notes:**

* A Guard Tour Report can be scheduled to run automatically at regular times (via a Macro). For further information refer to [Automatically Generated Reports](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports.md) and [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md).
* In a multi-server environment, for any given server where event aggregation is enabled, an operator can run a Guard Tour Report which incorporates events from remote guard tours. The Guard Tour Report can be filtered by remote guard tours.

### Site Configuration Report

A Guard Tour Site Configuration Report can be run to provide a printed list of checkpoints for a security guard to follow on a specific tour route and indicate expected times. The report can be run in a way that eliminates all other site configuration report data, and displays only the relevant Guard Tour details. For further detail see [Site Configuration Report](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/site-configuration-report.md).

### Procedure

1. Click **Reports** from the menu bar, then **Report Descriptions**.

   The **Report Description** List Window opens (in grid view).
2. **Right click** and select **New\...Guard Tour Report**.

   The **Reporting Dates and Times** page of the Guard Tour Report wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-62e1f3ee787013540c7d26b9c91bd6724a016db1%2Fguardtourreport_scrn1.png?alt=media)
3. This page allows 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.
4. Configure the period required for the report, and click the **Next** button.

   The **Select guards** page displays.

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

   This page provides a list of Cardholders (Guards) that may be included in the report. Cardholders shown here are restricted to those under the Division of the operator. The report will filter on the Cardholder (Guard) that performs the tour. All or multiple cardholders can be selected.
5. Select the Cardholders (Guards) you want to include.

   **Notes:**

   * The Find Tool may be used to locate guards, 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.
   * Should you wish to delete a Cardholder (Guard) or Access Group from your list on the right, **right click** on the item and click **Remove from List**.
6. Click the **Next** button.

   The **Select Guard Tours** page displays.

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

   This page provides a list of all the Guard Tours that may be included in the report. Guard Tours shown here are restricted to those under the Division of the operator. All or multiple Guard Tours can be selected.

   **Note:** In a multi-server environment, for any given remote server with event aggregation enabled, remote Guard Tours can be selected.
7. Select the Guard Tours you want to include.
8. If you want any events or alarms that the guard generates that are not related to the Guard Tour's checkpoints to be included in the report, check the **Include additional guard events generated during the tour** checkbox. When such events are reported on, they will be clearly separated and labelled "Additional guard events during tour".
9. Click the **Next** button.

   The **Select Operators** page displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c36715d0e1532d86148bebf26e47459c735b61cd%2Fguardtourreport_scrn4.png?alt=media)
10. This page provides a list of operators that initiate tours and may be included in the report. Operators shown here are restricted to those under the Division of the operator running the report.

    All or multiple operators can be selected. The report will be filtered by Guard Tours started by the selected operators.
11. Select the Operators you want to include, and click the **Next** button.

    The **Report Generation and Saving** page displays. 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.


---

# 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/licensable-features/guard-tours/creating-a-guard-tour-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.
