Documentation
23 articles covering the whole product — building and publishing schedules, the AI agent, compliance rules, your team, billing and the API. Written to be read, not skimmed for keywords.
The mental model, the first week, and bringing your data across.
The mental model behind the product: organizations, locations, positions, schedules, weeks, and shifts. Read this once and every other page makes sense.
ReadFrom signing up to a schedule your team can see, in about fifteen minutes. Five steps, in the order the product expects them.
ReadFour roles — Owner, Admin, Manager, Employee — what each one can reach, and how the permission check actually works underneath.
ReadPaste a CSV export from your current tool or a spreadsheet. Columns are detected for you, every row is previewed before anything is written, and nothing is imported until you confirm.
ReadBuilding weeks, publishing them, and everything that moves a shift.
The five views of the week grid, how to add and move shifts, the bulk actions that save the most time, and what happens when two managers edit at once.
ReadWhat publishing actually does, the compliance pre-flight that runs first, how people confirm they have seen it, and what happens when you need to change a published week.
ReadSave a week you like and reuse its layout on any future week — by hand, or automatically every Sunday. Including the guard rails that stop a recurrence from touching real work.
ReadPost coverage you cannot fill and let eligible staff claim it. Who is eligible, how the approval gate works, and why a claim can still be refused.
ReadLet staff trade shifts between themselves, with or without your approval. How candidates are suggested, what each status means, and where reciprocity shows up.
ReadThe scheduling agent, what runs on its own, and the analytics on top.
What the assistant can actually do, how a week gets drafted, why nothing is written without your say-so, and how to talk to it so it gets the week right first time.
ReadThree scheduled jobs run on Sunday so Monday is not a blank page: template recurrence, a seeded draft of next week, and a manager digest that reaches you in Slack or Teams.
ReadThe analytical layer on top of the agent: why a person got a shift, how the load falls across weeks, who is drifting, where coverage is thin, and whether breaks are being taken.
ReadPeople, availability, time off, and the qualifications that gate a shift.
How invites work, what a member record actually holds, the four employment statuses and why you should use them instead of deleting people.
ReadThe difference between a recurring availability pattern and a dated time-off request, how each one affects scheduling, and the seven request types.
ReadDefine what a position requires, record who holds what, set an expiry on the certifications that have one, and let the schedule enforce it instead of your memory.
ReadEncoding the rules you operate under so the schedule enforces them.
Written for team members rather than managers.
Everything you can do as a team member: see your week, set your availability, book time off, swap a shift, pick up extra hours, and get your shifts into your own calendar.
ReadClocking in and out, recording breaks, and how the optional location fence works — including what it does and does not do with your staff's location.
ReadBilling, notifications, security and the audit trail.
Why the bill is per location rather than per employee, what each plan unlocks, how the trial works, and what happens when a payment fails.
ReadWhat gets sent, to whom, through which channel, and how to mute the parts you do not want without losing the parts you do.
ReadHow tenants are isolated, what the audit log records, and the recovery paths that exist when somebody deletes the wrong thing.
ReadThe API, webhooks, and getting your data out.
One RPC endpoint exposes every operation in the product, authenticated by a scoped org key. Outbound webhooks are signed and retried. Reference for both.
ReadExport a pay period as CSV in the shape Gusto, QuickBooks or ADP expects, dump a week's shifts, or subscribe a personal calendar feed.
ReadA question these pages cannot answer is a page we still owe you — tell us and we will write it. For deeper reading, the blog covers the thinking behind particular decisions, the changelog records what shipped and when, and scheduling laws tracks what US state predictive-scheduling rules currently require.
Ask a questionNo credit card required.
We use cookies to see which pages get read, where people give up, and whether an ad click ended in a signup. Nothing loads until you choose, and none of it is personalised advertising. What we store