Data sources
All revenue figures come from the daily revenue report (tax-exclusive F&B sales — Dawn, Dusk, Pontoon, Sundeck, Beach House). Staff counts come from the active roster file — total headcount and per-venue counts are derived live from the loaded roster, not hardcoded. Salary basis: IDR 3,500,000 per person per month. Each shift is assumed to be 8 hours.
Labor Cost %
Monthly payroll ÷ Monthly revenue × 100
Data: Total roster headcount × IDR 3.5M = monthly payroll (shown in the KPI tile above). Revenue is annualised from the loaded period.
Why it matters: Industry benchmark is 25–35%. Being well below that means your payroll is lean relative to sales. If this creeps up, you're either overstaffing or revenue is falling.
Revenue per Labor Hour
Daily F&B revenue ÷ (staff on shift × 8 hrs)
Data: Each day's tax-exclusive revenue divided by total labor hours worked that day (roster headcount × 8).
Why it matters: Shows how hard each paid hour is working. A low number means you're paying for hours that aren't generating revenue — either too many staff, or too little revenue for that day.
Revenue per Staff / Shift
Daily F&B revenue ÷ number of staff on that day
Data: Same daily revenue, divided by how many people were rostered on (from the roster file — any shift code that isn't OFF, AL, PH, SICK, or CO is counted as working).
Why it matters: Your clearest daily efficiency signal. Compare this across days — the same revenue with fewer staff is a better outcome. The chart colours flag low days automatically (green = high, red = low).
Revenue vs Staff on Shift (chart)
Stacked bar = total covers by venue · Line = staff headcount
Data: Cover counts from the revenue report, staff count from the roster per day.
Why it matters: Lets you see at a glance whether staffing tracks with business volume. If the staff line is high but the bars are small, you're overstaffed. If bars are tall but the line is flat, you may be stretched.
Covers per Staff Member (chart)
Total covers that day ÷ staff on shift
Data: All venue covers combined, divided by daily roster headcount.
Why it matters: Measures how many guests each team member is serving. A very high number may mean staff are under pressure; a very low number means idle capacity. Use this alongside Revenue/Staff to understand whether low covers is a booking issue or a staffing one.
Venue Efficiency Cards
Venue revenue ÷ known FOH headcount for that venue
Data: Per-venue tax-exclusive revenue from the revenue report. FOH headcount is derived live from the roster file (matched by department / sheet name keywords: Dawn, Dusk, Pontoon, Sundeck, Beach House). Sundeck is cross-staffed from Pontoon, so they share one card.
Why it matters: Compares venues on a level playing field. A venue with higher revenue but more staff isn't necessarily more efficient. The card with the highest Rev/Staff/Shift number is generating the most revenue per person paid.
How the Actions are reached
Each action is flagged when a specific threshold is crossed in the data: Public Holiday flag — any PH day where labor cost % is more than 3 points above the period average. Saturday cap — the day with the highest headcount but below-average revenue/staff ratio. Dusk reinforcement — the day Dusk venue revenue peaks while its server count stays flat. Staff absence flag — any employee with fewer than 4 active shifts in a 9-day window. These are not manual judgements — they come directly from comparing the roster against the revenue data.
