One night, one sequence
The dining lane organizes a service night as a sequenced flow on one record. This page orients operators to the four stages and the policy inside each.
Before doors
Reservations and expected parties balance against the live floor map. Hosts start with the room's actual shape — where the large parties land, which sections turn fast — rather than a guess carried over from last week.
The phone
Aria covers inbound calls in the location's profile: inquiries answered, parties confirmed, the waitlist managed. Confirmations and reminders that leave the building pass the same consent and quiet-hours gates as every automated message on the platform, and the record keeps what was said, to whom, under which policy. The field note a service night, sequenced follows one full night through the same stages.
The pass
Tickets route and prioritize by entry time and firing sequence across one kitchen queue. The display screen is the single source of what matters next — not one tablet per ordering channel, each with its own opinion.
The close
Tip pools and payout splits compute from imported POS data, proportional by hours, sales, or role weights as house policy configures. Staff see the same math the back office sees, because both read the same record.
Boundary
No turn-time or cover figures are published here. Live floor state, waitlists, and payout records are authenticated console surfaces; this page is orientation.