> 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/preparation-speed.md).
# Preparation Speed
Maitre'D's preparation speed report shows you a summary of the order preparation speed of your employees according to your specifications. From the report filter window, select the dates, Revenue Centers and modes to be included in the report.
The following is a sample of the preparation speed report:
For each CVM in each Revenue Center and each mode, this report provides you with:
**under 30:**
Number of orders when the delay between when the orders were entered and the items were prepared was less then 30 seconds.
**30 to 60:**
Number of orders when the delay between when the orders were entered and the items were prepared was between 30 seconds and 1 minute.
**60 to 120:**
Number of orders when the delay between when the orders were entered and the items were prepared was between 1 and 2 minutes.
**over 120:**
Number of orders when the delay between when the orders were entered and the items were prepared was more then 2 minutes.
---
# 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/preparation-speed.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.