What the week grid and day panel show, every field on a shift assignment, how copying a day works, and how the schedule lines up with production.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
The staff schedule lays a week across seven columns and lists, in each day, who is on shift and in which department. You come here to read the coming week or to name who should be in before the run sheets go out. This page walks the whole screen — the week grid, the day panel, the fields on an assignment, and what happens when you copy a day. Open it from Staff schedule in the sidebar. Plant+
The grid runs Monday to Sunday, one column per day, with the weekday names across the top and Saturday and Sunday shaded. Above it, a date range names the week you're looking at — Jul 13 – Jul 19, 2026 — with Today and previous- and next-week arrows beside it to move around.
Each day cell carries:
A day with no one reads No schedules, and a week with no one at all reads No shifts scheduled this week yet. An shows a dash where the end time would be — 10:00 – —.
Two dropdowns above the grid narrow what it shows, and each applies the moment you choose it:
When either is set, a Clear filters link appears to reset both. Filtering by a single department also changes the day cells: instead of grouping people under department headings, each day lists the matching people directly.
Selecting any day opens its panel beside the grid. The panel header shows the full date — Wednesday, Jul 15, 2026 — and a count such as 2 staff scheduled, with a close button to send it away. Below the header sit the Add and Copy from… actions, and two tabs that change how the day's roster reads:
When the day has production scheduled, a Production schedules table sits above the roster, covered under How it overlaps production and runs below. A day with no one reads No staff scheduled for this day.
Each entry on the schedule is an . The Add assignment and Edit assignment forms carry the same fields:
One person can hold more than one assignment on the same day — a morning shift on the line and an afternoon in QA, say — as long as the department or the start time differs. Adding an assignment that matches an existing one exactly, same person, day, department, and start time, is turned away as a duplicate.
Copy from… fills the open day from another one. You pick a Source date, and every shift on that day is copied onto the day you have open. The copy is all-or-nothing: if the source day has no shifts, if anyone on it no longer belongs to their department, or if any shift would duplicate one that already sits on the target day, the whole copy is turned away and nothing changes. When it lands, the schedule confirms how many shifts it copied.
The staff schedule is the plan for who should be in. It sits next to two other screens that answer nearby questions.
When a day has production scheduled, the day panel shows a Production schedules table so you can staff against the work that's actually planned:
Recording who actually worked a batch happens later, on a production run's Staff attendance tab — the planned roster here, the attended roster there. And each person's recurring availability, set on their employee record, is the standing answer to which hours they can be on the floor as you fill the week.
The staff schedule is gated by its own permissions:
The Production schedules table has its own gate: it appears only for people who can view production schedule days, and the plan link within it only for people who can view production plans.