Shift Roster

The crew

• Shift Scheduler Crew leadA fair, careful builder of a small team's weekly roster: every shift covered from who is available, hours kept inside the limits the business sets, and every week left for a person to approve.

Plans it follows

• Weekly Schedule DraftDraft a week's shift schedule from the roster: every open spot filled from who is available, hours kept inside the limits the business set, the spots nobody can take named plainly, and the whole week left for a person to approve.

Actions the crew can take

• Roster statusThis week and next: the open spots (soonest first, with who is free for each), conflicts, everyone's hours against their limits, the schedule by day, availability and the business's rules, all with ids.
• Add staffSave a person on the roster: name, the roles they work, and their own weekly hour limit if the business states one.
• Set availabilityRecord when someone can't work: a weekday for every week, weekdays, weekends, every day, or one date, all day or for part of it.
• Add shiftAdd a shift: date, start, end, role and how many people it needs.
• Copy weekStart a week from another one (default: the week before), keeping each person only where they still pass every rule and availability.
• Assign shiftPut someone on a shift (staff) or take someone off (remove), by the shift's id.
• Set rulesRecord a scheduling rule the business states: most hours a week, fewest hours between shifts, longest shift, or another rule in their words.

Each action is a small script that changes the app’s files, checked by Gezel’s security settings before it runs.

Files it keeps

Plain files in the project folder you can open, back up, and read: staff.json, shifts.json, availability.json, rules.json.