Staff scheduling, with every shift in the right place.
Build an actual employee roster—not a generic calendar. Assign named people to shifts, rebalance team coverage, review paid-time estimates, flag double bookings and short rest gaps, then share a clean week.
Check the coverage before publishing.
From a team list to a roster that makes sense.
Employee scheduling is not simply placing colored rectangles on a week. The key questions are who is responsible for each shift, which role they cover, how much time is scheduled after breaks, and whether the assignments leave preventable gaps or double bookings.
A roster organized by people
Read each employee's Monday–Sunday assignments in one row. Empty cells are available for new shifts. Color-coded shift types make opening, day, closing and overnight assignments easier to distinguish.
Reassign without retyping
Drag a shift to another team member or weekday on desktop. On a phone, open its editor and change the employee and date. Exact start/end times, breaks and status stay editable.
See risks, don't guess
Review same-person overlapping shifts, user-configured minimum rest gaps, weekly hour limits, leave clashes and dates below your chosen staffing count before sharing the roster.
Accurate scheduled-time view
Shift spans may cross midnight. The builder calculates real elapsed hours and deducts entered break minutes; it does not pretend to calculate actual attendance, overtime wages or payroll compliance.
Spot thin coverage before it becomes a staffing problem.
The alternate Daily Coverage view counts scheduled people by day, breaks down opening/day/closing/night assignments and highlights days that fall below your own headcount threshold. It is deliberately transparent: there is no fictional claim of AI knowing customer traffic or skill requirements.
Use the count to start a coverage discussion, then check role mix, site requirements, rest policies and skills that this lightweight scheduler cannot validate.
How to build, correct and export a weekly staff roster
Follow this employee-specific workflow to prepare a schedule for named people. All settings below correspond to visible controls in the roster editor.
Start with your actual people and roles
On your first visit the example roster demonstrates the interface with fictional employees. Select More → Blank roster to clear the example after confirmation, or edit the sample employees one by one. Choose + Employee to add a person. Give every employee a distinct display name, a main role and an optional department or location. Consistent names prevent hours and collision warnings being split between near-duplicate names.
Employee rows appear on the left of the roster. The week spans Monday through Sunday. Use the arrow buttons to visit previous or following weeks, or select a week with the date picker. Moving between weeks does not delete the rest of the roster stored in the workspace.
Assign work to a particular date and clock time
Click an empty cell in the employee's row under the appropriate date to open a prefilled shift editor. Set a start time, end time, job role, department, shift type and optional note. The break field is minutes deducted from scheduled net hours. For example, 09:00–17:00 with a 30-minute unpaid break produces 7.5 net scheduled hours.
A shift ending earlier on the clock than it begins is treated as overnight: 22:00–06:00 lasts eight hours and ends the next calendar date. This avoids losing night assignments at midnight. Review the correct start date carefully because that is the date used for the employee's row and calendar export.
Drag, edit, duplicate or remove assignments
Press an existing shift card to open its exact-time editor. You can change its employee, date, type, break, role, location, status or notes. Choose Duplicate if you need a second assignment based on an existing one. Drag-and-drop between staff/day cells is available with mouse/trackpad; on touchscreen or keyboard, use the dialog instead of a fragile pointer gesture.
If an assignment is no longer required, delete it from the editor. The tool requests confirmation for destructive actions and keeps a short in-session Undo/Redo history. Use More → Copy week forward to create fresh copies for the following week only after reviewing potential existing assignments.
Check net hours, rest gaps and leave
The summary counts scheduled shift records and net hours for the selected week. An employee's shift can contribute hours to more than one calendar day; the week report counts the complete assignment by its start date. The warning report checks all stored employee shifts across date boundaries so late-night work can conflict with early work the next day.
In More, set your own rest-gap warning and weekly hours review threshold. These are planning alerts, not universal legal employment standards. Employees' leave dates can be marked using the Employee editor, and any shift starting on one of those dates will be flagged. Check local employment law, labor agreements and workplace policies outside this tool.
Review each day, not just total headcount
Choose Daily coverage to see daily assigned-employee counts and an opening/day/closing/night breakdown. The minimum daily people setting flags days below your chosen target. Different assignments for one person on the same day count as one person for headcount. An overnight shift may provide coverage after midnight; these high-level counts are based on shift start dates rather than a minute-by-minute on-duty demand model.
A day with enough scheduled people can still be unsafe or understaffed if required qualifications, stations, supervision or breaks are missing. Use the coverage table for initial planning and check detailed operational requirements separately.
Keep a recoverable copy of the finished roster
Changes autosave locally in this browser; they are not automatically shared with every device or employee. Select Save to My Schedules after signing into the site's global account system to write the currently saved shifts to your account. The existing My Schedules page can then list that compatible cloud schedule. A cloud events record does not preserve every personnel preference, leave entry or local Undo history.
CSV exports one row per shift, ICS creates calendar appointments, Print can produce a readable PDF, and JSON backup preserves the fuller local state including employees, leave and tool preferences. Keep private staff notes minimal and protect downloaded files. When importing JSON, review the destination carefully because restoration replaces the active editor state.
From six disconnected names to one readable coverage plan.
Imagine a support desk needs early coverage, a standard day team and someone to finish late. The manager starts with the fixed supervisor assignment, then adds front-desk and customer-support shifts. A person who closes at 22:00 and opens again at 07:00 next morning would have only nine hours between shifts, so a 10-hour preference flags this combination for review.
Rather than automatically moving work without permission, the tool shows the warning. The manager can edit the assignment, move it to a different employee, arrange a different start time or keep the original after checking the actual workplace rules. This preserves accountability for real scheduling decisions.
Things to confirm before relying on a roster.
The tool is an assignment planner, not a payroll, legal-compliance or real-time attendance system.
Does the example roster schedule real employees?
No. Initial names and shifts are fictional demonstrations. Replace them with your team, or use More → Blank roster to start from scratch. Existing saved browser data is never replaced automatically by the example.
Can I put the same person on multiple shifts?
Yes. You can add more than one shift for the same employee. Overlapping time intervals produce a double-booking warning. A brief rest interval between non-overlapping shifts can also trigger an optional warning.
Does the tool know employment laws and overtime rules?
No. It counts scheduled durations minus manually entered breaks and checks against thresholds you choose. Statutory rest, overtime, premiums and required coverage must be verified separately.
What happens when a shift passes midnight?
For example, a 22:00–06:00 shift is treated as finishing the next day. It stays in its original start-date cell while conflict calculations include the actual overnight interval.
Can staff be reassigned by dragging?
Yes. Drag a shift from its existing staff/day cell onto another employee and date on desktop. Click the shift to change assignment precisely on mobile, keyboard or touch devices.
Are leave dates supported?
Yes. Open an employee's profile from the row label and add or remove leave dates. A shift whose start date is marked as leave creates a warning. The tool does not automatically block an override.
Is the cloud copy identical to the JSON backup?
No. Cloud saving uses the existing Supabase schedules/events schema, primarily for dated shift records. The JSON backup is the complete local workspace export, including leave dates and preferences. Existing Supabase permissions must allow writes for cloud storage to work.
How should I distribute a finished roster?
Use CSV if colleagues need spreadsheet rows, ICS for calendar import, or Print/PDF for a readable schedule. Avoid publicly sharing files with confidential employee details.
Make every shift clear before the first person clocks in.
Edit the sample team, bring in your own staff and share only after reviewing rest, hours and coverage.