> 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/dineplan/front-desk/report.md).

# Report

## Overview

The Reports section provides access to different types of reports available in DinePlan. It allows users to review and analyze information related to restaurant operations, sales, transactions, items, tickets, and other business activities.

Reports are organized into different categories, making it easier for users to locate the required report based on the type of information they want to review. Each category contains reports related to a specific area of restaurant operations.

The available report categories are:

* [**General**](/dineplan/front-desk/report/general-reports.md) – Contains reports covering general restaurant and operational information.
* [**Day Shift**](/dineplan/front-desk/report/day-shift-reports.md) – Provides reports related to day and shift-based activities.
* [**Item**](/dineplan/front-desk/report/item-reports.md) – Contains reports related to items and their transactional information.
* [**Ticket**](/dineplan/front-desk/report/ticket-reports.md) – Provides reports related to tickets and ticket transactions.
* [**Group**](/dineplan/front-desk/report/group-reports.md) – Contains reports organized based on configured groups.
* [**Entity**](/dineplan/front-desk/report/entity-reports.md) – Provides reports based on configured entities.
* [**Member**](/dineplan/front-desk/report/member-reports.md) – Contains reports related to members and their activities.
* [**Summary**](/dineplan/front-desk/report/summary-reports.md) – Provides summarized information for reviewing overall activities and transactions.
* [**Custom**](/dineplan/front-desk/report/custom-reports.md) – Provides access to customized reports configured according to specific requirements.

The Reports section helps users review restaurant activities, monitor transactions, and access relevant business information from a centralized location.

## Accessing Reports

To access the Reports section:

**Dashboard → Front Desk → Report**

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-e8932ff2177d9f4b34c5bb9e426709e6479698ab%2Fimage%20(165).png?alt=media" alt=""><figcaption></figcaption></figure>

After selecting “Report”, the Report screen opens with the available report categories. Users can select the required category and then choose the appropriate report to view the relevant information.


---

# 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/dineplan/front-desk/report.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.
