Six Degrees — Staffing Pattern (roster snapshot)
Context
Aggregate view of how Six Degrees rosters its team, from one representative Tanda roster week (2026-06-01 → 2026-06-07). Counts only — no individual staff data. Useful as an operations baseline (coverage intensity, team breadth, weekly shape).
Detail
- 246 shifts rostered across the week
- 48 staff rostered (of 60 active — see staff-directory)
- 16 active departments/teams (functional areas; names pending the Tanda
departmentscope)
Shifts per day (operating 7 days):
| Day | Shifts |
|---|---|
| Mon 2026-06-01 | 21 |
| Tue 2026-06-02 | 40 |
| Wed 2026-06-03 | 39 |
| Thu 2026-06-04 | 40 |
| Fri 2026-06-05 | 47 |
| Sat 2026-06-06 | 38 |
| Sun 2026-06-07 | 21 |
- Peak day: Friday (47 shifts); Tue–Thu steady (~40); Mon & Sun lightest (21 each) — classic hospitality weekend-led pattern.
- Roughly 5 shifts per staff member per week on average (246 / 48).
Actions
- Add the Tanda
departmentscope → label the 16 teams by name (Kitchen / Bar / Floor / etc.) and split coverage by function. - Refresh this snapshot periodically (it's one week); trend it over time to spot seasonality.
qualificationsscope is also currently missing (blocks a certifications/compliance page).
Provenance
Aggregated from Tanda GET /api/v2/rosters/current (org 183031 Six Degrees, week 2026-06-01..07) on 2026-06-08. Only counts were extracted — no names, times, pay, or any individual-level data.
🔗 Relationships
graph LR
staffing_pattern["staffing-pattern"]:::self
staffing_pattern --> staff_directory["staff-directory"]
classDef self fill:#715EE3,color:#fff,stroke:#291F50;