First-run checklist
Create the organization
Owner
Capture the organization name, timezone, and the initial owner account. This becomes the boundary for schedules, users, rules, and analytics.
Organization identity and timezone are defined.
The first privileged user is attached to the workspace.
Invite the core team
Owner + Admin
Bring in admins and schedulers first so role management, rule configuration, and approval workflows have clear accountability.
Core operators can manage staffing data.
Role boundaries match the documented permission model.
Define templates and rules
Admin + Scheduler
Set up shift templates, required skills, and the first set of hard and soft constraints before any schedule is generated.
Coverage expectations are encoded as templates.
Legal limits and fairness weights are ready for the solver.
Collect staff preferences
Staff + Scheduler
Availability, preferred shift types, leave windows, and notes turn a valid roster into a fair one.
Availability is captured before scheduling starts.
Preference data is available for soft-constraint scoring.
Generate the first roster
Scheduler
Run the optimizer, inspect conflicts and fairness impact, and prepare the first publishable schedule.
Assignments are proposed with conflicts surfaced.
Fairness context is visible before publication.
Review and publish
Scheduler
Adjust assignments if needed, publish the roster, and notify staff so swaps and follow-up actions can begin.
Published schedules become visible to staff.
The system is ready for swaps, analytics, and audit logging.