> 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/visitor-management/using-visitor-management/receptionist-functions/performing-visitor-actions/marking-a-visitor-on-site.md).

# Marking a visitor 'On-Site'

### Introduction

When a visitor checks-in at the reception the visitor will need to be marked on-site.

Before a visitor can be marked on-site, the reception may require one or all of the following actions to be carried out:

* print badge
* assign access card
* assign escort
* capture biometrics

**Note:** The availability of these actions may vary depending on the configuration of your system in Command Centre.

When a visitor is successfully marked on-site the system will:

* check that all mandatory visitor details have been entered, for this visitor
* check that all mandatory actions have been performed, for this visitor
* set the visitor’s status to on-site
* move the visitor's record to the 'On-Site' status tab
* set the visitor's visit status to ‘Visit In Progress’
* assign site access to the visit, if access groups have been selected for the visit
* if the site is licensed for the 'Visit count' feature, the visit count for this visitor will be incremented when they are marked on-site for the first time per visit.

  **Notes:**

  * The 'Visit counting' thresholds are configured on the **Advanced** tab of the Command Centre Server Properties.
  * Events are generated in Command Centre, and prompts appear in Visitor Management when thresholds, (i.e. Warning, Alert and Denial Thresholds), are already met. *For example:*

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

### Procedure

To mark a visitor on-site, complete the following procedure:

**Note:** Only a visitor whose status is 'Expected', 'Expected Back' or 'Signed In' can be marked on-site.

1. Select the visitor record on either the Visit or Home screens.
2. Click the **Mark On-Site** action button.

   **Notes:**

   * When the first visitor on a visit is marked on-site, the arrival time for the visit is changed to the marked on-site time.
   * You can mark multiple visitors on-site at the same time.
   * You cannot mark a visitor on-site after the departing date and time of their visit.
   * In the event that a mandatory action has not been completed, the visitor will not be marked on-site and an appropriate error message displays.


---

# 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/visitor-management/using-visitor-management/receptionist-functions/performing-visitor-actions/marking-a-visitor-on-site.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.
