Fairness score
96.2
Targeting balanced nights, weekends, and overtime load.
Equal workspace
The workspace now carries the documented first-run flow directly in the app: setup, role handoff, rule definition, preference intake, and first roster generation.
Database schema and RLS
Create the Postgres tables, indexes, and row-level policies before mutating schedule data.
Auth and organization claims
Set up Supabase auth and attach user, organization, and role claims for server-side access control.
Core entities and APIs
Implement users, skills, shift templates, schedules, and the supporting server functions.
Constraint engine
Build the rule interpreter and assignment optimizer that can propose valid, fairness-aware rosters.
Fairness score
96.2
Targeting balanced nights, weekends, and overtime load.
Coverage confidence
99.4%
All critical shifts staffed across the current planning horizon.
Open swap requests
07
Requests ranked by viable replacements and fairness impact.
Time saved / roster
11.8h
Estimated reduction versus manual spreadsheet scheduling.
The schedule surface is set up for drag-and-drop review, fairness context, and eventual optimization results.
Mon
Mia Cruz
Kai Morgan
Tue
Lena Park
Owen Diaz
Wed
Rae Taylor
Zara Ali
Thu
Ivy Chen
Noah Kent
Fri
June Hall
Ava Brooks
Mia Cruz
-1 vs team median2 nights
Kai Morgan
on target3 weekends
Lena Park
+1 credit banked1 holiday
Owen Diaz
monitor next cycle4 overtime hrs
Bootstrap residue, build output, and old backup folders were removed from the workspace.
The documented first-run flow is now centralized in code instead of duplicated in pages.
Clean and startup verification scripts are available for repeatable local launches.
Dashboard and onboarding surfaces now point to the same documented startup path.
These are the first six actions the app is designed to support for a new organization.
Create the organization
Capture the organization name, timezone, and the initial owner account. This becomes the boundary for schedules, users, rules, and analytics.
Invite the core team
Bring in admins and schedulers first so role management, rule configuration, and approval workflows have clear accountability.
Define templates and rules
Set up shift templates, required skills, and the first set of hard and soft constraints before any schedule is generated.
Collect staff preferences
Availability, preferred shift types, leave windows, and notes turn a valid roster into a fair one.
Generate the first roster
Run the optimizer, inspect conflicts and fairness impact, and prepare the first publishable schedule.
Review and publish
Adjust assignments if needed, publish the roster, and notify staff so swaps and follow-up actions can begin.
Module
Calendar-first review flow with assignment explainability and fairness context.
Module
Profiles, skills, availability, and preference capture for every staff member.
Module
Templates, compliance signals, and fairness reporting for administrators.