conceptsix-degrees last reviewed 2026-06-11

Six Degrees โ€” Roster Review Pack (for venue manager)

Context

A one-page summary of six weeks of rostered/worked hours (Tanda) crossed with daily sales (PowerEPOS), 27 Apr โ€“ 7 Jun 2026. Written for the venue manager conversation โ€” the numbers raise questions; they don't make decisions. Nothing changes without your input.

Detail

What the data shows, in plain terms

  1. The weekly roster is essentially identical every week โ€” about 1,580 hours and ~250

shifts, week in week out โ€” while takings move a lot (best week $57k, slowest $39.8k). The roster looks copied forward rather than built from expected trade.

  1. **Wednesdays and Thursdays carry nearly as many hours as Saturday but take a third of

the money.** Six-week averages:

DayHours rosteredTakings$ taken per rostered hour
Wednesday~258 h~$4,000$15.72
Thursday~259 h~$3,900$15.09
Saturday~238 h~$11,600$48.82

In six weeks, Wednesday never beat $21/hour and Thursday never beat $19/hour. Saturday runs on fewer hours than either.

  1. Monday and Sunday rosters look right โ€” light crews (~135โ€“140 h) and solid

$-per-hour. Friday is up and down week to week but broadly earns its big roster.

The questions only you can answer

  1. What do the Wed/Thu hours cover that the till doesn't show? Prep for the weekend,

functions/events billed on other days, deliveries, deep cleans, training?

  1. Are there minimum-staffing or skills constraints (e.g. one chef + one duty manager

regardless of trade) that put a floor under quiet days?

  1. Is mid-week trade expected to lift (bookings, functions pipeline, seasonal events)

that the last six weeks don't reflect?

If the answers are "no, mid-week is just quiet"

$-per-hour at current takings โ€” in practice a smaller, safer trim phased over a few rosters would prove the point without service risk.

not the problem.

Actions

scope is enabled โ€” that will show where in the day/teams the spare hours sit.

Provenance

Summarised from labour-vs-sales (full method + tables there). Aggregate hours and takings only โ€” no individual staff data, no wages.

Related

๐Ÿ”— Relationships

graph LR roster_review_pack["roster-review-pack"]:::self roster_review_pack --> labour_vs_sales["labour-vs-sales"] roster_review_pack --> staffing_pattern["staffing-pattern"] roster_review_pack --> staff_directory["staff-directory"] classDef self fill:#715EE3,color:#fff,stroke:#291F50;