HourSaved

Draft a weekly staff schedule from availability and your rules

Give the AI your shifts, your hard rules and each person's availability, and it drafts a week's schedule with hours per person and every gap or risk flagged, for you to approve before anyone sees it.

Setup
15 min
Saves
About 30 min a use (our estimate)
Level
Medium
Last checked
Works with
Any AI chat, Spreadsheet, When I Work
Step in a real app
Described from the official help page, not run on a real account

Run once on made-up data on with Claude. One run, not proof.

Version 1 · Draft: not yet approved by the owner · How we test

What this does

It drafts next week's schedule from your staff's availability and your rules. It shows hours per person, marks any shift it can't fill, and lists wishes it couldn't meet. You decide and post. The AI never posts or messages anyone.

This is not HR or legal advice. Rules on breaks, overtime, minors' hours and schedule notice differ by state and city; check yours.

Before you start

  • Any AI chat (ChatGPT, Claude, Gemini or Copilot).
  • Your shifts, people needed per shift, hard rules (never break) and soft wishes (try to meet).
  • Each person's availability for the week, typed out.
  • Setup: about 15 minutes the first time (our estimate).
  • Privacy: first names only. Leave out why someone is unavailable.

Steps

  1. Save your shifts, staffing needs and rules in a note to reuse each week.
  2. Type the week's availability as "name: days and times".
  3. Paste the prompt into a new AI chat and fill in the blanks.
  4. Check every shift against availability yourself, especially each GAP and risk the AI lists.
  5. Ask people before giving them extra hours, then fix the draft.
  6. Enter the final schedule in your app or spreadsheet and post it yourself. In When I Work, managers can save a week as a schedule template and load it later.

The prompt

Prompt · fill the [brackets]
Help me draft next week's staff schedule. Use only the availability and rules I give you. Don't send, post or publish anything. This is a draft for me to approve.

Week: [dates]
Shifts: [for example, AM 7:00-11:00, PM 11:00-15:00]
People needed per shift: [numbers by day]
Hard rules (never break): [max hours per person, key-holder at open, max days per week, breaks, minors' limits]
Soft wishes (try to meet): [hours each person would like]

Staff availability:
[name: days and times they can work]

Do this:
1. Fill each shift only with people who are available. Never break a hard rule.
2. If a shift can't be filled, write GAP and say why. Don't invent availability.
3. Show the schedule as a table: day, shift, who.
4. List hours and days per person, next to their max and their wish.
5. List every soft wish you couldn't meet and anything risky (no backup, someone at their limit).
6. If any availability or rule is unclear, write UNCLEAR and ask me instead of guessing.

Before and after: the made-up input, then the real output the AI gave us.

Try it with made-up data

Lantern Coffee (made up), week of Mon 2030-04-08 to Sun 2030-04-14. Shifts: AM 7-11, PM 11-15. Need 2 people per shift; 3 on Saturday and Sunday AM. Hard rules: max 32 hours and 5 days per person; a key-holder (Ana or Ben) on every AM shift. Wishes: Ana 24-32 hours, Ben about 24, Cara 16, Dev 20, Eli 12.

Ana: Mon-Fri, any time. Ben: Wed-Sun, any time. Cara: Mon, Tue, Sat, Sun, AM only. Dev: PM only, every day except Thu. Eli: Fri PM, Sat and Sun any time.

What the AI gave us

DayAM 7-11PM 11-15
MonAna, CaraAna, Dev
TueAna, CaraAna, Dev
WedAna, BenBen, Dev
ThuAna, BenAna, Ben
FriAna, BenBen, Eli
SatBen, Cara, EliDev, Eli
SunBen, Cara, EliDev, Eli
NameHoursDaysMaxWish
Ana32532 / 524-32
Ben32532 / 5~24
Cara16432 / 516
Dev20532 / 520
Eli20332 / 512

No GAPs. Wishes not met: Ben is 8 hours over his wish; Eli is 8 hours over his.
Risks: Ana and Ben are both at the 32-hour cap, and Dev is at 5 days. If anyone calls out, no one can cover without breaking a rule. Mon and Tue AM depend on Ana alone as key-holder; Sat and Sun AM on Ben alone.

Good: every shift matches the availability, no hard rule is broken, and it was honest that the week has zero slack. A person still had to ask Ben and Eli about the extra hours and plan for call-outs (a second key-holder would help).

Check before you send

  • Each person works only days and times they said they can.
  • No one is over your hour, day or break limits, or your state's rules.
  • A key-holder or manager is on every shift that needs one.
  • Anyone given extra hours agreed first.
  • Dates and days of the week match the calendar.

Don't paste

  • Why someone is unavailable (medical, family, school, legal reasons).
  • Pay rates, Social Security numbers, home addresses or phone numbers.
  • Logins to your scheduling or payroll app.

When not to use this

  • As the final word on labor-law compliance. The AI knows only the rules you type in, and it can still miss one.
  • Large teams with many roles and locations. A scheduling app's own tools may fit better.
  • When availability changes daily.

Questions owners ask

Can AI make my staff schedule for me?

It can draft one from your rules. You still check it, ask people about extra hours, and post it yourself.

What if the AI breaks one of my rules?

Point out the broken rule in the chat and ask for a new draft. Then check every line again.

Sources

Related guides

All 6 scheduling and meetings guidesAll 45 guides

The newsletter

One new guide a week, free.

Start with the free starter: three short emails over your first week. First the 15-minute Start here guide, then the three jobs we'd hand to AI first, then one question about what eats your week. The first two come with a practice task and the check you do before anything goes out. After that, one new guide every Tuesday: one task, the prompt to paste and the check to do. At most one ad, always labeled.

  1. Day 1Your first 15 minutes with a free AI assistant
  2. Day 3Summarize a long email thread into decisions, open questions and next steps
    Draft routine email replies in your own voice, without promises you didn't approve
    Write payment reminder emails in three tones (friendly, firm, final)
  3. Day 6What eats your week? Reply in one line, plus how the weekly guide works