To schedule employees effectively, check every person against the same list before you give them a shift: where they work, their approved time off, the days and hours they cannot work, whether they are already on a shift, the role the shift needs, their hours so far this week, their days in a row, the gap since their last shift and what the shift costs. XShift AI runs that whole list for you. The AI Copilot fills your shifts from one sentence, and Autopilot blocks any shift that breaks a rule you wrote.
Every tip below is built the same way.
First the practice, in plain words. Then what skipping it costs you, with the arithmetic on the page so you can argue with it. Then what to do by hand. Then the checks a piece of software has to run if you want it done for you, and exactly how XShift AI does each one.
These staff scheduling tips apply to any business that runs shifts.
One example runs through the whole page. Let’s say you have 40 people, they are paid $20 an hour, and you are open seven days a week, which means an overtime hour costs you $30 instead of $20 and $10 of every one of those hours buys you nothing at all.
The 12 employee scheduling tips, and what each one costs to skip
These twelve checks are the employee scheduling best practices that change a week, and together they are how to build a schedule for employees without missing anything. Read the second column slowly, because almost every manager I talk to is certain they already do all twelve, and the column is what each one costs the week you skip it.
| The tip | What skipping it costs you |
|---|---|
| 1. Run one list of checks | When you build a schedule there is a list of things to check on every person before you give them a shift: can they work that day, are they about to pass 40 hours, does the shift fit the budget, do they have the right role. If that list only lives in your head, you skip one most weeks without knowing it. Every skip is a shift you discover is wrong on the day itself, and you spend twenty minutes fixing it while the floor runs short. One skip a week is 17 hours a year spent repairing weeks you already built. |
| 2. Collect availability first | Put somebody on a day they told you they cannot work, and one of three things happens. They call out, and you scramble at the last minute to find a replacement. They do not show up at all, and you run that shift short without seeing it coming. Or they come in, resent that the availability they gave you was ignored, and eventually quit, and now you are down one person. |
| 3. Count the week before you assign | Say somebody already has 36 hours this week and you give them one more 8-hour shift. Four of those hours are past 40, so they pay time and a half. At $20 an hour that is $30 an hour for those four hours, which is $40 more than the same shift given to somebody with room. Do that to ten people a week and it is $400 a week. Over 52 weeks that is $20,800 a year, and you find out on the payroll run. |
| 4. Price the shift | You put five people on Saturday at what you think is $18 an hour. Two are on $22, and one already has four hours past 40. The day lands $100 over the number you had in your head. Ten shifts like that a week is $1,000, and $52,000 a year you never budgeted. |
| 5. Cap the days in a row | Say somebody works seven days straight and the seventh is a 9-hour day. By then they are already past 40 hours, so all nine hours pay time and a half. At $20 an hour that is $10 extra on each of them, or $90 extra for the day, from a person who is worn out and slower than usual. If that happens to one person a week, $90 × 52 is $4,680 a year. |
| 6. Set a gap between shifts | Say somebody closes at 11 at night and you have them opening at 6 the next morning. That is seven hours between shifts, and about five of them asleep. Two things happen. They call out in the morning and you are phoning around at 5:30 for a replacement. Or they come in exhausted, work badly, and start hating the job. |
| 7. Rotate the weekends | If the same three people work every Saturday, one of them eventually quits over it. Now you are short one person, spending your weeks interviewing and training a replacement who cannot cover a shift yet, while the other two watch and wonder if they are next. |
| 8. Set a headcount per role | Say a Tuesday needs two servers and you schedule three. The third one is a 7-hour shift at $20 an hour, or $140, paid to stand around. If you overstaff two shifts a week like that, it is $280 a week, and $280 × 52 is $14,560 a year. |
| 9. Decide call-off order first | Say somebody calls off a 6-hour shift. You spend twenty minutes phoning people and you take the first yes. The first yes is usually the person who is already past 40 hours, so all six hours pay time and a half. At $20 an hour, that cover costs $180 instead of $120. That is $60 extra every time you cover a call-off this way. |
| 10. Answer time off by rule | Say two people ask for the same Friday off, both a week ahead, and one gets a yes and the other gets a no. The one who got the no finds out. From then on every decision you make looks like favoritism, even the fair ones, and people stop asking for time off and start calling out instead. |
| 11. Post with real notice | Say you post the week on Thursday for a Monday start. Nobody can arrange childcare or a second job around a schedule they got three days before it starts. So they call out, or they leave for a place that posts two weeks ahead. |
| 12. Write the rules down | Say your rule is that nobody works two closing shifts in a row, and it lives only in your head. It holds on the weeks you remember it. The week you are tired or away, somebody gets two closes, and the exact thing the rule was there to stop happens: a worn-out closer, a call-out, or a resignation. |
1.Check every person against the same list before you give them a shift
A good schedule is not a creative act. It is the same list of questions, asked about every person, for every shift, in the same order, and the only reason it feels hard is that the list lives in your head, where things get skipped at eleven at night.
I think the list is the whole job. Learning how to schedule employees effectively is learning that list, and the same list answers how to schedule workers at 12 people and at 400.
Let’s say it takes six minutes a person. For 40 people that is 4 hours a week, and 208 hours a year. Skip it and the week comes back to you anyway, as call-outs, as swaps, and as a shift somebody was never able to work.
What to do
Write the checks down in one order. Run every person through all of them, the same way, for every shift, before anyone sees the schedule.
What the software has to handle
So this is the first thing to look for in employee scheduling software. It has to build against every constraint you actually have, not lay out a grid.
Checked by hand, for every person, on every shift
20 checksXShift AI’s AI Copilot runs all twenty when you type one sentence. It fills the shifts you already have, in that order, then sorts whoever survives. Fair mode gives the next shift to whoever holds the fewest hours. Max mode fills for coverage. Either way it stops at the number each role still needs.
For example, say you type “Fill next week, Monday to Sunday”. Checks one to eight are built in. Checks nine to twenty are the rules you wrote, and while it builds, a rule that would normally just warn a manager blocks the shift instead, because nobody is there to override it. The whole set is on the features page.
Build next week against all twenty checks
2.Collect the days and hours people cannot work, in one place
Ask anyone how to schedule staff and they will describe the grid. The grid is the last step. Availability comes first, and it is two things most managers only half collect: days a person can never work, like a Tuesday class, and hours they are blocked on the days they can, like a school pickup at three.
I would ask for it again every month. Lives change and nobody thinks to tell you.
Let’s say you schedule over somebody’s availability twice a week. Each one costs 20 minutes of fixing, so 40 minutes a week, and the shift is short the whole time. Do it to the same person twice and they stop telling you when they are free, which is how you lose the information for good.
What to do
Ask each person for the days they can never work and the hours they are blocked, keep it in one place, and check it before every shift.
What the software has to handle
Scheduling software that checks availability has to hold both kinds and test both before it gives anybody a shift: the days they blocked, the time windows they blocked, and any shift they are already on.
Mon
Free
Tue
Never
Wed
Free
Thu
Can’t work after 3 PM
Fri
Free
Sat
Free
Sun
Never
In XShift AI each person carries their own blocked days and their own blocked hours. Building the week or covering a call-off, XShift AI will never put somebody on a day they blocked, never inside hours they blocked, and never on top of a shift they already have. Ask the AI Copilot who is free on Thursday evening and it tells you.
See availability checked before a shift saves. Book a demo
3.Count someone’s week before you add the shift, not after payroll
Overtime is decided when you hand out the shift. Not when payroll runs. By the time the number reaches a payroll report every hour behind it has been worked, and nothing is left to decide except how to explain it.
Let’s say somebody is at 38 hours and you give them one more 7-hour shift.
I would leave the shift open for an hour rather than hand it to whoever is closest to 40. That is how to avoid overtime when scheduling. Count the week first.
What to do
Add the new shift to the hours that person already holds that week. If the total passes your limit, give the shift to somebody with room.
What the software has to handle
A tool that blocks overtime has to do four things: hold a weekly hour cap, cap the number of shifts, cap how long one shift can be, and use your own overtime threshold rather than a fixed one. All four have to run as the shift is saved, not on a report afterwards.
XShift AI does it in two places. An Autopilot rule adds the shift you are saving to the hours that person already holds that Sunday to Saturday week, and blocks it if the total passes your number. Your threshold is 40 hours unless you change it, matching the federal rule that overtime is owed past 40 hours in a workweek.
The second place is the week you already built. A manager presses Run Scan Now with Workforce Insights on, and the Overtime Agent adds up this week’s shifts for everyone not marked exempt, flags anyone past the threshold with the estimated cost, picks the shift that brings them back under, and finds someone at the same location and role who is free then and stays under. Nothing moves until a manager approves it. More in how to reduce overtime costs.
Block the overtime hour before it is booked
4.Price the shift before you save it
A labor budget is a dollar ceiling for a day or a week, set before the schedule is built. Without one you find out what the schedule cost after the week is over. That is a receipt, not a budget.
Let’s say Saturday is allowed $2,000 and the shifts on it already come to $1,880, so $2,000 minus $1,880 leaves $120 of room. Watch what one more 8-hour shift at $20 an hour does.
Saturday’s ceiling: $2,000
$1,880 + $160 = $2,040, which is $40 over. Autopilot blocks that shift and Saturday stays at or under $2,000.
What to do
Pick what a day and a week are allowed to cost in wages. Add each new shift to the running total and stop when the total passes the number.
What the software has to handle
Scheduling software with a labor budget has to price the shift, not report on it afterwards. It needs each person’s pay, hours past your overtime threshold charged at time and a half, the right bucket, day or week, and a separate number per location.
In XShift AI the ceiling is one written sentence, for a day or a week, everywhere or at one named location. For every shift it takes the person’s hourly rate, or their salary divided by 2,080, charges any hour past your overtime threshold that week at time and a half, and adds the result to what that day or week already holds. Over your number, and the shift is blocked. Building the week or covering a call-off, it moves to the next person who fits.
Hold a dollar ceiling on every shift. Book a demo
5.Cap the days anyone works in a row
Most shift scheduling tips stop at hours. Days in a row is the one they miss, and it is a separate number: a person can sit under 40 hours and still work eleven days without a break, because short shifts never trip an hour cap.
Let’s say your most reliable person is at 40 hours by day six, and you give them a seventh day of 8 hours. Every one of those 8 hours is overtime: 8 × $30 = $240 for one day, with $80 of it buying nothing. And because they are the reliable one, you will do the same thing next week.
Mon
Day 1
Tue
Day 2
Wed
Day 3
Thu
Day 4
Fri
Day 5
Sat
Day 6
Sun
Blocked
What to do
Pick the most days in a row anyone may work. Count days across every location, and count two shifts on one date as one day.
What the software has to handle
The tool has to count calendar days rather than shifts, count days worked at every location you run, and treat two shifts on one date as one day so a double does not eat the allowance.
XShift AI counts it exactly that way. A days-in-a-row rule reads the unbroken run of dates around the shift you are saving, counts days worked anywhere in your account because being worn out does not stop at a location line, counts two shifts on one date as one day, and blocks the shift that would push the run past your cap. Say the cap is six. The seventh straight day is refused before anybody is told they are working it.
Cap the days in a row across every location
6.Give people enough hours off between two shifts
The gap between two shifts matters more than either shift does. A close at midnight followed by an open at eight is eight hours off, and a good part of that is the drive home and back.
Let’s say it happens once a week. The opener is slow, and by Friday that is the person who calls out. Covering their shift costs you 20 minutes of calls and an overtime hour on whoever answers, so one short turnaround has cost you twice.
Close at midnight, open at 8 AM
Your written minimum
What to do
Pick a minimum gap, such as 10 hours. Check when the person’s last shift ended before you give them the next one.
What the software has to handle
Scheduling software that enforces rest has to read when the previous shift actually ended, not what day it was on, and handle the case where there is no previous shift without locking out a new hire.
In XShift AI a rest rule reads the end time of the last shift before the one being saved and works out the real gap in hours. Smaller than your minimum, and the shift is blocked. If there is no earlier shift to measure against, the rule does not fire, so a new starter is never caught by it.
Put a floor under rest between shifts. Book a demo
7.Stop the same people working every single weekend
Weekends are the shifts people plan their lives around, and they land on the same three names every week because those three always say yes.
Schedule instability turns out to be a strong predictor of somebody quitting, in a study of 1,827 hourly retail and food service workers (Choper, Schneider and Harknett, ILR Review, 2022). Lose the person who always says yes and you have lost every future weekend they would have covered for you.
Last weekend
This weekend
What to do
Check whether the person worked the weekend before or the weekend after before you put them on a Saturday or a Sunday.
What the software has to handle
The tool has to look at the weekend before and the weekend after the shift, count somebody who worked only the Saturday as having worked that weekend, and treat approved leave as a weekend off rather than a turn used up.
XShift AI handles all three. A back-to-back weekends rule fires only when the shift falls on a Saturday or Sunday, checks whether that person worked any day of the weekend before or after, and blocks it if they did. Working just the Saturday still counts, so it cannot be dodged by handing everybody Saturdays. Somebody on approved leave last weekend has no shifts on those dates, so their leave counts as their weekend off. Spreading the hours themselves is a different job, and it has its own article below.
Stop the same people losing every weekend
8.Give every shift a headcount for each role
If you take one thing from how to make a shift schedule, take this. A shift is not covered when somebody is on it. It is covered when each role has the number of people that role needs, so four people on a shift wanting two of one role and two of another is only covered if they are the right four.
Let’s say you put one extra person on three shifts a week. 8 hours × $20 = $160 a shift, so $480 a week and $24,960 a year, spent on people the work did not need. Go the other way and everybody else covers more than they can, which is where slow service and the bad review start.
What to do
Decide how many people in each role a shift needs, write it down per location or per time window, and fill to that number exactly.
What the software has to handle
The tool has to hold a number per role rather than per shift, let it differ by location, let it differ again for a day and time window, and stop filling the moment the number is met.
In XShift AI you set that number through the AI Copilot, one of three ways. Per role for a location, per role for a day and a time window, or on one individual shift. Where a time window applies it overrides the location number for the hours it covers. Filling shifts, XShift AI fills each role separately and stops at that role’s count. Ask the AI Copilot which shifts are short and it lists every one with fewer people than it needs.
Fill every role to the number it needs
9.Decide who is allowed to cover a call-off before anyone calls off
A call-off does not cost you the missing person. It costs you the twenty minutes after the call, when you are working out who is even allowed to take the shift with nothing to check against.
If I am ringing people, I have already lost. That decision should have been made weeks earlier.
Let’s say you get two a week at 20 minutes each. That is 40 minutes a week, and the first person who answers is usually the one already near 40 hours. So the cover costs time and a half on top, and next week you will ring the same three people.
What to do
Write the order you rule people out in. Work it the same way every time instead of phoning whoever you remember first.
What the software has to handle
A tool that handles call-outs has to rule people out in a fixed order, then decide what to do with whoever is left. Here is the same job done two ways.
By phone
- You remember three names
- You do not know who is off that day
- You do not know who is already working
- You do not know who is on approved leave
- You do not know anyone’s hours this week
- The first yes wins, whatever it costs
- Nobody answers and you cover it yourself
On Autopilot, in this order
- Attached to this location
- Holds the role the shift needs
- Has not marked that day unavailable
- Has not blocked off those hours
- Passes every rule you wrote
- Not already on a shift then
- Not on approved time off
XShift AI is the scheduling software that covers call-offs automatically, once you switch call-off coverage on. Whoever survives those seven checks gets sorted so the people who stay under overtime go first. If the shift is at least the number of days away you set, seven unless you change it, Autopilot gives it to the first person outright. Sooner, and every qualified person can take it in one tap. If nobody qualifies, every manager gets an email naming each person and the exact reason.
Watch a call-off get covered without a phone call
10.Answer time off by rules, not by who asked
Time off feels fair to the person who asked and unfair to everybody else, because everybody else only sees the answer. The fix is not to be more generous. It is to decide by a rule written down before anybody asked.
Let’s say 40 people send 10 requests a week at 5 minutes each. That is 50 minutes a week of deciding, and two identical requests can still get two different answers. The person who got the no remembers it for a year.
What to do
Write down the notice you need, the dates nobody gets off, how many requests one person may make and how many people may be off at once.
What the software has to handle
The tool needs four things: the notice a request must carry, the dates nobody gets off, how many requests one person may make in a period, and how many people may already be off on those dates.
Sent 20 days ahead
Approved on submission
Your 14 days notice rule
Asks for December 24
Denied on submission
Your blackout dates rule
Their third request this month
Denied on submission
Your two a month rule
Three people already off that day
Denied on submission
Your overlap rule
In XShift AI those four are Autopilot rules written as sentences, and the highest ranked rule that matches decides the moment the request is submitted. It records which rule decided, so you can point at it a month later. If no rule matches, the managers who cover that person’s location get an email and decide it themselves. Approved time off is then never scheduled over when XShift AI builds the week or covers a call-off.
Let the same rule answer every request
11.Post the schedule with real notice, and tell people when it changes
Posting the schedule is not the end of the job. Two things decide whether it lands: how far ahead it goes out, and whether each person received their own shifts instead of being expected to go and look.
I would never post a week on a Thursday for a Monday start. That is not notice, that is a warning.
The Shift Project at the Harvard Kennedy School surveys hourly service workers. The numbers on notice are not close.
60%
received less than two weeks of notice of their schedules
57%
had last-minute changes to the timing of their shifts
66%
would prefer a more predictable schedule
Source: The Shift Project, Harvard Kennedy School. Notice is the cheapest thing on this whole page to fix, and it is the one people actually quit over.
What to do
Pick how far ahead you post. Publish only shifts that are fully staffed, and send every person their own shifts instead of pinning one sheet up.
What the software has to handle
The tool has to stop you publishing a week that is not finished, send every person their own shifts rather than one notice to everybody, and tell somebody directly when their shift changes later.
In XShift AI, publishing only moves the shifts that are fully staffed. A shift still needing one more person stays in draft, so a half-finished week never goes out looking finished, and you are told how many are short. Every person assigned to a newly published shift is notified, and anyone a manager adds to a shift later gets their own email. The AI Copilot also posts an announcement to the whole team from one sentence.
Build the week in seconds and post it early
12.Write your rules down once so they run without you
Every rule on this page is currently in somebody’s head. That works until the person is on holiday, or the new assistant manager builds a week, or it is late and you just want the grid finished.
If I could fix one thing on this page, it would be this one.
A rule nobody wrote down gets enforced about as often as you remember it. And the week it gets forgotten is the week it costs you, because the whole reason the rule existed was the thing it was quietly stopping.
What to do
Turn each rule you keep in your head into one written sentence, put them in order, and apply them to every shift anyone saves.
What the software has to handle
So the last thing to look for is software where your own rules are the thing being enforced, in your own words, on every path a shift can be created. Here is what a written rule can say.
You write the sentence. Autopilot does the checking.
15 rules“Nobody works more than 40 hours a week”
Adds the shift to that week and blocks it over the cap
“Nobody works more than 5 shifts a week”
Counts their shifts and blocks the sixth
“No shift longer than 10 hours”
Measures the shift and blocks a longer one
“Never put anyone into overtime”
Uses your threshold and blocks the crossing shift
“Keep the week under $12,000 in wages”
Prices the shift and blocks it over the number
“Keep Saturday under $2,000 in wages”
Does the same for that single day
“Nobody starts within 10 hours of finishing”
Reads the last end time and blocks the short turnaround
“No more than 6 days in a row”
Counts days at any location and blocks the seventh
“Nobody works two weekends in a row”
Checks the weekend either side and blocks the repeat
“Alex and Sam never work together”
Blocks the second onto a shift the first holds
“Approve time off with 14 days notice”
Counts the notice and approves on submission
“Deny time off from December 20 to 31”
Checks the dates touched and denies it
“No more than 2 time off requests a month”
Counts their requests and denies the next
“Deny it when 3 people are already off”
Counts who is approved off and denies it
“Only apply this rule on Fridays and Saturdays”
Reads the day the shift falls on
This is what AI employee scheduling software should mean: you type the rule in plain English and XShift AI turns it into something it can check. You put the rules in the order you want them applied, and the top one that matches decides. For example, say you write “no more than 6 days in a row”. From then on, a shift that would be somebody’s seventh straight day is refused, whether XShift AI was generating the week, covering a call-off, or a manager was saving that shift by hand. You decide whether crossing the line stops the shift or lets a manager push it through, and it records who did.
Write one rule and watch it hold. Book a demo
What running all twelve on XShift AI costs
XShift AI is $29 a month plus $1 per active user after the first, after the free trial of 21 days. Every manager counts as a user.
12 staff and 2 managers is 14 users: $29 + (13 × $1) = $42 a month
40 staff and 2 managers is 42 users: $29 + (41 × $1) = $70 a month
The overtime in tip three alone came to $26,000 a year in the example. $70 a month is $840 a year, so one of the twelve tips pays for the whole thing about 31 times over.
These staff scheduling best practices cost nothing to adopt, and that is really all there is to how to do scheduling for employees. The best employee scheduling software is simply the one that still holds them at eleven at night, when you have stopped.
Picture next Sunday. The week is built, every person checked against all twenty constraints, your rules held without you in the room. That is the evening back, every week. Get fully set up in minutes: paste your staff list into the AI Copilot, upload a spreadsheet of it, or take a photo of the one you have. Keep your current tool running while you look. Every feature is on the features page, and the pricing page has the rest.
Frequently asked questions
What is the best scheduling software for small teams?
XShift AI is the best scheduling software for small teams because one person can run the whole schedule from plain sentences. Type "Build next week and spread the hours evenly" and the AI Copilot fills your shifts in seconds, checking location, approved time off, blocked days and hours, overlapping shifts and the role each shift needs. Write "no more than 40 hours a week" and Autopilot blocks any shift that breaks it. It is $29 a month plus $1 per active user after the first, after the free trial of 21 days.
How do I schedule employees effectively?
Use XShift AI to run the same checks on every person, for every shift, in the same order. Filling a shift, it rules out anyone not attached to that location, anyone on approved time off, anyone who blocked that day or those hours, anyone already on an overlapping shift and anyone without the role. Then it applies the rules you wrote and stops at the headcount each role needs. Fair mode gives the next shift to whoever holds the fewest hours.
What scheduling software enforces hour limits?
XShift AI is the scheduling software that enforces hour limits, through Autopilot rules you write as sentences. A weekly hour rule adds the new shift to the hours that person already holds that week and blocks it over your number. A shift-count rule caps shifts per week. A shift-length rule caps one shift. An overtime rule uses your own threshold, 40 hours unless you change it. All four run when the software builds the week, covers a call-off, or a manager saves a shift by hand.
How do I stop scheduling someone who is unavailable?
Use XShift AI to record availability once and check it automatically. Each person gets the days they can never work and the hours they are blocked on the days they can. Building the schedule or covering a call-off, XShift AI will never put somebody on a day they blocked, never inside hours they blocked, and never on top of a shift they already have. With that in place, how to schedule around employee availability stops being a memory test.
How do I avoid overtime when scheduling employees?
Use XShift AI, the scheduling software that blocks overtime before it is booked instead of reporting it afterwards. An Autopilot overtime rule adds the shift you are saving to that person’s hours for the week and blocks it if the total crosses your threshold, 40 hours unless you set another. The Overtime Agent then scans the week you already built, flags anyone past the threshold with the estimated cost and finds a swap at the same location and role. Nothing moves until a manager approves it.
How do I cover a call-off without phoning around?
Use XShift AI’s Autopilot to cover call-offs automatically, once call-off coverage is switched on. When someone gives up a shift it works one list in order: it drops anyone not attached to that location, anyone without the role, anyone who blocked that day, anyone whose blocked hours overlap it, anyone a rule blocks, anyone already working then, and anyone on approved time off. People who stay under overtime go first. If nobody qualifies, every manager gets an email naming each person and the reason.
How do I handle employee time off requests fairly?
Use XShift AI’s Autopilot to decide time off by rules, so the answer never depends on who asked. A rule can require days of notice, deny any request touching a date range you name, deny it when that person already made a set number of requests this month, quarter or year, or deny it when a set number of people are already off. The highest ranked matching rule decides on submission and records which rule decided.
How far in advance should I post the employee schedule?
Post it far enough ahead that people can plan around it, and use XShift AI to make that possible by building the week in seconds. The Shift Project at the Harvard Kennedy School found 60 percent of hourly service workers received less than two weeks of notice, 57 percent had last-minute changes to shift timing, and 66 percent would prefer a more predictable schedule. In XShift AI, publishing moves only fully staffed shifts, and everyone on a newly published shift is notified.
How long should it take to build an employee schedule?
With XShift AI it takes seconds, because you type one sentence and it fills the shifts you already have. By hand it means checking every person against every shift from memory: location, time off, days off, blocked hours, overlapping shifts, role, hours so far, days in a row, rest and cost. The AI Copilot runs those checks, orders people by hours worked and stops at each role’s headcount. Get fully set up in minutes by pasting your staff list or a photo of it.
When does overtime start for hourly employees?
Under the federal Fair Labor Standards Act, covered employees "must receive overtime pay for hours worked over 40 in a workweek at a rate not less than time and one-half their regular rates of pay," according to the US Department of Labor. A workweek is a fixed, regularly recurring period of 168 hours, so it need not start on a Monday. Some states add their own rules, including daily overtime, so check where your business operates.