> 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/the-home-screen/printing-a-visitor-status-report.md).

# Printing a Visitor Status report

### Description

The Visitor Status report records the information shown on the Home screen. You can print a separate report for each of the status tabs: 'Expected', 'On-Site', 'Departed' or 'Exceptions'. The Visitor Status report takes into account the filtering used on the Home screen.

You may want to print a Visitor Status report that records all visitors who are expected for the current day, or all visitors who are currently on-site.

To print a Visitor Status report, click the **Print Report** button located on the Home screen.

### The Visitor Status report

This report shows all visitors who are 'Expected' at the time the report was generated: 16/04/2012 at 13:02

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

**Notes:**

* The user who requested the report and the date and time the report was generated is displayed at the bottom.
* The information shown in the report is the same as the information shown on screen. If you require additional information to be shown in your report, refer to your Command Centre administrator, with regards to configuring different columns on the Home screen.


---

# 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/the-home-screen/printing-a-visitor-status-report.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.
