> 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/receptionist-functions/grace-period-and-overdue-alarm.md).

# Grace period and overdue alarm

### Introduction

This topic defines what the grace period and overdue alarm is and when they occur.

### Definitions

* **Grace Period**

  The grace period is the length of time (default 30 minutes) between when a visitor's status is set from 'Due to Leave' to 'Overdue'.

  Note: Your Command Centre administrator can configure, in Command Centre, a different grace period for each reception. If the grace period has been changed, this change will only affect newly created visits.
* **Overdue Alarm**

  When a visitor's status is set to 'Overdue' an alarm is raised in Command Centre.

IMPORTANT: A visitor must be marked off-site before the Command Centre Operator/Guard can process the alarm. Alternatively the visit details can be changed, (e.g. visit departure time) so that the visitor is no longer considered overdue.

### Example

**Situation:**

A visitor on a visit, has not checked-out and the departure time plus grace period has expired.

**Result:**

The following occurs:

* The visitor's status is set to 'Overdue' and an overdue alarm is raised.
* A copy of the visitor record is created on the 'Exceptions' status tab on the Home screen.
* If it has been configured in Command Centre, Hosts and Escorts will automatically receive a notification (via e-mail and/or sms message) that the visitor has become overdue, and the visit will have a notification icon next to it on the Home screen.

  **Note:** By hovering over the visit, a message displays indicating who has been automatically notified.


---

# 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/receptionist-functions/grace-period-and-overdue-alarm.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.