> 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/running-a-guard-tour.md).

# Running a Guard Tour

### Introduction

A previously configured Guard Tour can be selected by an appropriately privileged operator, assigned to a guard and started at any checkpoint in the tour.

This procedure describes how operators with the "Manage Guard Tours" privilege can start, stop and restart a Guard Tour.

**Notes:**

* The "Manage Guard Tours" privilege also includes the "View Guard Tours" privilege, which allows operators to view the details of a Guard Tour.
* A Macro item can be used to trigger Guard Tours actions, (e.g. a macro can be used to start more than one Guard Tour item at once, or stop them at once). See [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md) for further detail.

### Procedure

#### Starting a Guard Tour

1. Click **Monitor** from the menu bar, then **Guard Tours**.

   The **Guard Tour** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the Guard Tour you want to run, and select **Start Tour...** from the drop-down menu.

   The **Status and Overrides** tab of the Guard Tour properties displays, with the Status *"Tour not running"*.
3. Select the guard that is responsible for performing the tour from the **Guard** drop-down list.

   The **Start Tour** button becomes enabled.

   **Notes:**

   * The **Guard** drop-down list is populated with all cardholders viewable to the operator and belonging to the Access Group assigned to the tour on the **Checkpoints** tab.
   * If the guard you select is already allocated to another Guard Tour, they will not be able to be allocated to this tour whilst the original tour is in progress.
4. Select the checkpoint you want the tour to start at from the **First checkpoint** drop-down list.

   **Note:** The **First checkpoint** drop-down list is populated with all the checkpoints for the tour in order. It is updated to the current checkpoint each time a checkpoint is reached during the tour, and is reset back to the first checkpoint upon the tour completing. Thus if the tour is halted for some reason, an operator can simply click the **Start Tour** button to resume the tour from the checkpoint it was last up to.
5. Click the **Start Tour** button.

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

   The Status changes to *"Tour running for \[Guard name]"*, and all the checkpoints on the tour display in sequence, with updates occurring dynamically as each checkpoint is reached, including the due and when appropriate overdue status of the next checkpoint. The appropriate update to the Status column occurs as follows:

   <table><thead><tr><th width="108">Status column</th><th>Description</th></tr></thead><tbody><tr><td>-</td><td>For checkpoints that are after the current checkpoint.</td></tr><tr><td>Not due</td><td>For the current checkpoint when the expected minus deviation time has not been reached yet.</td></tr><tr><td>Due</td><td>For the current checkpoint when the current time is between the expected time plus or minus the deviation time, (i.e. in the time range specified in the <strong>Expected time</strong> column).</td></tr><tr><td>Overdue</td><td>For the current checkpoint when the expected plus deviation time has been exceeded.</td></tr><tr><td>Halted</td><td><p>When the tour was aborted at this checkpoint. The tour was either:</p><ul><li>manually stopped,</li><li>the guard did not arrive, or</li><li>the guard arrived at the wrong checkpoint.</li></ul></td></tr><tr><td>Early</td><td>When the guard arrived early to this checkpoint.</td></tr><tr><td>On Time</td><td>When the guard arrived on time to this checkpoint, (i.e. in the time range specified in the <strong>Expected time</strong> column).</td></tr><tr><td>Late</td><td>When the guard arrived late to this checkpoint.</td></tr></tbody></table>

#### Stopping a Guard Tour

Perform the following steps to manually stop a Guard Tour that is "In Progress" from a workstation:

**Note:** As well as an operator being able to stop ("Halt") a tour, they can also be stopped due to an alarm.

1. Do you already have the Guard Tour properties open on the **Status and Overrides** tab?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>go to Step 2.</td></tr><tr><td>no</td><td><ol><li>From the <strong>Guard Tour</strong> List Window, <strong>right click</strong> on the Guard Tour you want to run.</li><li><p>Select <strong>Stop Tour...</strong> from the drop-down menu.</p><p>The <strong>Status and Overrides</strong> tab of the Guard Tour properties displays, with the Status <em>"Tour running for [Guard name]".</em></p></li></ol></td></tr></tbody></table>
2. Click the **Stop Tour** button.

   A "Stop Tour" dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a6952e836ff1197e6a7595421e6065e22d66ed6b%2Fstoptour_dialog.png?alt=media)
3. Do you want to enter a reason for stopping the tour?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>click the <strong>OK</strong> button.</td></tr><tr><td>yes</td><td><p>enter the reason (up to 200 characters) and click the <strong>OK</strong> button.</p><p>This message will be logged as part of the event generated to record your action.</p></td></tr></tbody></table>

   The Status changes to *"Tour Halted"* and the "current" checkpoint changes to red text.

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

#### Restarting a Guard Tour

Perform the following steps to restart a Guard Tour in the "Halted" state:

**Note:** It can be restarted from the "current" checkpoint, (i.e. the one that has the "Halted" state), or from any other checkpoint including the first checkpoint.

1. Do you already have the Guard Tour properties open on the **Status and Overrides** tab?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>go to Step 2.</td></tr><tr><td>no</td><td><ol><li>From the <strong>Guard Tour</strong> List Window, <strong>right click</strong> on the Guard Tour you want to restart.</li><li><p>Select <strong>Start Tour...</strong> from the drop-down menu.</p><p>The <strong>Status and Overrides</strong> tab of the Guard Tour properties displays, with the Status <em>"Tour Halted".</em></p></li></ol></td></tr></tbody></table>
2. Select any checkpoint as the "First checkpoint" to restart the tour, from the **First checkpoint** drop-down list.
3. Click the **Start Tour** button.

   The Status changes back to *"Tour running for \[Guard name]"*, and updates start occurring again for all the checkpoints on the tour as they are reached.


---

# 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/running-a-guard-tour.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.
