Setting Up Shifts Without Losing Your Mind
Homebase Schedule Builder is part of the Homebase workforce management platform. It lets you create and publish employee schedules, swap shifts, and track availability. That's the surface-level description. The reality is a bit messier depending on how your team operates and what region you're in. I'll start with the actual workflow because most people don't need a definition — they need to know what buttons to click. Log into Homebase. Navigate to the Schedule tab on the left sidebar. You'll see a default view — weekly, with employees listed down the rows and days across the top. Click any open time slot and a small form pops up. You select the employee, set the start and end times, and optionally add a note or assign a specific role if your account has roles configured. Hit save and the shift appears on the board.
From there you can publish the schedule. Publishing sends notifications to employees through the app and email, depending on their settings. They can request time off from their end, swap shifts with coworkers if you've enabled that feature, or mark themselves unavailable. The swap feature is where things get interesting. Two employees can request a shift exchange directly in the app. As long as both parties agree, it auto-approves. No manager intervention needed. This saved me roughly two hours a week when I had a small team constantly asking me to facilitate trades over text. But here's the catch that nobody mentions. If your business has overtime rules based on daily hours rather than weekly hours — like California does — the builder doesn't flag it automatically. It calculates overtime on a standard weekly 40-hour basis by default. I ran into this when scheduling a bakery where my line cook kept getting 11-hour days, four days in a row. Homebase showed zero overtime flags because they never hit 40 in a single week. I had to export the schedule and manually cross-reference daily hours against state rules. Took me another hour on top of the normal scheduling time. There's no setting to turn on daily overtime alerts that I found. You have to do the math yourself.
If you're in a multi-state situation, this is going to be a recurring problem. The platform treats all locations under the same overtime configuration regardless of where employees actually work. My workaround was to keep a separate spreadsheet alongside Homebase for multi-state teams. I built it with simple formulas that summed daily hours and flagged anything over 8. It's not elegant, but it caught violations the platform missed. Another thing to know about the interface. The drag-and-drop shift moving works fine for small teams. Once you get past about 15 employees on a single board, it gets sluggish. Not broken, just noticeably delayed between clicks and visual updates. I learned this the hard way during a seasonal hiring push when we went from 10 to 28 people in a single week. Switched to keyboard-based entry for the bulk of the week — type the name, hit tab to move fields, enter to save. It's faster once you memorize the key sequence and it doesn't stall. Role-based scheduling is another feature that sounds useful until you try to use it. You can assign roles to shifts, which helps if your business distinguishes between different job types. The issue is that Homebase doesn't enforce role compatibility. Assigning someone to a role they haven't been trained for won't trigger any warning. The system trusts you to not put a cashier on a frying station shift. That's on you.
Get the Full Details
One more practical detail. The free plan includes basic scheduling. If you need anything beyond that — time tracking integration, labor cost forecasting, or multiple locations — you're on the paid tier. The scheduling itself works the same whether you're on free or paid. The limitations are around features that sit outside the schedule board. If you manage a single location with a small team and straightforward scheduling needs, Homebase Schedule Builder covers the basics without much friction. If you're running something with complex overtime rules, multi-state compliance, or 20-plus employees on one board, you'll want to build supplemental tools around it. The platform isn't going to solve every edge case for you.
