Help

What everything means, in the order you meet it. Every rule, button, and term here also appears as a hover or tap-? explanation inside the app; this page is the same text in one place.

Getting started Terms Buttons and controls Rules For employees Who can see what

Getting started

Shifts. Name the schedule, say whether you run around the clock or set hours, list holidays, and define your shifts: name, hours, and how many people each needs on weekdays, weekends, and holidays. The coverage table beside it shows how many spots the month has.
Employees. Add your people. Each person has the shifts they may work, the weekdays they are available, and a baseline number of shifts. Put in their email: that is what lets them sign in and enter requests. This section also lists what each person asked for this month, with your overrides.
Rules. Rest rules (minimum hours between shifts, sequences that are never allowed, such as night into day), one-off date overrides, and the rule weights. Start with the defaults and change only what you have an opinion about. The ladder shows what beats what.
Build a month. The schedule sits at the top of the page. Pick the month, set a due date and email people that requests are open, then Build. Read the ledger, pin anything you'd rather decide yourself, Refine, and Publish when it's right. The table beside the schedule shows each person's shifts, how many spots they could have taken, and the days they asked off.
Metrics. Once you have a few published months, see who has carried extras, weekends, nights, and holidays over time, and how often requests were honored.

The single most useful habit: after a build, read the ledger top to bottom. The largest entries are the compromises the schedule made. If one looks wrong, that is a weight to change, not a spot to fix by hand.

Terms

Buttons and controls

Rules

Grouped as they appear under Rules. Absolute rules can never be broken; everything else carries a weight you can change.

For employees

Your page has three parts: requests for the coming months, your holidays for the year, and standing preferences that stay true month to month.

Who can see what

Admin: Everything: setup, building, publishing, adding people.
Auditor: Sees everything an admin sees, including rules, weights, requests, the ledger, and metrics, but cannot change anything. For a compliance officer or a department head who wants to understand how a schedule was built.
Viewer: Sees published schedules only, in calendar or list form, and can print or download them. For whoever posts the schedule.
Employee: Anyone whose email is on a roster. Sees their own page: requests, holidays, preferences, and their shifts once a month is published. Employees are not added under People; their roster email is enough.