> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/kot-audit.md).
# KOT Audit
The **KOT Audit Report** is used to track and review Kitchen Order Ticket (KOT) activities in detail. It provides a complete history of KOT transactions, including created, amended, and cancelled orders.
* This report helps in monitoring kitchen operations and order accuracy.
## Steps to View KOT Audit Report
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **KOT Audit**.
* The KOT Audit Report screen will open.
Step 2: Choose the required **additional options** that you want to include in the report.
1. If needed, apply **sorting options** to organize the data as required.
* These options help customize the report for better analysis.
Step 3: Generate the Report
1. After selecting all required options, click on the **Display** button.
2. The system will generate and display the **KOT Audit Report**.
* The report will show detailed KOT information, including created, amended, and cancelled entries.
---
# 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.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/kot-audit.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.
