> 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/workday/about-work-day.md).

# About Work Day

## **Overview** <a href="#about-sold-out" id="about-sold-out"></a>

The Workday module is used to manage the restaurant's daily operational cycle in DinePlan. It enables authorized users to start and end the business day while controlling access to key operational modules such as POS and Tickets.

A Workday must be started before the restaurant can begin accepting customer orders or processing transactions. Once the Workday is active, a Work Shift must be started on every terminal that accepts payments before transactions can be processed.

In addition to managing the business day, the Workday module allows users to:

* Start and end Work Shifts.
* Record opening and closing cash amounts.
* Synchronize data with Dine Connect.
* Enable or disable Training Mode.
* Print Workday and Work Shift information.
* Complete the end-of-day process after validating open tickets.

**Important**

Before the Workday and Work Shift are started, the POS and Tickets modules remain unavailable. Start the Workday first, followed by a Work Shift on each payment terminal to enable restaurant operations.

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

**Note**

* A restaurant can have multiple POS terminals.
* A Workday can be started from any terminal.
* Every payment terminal must have its own active Work Shift before transactions can be processed.

## **Workflow** <a href="#workflow" id="workflow"></a>

The following workflow illustrates the key steps involved in starting, operating, and closing the Workday and Work Shift.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-5f65ad07f70cbbb40da7597d2e7c58075686d8a4%2FChatGPT%20Image%20Aug%2031%2C%202026%2C%2006_38_54%20PM-20260831-130857.png?alt=media" alt=""><figcaption></figcaption></figure>

## **Workday** <a href="#open-workday" id="open-workday"></a>

The Workday module can be accessed from the DinePlan Home screen. Users with the required permissions can open the module to start or end the business day, manage Work Shifts, and perform Workday-related administrative functions.

### **Access Workday** <a href="#steps-to-open-workday" id="steps-to-open-workday"></a>

1. Log in to “DinePlan” using your credentials.
2. Navigate to the “Home” screen.

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

2. Click “Workday”.

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

3. The “Workday” screen opens.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-36c5adef2da76c519d9653ed0a70b927961498ec%2F1.1.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Workday** screen provides the options required to manage the business day and its associated Work Shifts. Once the Workday screen is opened, users can start the business day and proceed with the required Work Shift operations.

The following sections explain how to start the Workday and manage the Work Shift.


---

# 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/workday/about-work-day.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.
