Shift Scheduling & Swap Board
Build rosters against coverage requirements, publish them, and let employees request swaps and pickups that a manager approves before the schedule ever changes - so coverage holds and swaps stop creating chaos.
A team scheduling tool that builds shifts against your coverage needs, gets a manager's approval to publish, and routes every swap or pickup through a manager who checks coverage, overtime, rest, and qualifications before it takes effect.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- Your current schedule and availability in a spreadsheet (CSV or Google Sheet)
The problem this kills
You build the schedule in a spreadsheet, post it, and then the texts start. "Can someone cover my Saturday?" "I traded with Dana, that's cool right?" By Friday you have three people who think they swapped into the same shift, a closing slot with nobody qualified on it, and someone quietly sliding into overtime you didn't approve.
The spreadsheet was never the problem. The problem is that every change after you publish happens in a side channel - text, Slack, a sticky note - where coverage, rest rules, overtime, and qualifications aren't being checked, and where nothing is written down. Swaps don't fail because people are careless. They fail because there's no place that knows the rules and no gate before a change goes live.
What you'll build
A web app your whole team logs into. You load your roles, your people and their availability, and your coverage requirements per shift. The tool drafts a schedule that actually meets coverage, then shows it to you - the manager - to approve and publish. Once it's live, employees request swaps and pickups right in the app. Each request is checked against the rules (rest, max hours, overtime, qualifications) and shown to you with the coverage impact spelled out. Nothing changes until you approve. When you do, the schedule updates, the people involved get emailed, and the whole thing is logged. Export to CSV or to a calendar (.ics) file any time.
What's inside the Implementation Plan
The plan opens by interviewing you about your own operation - your roles, your shift pattern, how you label people and qualifications, your real rules for rest and max hours, your peak weeks, and the messy exceptions you handle by hand today. It reflects a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks you step by step - data model, schedule builder, approval-and-publish, the swap board, the rule checks, email notifications, the audit log, and the CSV/.ics exports - and every step ends with a prompt you paste straight into your AI coding agent.
The governance it includes (this is the point)
- Login so only your team can get in.
- Row-level security so each location or team sees only its own schedule and people.
- A human approval gate - the AI drafts the roster and screens every swap, but nothing is published or changed until a manager approves it.
- A full audit trail - who requested, who approved, what changed, and when.
- Duplicate guards - keyed on employee + shift and on swap-request ID, so the same shift can't be double-booked and the same request can't be processed twice.
Who it's for
Shift managers in retail, hospitality, healthcare, and support teams who build the schedule in a spreadsheet and run swaps over text. If you spend your week refereeing coverage and trades, this is for you.
You've got this - paste the first prompt and let the interview tailor the rest.