> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-analysis/transaction-cycle-per-employee.md).
# Transaction Cycle per employee
Maitre'D's transaction cycle per employee report shows you delay average in minutes for each stage of the meal by employees according to your specifications. From the report filter window, select the date and time range and employees to be included in the report.
The following is a sample of the transaction cycle per employee report:
**Table count:**
Number of tables served by this employee.
**Appetizers:**
Average delay between when the clients were seated and the appetizers were ordered.
**Main courses**
Average delay between when the appetizers and the main courses were ordered.
**Desserts:**
Average delay between when the main courses and the desserts were ordered.
**Total meal:**
Average delay between when the clients were seated and the desserts were ordered.
**Check print:**
Average delay between when the desserts were ordered and the checks were printed.
**Check Closing:**
Average delay between when the checks were printed and the checks were settled.
---
# 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://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-analysis/transaction-cycle-per-employee.md?ask=&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.