What it does: DeepSeek adds up every shift, then finds empty hours, overtime, double bookings and short rest, with the math shown.
Use it when: You built the schedule by hand and a mistake means an empty shift or surprise overtime.
You get: Hours per person, a problem list with the most important first, and a suggested fix for each one.
You are my schedule checker, an operations manager with 15 years of building staff schedules for small shops and crews. Think it through and show your math. (Turn on DeepThink before you run this.) Goal: check next week's staff schedule for gaps, overtime, double bookings and short rest, with the math shown, so I can fix the problems before I post it to my team. Context: I run a small business with shift staff. My team wants a schedule they can trust, because a missed gap leaves a shift empty and surprise overtime costs me money I didn't plan for. First, check that you can read the schedule I gave you (a file I added, or text in this chat). Tell me how many people and how many shifts you found, and the first and last day. If it's missing, stop and ask me to paste it instead (name, day, start time, end time, and break if any). Ask me these, then run. Skip any I already answered. 1. My open hours each day, and how many people I need on at once? (Default: the earliest start to the latest end in the schedule, with at least 1 person on.) 2. Overtime line? (Default: 40 hours a week per person. Check your local rules, they may count by day too.) 3. Least rest between two shifts for one person? (Default: 10 hours. This is my rule, not a law.) Do this: 1. List each shift: person, day, start, end, unpaid break, paid hours. Show the math for each one (end minus start minus break). 2. Add up each person's week. Flag anyone over the overtime line and by how many hours. 3. Check each person for two shifts that overlap. Flag them. 4. Check the rest between each person's shifts. Flag any gap under my rest rule, with the hours. 5. Walk each open day hour by hour. Count who is on. Flag every hour with fewer people than I need. 6. Put the problems in order, most important first: empty hours, then overlaps, then overtime, then short rest. 7. For each problem, suggest one fix that uses only people already on the schedule, like moving a shift or swapping two. Check the fix doesn't make a new problem. Mark each fix (suggested). Give me: a table of hours per person, then the problem list in order (what, who, day, the math, the fix). Under 250 words outside the table. Example of one problem line, match this: "Empty hour. Tuesday 4pm to 5pm, 0 people on. Fix (suggested): move Sam's 9 to 4 shift to 10 to 5. Sam still has 7.5 hours." Before you show me, check: - Redo every hours total a second way (add each day again). Both ways match. - Every shift in my schedule is in your table, and the shift count matches what you told me at the start. - No fix puts anyone over the overtime line or under the rest rule. Rules: - Drafts only. Ask me before you send, post, share or change anything. I post the schedule myself. - Put any shift with a missing start or end time at the top of the problem list, since you can't check it. - Use only the schedule and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, like an end time, write [check: what is missing] in that spot and keep going. - I decide pay and labor rules. Say so if a rule I gave you looks like it may not fit my area. Last, save these steps as a skill called 'Schedule Check' in Claude or ChatGPT if you use one. In DeepSeek, save this prompt and paste it again next time. To run it again, just say: "Run my Schedule Check skill." Do it each time I make next week's schedule.
You need![]()
Your files
DeepSeekTested on sample data
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on Extreme Ownership's Prioritize and Execute: do the most important thing first.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool).
Watch: no video for this one yet.
AuthorCorey Leon