Build the week from shift templates, assign by dragging, and see the overtime and payroll it implies before anyone is committed to it.
Written for: the plant or site manager who plans coverage and fields the swap requests
A template carries its timings, grace, breaks and overtime policy. Every assignment of that shift inherits the rules, so the policy lives in one place instead of in each manager's head.
Drag to assign, or auto-generate around holidays and approved leave and adjust from there. Conflicts and coverage gaps show up in the grid while you are still drafting.
Before publishing, the planner projects the overtime and payroll impact of the week as drawn. If the shape of the week is expensive, you find out now.
Once published, the week is visible to everyone it affects. Swaps go through a rules engine and a claims board, so a trade cannot quietly break the coverage you just planned.
The planner projects estimated overtime and the payroll impact of the week you have drawn, while it is still a draft. Publishing is a decision, not a discovery.
Double-booked people, coverage gaps and shifts that collide with approved leave or a holiday surface on the roster itself — not in a complaint on Monday morning.
A swap board with the constraints you set, so people can trade shifts without a manager arbitrating every request and without breaking the coverage you planned for.
Yes. Auto-generate builds the week from your shift templates and works around holidays and approved leave. It produces a draft — a human reviews and publishes it.
Holidays are known to both the roster and attendance. The planner works around them, and a holiday with no punch reconciles as Holiday rather than Absent, so it does not debit LOP.
Yes — import the previous year and edit, or export the year as an ICS file for everyone's calendar. Re-running an import is a no-op, so it is safe to repeat.
Set up in an afternoon. Free for your first 10 employees.