Bring the context
Type a note, upload a chat screenshot or bring a spreadsheet.
Shiftly turns opening, lunch, dinner and closing needs, staff roles and last-minute changes into a schedule your manager can review before it reaches the team.
“Dinner needs two front-of-house people. Sam cannot close on Tuesday. Keep kitchen coverage on every service.”
A roster with coverage, gaps and trade-offs visible before publishing.
The scenario gives the manager enough context to judge whether the interpretation fits before adding real data.
| Employee | Role | Target |
|---|---|---|
| Sam · #1 | Front of house | 32h |
| Maya · #2 | Kitchen | 36h |
| Omar · #3 | Barista | 24h |
| Leah · #4 | Front of house | 20h |
Type a note, upload a chat screenshot or bring a spreadsheet.
See roles, coverage and temporary rules before they affect the solver.
Compare cost, hours and open shifts; adjust assignments when needed.
Keep the manager in control, then confirm or export the roster as CSV.
A copied roster does not explain which dinner rule changed, whether a role is covered, or why a last-minute absence created a gap.
A lightweight scheduling layer that makes tacit manager knowledge explicit, reviewable and connected to a solver—without forcing a full HR or payroll replacement.
Yes. Start from a restaurant template or define your own shift names and times. Role coverage can be reviewed separately for each period.
No. The absence becomes a visible constraint. You can regenerate, compare the result and confirm it yourself.
No. Shiftly focuses on the roster. Confirmed schedules can be exported as CSV and connected to other systems later.
No payment details. Review the AI interpretation before generating anything.