Tips & Tricks: Locations
Name locations by city and purpose β "Zurich Warehouse" and "Zurich Office" are instantly distinguishable in a dropdown. Vague names like "Main" or "Site A" cause confusion the moment you add a second location.
Check the canton before publishing shifts β The canton determines public holiday rules and regional payroll calculations. A wrong canton means incorrect holiday surcharges. Verify it once during setup and you won't have payroll surprises later.
Use one location per physical address β Resist the urge to create separate locations for different floors or departments at the same address. Use teams within the location instead β the schedule grid handles multiple teams cleanly, and reporting stays consolidated.
Link the client at the location level for single-client sites β If every hour worked at a site is billed to the same client, set the client on the location. This saves you from selecting the client on every shift or time entry and keeps billing reports accurate.
Unpublish the schedule before a major reshuffle β If next week's shifts need a complete rework, unpublish first. Employees won't see the chaos of moving shifts around, and you avoid triggering a flood of change notifications until the new plan is ready.
Was this article helpful?
Still need help?
Contact support