FirstHR

How to Make a Work Schedule

How to make a work schedule for your small business: a 7-step guide to forecast coverage, stay compliant, and avoid overtime. Free template included.

How to Make a Work Schedule

A step-by-step guide for a small business owner building shift schedules without an HR department

The first schedule I ever built took me most of a Sunday, and it was still wrong by Wednesday. I had guessed at how busy we would be, forgotten that two people had asked for the same day off, and accidentally scheduled someone into overtime I had not budgeted for. The problem was not that scheduling is hard. It was that I was building it backward, starting from a blank grid and filling names in, instead of starting from what the business actually needed and working out from there.

Making a work schedule means turning your coverage needs, your team's availability, and the relevant labor rules into a clear plan of who works when, published early enough for everyone to rely on. Most guides on this either sell you software or bury the practical steps under productivity theory. This one walks you through the actual sequence, built for a small business owner or manager doing this without a dedicated HR department, and it ends with a free template you can copy and use today.

Below you will find what making a schedule really involves, what to line up before you start, the seven steps that turn demand into a published schedule, an honest look at paper versus spreadsheet versus software, the compliance you actually need to know (which is less than the enterprise guides imply), the mistakes to avoid, and a ready-to-use template. I build scheduling alongside onboarding, time tracking, and time-off into FirstHR, because a schedule works best when it connects to the rest of your people operations rather than sitting in a silo. This is general information, not legal advice, so confirm the specifics for your state and city.

TL;DR
To make a work schedule, follow a repeatable sequence: forecast coverage from demand, collect availability and time-off requests, set your rules and check the wage-and-hour basics, build the schedule (fixed shifts first, then peak coverage, then gaps), balance labor cost and fairness, publish it in advance, and review it afterward. Start from what the business needs, not from a blank grid. The only federal rule that really binds you is FLSA overtime (time and a half over 40 hours a week for non-exempt staff); advance-notice fair-workweek laws exist in Oregon and some cities but mostly cover large employers. Use a spreadsheet while your team is small and simple, and move to software once availability, changes, and overtime get hard to track by hand.

What Making a Work Schedule Actually Means

Making a work schedule is the process of deciding who works which shifts over a defined period, based on your coverage needs and your team's availability, and communicating that plan in advance. It is not just filling in a grid; it is a small planning exercise that balances three things at once: what the business needs, what your people can and want to work, and what the law requires.

Definition
Making a Work Schedule
Making a work schedule is the process of assigning employees to shifts across a defined period so the business has the coverage it needs, while respecting employee availability, controlling labor cost, and complying with wage-and-hour law. It runs from forecasting demand through publishing the finished schedule to reviewing it afterward. Done well, it produces reliable coverage, fair and predictable shifts for the team, and controlled costs, without consuming the manager's week.

The distinction worth drawing early is between a work schedule and a personal schedule. A personal daily or weekly schedule is about organizing your own time and tasks. A work schedule, in the sense this guide means, is about staffing a business: an employer assigning a team to shifts. This guide is squarely about the second one, the owner or manager's job of building shift coverage for hourly staff in a shop, restaurant, clinic, or similar small business, which is one part of the broader topic of work schedules.

What makes a schedule good is not elegance; it is that it holds up. A good schedule covers your busy periods without overstaffing the slow ones, respects the availability people gave you, keeps labor cost and overtime in check, and reaches everyone early enough that they can plan around it. Every step below exists to serve one of those outcomes, which is why treating scheduling as a sequence rather than a guessing game makes it so much less painful.

Before You Start: What to Line Up First

Almost every scheduling headache traces back to starting without the right information in front of you. Before you place a single shift, gather three things, because building a schedule without them is exactly the backward approach that cost me that ruined Sunday.

The first is your demand picture: when is the business actually busy, and how many people does each period need? For most small businesses this comes from experience and simple records, sales by hour, foot traffic, appointment volume, or bookings. The second is availability: when each employee can and cannot work, plus any approved time off, ideally collected in one place before you build rather than discovered mid-schedule. The third is your own rules: maximum hours per person, minimum notice for swaps, who can work which roles, and any preferences you honor. With those three in hand, scheduling becomes assembly rather than invention, which is the heart of good staffing and scheduling.

Collect Availability Once, Not Every Week
The single biggest time-saver is having a standing record of each person's availability and recurring constraints, updated only when something changes, rather than re-asking everyone every week. When availability lives in the same place as your team's employee records, building the next schedule starts from a known picture instead of a round of texts. That one habit turns scheduling from a weekly investigation into a quick assembly job.

The 7 Steps to Build a Work Schedule

Here is the sequence that turns demand and availability into a published schedule. It mirrors how experienced managers build schedules across retail, restaurants, and healthcare, and it works whether your tool is a whiteboard, a spreadsheet, or software. Here is the whole thing at a glance before we walk each step.

1. Forecast coverageWork out how many people you need, when, based on demand.
2. Collect availabilityGather everyone's availability and time-off requests first.
3. Set rules and check lawsDecide your scheduling rules and know the wage-and-hour basics.
4. Build the schedulePlace fixed shifts, cover the peaks, then fill the gaps.
5. Balance cost and fairnessWatch overtime and spread shifts evenly across the team.
6. Publish in advancePost the schedule early and communicate it clearly.
7. Review and adjustGet feedback, fix what broke, and improve the next one.
1
Forecast your coverage needs
Start from demand: for each day and time block, decide how many people (and which roles) you need, using sales data, foot traffic, bookings, or experience. This is the foundation everything else builds on.
2
Collect availability and time-off requests
Before assigning anyone, gather each person's availability and approved time off in one place. Building around known constraints beats discovering conflicts after you have published.
3
Set your scheduling rules and check the law
Decide your rules (max hours, notice for swaps, role coverage) and know the basics: FLSA overtime over 40 hours a week, plus any state or city scheduling rules that apply to you.
4
Build the schedule from fixed points outward
Place the shifts you know first (fixed roles, opening and closing), then cover your peak periods, then fill remaining gaps. Working outward from certainty is faster than filling a blank grid randomly.
5
Balance labor cost and fairness
As you assign, track each person's weekly hours to avoid unplanned overtime, and spread desirable and undesirable shifts evenly so no one feels singled out. Both cost and morale live here.
6
Publish the schedule in advance
Post the finished schedule early, at least a week or two out where you can, and communicate it clearly so everyone sees it and can raise conflicts before the week starts.
7
Review, get feedback, and adjust
After the week, note what broke: where you were short, where you overstaffed, which swaps happened. Feed that back into the next schedule so each one is better than the last.

The order matters more than any single step. Forecasting before availability, availability before building, and building before publishing each prevent a specific, common failure: overstaffing a slow day, scheduling someone who was off, or dropping a finished schedule on people with no notice. Follow the sequence and most scheduling problems never occur in the first place.

Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Paper vs Spreadsheet vs Software

You can build a schedule three ways, and the right choice depends entirely on your size and complexity rather than on which is objectively best. Each has a real place, and moving up the ladder only makes sense when the current tool starts costing you more than it saves.

MethodBest forWhere it breaks down
Paper / whiteboardTiny teams, one location, fixed shiftsNo history, easy to lose, hard to share or change
SpreadsheetSmall stable teams comfortable with manual entryAvailability, overtime, and changes get hard to track by hand
Scheduling softwareGrowing teams, variable shifts, multiple constraintsCost and setup, though most is offset by time saved

Paper or a whiteboard genuinely works for a very small team with simple, repeating shifts, and there is no shame in it. A spreadsheet is the natural next step: list employees down one side, days across the top, and you have a shareable, reusable schedule with a bit of formula help for totaling hours. Most small businesses start and stay here for a while, and a good template (like the one at the end of this guide) covers a lot of ground, whatever type of work schedule you run.

Software earns its place when the manual approach starts breaking down: when you are juggling many availability constraints, frequent changes, and overtime risk, and a spreadsheet can no longer keep up without errors. Scheduling software centralizes availability, prevents double-booking, totals hours and flags overtime before it happens, and pushes the schedule to everyone instantly. The strongest setups connect scheduling to time and attendance and time-off, so the schedule, the hours actually worked, and approved leave all line up. For most small businesses the move to software comes when scheduling regularly eats real time or when a spreadsheet starts producing mistakes that cost you coverage or pay.

The Compliance You Actually Need (Less Than You Think)

Scheduling compliance sounds intimidating, but for most small businesses it comes down to one federal rule plus a check on your local laws. The enterprise guides pile on requirements that mostly apply to large employers, so the useful move is separating what actually binds you from what does not.

The one rule that applies to nearly everyone is overtime. Under the Fair Labor Standards Act, non-exempt employees must receive overtime pay at not less than one and a half times their regular rate for hours worked over 40 in a workweek, per the Department of Labor. There is no federal cap on hours for adults and no federal requirement to pay extra for nights, weekends, or long days; overtime is purely about crossing 40 hours in a workweek. This is why watching weekly hours as you build the schedule is the core compliance habit for a small business, and it ties directly to the exempt vs non-exempt distinction that determines who is owed overtime.

Overtime Is About the Workweek, Not the Day
Federal overtime under the FLSA is triggered by more than 40 hours in a workweek (a fixed, recurring 168-hour period), paid at 1.5x the regular rate for non-exempt employees, per the Department of Labor. There is no federal daily overtime and no federal premium for nights or weekends. A few states add their own rules, most notably California, which requires overtime after 8 hours in a day, so confirm your state's standard. The federal minimum wage is $7.25 per hour, though many states set a higher one.

The other area to check is predictive scheduling, also called fair workweek, and here is the reassuring part: it probably does not apply to you. These laws require posting schedules 14 days in advance and paying a premium for last-minute changes, but they mostly cover large employers in retail, hospitality, and food service. Oregon is the only state with a statewide law, and it applies to employers with 500 or more employees; the rest are a handful of cities. Around a dozen jurisdictions have such laws, and separately, eleven states actively ban local versions, so a typical small business is usually not covered either way; the full picture is in the guide to predictive scheduling laws.

Fair-Workweek Laws Mostly Miss Small Business, But Check Your City
Predictive-scheduling laws generally target large employers. Oregon's statewide law covers retail, hospitality, and food-service employers with 500 or more employees; city ordinances (in places like Seattle, Chicago, Philadelphia, New York City, San Francisco, and Los Angeles County) set their own thresholds, often in the hundreds of employees, per the Oregon Bureau of Labor and Industries. Most require 14 days' notice and premium pay for changes; NYC retail requires 72 hours. Eleven states preempt (ban) local versions entirely. The practical takeaway: a small business is usually not covered, so do not over-comply, but confirm your specific city if you are in one of these jurisdictions.

So the honest compliance picture for a small business is short: pay overtime correctly by watching the 40-hour line, and check whether your specific city has a scheduling ordinance (most owners find they do not). Beyond that, keep good records of hours and schedules, which protects you in any wage dispute and connects to the wider Fair Labor Standards Act framework. That is genuinely most of it, which is a relief given how the topic is usually presented.

Common Scheduling Mistakes to Avoid

A handful of mistakes account for most scheduling pain, and all of them are avoidable once you know to watch for them. Recognizing these ahead of time is often more useful than any single technique, because it heads off the failures before they reach your team.

The most common is building from a blank grid instead of from demand, which produces schedules that overstaff slow periods and leave peaks short. Close behind is publishing late, which forces swaps and no-shows because people cannot plan; a consistent advance schedule prevents most of that friction. Then there is ignoring availability you already collected, double-booking someone who was off, which erodes trust fast on a small team. And a quiet but expensive one is not tracking weekly hours as you build, so overtime creeps in unnoticed and inflates labor cost, which is where accurate timesheets pay off.

Two more are worth naming. Concentrating the good and bad shifts unfairly, always giving one person the closing shifts or the weekends, breeds resentment even if no rule is broken, so spread them deliberately. And treating the schedule as fire-and-forget, never reviewing what actually happened, means you repeat the same misjudgments week after week. A short post-week review, noting where you were short or overstaffed, is what turns scheduling into something that improves rather than a recurring gamble. The through-line: schedules fail from process gaps, not from bad luck, which means a better process fixes them.

Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Free Work Schedule Template

Here is a simple weekly schedule template you can copy into a spreadsheet or use as-is. It lists employees down the side and days across the top, with space to total weekly hours per person so you can catch overtime before it happens. Fill it in following the seven steps above, and it will cover most small-team scheduling needs.

Weekly Work Schedule Template
WEEKLY WORK SCHEDULE

Business: Location: Week of: to
Schedule published on: (aim: at least 1 to 2 weeks ahead)
COVERAGE PLAN (fill this first, from demand)

Mon: people needed by time block: _______
Tue: people needed by time block: _______
Wed: people needed by time block: _______
Thu: people needed by time block: _______
Fri: people needed by time block: _______
Sat: people needed by time block: _______
Sun: people needed by time block: _______
SHIFT GRID (enter start-end times per person, per day)

Employee | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Total hrs
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
OVERTIME CHECK

Any employee over 40 hours this week? _______
If yes, adjust before publishing (overtime is 1.5x over 40 hrs/week)
TIME OFF AND AVAILABILITY NOTES

Approved time off this week: _______
Availability constraints to remember: _______
BEFORE YOU PUBLISH

[ ] Every needed time block is covered
[ ] No one scheduled who requested off
[ ] No unplanned overtime
[ ] Shifts spread fairly across the team
[ ] Schedule sent to everyone with time to plan

Save this as your reusable base and copy it each week; most of it stays the same, so scheduling becomes editing rather than starting over. When copying and totaling hours by hand starts to feel like a chore, or you begin hiring across roles and constraints, that is the signal to move from this template into a scheduling tool that does the totaling, conflict-checking, and communicating for you, which connects to running HR for a small business as one system.

What worked for me
What finally fixed my ruined-Sunday problem was not a better spreadsheet; it was changing the order I worked in. Once I started by writing down how many people each shift actually needed, before touching names, the rest fell into place fast, because I was placing people against real coverage instead of guessing. The other change was pulling availability and time off into the same place as the schedule, so I stopped double-booking people who had asked for a day off. The tool mattered far less than the sequence. When I later moved scheduling into the same system as time tracking and time-off, the whole thing went from a dreaded weekend job to a fifteen-minute edit, mostly because the information I needed was finally all in one place.
Key Takeaways
Making a work schedule means turning coverage needs, availability, and labor rules into a clear plan of who works when, published in advance. Start from demand, not a blank grid.
The seven steps: forecast coverage, collect availability, set rules and check laws, build from fixed points outward, balance cost and fairness, publish early, then review and adjust.
Line up three things before you build: your demand picture, everyone's availability and time off, and your own scheduling rules. Missing any one causes most scheduling problems.
Use paper or a spreadsheet while your team is small and stable; move to software once availability, changes, and overtime get hard to track by hand.
The compliance that really binds a small business is short: pay FLSA overtime (1.5x over 40 hours a week for non-exempt staff) and check your city, since fair-workweek laws mostly cover large employers.
Avoid the common mistakes: building from a blank grid, publishing late, ignoring availability, letting overtime creep in, distributing shifts unfairly, and never reviewing what happened.

Frequently Asked Questions

How do I make a work schedule for my employees?

Making a work schedule comes down to a repeatable sequence: forecast how many people you need and when, collect everyone's availability and time-off requests, set your scheduling rules, build the schedule by placing fixed shifts first and then covering peaks, balance labor cost and fairness, publish it in advance, and review it afterward. Start from demand, not from a blank grid. For a small team you can do this in a spreadsheet or a simple scheduling tool. The goal is a schedule that covers your busy periods, respects availability, avoids surprise overtime, and reaches your team early enough to plan around.

How far in advance should I publish a work schedule?

Publish as far ahead as you reasonably can, and at least one to two weeks is a good target for most small businesses. Even where no law requires it, advance notice reduces no-shows, swap requests, and last-minute scrambling, because people can plan their lives around known shifts. Some cities and one state (Oregon) legally require 14 days' advance notice under fair-workweek laws, but those generally apply to large employers in retail, hospitality, and food service, so most small businesses are not covered. Regardless of the law, a consistent two-week schedule is simply good practice that your team will appreciate.

What is the best way to make an employee schedule?

The best method depends on your size. A very small, stable team can manage with a spreadsheet template that lists employees down one side and days across the top. As you grow, add more shifts, or deal with availability and time-off requests, scheduling software becomes worth it because it handles availability, prevents double-booking, flags overtime, and lets employees see the schedule instantly. Whatever the tool, the process is the same: start from demand, respect availability, avoid overtime, and publish early. The tool should serve the process, not replace thinking about coverage.

Do I need scheduling software or is a spreadsheet enough?

A spreadsheet is genuinely enough for a small, stable team with simple, repeating shifts. It becomes a liability once you are juggling many availability constraints, frequent changes, time-off requests, and overtime risk by hand, at which point errors and time cost more than software would. The signal to switch is when building and communicating the schedule regularly eats your time or produces mistakes. Software centralizes availability, prevents conflicts, flags overtime before it happens, and pushes the schedule to everyone automatically, which is where it earns its place for a growing team.

What laws do I need to know when making a schedule?

The main federal rule is the Fair Labor Standards Act, which requires overtime pay at one and a half times the regular rate for hours worked over 40 in a workweek for non-exempt employees. There is no federal law requiring advance notice of schedules. Some cities and Oregon have predictive-scheduling or fair-workweek laws requiring 14 days' notice and premium pay for changes, but these mostly cover large employers in specific industries, so most small businesses are not subject to them. Check your state and city rules, since a handful of states also have their own requirements. This is general information, not legal advice.

How do I avoid overtime when scheduling?

Avoiding unplanned overtime starts with watching weekly hours as you build the schedule, since federal overtime is triggered by more than 40 hours in a workweek for non-exempt employees. Track each person's scheduled hours as you assign shifts, spread coverage across enough people rather than overloading a few, and leave a small buffer so covering a sick day does not push someone over 40. Cross-training helps, because more people who can cover a shift means fewer forced overtime hours. Scheduling tools that total hours as you build and warn you before someone crosses 40 make this far easier than doing the math by hand.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial