Scheduling setup (Settings, in the sidebar’s branch section) describes what a day at this location can look like: a day type lists which shifts run that day and how many people of which position (and optionally which duty) each shift needs. Set it once, then apply it to dates on the calendar.
The three tables
- Shift types — the day’s sessions: code, name, start, end (a morning session A 08:45–12:45, an evening C 17:30–21:15).
- Duties — role labels inside a shift: examination, front desk… Optional, and assignable per person at scheduling time.
- Day types — compose the two above into “a kind of day”: which shifts this day type runs, and each shift’s coverage — how many of which position, which duty. “No coverage yet — as it stands this day type is a closed day.” Coverage is the substance of a day type, not a footnote.
Edit coverage (on a day type’s row) lays the needs out like the paper roster: one section per shift type, in clock order, headed by its name, code and hours (Morning A · 08:45–12:45). Each session lists the positions it needs and how many — Add position adds a row — and a shift type with no positions reads “Not open this day”. A duty is optional, folded behind each row’s Duty.
The weekly rhythm lives on the same page: which day type each weekday usually is (or Closed). The hint states the division of labour: the planning page applies it to real dates; exceptions are handled there, month by month — “we’re closed Sundays” is said once, not every month.
Each branch owns its set
Scheduling setup is per branch — the branch switcher in the sidebar decides which clinic you are configuring. The two admin tiers differ in exactly one way: branch-level admins see their own branches; org-wide admins additionally get the organisation template.
- The org template (Company ▸ Settings ▸ Scheduling, under Policy in the settings list) is the starter set a new branch can copy — it is copied only when someone presses Copy the organisation template, after which the branch owns its vocabulary outright: editing the template never reaches back into a live branch.
- A brand-new branch’s empty state offers both roads: copy the org template and start from the usual shift and day types, or start from scratch with a first shift type.
- An empty template (every new org starts with one) has nothing to copy, so the empty state offers only Add shift type and says the template is empty. Org-wide admins also get Open the organisation template, to fill the template first.