Orbit Dine Captain Handheld SOP: Mobile Ordering, Course Sequencing & Offline Firing

1. Operational Mission & Pre-Flight Verification Gate

The mission of this standard operating procedure is to eliminate floor-to-kitchen latency, eradicate illegible handwritten tickets, and prevent table race conditions between the central POS terminal register and mobile service staff during high-volume service rushes. By enforcing deterministic state transitions on portable handheld terminals, floor captains coordinate seamlessly with customer-facing displays and guest self-service channels.

Operator Security Tier & Role Permissions

• Assigned Persona: Floor Captain, Head Waiter, Station Lead
• Required Security Tier: Tier 1 Operator Authentication (Captain PIN badge)
• Supervisory Override Required For: Check Voiding, Comp Discounts exceeding 15 percent, Table Transfer between distinct floor zones

2. Environmental Pre-Conditions & Station Readiness Matrix

Before accepting dining floor assignments, captains must verify the operational state of all interconnected subsystems according to the following readiness matrix:

3. Granular Procedural Execution Workflow

The tableside service lifecycle progresses through four standardized execution phases. Every action must follow the sequence outlined below.

Phase 1: Table Acquisition & Session Lock

1. Trigger Condition: Guests are seated at a dining table or call for service.
2. Operator Action: From the floor canvas, tap the designated table badge (e.g., T-04). If the party is seated across merged banquets, select the primary master table.
3. Terminal System Response: The handheld client requests a mutual exclusion lock from the floor session coordinator. The table background turns amber on all floor terminals, indicating an active editing session.
4. Verification State: The top context bar displays the table number, hall designation, and guest headcount within 14 milliseconds.

Phase 2: Rapid Item Capture & Kitchen Notes Formulation

1. Trigger Condition: Guests provide their order selections.
2. Operator Action: Use category tabs or the rapid search bar to locate items. Tap the plus button to increment portion counts. Use 48px minimum touch targets to prevent mis-clicks during rapid entry.
3. Terminal System Response: A 30ms haptic pulse confirms selection. The item registers in the draft check with its standard recipe price and associated station routing tag.
4. Kitchen Notes Formulation: Tap the Note icon on any item requiring customization. Select structured modifier tags (e.g., "Less Spicy", "No Coriander", "Dairy Free") or enter freeform operational instructions. Unstructured notes are limited to 60 characters to ensure full readability on thermal paper tickets and compact kitchen display screens.

Phase 3: Course Allocation & Fire/Hold Staging

1. Trigger Condition: Menu items are captured in the active draft check.
2. Operator Action: Assign each item to its operational course tier:
   • Course 1 (C1: Starters & Beverages): Appetizers, soups, cold drinks. Set default status to Fire Now.
   • Course 2 (C2: Mains & Accompaniments): Karahis, curries, rice, tandoori breads. Set status to Fire Now if immediate preparation is requested, or Hold if staged after starters.
   • Course 3 (C3: Desserts & Hot Beverages): Teas, halwas, kheer. Set status to Hold by default.
3. Terminal System Response: Visual badge colors update dynamically: amber badges signify immediate kitchen firing; slate badges signify held items awaiting subsequent captain release.
4. Verification State: Confirm that no hot entrees are inadvertently set to immediate fire when guests explicitly request starter pacing.

Phase 4: KOT Dispatch & Audited Handoff

1. Trigger Condition: Captain confirms the itemized check with the dining party.
2. Operator Action: Tap the primary dispatch button: SEND KOT TO KITCHEN STATIONS.
3. Terminal System Response:
   • The ticket payload is decomposed into station-specific sub-tickets.
   • Grill items route to the Charcoal Station display.
   • Karahis route to the Wok Station display.
   • Breads route to the Tandoor Station printer.
   • The central terminal emits a high-frequency acoustic chime and vibrates in a double-pulse pattern (100ms on, 50ms off, 100ms on).
4. Verification State: The order confirmation banner displays the assigned order token (e.g., #ORD-9024) and the table status updates to Occupied across all floor devices.

4. Interactive Operational Decision Logic: Captain Handheld Routing

The following state machine governs order routing, course sequencing, and network partition failover during tableside order intake:

5. Deviation Handling & Exception Protocol Matrix

High-pressure dining rooms inevitably encounter exceptions. Staff must follow these verified recovery paths:

6. Shift Handoff, Reconciliation & Terminal Sign-Off

At shift termination, captains must complete the standardized checkout protocol to ensure zero orphaned checks and complete station accountability:

Shift Checkout Sequence

1. Open Check Audit: Review the floor canvas. Zero un-settled tables may be left unassigned. All active dining checks must be transferred to the incoming relief captain using the Transfer Station command.
2. Offline Queue Flush Verification: Check the top header status. The offline queue counter must read exactly 0. If pending transactions remain, walk the terminal into direct range of the primary access point until the queue status displays SYNC COMPLETE.
3. Hardware Sanitization & Return: Power down the display backlight, wipe the handheld casing with food-grade sanitizing wipes, and seat the unit in the multi-dock charging rack.
4. Session Unbind: Tap Operator Logout. The terminal returns to the locked PIN authentication screen, revoking all active check editing tokens.

7. Operator Quick-Reference FAQs & High-Frequency Triage

How does the captain handheld prevent two servers from firing conflicting orders to the same table?

The terminal client acquires an atomic session lease upon selecting any vacant or occupied table. Sibling handheld terminals receive an instantaneous locked-draft broadcast within 14 milliseconds, preventing concurrent check modification until the active captain commits or releases the session.

• Verify table color turns amber on floor canvas.
• If locked inadvertently, wait 120 seconds for automatic lease expiry.
• Use Manager PIN override for emergency session revocation.

What happens when an order is fired in a dining room zone with zero Wi-Fi or cellular signal?

The handheld transitions automatically to air-gapped queue mode without interrupting service. The kitchen ticket payload is stamped with a cryptographic UUID and stored in durable client storage. The local printer subsystem routes the physical ticket directly over Bluetooth or ad-hoc wireless, and the queue syncs automatically upon reconnect.

• Confirm yellow OFFLINE indicator appears in the header.
• Tap Send KOT; verify local confirmation chime sounds.
• Do not attempt manual device reboots while offline queue counter is greater than zero.

How do kitchen display stations distinguish between courses that should be prepared immediately versus held?

Items marked as Course 1 or flagged with Active Fire immediately trigger SLA countdown timers on station displays. Items tagged as Course 2 or Course 3 in Hold state appear in a staged queue on the display until the captain transmits a Course Fire command.

• Review course indicators (C1, C2, C3) on the cart review screen.
• Tap the Hold/Fire toggle to toggle line preparation readiness.
• Emit Course Fire when guests have completed previous course service.

Can floor captains modify kitchen notes after a KOT ticket has been dispatched?

Once dispatched, the initial KOT is immutable to preserve station accountability. Modifying an active dish requires dispatching a supplemental Kitchen Addendum ticket that references the original ticket token with a prominent revision flag.

• Select the active table on the floor canvas.
• Add the revision note to the addendum line item.
• Dispatch KOT Addendum; verbally alert kitchen expeditor for time-sensitive modifications.

Connected Front-of-House Systems & Operational SOPs

• POS Terminal Operations & Floor Navigation: Central cashier terminal workflows, table canvas management, and cash drawer balancing.
• Customer-Facing Display (CFD) Architecture: Real-time dual-screen cart reflection, promotional rotation, and digital settlement.
• Contactless QR Guest Ordering Systems Manual: Self-service guest ordering, table nonces, and live kitchen progress tracking.
• Offline Mode & Local Queue Durability Guide: Disaster recovery, air-gapped buffer replay, and network partition resilience.
• FrontOrbit Documentation Hub: Complete repository of platform architectures, protocols, and standard operating procedures.

8. Schema.org HowTo & TechArticle Structured Data

The technical structure of this operational runbook is encoded below for search engine indexing and automated operational compliance auditing:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "TechArticle",
      "headline": "Orbit Dine Captain Handheld SOP: Mobile Ordering, Course Sequencing & Offline Firing",
      "description": "A tactical operational runbook for floor captains and station leads covering handheld table allocation, three-course kitchen routing, modifier specification, and air-gapped queue operations.",
      "proficiencyLevel": "Intermediate",
      "articleSection": "Front-of-House Operations",
      "inLanguage": "en",
      "publisher": {
        "@type": "Organization",
        "name": "FrontOrbit"
      }
    },
    {
      "@type": "HowTo",
      "name": "How to Operate Orbit Dine Captain Handheld for Table Ordering and Course Sequencing",
      "description": "Standard operating procedure for front-of-house staff taking tableside orders, staging courses, and dispatching kitchen tickets.",
      "estimatedCost": {
        "@type": "MonetaryAmount",
        "currency": "USD",
        "value": "0"
      },
      "step": [
        {
          "@type": "HowToStep",
          "name": "Table Acquisition & Session Lock",
          "text": "Select the designated table on the handheld floor canvas to acquire exclusive modification rights."
        },
        {
          "@type": "HowToStep",
          "name": "Dishes Capture & Modifier Specification",
          "text": "Capture menu selections, adjust portion quantities, and formulate structured preparation notes."
        },
        {
          "@type": "HowToStep",
          "name": "Course Allocation & Staging",
          "text": "Assign dishes to Course 1 (Starters), Course 2 (Mains), or Course 3 (Desserts), and designate Fire or Hold states."
        },
        {
          "@type": "HowToStep",
          "name": "KOT Dispatch & Confirmation",
          "text": "Transmit the order to kitchen display stations and verify acoustic confirmation chime."
        }
      ]
    }
  ]
}