> 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/site-management/reports/automatically-generated-reports.md).

# Automatically Generated Reports

### Introduction

The following three reports can be set to generate automatically:

**Note:** There are a number of ways these reports can be scheduled to generate automatically. For examples, refer to [Configuring Report Scheduling](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-report-scheduling.md).

<table><thead><tr><th width="384">Report type</th><th>Purpose</th></tr></thead><tbody><tr><td>Evacuation Report (referred to as an 'Auto-Evacuation' Report)</td><td>Used in emergency type situations,<br>(e.g. fire evacuation).</td></tr><tr><td>Exception Report</td><td>Used mostly for information purposes,<br>(e.g. doors currently unlocked which were scheduled to be secure).</td></tr><tr><td>Activity Report</td><td>Used mostly for information purposes,<br>(e.g. alarms occurring over the last 8 hours).</td></tr></tbody></table>

These reports are supported by macros so they can be generated automatically when a specific system event occurs, (e.g. a fire alarm in the case of an Evacuation Report). They are triggered by an event or alarm. To achieve automatic generation of one of these reports, a macro which executes the report must be able to be initiated from an Action Plan. Using the macro scheduling feature, these reports can be set up to run automatically on a scheduled basis, (e.g. every 8 hours at a shift change, to present to the next guard).

**Note:** These reports can only print to printers that are on the same domain as the server. To print from a workstation, the workstation user needs privileges to that printer. See [Configuring Printers for Reports automatically generated via Macros](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-printers-for-reports-automatically-generated-via-macros.md) for further detail.

When a macro initiates one of these reports, and the report is configured to send the report to "Print Preview", the report will fail as there is no operator to view the print preview or to send the report to a printer. When a macro initiates a report, and the report is configured to send the report to a file on a local drive, the report is placed on the Command Centre Server's local drive rather than the local drive of the operator running the macro. This is due to there not always being an operator currently logged on and hence the local workstation drive may not be available.

When an automatically generated report is triggered by an alarm, if the server is offline at the time, the report will be produced once the server comes back online. However, if the report is included in a scheduled macro, after one minute the action will be cancelled and the report will not be produced.

### Auto-Generated Report Events

When an automatically generated report is run, an event is generated indicating it has run. Also receiving a "Report Completed" event indicates that the report has been spooled to the printer. If this event is **not** generated, it may be because the printer setup is incorrect.

If printing fails it will be for one of the following reasons:

<table><thead><tr><th width="390">Reason</th><th>Result</th></tr></thead><tbody><tr><td>The report description is configured with an unknown printer</td><td>An alarm will generate with details of the unknown printer.</td></tr><tr><td>The printer is offline or out of paper</td><td>An event will not generate, as Command Centre will not know.</td></tr></tbody></table>

### In This Section

* [Configuring Report Scheduling](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-report-scheduling.md)
* [Configuring Printers for Reports automatically generated via Macros](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-printers-for-reports-automatically-generated-via-macros.md)


---

# 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/site-management/reports/automatically-generated-reports.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.
