> 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/pos-reports-2/faq-on-reports/how-do-i-use-pending-kot.md).

# How do I use Pending KOT?

The Pending KOT report is used to track Kitchen Order Tickets (KOT) that have been created but have not yet been processed for billing. Each entry in this report shows the specific food items punched for that KOT.To use the Pending KOT report, follow these steps:

1. **Navigate to the Report:** Go to the Reports menu and select Pending KOT.
2. **Apply Filters:** Select the required date, outlet, and session.
3. **Generate the View:** Click the display icon to load the report.

**Additional Features and Options**

* **Serve Instructions:** You can tick a specific checkbox to see if serve instructions were added to the KOT.
* **Printing:** The report can be printed directly by clicking the print icon.
* **Exporting:** You can convert and save the report into an Excel format by clicking the corresponding icon


---

# 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/pos-reports-2/faq-on-reports/how-do-i-use-pending-kot.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.