Scheduling and labor rules without spreadsheet chaos

Scheduling is the highest-touch back-of-house workflow. GMs rebuild schedules weekly, balance availability with coverage, respond to callouts, and answer leadership questions about labor — often in spreadsheets that break the moment service gets busy.

Luminix scheduling is part of the People pillar — connected to HR records, certifications, and location structure instead of a standalone calendar tool.

Why spreadsheets fail at scale

Spreadsheet schedules work until they do not:

• No conflict detection — double-bookings discovered on the floor, not before publish
• Availability in another tab — or another app, or a group text
• Certification blind spots — scheduled shifts for roles a team member is not certified for
• No roll-up — operating partners cannot see schedule status across stores without opening five files
• Version chaos — "final_v3_REAL.xlsx" is not a publish workflow

At multi-unit scale, spreadsheet scheduling becomes a full-time reconciliation job for someone who should be running operations.

Core scheduling capabilities

Luminix scheduling supports restaurant-specific workflows:

Availability and time off

Team members submit availability; GMs see it during build. Time-off requests follow the same people record — not a separate form that HR re-enters.

Conflict checks before publish

Scheduling surfaces conflicts — overlapping shifts, unavailable team members, role mismatches — before the schedule hits the floor. Fixing conflicts at publish time is cheaper than fixing them during service.

Labor rules

Configure rules that match how your group thinks about labor — minimum coverage, role requirements, constraints by location. Rules vary by operator; discuss your policy during demo and provisioning.

Publish workflow

Draft → review → publish. Published schedules are the source of truth for the floor — not a screenshot in a chat thread.

Connection to HR and certifications

Scheduling disconnected from HR creates compliance risk. In Luminix:

• People records include role and certification status
• Scheduling references the same employee IDs HR maintains
• Certification expiry can inform assignment decisions

When HR updates a certification, scheduling context reflects it — without CSV imports between systems.

Multi-location scheduling

For groups with multiple stores:

• Each location has its own schedule; district and owner roles see portfolio views as configured
• GMs build for their store; district managers coach across stores using consistent data
• Templates and patterns can repeat across locations where concepts match

See multi-location rollout for how scheduling training fits in go-live.

Daily ops connection

Scheduling does not end at publish. Daily ops covers what happens on shift — checklists, handoffs, execution. When scheduling and daily ops share location and people context, leadership connects "who was scheduled" with "what happened on shift."

That connection is the difference between a calendar tool and an operations platform.

Migration from spreadsheets

During provisioning, we help groups transition:

1. Import or enter team roster and roles
2. Configure availability baselines
3. Build first schedule in parallel with existing tool
4. Publish in Luminix on cutover week

Parallel week is critical for scheduling — GMs need confidence the published schedule is correct before they stop using the spreadsheet.

Evaluation questions for scheduling

When comparing scheduling tools, ask:

• Does conflict detection run before publish?
• Are availability and time off in the same system as the schedule?
• Does scheduling reference HR/certification data natively?
• Can leadership see schedule status across locations?

Our demo questions guide includes scheduling-specific prompts.

Next steps

Explore the People pillar or book a demo to walk through schedule build, conflict resolution, and publish workflow with realistic restaurant data.