> 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/products/cc-software/operate/visitor-management-client/pre-registration-and-receptionist-functions/the-visit-screen/visit-status.md).

# Visit status

The visit status is shown in the top left corner of the Visit screen.

This table describes each visit status.

<table><thead><tr><th width="162">Visit status</th><th>Description</th></tr></thead><tbody><tr><td>New Visit</td><td>The visit is being created.</td></tr><tr><td>Visit Scheduled</td><td>The visit has been saved but no visitors have been marked on-site.</td></tr><tr><td>Visit In Progress</td><td>At least one visitor has been marked on-site.</td></tr><tr><td>Visit Completed</td><td>All visitors have been marked off-site or cancelled.</td></tr><tr><td>Visit Cancelled</td><td>The visit has been cancelled.</td></tr></tbody></table>

**Note:** In the event that some visitors on a visit have not arrived before the last on-site visitor has been marked off-site, it is assumed the remaining visitors won't be coming.

If it is assumed the remaining visitors won't be coming the visit status will be set to 'Completed' and the expected visitors 'Cancelled'. However, if one of the expected visitors has been assigned an access card the visit status will remain 'In Progress'.


---

# 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/products/cc-software/operate/visitor-management-client/pre-registration-and-receptionist-functions/the-visit-screen/visit-status.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.