Release Date: 16 February 2026

Release Scope

This release extends the F&B Yield (FBY) Server Leaderboard beyond the initial MVP implementation, which was Toast-only, to support additional POS systems.

The underlying metric, benchmark logic, and interpretation principles remain unchanged, ensuring consistency of performance measurement across POS platforms while enabling broader portfolio adoption.

Purpose & Scope

The FBY Server Leaderboard is a performance and coaching metric designed to measure how effectively servers generate revenue per guest, normalized against each outlet’s menu pricing.

By anchoring performance to the average entrée price, FBY enables fair, comparable insights across:

• Different POS systems
• Different restaurant concepts
• Different price points
• Different locations and meal periods

This release makes FBY available across supported POS integrations, maintaining a consistent methodology regardless of source system.

Core Metric Definition

FBY (%) represents the revenue a server generates per guest as a multiple of the outlet’s average entrée price.

Example

• Average entrée price: $35
• Server revenue per guest: $87.50
• FBY = 250%

This normalization avoids distortions caused by raw check averages or outlet-level averages and allows meaningful cross-location and cross-concept comparison.

Why Benchmarks Exceed 100%

A 100% FBY would indicate that guests only purchased one entrée. In real dining scenarios, guests also purchase beverages, appetizers, desserts, and add-ons.

High-performing servers typically generate 2–3× the entrée value per guest, which is why realistic benchmarks commonly fall between 200–300%, depending on the meal period.

Benchmark Methodology (Top 20%)

Benchmarks are data-driven and outlet-specific.

• Servers are ranked by FBY for a selected:

  • Date range
  • Meal period
• The top 20% of performers are averaged using a weighted calculation to produce the benchmark.
• Benchmarks are calculated separately per meal period (breakfast, lunch, dinner) to reflect different guest behaviors.

This ensures benchmarks are achievable, relevant, and grounded in actual on-property performance.

Typical Benchmark Ranges

Reading the Leaderboard

• Green: Performance above benchmark
• Gold: Within 30% below benchmark
• Red / Gray: More than 30% below benchmark

Additional indicators:

• ± % value shows how far a server is above or below the benchmark
• “X Above / Y Below” summarizes how many servers exceed the benchmark (by design, this will be a minority)

Data Treatment & Accuracy

• Guest count is sourced from POS cover counts
• Revenue is post-discount (actual collected revenue)
• Voids and refunds are excluded
• Comps and discounts reduce FBY, reflecting real sales outcomes
• Servers with insufficient transaction volume may be flagged or excluded to prevent skewed results

These rules are applied consistently across all supported POS systems.

Interpretation Guidelines

• FBY identifies where performance gaps exist, not why

• Root-cause analysis should be supported by additional metrics such as:

  • Revenue per check
  • Beverage, appetizer, and dessert attach rates
  • Tip percentage
• Performance should always be evaluated relative to the benchmark for the same meal period
• Cross-meal-period comparisons (e.g., lunch vs dinner) are not valid

Operational Use Cases

FBY enables:

• Objective, dollar-based coaching conversations
• New-hire progression tracking
• Shift and section scheduling optimization
• Cross-location performance normalization
• Detection of data anomalies (e.g., guest-count inaccuracies)
• Quantification of revenue uplift from training and coaching

FBY is not intended to replace managerial judgment or be used in isolation for disciplinary decisions.

Known Considerations

Certain scenarios may affect interpretation and should be reviewed with context, including:

• Promotional or prix-fixe periods
• Very small sample sizes
• Large parties with incorrect cover counts
• Mixed service roles (bar and floor)
• Catering, delivery, and non-table-service transactions