What Weekwright is, and the six words it uses
The mental model behind the product: organizations, locations, positions, schedules, weeks, and shifts. Read this once and every other page makes sense.
What it does
Weekwright is workforce scheduling software with an AI agent that drafts the week for you. You describe the coverage you need; the agent reads your team's availability, time-off, skills and recent workload, and returns a full week you can edit, argue with, or apply as-is.
It is vertical-agnostic on purpose — restaurants, retail floors, clinics, call centres and factories all run the same underlying problem (people, coverage, rules) with different vocabulary. The industry preset you pick when you create your organization seeds the vocabulary; nothing about the engine changes.
Everything the AI can do, you can do by hand, and everything you can do by hand, the AI can do. That is not a slogan — it is an architectural property. Every action in the product is a single named operation, and the buttons, the agent, the mobile app and the API all call the same one. There is no "AI mode" that behaves differently from the UI.
The six words
Almost every screen is built from these. Learn them once:
| Word | What it is |
|---|---|
| Organization | Your company or tenant. Everything below belongs to exactly one. You can belong to several with a different role in each. |
| Location | A physical site — a store, a kitchen, a ward, a floor. It carries its own timezone and, optionally, a geofence for clock-in. Locations are also the billing quantity. |
| Position | A role someone works as: Server, Barista, Triage Nurse, Line Lead. Shifts are assigned to a position, and positions can require skills. |
| Schedule | A recurring plan container — usually one per location, or one per department. It holds settings and owns the weeks below it. |
| Week | One ISO week inside a schedule, keyed like 2026-W32. A week is either a draft or published. |
| Shift | One person, one position, one start and end time — with its own timezone stored alongside, so a multi-site org spanning timezones stays correct. |
One more you'll meet quickly: a member is a person's seat in one organization. The same human in two orgs is two members, with independent roles, pay rates and display names.
Draft, then publish
The single most important behaviour in the product: a week you are working on is a draft, and your team cannot see it. Publishing is the deliberate act that makes it real — it notifies everyone assigned and moves the shifts into their view.
This is why the AI is safe to let loose. The agent drafts into an unpublished week; nobody is told anything until you press publish. You can regenerate, hand-edit, or delete the whole thing with no consequence to your staff.
Publishing runs a compliance pre-flight first, so a week that breaks one of your blocking rules is stopped before it reaches anyone. See Publishing a schedule.
Who sees what
Managers see the whole roster, the analytics and the settings. Employees see their own week, their availability, their time-off and the swap and open-shift boards. Nobody sees another person's pay rate or private notes unless they are a manager.
A person's profile — avatar, pronouns, emergency contact, language, timezone — belongs to the human and follows them across organizations. Their membership — role, pay rate, employment status — belongs to the employer. Employees can edit the first and never the second.
Common questions
- Do I need a separate schedule per location?
- It is the usual setup and the one we recommend, because a schedule carries its own settings and each location has its own timezone. But nothing forces it — a single-site org with two very different departments often runs two schedules at one location.
- Is my data shared between organizations?
- No. Every query is scoped to one organization, and the database enforces it independently of the application. The only thing that crosses is your personal profile, which is yours rather than any employer's.
Related
Quickstart: your first published week
From signing up to a schedule your team can see, in about fifteen minutes. Five steps, in the order the product expects them.
Roles and permissions
Four roles — Owner, Admin, Manager, Employee — what each one can reach, and how the permission check actually works underneath.
Building a week
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.