> 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/integrations/reporting-and-notifications/t-and-a-database-export-utilities.md).

# Time and Attendance Database EXPORT Utilities

**T\&A Database Export** utilities add a table to the Command Centre SQL database, letting a client retrieve **Time and Attendance (T\&A)** data for a specified time period. Several variants exist for different customer needs.

## Retrievable data

* Cardholder Name
* Cardholder Division
* Entry Reader Name
* Entry Reader Time
* Exit Reader Name
* Exit Reader Time
* Total time **"in-zone"** for a single entry/exit combination
* A Personal Data Field (for example "Grid ID")

Additional data can be retrieved by modifying the SQL query. See the release notes for examples.

> **Notes:** each run **replaces** the previous dataset (for the configured time period) rather than appending. The utility can be **scheduled** to run automatically at an interval, or run **manually**.

If the available variants do not fit, contact Professional Services for a quote.

## Versions

Supported in **v7.90** and **v8.20**.

***

🔗 **Related**

* [Mantrack CSV Export](/knowledge-hub/products/integrations/reporting-and-notifications/mantrack-csv-export.md). A related cardholder-event export utility.


---

# 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/integrations/reporting-and-notifications/t-and-a-database-export-utilities.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.