> 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-off-site-leave-site.md).

# Marking a visitor 'Off-Site' (Leave Site)

### Introduction

When a visitor leaves, having completed their visit, they need to be marked off-site. There are two ways that this can be achieved, as follows:

1. The Receptionist can manually record them as having left the site, or
2. If visitor access cards are used, the Visitor or the Receptionist can badge the card at a designated exit reader, which triggers the system to automatically complete the leave site process.

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

* set the visitor's status to ‘Departed’
* move the visitor's record to the 'Departed' status tab
* remove the access card and access assigned to this visitor
* remove the escort assigned to this visitor
* set the visit status to 'Completed' if the visitor is the last person remaining on the visit

**Note:** The visitor’s status cannot be changed once marked off-site.

### Procedure

This procedure describes how a Receptionist manually marks a visitor off-site in Visitor Management:

1. Select the visitor record, on either the Visit or Home screens.
2. Click the **Leave Site** action button.

   **Note:** The visitor should return their access card, if issued to the reception.


---

# 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-off-site-leave-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.
