# Run opening, service, and closing

For the shift leader and restaurant team. Confirm the working location and
coordinate checks before guests arrive. The trading daily, staff clock records,
orders, preparation, cash, and report delivery are separate states.

## Opening the day

1. Check staff identities, roles and location access; record actual work starts
   through [Clocking](/staff/time-tracking).
2. In **Stats**, inspect current daily state. Use **Open daily** when confirmed
   closed and authorised. A connection error cannot establish that no day is
   open.
3. Review today's bookings, late/changed parties, and
   [floor/table setup](/guides/table-floorplan-setup).
4. Verify menu availability, service portions, printer/host connections and
   kitchen-display views. Coordinate a safe test with the kitchen where needed.
5. Record the actual opening float and other cash movements through
   [Cash drawers](/daily-reports/cash-drawers).

If yesterday's daily is still open, resolve its actual outstanding work with the
manager before closing and opening the next. Do not create replacement records
or reset a device to conceal the old state.

## Taking orders and managing service

Use the configured staff or [guest ordering flow](/orders/order-types). Check
order/table identity, items and choices, seat/round, due time and address where
needed, and kitchen instructions before **Send**.

Route through the categories assigned to the actual prep stations; Food does not
inherently mean a station named Kitchen. Follow
[Rounds and firing](/orders/rounds) and
[Kitchen display](/orders/kitchen-display) for preparation timing and actual
handover. A fired or Ready ticket is not a settled bill.

Track bookings and active orders throughout service. Record
[cancellation outcomes](/orders/cancellations) according to what physically
happened. Verify discounts, promises and card balances through their supported
flows. After uncertain writes or payments, inspect the existing order and
[Sync status](/troubleshooting/connection-and-sync) before retrying.

## Closing the day

1. Inspect **Before closing / Settle pending work** with the shift leader.
   Resolve legitimate unpaid work through the authorised order/payment flow; do
   not charge twice or void bills just to clear closing.
2. Verify actual staff finish times and pending clock sync. Do not clock out
   someone still working or guess a time to remove a warning.
3. Record real cash movements, count the correct drawers, and preserve actual
   differences. A fabricated Deposit/Withdraw is not a variance correction.
4. In **Stats**, confirm the daily is still open, choose **Close daily**, review
   the optional count prompt and confirmation, then verify the closed result.
5. Check report email/printing separately. A missing email or slip is not proof
   the day failed to close; use
   [Delivery recovery](/troubleshooting/daily-report-delivery) or
   [Printer recovery](/troubleshooting/printers).

See [Opening and closing recovery](/troubleshooting/opening-and-closing) for
unresolved work and uncertain outcomes. Open the next daily before its service.

## Reviewing and handing over

Use **Console → Reports → Daily reports** at the correct location. Review
trading sales versus held deposits/gift cards, billed versus payments, cash,
menu, actual team hours and estimates, guests, cancellations, tax/close-out, and
automatic checks. Read the labels and source records before drawing conclusions.

Handover unresolved records, device sync, stock/portion shortages, bookings,
menu changes, and the next team's coverage. Use
[Daily report definitions](/daily-reports/console-report),
[Inventory reports](/reports/inventory), and [Reviews](/customers/reviews) for
follow-up. Keep staff credentials and guest/financial records in authorised
channels; no live reset, deletion, or financial workaround is a generic
recovery.