Quickstart: your first published week

1. Create your organization

The preset matters more than it looks. Picking Hospitality, Retail, Healthcare, Call centre or Manufacturing seeds your organization with positions, shift templates and compliance rules that fit that vertical, so you start from something rather than an empty grid. Choose Custom to start clean.

You become the owner. Every default the preset created is editable afterwards — delete the positions you don't use, rename the rest.

2. Add your locations and positions

Go to Locations and make sure each physical site exists with the right timezone. This is the field people skip and regret: shift times are stored with their location's timezone, so an incorrect one silently shifts everybody's day.

Then Positions. A position is what someone works as, and the preset has probably already created the common ones. Give each a colour so the week grid is readable at a glance, and set a default duration if your shifts are regular.

On the free Starter plan you get one location. Paid plans are billed per location, so adding a second site is also the moment the bill changes — see Plans and billing.

3. Invite your team

Team → Invite sends an email invitation with a role attached. Most people are Employee; give Manager to anyone who needs to build schedules or approve requests.

Coming from another scheduling tool or a spreadsheet? Don't type them in one at a time. Paste your existing roster export and Weekwright maps the columns, flags the rows that need attention, and invites the rest in one action — Importing your data covers the format.

An invite link is valid for seven days. People appear on your roster — and become assignable — once they accept it, so send the invites before you sit down to build the week rather than after. You can re-send or revoke a pending invite at any time from the same screen.

4. Let the agent draft the week

Open Schedules, pick next week, and open the chat panel. Then say what you need in plain language:

Two servers and a barista every weekday from 7 to 3, three servers Friday and Saturday nights, and keep Marta off Wednesdays.

The agent gathers context first — availability, approved time-off, skills, and how the load fell over the previous six weeks — then proposes a full week. You get a reviewable proposal, not a silent mutation: nothing is written until you apply it.

The agent is on every paid plan. On Starter, build the week by hand or from a template — the grid, the copy-week action and the bulk edits all work the same.

5. Review, then publish

Fix whatever you disagree with. Drag a shift to another person, change a time, delete one. If there are holes, ask the agent to fill the gaps and it will re-check eligibility for just those slots.

Then press Publish. Weekwright runs a compliance pre-flight over the whole week, blocks on anything you marked blocking, and — once clear — notifies everyone assigned.

That is the loop. Every following week is steps 4 and 5, and if your weeks rhyme you can shorten it further by saving one as a template or turning on automatic Sunday drafts.

Common questions

How long does this actually take?

Fifteen to twenty minutes for a single-site team of ten to thirty, most of it spent inviting people. The first agent-drafted week takes under a minute to generate.

Can I try it without inviting anyone real?

Yes. Ask the assistant for something like 'add a sample restaurant team of 12' and it seeds placeholder members you can schedule against. They never receive email and cannot sign in — they exist so you can exercise the week grid, swaps and conflict detection before your real team arrives. It runs through the agent, so it needs a paid plan.