Shift Scheduler Copilot
The weekly schedule builds itself from memory; you make the judgment calls
The problem
The [Shift Schedule Builder](/toolbox/shift-schedule-builder) solves one week, and for one week it is enough. But scheduling is not a weekly puzzle; it is a running story. Who covered the last three Saturday closes, whose availability changed when school started, which swap Dana still owes Marcus, who is quietly drifting toward overtime every second week: none of that fits in a paste, and all of it is what makes a schedule feel fair or slowly poison a team. This skill installs the scheduler who remembers.
The tool
Once installed, this skill turns your assistant into your standing scheduler. It learns the roster once (people, roles, max hours, availability, your hard rules) and then builds each week's schedule from memory: you say "build next week, Priya is away Thursday," and it produces the draft, the conflicts with suggested trades, the single-point-of-failure risk list, and the one-line asks that need a yes before posting.
The memory is what earns the install. It tracks who took the unpopular shifts and rotates them without being reminded. It logs swaps and callouts, so the "can you cover" asks go to the people who owe one, not the same reliable person every time. It carries availability changes forward permanently instead of you re-typing them weekly. And it watches patterns you would only notice in a bad month: the same person flagged in the risk list four weeks running is a hiring gap, and it says so plainly instead of solving around it forever.
What's inside
- A one-time roster interview: people, roles, hours, availability, hard rules
- Weekly builds from memory: schedule, conflicts with trades, risk list, drafted asks
- An unpopular-shift ledger that rotates closes, weekends, and holidays fairly
- Swap and callout logging, with the favor balance consulted before every ask
- Standing availability updates ("school started, Jess is 3pm+ now") applied forever
- Pattern flags: recurring risk-list names and creeping hours become a plain recommendation
How to use it
- 1Click "Install skill" on this page and copy the install prompt.
- 2Paste it into your AI assistant (Claude, ChatGPT, anything that accepts pasted text).
- 3Do the roster interview once, hard rules included.
- 4Each week, say what changed and ask for the build; send the asks before posting.
- 5Report swaps and callouts as they happen, two words is enough ("Dana covered Marcus").
Example
A restaurant with fourteen staff installs the skill and runs it for a month. Week one is the interview plus a first build. By week three, the owner types one line ("build next week, Sam requested Friday off") and gets the draft with a note that Sam also had last Friday off while Jess covered both, so the suggested trade runs the other way this time. In week four a callout gets logged, and the "who to ask" list leads with the two people who owe covers. At the month's end, the pattern flag is blunt: Tuesday close has had exactly one qualified person available for five straight weeks, and that is a cross-training or hiring decision, not a scheduling trick.
Pro tip
Log the tiny stuff, especially covers and swaps, the moment they happen; the fairness ledger is only as good as its entries, and "the schedule finally feels fair" is the single loudest thing staff say when it works. When a pattern flag names the same person three weeks running, take it to a real conversation early; the [Tough Conversation Scripts](/toolbox/tough-conversation-scripts) exist for exactly the talk you are tempted to let the schedule keep absorbing.
Related tools
Want this customized and automated for your business?
We take the tools in this toolbox and wire them into your business: your data, your brand voice, running on autopilot.
Talk to Vexlo