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

# Marking a visitor 'Temp Off-Site'

### Introduction

When a visitor checks-out temporarily at the reception the visitor will need to be marked temporarily off-site. The visitor can be marked back on-site at a later stage.

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

* set the visitor's status to 'Expected Back'
* remove the access card and access assigned to this visitor
* remove the escort assigned to this visitor

**Note:** The reception configuration determines if the **Temp Off-Site** button or **Temp Off-Site** Next Action button is displayed, or not.

### Procedure

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

**Note:** Only a visitor whose status is on-site can be marked temporarily off-site.

1. Select the visitor record on either the Visit or Home screens.
2. Click the **Temp Off-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-temp-off-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.
