Scheduling Two Locations Without Two Schedules

The second location changes less than you expect and costs more than you expect. Most of what you do stays the same: you still build a schedule around demand, availability and time off. What changes is that one person's hours can now be split across two places, and the law counts all of them together. A spreadsheet or a per-site tool that shows each location on its own will not.

If you are opening a second site, or already run two and share people between them, this post covers the four things that genuinely change: overtime, travel time, who owns each schedule, and how you compare software that prices by location.

Does overtime get calculated per location or per employee?

Per employee. The federal rule is that an employer must "total all the hours worked by the employee for him in that workweek (even though two or more unrelated job assignments may have been performed)" and pay overtime on every hour past the limit. That language comes from 29 CFR 778.103, and it is the most expensive sentence in multi-site scheduling.

The threshold itself is simple. The Department of Labor's overtime fact sheet says covered employees must receive overtime for hours worked over 40 in a workweek, at not less than time and one-half their regular rate. A workweek is "a fixed and regularly recurring period of 168 hours," it can start on any day, and averaging hours across two or more weeks is not permitted.

Nothing in that rule cares which address the person clocked in at. If both locations are the same business, one person working at both is one employee with one set of hours.

What does that look like with real numbers?

Take a hypothetical employee, Maya, who earns $18 an hour and works 26 hours at your downtown location and 18 hours at the new one in the same workweek.

Each site's schedule looks fine on its own. 26 hours is part-time. 18 hours is a few shifts. Neither view shows overtime. Together, Maya worked 44 hours, and 4 of them are overtime.

The per-site view is $36 short for one person in one week. That is small on paper and large in practice, because the shortfall repeats every week, it scales with every person you share, and it is the kind of error that shows up in a back-wage claim rather than in a budget review. With a per-site view, nothing flags it until payroll, after the schedule has already been published and worked.

Maya is hypothetical, but overtime slipping through a manual schedule is not. We've had customers managing their schedules by hand in Google Sheets or Excel struggle to keep track of overtime, and depending on the size of the business and its workforce, it can cost hundreds or even thousands of dollars. A second location makes that tracking harder, because the hours that add up to overtime now sit in two places. It's one of the reasons I don't see a dedicated scheduling tool as an added cost: it goes after money you're already spending on overtime you didn't need.

What if the two sites pay different rates?

Then the overtime rate is not simply time and a half of either site's wage. 29 CFR 778.115 says that when an employee works at different rates in one week, total earnings from all rates are added up and divided by the total hours worked at all jobs. That gives a weighted average regular rate, and the overtime premium is built on that blended figure.

Change the example: Maya earns $18 at site A (26 hours) and $22 at site B (18 hours). Straight-time earnings are $468 plus $396, which is $864 for 44 hours, so her regular rate for the week is about $19.64. The overtime premium is half of that for each of the 4 overtime hours, roughly $39.27, for a total of about $903.27. Neither site's rate produces that number by itself.

This is another reason to put one person's hours in one place. If the two locations run separate schedules and separate time reports, somebody has to do this blending by hand every week.

Is travel between my two locations paid time?

Yes, when it happens during the workday. The Department of Labor's hours worked fact sheet says "travel from job site to job site during the workday, is work time and must be counted as hours worked." The regulation behind it, 29 CFR 785.38, says the same thing.

The same fact sheet draws the other line: ordinary travel from home before the workday and back home afterwards is not work time. So the question for any trip is whether it is a commute or a transfer between jobs.

Three situations come up constantly:

• Home to site A, then home from site B. Commuting. Not paid.
• Site A to site B in the middle of a day. Paid, and it counts toward the 40.
• Site A at 9, home for lunch, then site B at 2. This is where the answer depends on facts. The more the person was free to use that time as their own, the closer it looks to a commute. If you sent them from A to B and they stopped on the way, treat it as a paid transfer, and ask your payroll provider or an attorney about the edge cases.

Back to Maya. Suppose she covers three days that include a half-hour trip between sites, so 1.5 hours of paid travel. Her week is 45.5 hours, which means 5.5 overtime hours, not 4. At $18 an hour that comes to $868.50 for the week against the $792 the per-site view would have paid, a gap of $76.50.

Travel time is also a scheduling cost you can design away. Two sites ten minutes apart can swap people on a split day cheaply. Two sites forty minutes apart cannot, and every cross-site shift you publish carries paid driving time that no one budgeted. Before you let people float, decide which sites can share staff, and write the real travel time into the schedule as hours.

Do state rules change the answer?

They can, and California and New York both add something.

California measures overtime by the day as well as the week. According to the state's Division of Labor Standards Enforcement, hours beyond 8 in a workday are paid at one and a half times the regular rate, hours beyond 12 at double, and the seventh consecutive day carries its own premium. That makes the two-site problem worse. A person who works 6 hours at one location in the morning and 4 hours at the other in the afternoon has worked a 10-hour day, so 2 of those hours are overtime even though neither site had a long shift and the week is nowhere near 40.

California also treats travel the employer requires as paid time. In a 2003 opinion letter on an employee with alternative worksites, the DLSE says travel the employer requires during the workday is compensated travel time, and it bases that on a 2000 California Supreme Court decision that separates travel the employer compels and controls from an ordinary commute. Opinion letters are informal guidance and this one is more than twenty years old, so check the current wage order for your industry before you rely on it.

New York's Department of Labor uses a weekly threshold for most employees: overtime for "all hours worked over 40 in a workweek," with a threshold of 44 for residential employees, meaning people who live in their employer's home. Its workweek definition is the same fixed 168-hour period the federal rule uses. The state FAQ does not address travel between locations, and it says New York's requirements apply in addition to federal law, so the federal travel rule above still applies. Anything stricter in your industry's wage order is worth confirming.

If you operate in a city or state with predictive scheduling rules, a second location can also change whether you are covered by them. Our guide to predictive scheduling laws covers where those apply, including the headcount and location thresholds that decide coverage.

Does joint employment matter if both sites are my business?

Usually not, and this is where older advice gets confusing. Joint employment rules deal with one worker employed by two separate employers. If both locations are run by the same legal entity, there is one employer and the hours are simply added.

Joint employment becomes a real question when the two sites are different companies. Say you own one location through one LLC and a partner owns the second through another, and the same person works both. The overtime regulation says that where an employee is employed jointly by two or more employers, all hours worked for them during the workweek must be totaled. Whether you are joint employers is a fact question, and it deserves a conversation with an employment lawyer before you set up shared staff across entities.

This part of the rules is moving. 29 CFR 778.103 still points to "part 791" for joint employment, but as of October 2026 the eCFR shows part 791 as reserved, with no text. The Department of Labor proposed a new joint employer rule in April 2026 that would put guidance back in part 791, but it is still a proposal, not a final rule. The principle in 778.103 stands either way. If your structure involves separate entities, do not lean on any summary that quotes the old part 791 as current, and check whether a final rule has been published since.

Who should own each location's schedule?

One person should own the combined view, even if two people own the pieces. This is the operational change that matters most at the second site.

From what I've seen, who ends up owning the schedule depends on the size of the business and even the industry. In healthcare, there are often dedicated roles for managing staff schedules. In a smaller retail or restaurant business, it's typically the owner or the general manager.

Some businesses split the work instead, with a manager at each location building and publishing their own schedule. That is a reasonable way to divide it, since site managers know their own demand. The failure happens at the seam. Manager A schedules Maya for 26 hours. Manager B, who cannot see Manager A's schedule, schedules her for 18. Neither did anything wrong, and you now owe overtime that nobody approved. An owner or general manager who builds both schedules can hit the same problem if each site lives in its own spreadsheet.

Three rules prevent most of it:

1. Decide who can claim a shared employee. Pick a home site for each person. The other site can request them, and a request that pushes the person past a threshold needs approval from whoever owns the budget.
2. Check combined hours before publishing, not after. The number that matters is the person's total across both sites. A weekly review on the day before each schedule goes out is enough if every manager can see it.
3. Keep availability in one place. If a person has availability on file at both locations, those can conflict, and a person who said they cannot work Thursday should not be bookable by the other site on Thursday.

If you want a starting point, our post on overtime policy covers the policy side, and how to calculate overtime walks through the arithmetic for a single site.

What should you ask a scheduling tool before you buy it?

Ask how it prices, then ask whether it can see across locations. Those are different questions and tools differ on both.

Pricing first. Some vendors charge per location and some charge per person. Per-location pricing is predictable when each site has its own team, and it becomes more expensive the moment you open a third site for four employees. Per-person pricing tracks headcount. Run both numbers for your real team in the plan you would actually buy, because add-ons for things like time clocks can change the comparison. Pricing pages change, so check the current page for anything you are comparing and write down the date.

I'll be upfront about where Shift Amp sits on this. We built its multi-location scheduling to save businesses money. Many of our competitors charge extra for each location, and we don't think that's fair to small businesses, so we set out to build a more affordable option that's also easier to use. As of October 2026, Shift Amp prices per user, however many locations you run, and multi-location scheduling is in both plans rather than sold as a higher tier. One person can be scheduled across several sites, with their hours and overtime totaled across all of them rather than per location.

Whichever tools you compare, these are the questions that matter for the second location:

• Can one employee appear on both schedules, with their hours totaled? If the tool treats each location as a separate account, it will not total anything.
• Does it warn you about overtime across sites before you publish? A warning after payroll closes is not a warning.
• Can a manager at one site see availability and hours at the other? And can you limit what they can edit?
• How does it handle a shift that starts at one site and ends at another? This tells you whether travel time has a place in the system at all.
• What does the time clock export look like? Payroll needs one row per person per week, not one per site.

Our roundup of employee scheduling apps is a good place to start your list before you test any of them with real data.

What does the Monday checklist look like?

If you run two sites today and you are not sure whether you are exposed, do these in order:

1. List every employee who worked at both locations in the last four weeks.
2. Total their hours for each workweek, using your actual payroll workweek start day.
3. Add paid travel time for any mid-day trips between sites.
4. Mark any week above 40 (or the daily limit if you are in California) and compare that to what was paid.
5. If you find a gap, talk to your payroll provider or an attorney about correcting it. This is not a place for a quiet fix.

Then decide who owns the combined view going forward and what tool, if any, gives it to them.

This article is general information, not legal advice. Overtime and travel-time rules vary by state, city and industry and can change, so check the current rules for each of your locations or talk to an employment attorney.