First week checklist (admins)

Set Slota up in this order. Each step depends on the one before it — building the schedule before positions and locations exist means going back and re-doing shifts.

1. Create the organisation — name, and the account that will be the first administrator.
2. Company settings — visibility, messaging and which features are on. Do this before inviting anyone, so the first thing staff see is already configured.
3. Locations — every outlet or site, with its timezone. Times are meaningless without this.
4. Positions — every job role, with a colour and a default hourly rate. Colour is what makes the schedule readable at a glance.
5. Groups — optional, but worth doing early if you message or filter by team.
6. Schedule settings — week start, default view, open shifts, confirmation rules, clopening threshold.
7. Time clock settings — clocking rules, overtime, breaks, geofencing. Do this before anyone clocks in; changing rounding or overtime later does not retroactively fix entries.
8. Time off settings — accrual, caps, notice period, approvals.
9. Labor cost settings — currency, budget, target labour %, overtime and holiday multipliers.
10. Notification settings — decide what fires before staff arrive, or their first week is noisy.
11. Invite people — one at a time, or Import CSV for a whole team.
12. Build the first week as drafts, check it, then publish once.

Steps 3 and 4 are the ones people skip and regret. A position carries the default rate that feeds every wage estimate, and a location carries the timezone that every shift time is read against.

Before you invite anyone

• Decide your roles policy — who is a Manager, who is an Admin. Managers cannot grant the Admin role.
• Decide whether open shifts are allowed, and whether shift exchanges are restricted by location and position.
• Decide whether employees can see each other's contact details and coworker names on shifts.