FirstHR

How to Make a Work Schedule: A Complete Guide

How to make a work schedule for your team: schedule types, a 7-step process, spreadsheet vs software, and the overtime and scheduling rules to know.

How to Make a Work Schedule

A step-by-step guide to building a schedule that covers your needs and stays compliant

Making a work schedule was, for the first year of running my business, the task I dreaded most. Every week I sat down with a spreadsheet, a list of who could work when, and a vague memory of who had asked for which day off.

Every week I got something wrong: a shift uncovered, someone scheduled on their kid's recital, an accidental 46-hour week that cost me overtime I had not planned for. Scheduling looks simple until you do it, and then it becomes clear how many moving parts have to line up.

A good work schedule does three things at once: it covers the business when it needs coverage, it respects the lives of the people working it, and it keeps you compliant and on budget. A repeatable process makes that far easier than starting from a blank page every week.

This guide walks through it step by step: what to gather first, a seven-step process, the types of schedules to choose from, how to build one in a spreadsheet, when to move to software, and the overtime and scheduling rules to keep in mind. I built FirstHR to hold the people side of scheduling: employee records, the written scheduling policy and each signed acknowledgment, while the schedule itself comes from the process below. This article is general information, not legal advice.

TL;DR
To make a work schedule, map your coverage needs, gather availability and time-off requests, pick a schedule type, assign shifts fairly, and watch weekly hours, since non-exempt staff earn overtime past 40 in a workweek. Build from a reusable template, and publish with as much notice as you can; fair workweek laws typically require 14 days.

What Is a Work Schedule?

A work schedule is a plan that sets out when employees are expected to work: their days, their shifts, and their hours. At its simplest, it answers a basic question for every person on the team: when do I need to be here?

For the business, the same document answers the mirror-image question: will I have the right number of people at the right times? A work schedule is the practical tool that matches staffing to demand.

Definition
Work Schedule
A work schedule is a plan specifying the days, shifts, and hours each employee is expected to work. It ensures the business has adequate coverage while telling employees when to report. Work schedules range from a simple fixed weekly pattern to complex rotating shift systems, and they are the primary tool employers use to align staffing with demand, manage labor costs, and meet compliance requirements.

Behind that simple definition sits a balancing act. A work schedule has to satisfy several goals that often pull against each other: enough coverage to run the business, fair and predictable hours for employees, controlled labor costs, and compliance with overtime and scheduling laws.

A schedule can fail in either direction. One that nails coverage but ignores employee availability generates constant conflict and turnover, and one that keeps everyone happy but leaves gaps fails the business. Good scheduling is the craft of satisfying all of these at once.

Work schedules come in many forms, from a fixed Monday-to-Friday office pattern to intricate rotating shift systems that keep a hospital or factory running around the clock. The right form depends entirely on the nature of the work and the pattern of demand.

Before You Build: What to Gather

Before you build, gather three inputs: your coverage needs, employee availability and time-off requests, and your policies. The biggest scheduling mistakes happen before a single shift is assigned, in the rush to start filling in a grid without the information the schedule depends on. Having all three ready turns scheduling into a straightforward assembly job and saves hours of rework.

The first is your coverage needs. Before thinking about people, map out demand: how many workers you need at each hour and each day, based on your busy and quiet periods. A restaurant needs more staff at dinner than mid-afternoon; a store needs more on weekends.

Coverage needs are the target the schedule has to hit, so define them first and build people around them rather than the other way around. If no arrangement of the people you have covers those needs, that is a staffing problem rather than a scheduling one.

The second is employee availability and time-off requests. Collect each person’s availability, standing commitments, and any requested time off before you start assigning shifts. Building a schedule and then discovering it conflicts with three people’s known constraints means starting over.

The third input is your policies: overtime rules, any predictive scheduling requirements in your area, and your own rules on shift swaps and time off. With coverage needs, availability, and policies in hand, the actual building goes quickly.

How to Make a Work Schedule in 7 Steps

With your coverage needs, availability, and policies gathered, building the schedule becomes a clear sequence. These seven steps work whether your team is small or mid-size, and whether you use a spreadsheet or software. The order matters: each step builds on the one before, and skipping ahead is where scheduling goes wrong.

1
Determine your coverage needs
Start with demand, not people. Map out how many workers you need at each hour and day, based on your busy and slow periods. This is the foundation the whole schedule is built on.
2
Gather availability and time-off requests
Collect each employee's availability, standing commitments, and any requested time off before you build. Building around known constraints from the start avoids immediate rework.
3
Choose your schedule type
Decide whether fixed, rotating, flexible, or another type fits your operation. The right type depends on your coverage needs and the nature of the work.
4
Assign shifts to people
Match employees to shifts based on availability, role, and skills, distributing desirable and undesirable shifts fairly to avoid resentment.
5
Check hours and overtime
Add up each person's weekly hours as you assign, watching for anyone crossing 40 hours and triggering overtime, so cost surprises do not appear at payroll.
6
Publish with enough notice
Share the finished schedule as far in advance as you can, and where local law requires it, at least the mandated notice period. Early publishing lets people plan their lives.
7
Manage changes through one channel
Set a clear process for shift swaps and time-off requests so every change flows through one place and the schedule stays accurate and documented.

The step most people rush is checking hours and overtime as they assign, rather than after. It is far easier to see a 44-hour week forming and adjust a shift than to discover it when payroll runs. Watching the running total for each person as you build lets you control overtime deliberately, keeping it where you want it rather than where it accidentally lands.

The other step that pays off disproportionately is the last one: managing changes through a single channel. Schedules always change, but when swap requests come by text, time-off requests by email, and call-outs by phone, the schedule drifts out of sync with reality.

One channel fixes that cheaply. Funneling every change through a single process keeps the schedule accurate, tells you who is actually working, and leaves a record, which matters both operationally and for compliance.

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

Types of Work Schedules

There are six main types of work schedule: fixed, flexible, rotating, split shift, on-call, and compressed. Choosing the right one is among the more consequential scheduling decisions, because the type shapes everything else: coverage, cost, compliance, and how employees experience their work. No type is universally best; each fits a different pattern of demand and a different kind of work.

FixedThe same hours every week, like a standard 9-to-5. Predictable and simple to manage, best for roles with steady, consistent demand.
FlexibleEmployees have latitude over start and end times within limits. Suits knowledge work and roles measured by output rather than presence.
RotatingEmployees cycle through different shifts, such as day and night, over a repeating pattern. Common in 24/7 operations to share the shift burden fairly.
Split shiftA single day divided into two or more segments with a long unpaid gap, common in food service to match peak meal times.
On-callEmployees are available to work if needed rather than scheduled for fixed hours. Used where demand is unpredictable, with rules on whether on-call time is paid.
CompressedFull-time hours in fewer, longer days, such as four 10-hour days or a 9/80. Gives more days off in exchange for longer shifts.

Most businesses use some combination rather than a single pure type. An office might run fixed schedules for most staff and flexible arrangements for a few roles, or a hybrid work schedule that splits time between office and home.

Round-the-clock operations sit at the other end of the range. They typically use rotating shifts, and the rotation pattern matters a great deal for coverage and fatigue. The 2-2-3 rotation keeps four teams on a site that never closes, and the twelve-hour DuPont schedule runs continuous industrial operations.

The practical way to choose is to start from your coverage pattern and work backward. If demand is steady and predictable, a fixed schedule is simplest. If you need coverage across a longer day, a compressed schedule may fit. It trades longer shifts for more days off; the 9/80 version, for example, gives every other Friday off.

If you never close, a rotating pattern is likely necessary. Spiky, unpredictable demand is the awkward case, and on-call or flexible arrangements are the usual answer. Match the type to the actual shape of your demand rather than adopting a pattern because it is common elsewhere.

One option is off the table whatever you choose. Time off in place of overtime pay, known as comp time, is allowed only for public agencies under 29 U.S.C. 207(o), so a private employer pays the overtime rather than banking it.

Examples of Shift Work in Practice

A retail store might run an opening shift from 7am to 3pm and a closing shift from 2pm to 10pm, overlapping through the busy afternoon. A plant running around the clock usually splits the day three ways: a first shift in the morning, a second shift through the evening, and a third shift overnight.

A restaurant is the classic split shift case, with servers working lunch, going home, and returning for dinner. A clinic often runs fixed weekday hours plus a rotating weekend on-call list.

The overnight examples raise a pay question worth settling early. The Fair Labor Standards Act does not require extra pay for night work, so a shift differential (a higher rate for working nights) is a matter of agreement rather than federal law.

A Work Schedule Example for a Full Week

Here is a finished week for a five-person store that opens at 7am and closes at 10pm. Nobody crosses 40 hours, every hour the doors are open has someone on the floor, and the busiest stretch of the week gets a second person.

PersonDays workedShiftWeekly hours
Store leadMon to Fri7am to 3pm40
Associate AMon, Tue, Thu, Fri2pm to 10pm32
Associate BWed to Sun2pm to 10pm40
Weekend associateSat and Sun7am to 3pm16
FloaterThu, Fri, Sat11am to 7pm24

Read it the way you would build it. The opening and closing shifts cover the whole day between them, the floater lands on the three busiest days, and the weekend associate takes the mornings the lead does not work. If your state requires an unpaid meal period, subtract it from each shift before you total the week.

How to Make a Work Schedule in Excel or Google Sheets

For many small teams, a spreadsheet is the right tool to start with, and it costs nothing. The basic structure is simple: put employees down the left side, days of the week across the top, and each person's shift times in the cells where their row meets each day.

That grid is the core of nearly every manual schedule, and it works well for a stable team of a handful of people.

A few additions make the spreadsheet genuinely useful rather than just a grid. Add a column on the right that sums each employee's total weekly hours, so you can see at a glance who is approaching overtime.

Coverage is the other thing worth making visible. Add a row or a separate tab that totals the number of people scheduled for each shift, and color-code shifts or roles so the sheet reads at a glance instead of being counted by hand. These small touches turn a static grid into a working tool.

The single most important habit with a spreadsheet schedule is to save it as a reusable template. Most of your schedule is the same from week to week, so starting from last week's structure and adjusting is far faster than building from scratch.

The weekly routine then shrinks to two moves. Duplicate the template, update availability and time off, and you are most of the way done. The spreadsheet approach has real limits as you grow, but for a small, stable team it is often all you need.

Turning the Sheet into a Work Schedule Calendar

A grid is how you build the schedule. A work schedule calendar is how most people prefer to read it. The same data serves both: keep the weekly sheet as your working document, then publish it as a shared team calendar where each shift lands as an event on the right person's phone.

Paper still has a place alongside it. Plenty of small teams post a printed grid somewhere everyone walks past it, which reaches the people who never open a calendar app.

The rule that keeps this from backfiring is one master version. If both the sheet and the calendar can be edited, they drift apart inside a week and nobody knows which one is current. Publish in one direction only. If you would rather not build the grid from scratch, the employee schedule template already has the hours and coverage columns set up.

Spreadsheet vs Scheduling Software

The honest question every growing business faces is when to move from a spreadsheet to dedicated scheduling software. A spreadsheet is free and flexible, but it puts all the work on you: every hours calculation, every availability check, every change is manual.

Software takes that work off you at a price. It automates the arithmetic and the matching, but it costs money and adds a tool to learn, so the right choice depends on where your team sits on a few dimensions.

FactorSpreadsheet WorksSoftware Earns Its Cost
Team sizeA handful of peopleLarger teams where manual tracking breaks down
Schedule stabilityStable, similar each weekVariable shifts changing constantly
Availability complexityFew constraintsMany availability and skill constraints to match
Overtime and complianceSimple to track by handAutomatic hours and compliance calculation needed
Change frequencyRare changesFrequent swaps and requests to manage

The tipping point usually arrives when scheduling starts eating serious time each week, or when manual tracking starts producing errors you cannot afford: missed overtime, coverage gaps, or compliance mistakes.

The arithmetic at that point is simple. When you spend hours every week wrestling a spreadsheet, or when a scheduling error costs real money, the monthly cost of software is easily justified by the time and errors it saves. Below that threshold, a spreadsheet is perfectly adequate and the simpler choice.

Whichever tool you choose, it draws on the same underlying people data as the rest of your HR: who works for you, their roles, their availability, and their records. The most efficient setups connect scheduling to that data rather than maintaining it separately, so weigh that when you compare options.

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

Overtime and Scheduling Laws to Know

Two sets of rules matter most when you build a schedule: overtime and, in a growing number of places, predictive scheduling laws. The schedule you build directly determines your legal exposure under both, so they are worth understanding before you finalize it. Getting either one wrong turns a routine schedule into an expensive liability.

Overtime is the first. Under the Fair Labor Standards Act, non-exempt employees must be paid overtime at time and a half for hours worked over 40 in a workweek. Because the schedule determines how many hours each person works, it is where you control overtime, and watching weekly hours as you build keeps it deliberate.

Daily overtime is the trap for schedules built around long shifts. California requires time and a half past 8 hours in a single day, double time past 12, and time and a half for the first 8 hours on the seventh consecutive day in a workweek. In a state with a daily rule, the length of an individual shift matters as much as the weekly total.

Predictive Scheduling Laws Are Spreading
A growing number of US jurisdictions have predictive scheduling or fair workweek laws that require covered employers to post schedules in advance, typically 14 days, and pay a premium when they change a posted schedule late. Oregon runs a statewide version covering retail, hospitality, and food service employers with 500 or more employees worldwide, and the rest of the map is city and county ordinances that set their own size thresholds and mostly reach larger employers in the same industries. Because these rules vary by location and change often, confirm what applies where your employees work.

Predictive scheduling, also called fair workweek, is the fast-moving area to watch. These laws give hourly workers more stable schedules by requiring covered employers to post the schedule a set number of days ahead and to pay a premium, often called predictability pay, when a posted schedule changes late.

Oregon's law shows the shape of them. It gives covered employees 14 calendar days of written notice, and the premium for a late change depends on what kind of change it is.

Under Oregon's rules, an employer that adds more than 30 minutes to a shift, or moves its date or start time with no loss of hours, owes an extra hour at the regular rate. Cutting hours or canceling a shift costs half the regular rate for each scheduled hour the employee does not work.

The map runs the other way in places too. Iowa bars its cities from adopting any ordinance that sets scheduling practices beyond what state or federal law requires (Iowa Code 364.3), which rules out a local fair workweek ordinance there entirely.

The practical step is the same everywhere. Check the rules in each place you operate before you build the schedule, and keep a record of what you posted and what changed, because that record is the evidence if a complaint arrives.

Scheduling and Your People Data

The point most scheduling advice misses is that a work schedule is not a standalone document; it is built from your people data. Every schedule draws on the same underlying information: who works for you, their roles and skills, their availability, their time-off balances, and their employment records.

Where that data lives decides how long the job takes. When it sits in one place and the schedule is built from it, scheduling gets faster and more accurate. When it is scattered, you end up maintaining the same information in several places and reconciling the differences by hand.

This is especially true for a small business without a dedicated HR person, where the same owner or office manager handles scheduling, onboarding, records, and compliance. For them, the efficiency comes from not repeating work. In a connected setup, a new hire's availability, role, and start date are captured once during onboarding and feed directly into scheduling, rather than being re-entered.

The schedule also connects to time tracking on the other side. The schedule is the plan; the timesheet is the record of what actually happened. Comparing the two reveals the patterns worth acting on: consistent overtime, frequent absence, or shifts that always run long.

Connection is the whole point. Keeping scheduling, people records, and time tracking together rather than siloed turns scheduling from an isolated weekly chore into part of a coherent picture of your workforce.

What worked for me
The change that made scheduling bearable for me was not a fancy tool. It was keeping one source of truth for my people: their availability, roles, time-off balances, and contact details all in one place. Before that, I was rebuilding the same information every week from memory and scattered messages, which is where most of my errors came from. Once the schedule was built from data I maintained once, the weekly task went from a dreaded afternoon to a quick update. The tool mattered less than having the underlying information organized.

Common Scheduling Mistakes to Avoid

Most scheduling problems come from a handful of avoidable mistakes. Recognizing them is most of the fix, because each has a clear alternative. The thread connecting them is treating scheduling as an isolated weekly scramble rather than a repeatable process built on good information.

Building the schedule from scratch every weekStart from a repeatable template and adjust, rather than reinventing it each time. Most of the schedule is the same week to week.
Ignoring employee availabilityCollect availability and time-off requests before you build, not after. A schedule that conflicts with known constraints gets reworked immediately.
Publishing too lateGive employees as much advance notice as you can, and in some places it is legally required. Last-minute schedules disrupt lives and drive turnover.
Forgetting overtime mathTrack hours as you build so you see overtime before it happens. Discovering a 45-hour week at payroll is an expensive surprise.
No process for changesSet clear rules for shift swaps and time-off requests so changes flow through one channel instead of scattered texts you lose track of.
Treating the schedule as separate from HRThe schedule is built from your people data: who works where, their roles, and availability. Keeping it disconnected from employee records creates duplicate work and errors.

The mistake that causes the most compounding damage is publishing schedules too late. Beyond the legal risk wherever predictive scheduling laws apply, last-minute schedules make it impossible for employees to plan their lives, which drives dissatisfaction, absence, and turnover.

Survey data on service sector workers puts numbers on it. According to the Shift Project, a research program based at the Harvard Kennedy School and the University of California, 60 percent of those workers get less than two weeks of notice and 66 percent would prefer a more predictable schedule.

Giving people their schedule with real advance notice is one of the highest-return things an employer can do, and it costs nothing but a bit of planning discipline. Pick a set day each week to publish the next schedule, as far ahead as you can manage, and stick to it.

Key Takeaways
A work schedule is a plan setting out when employees are expected to work, and a good one balances coverage, fair and predictable hours for employees, controlled cost, and legal compliance.
Make a schedule in seven steps: determine coverage needs, gather availability, choose a type, assign shifts fairly, check hours and overtime, publish with notice, and manage changes through one channel.
Gather coverage needs, availability, and policies before you build, because most scheduling mistakes happen in the rush to fill a grid without the information the schedule depends on.
A reusable spreadsheet template works for small, stable teams, and scheduling software earns its cost as team size, shift variability, and change frequency grow.
Watch overtime as you build, since non-exempt staff earn time and a half over 40 hours in a workweek, and check whether a state daily overtime rule or a predictive scheduling law applies where your team works.
A schedule is built from your people data, so keeping availability, roles, records, and time tracking connected rather than siloed makes scheduling faster, more accurate, and less repetitive.

Frequently Asked Questions

What is a work schedule?

A work schedule is the plan that tells each employee which days, shifts, and hours they are expected to work. For the employee, it answers when to show up. For the employer, it is how staffing gets lined up with demand, so the business has the coverage it needs at all times. A schedule can be as simple as a fixed 9-to-5 week or as involved as a rotating pattern of day and night shifts. Whatever its shape, it is also where an employer keeps labor costs in check and stays compliant.

How do you make a work schedule?

To make a work schedule, first determine your coverage needs by mapping how many people you need at each hour and day. Then gather employee availability and time-off requests, choose a schedule type that fits your operation, assign shifts to people based on availability and skills, check the hours to avoid unexpected overtime, publish the schedule with as much notice as possible, and set a clear process for handling changes. Building from a repeatable template rather than starting from scratch each week makes this far faster.

How do I make a work schedule in Excel?

To make a work schedule in Excel, or in Google Sheets, which works the same way, start with a simple grid: one row per employee and one column per day of the week, with each cell holding that person's shift times for the day. At the end of each row, add a totals column for the week's hours, so anyone close to overtime stands out. A coverage row, or a second tab, that counts how many people are on each shift confirms every shift is staffed. Once the layout works, keep it as a template and copy it each week rather than starting a fresh sheet. This approach suits small teams whose schedules stay much the same from week to week.

What is the best way to schedule employees?

The best method depends on your team size and complexity. For a small team with a stable, fixed schedule, a reusable spreadsheet template is often enough. As you add more employees, variable shifts, availability constraints, and compliance requirements, dedicated scheduling software becomes worth the cost because it automates the hours math, availability matching, and change management that consume the most time manually. The key in either case is building from your people data and publishing with enough advance notice.

How far in advance should a work schedule be posted?

As a best practice, post schedules at least one to two weeks in advance so employees can plan their lives, which also reduces turnover and no-shows. In some jurisdictions it is legally required: predictive scheduling or fair workweek laws in Oregon and a number of cities and counties require covered employers, typically larger retail, hospitality, and food service businesses, to post schedules in advance, usually 14 days ahead, and pay a premium for late changes. Even where not required, generous advance notice is one of the highest-value scheduling practices.

What are the different types of work schedules?

The main types are fixed, where hours are the same every week; flexible, where employees have some control over their hours; rotating, where employees cycle through different shifts like days and nights; split shift, where the day is divided into segments with a gap; on-call, where employees are available as needed; and compressed, where full-time hours are worked in fewer, longer days such as a four-day week or a 9/80 schedule. The right type depends on your coverage needs and the nature of the work.

Does making a work schedule affect overtime?

Yes. The schedule sets how many hours each person works, and hours are what trigger overtime, so the schedule directly determines it. Federal law, the Fair Labor Standards Act, requires time and a half for a non-exempt employee's hours beyond 40 in a single workweek. If you keep a running weekly total for each person while you assign shifts, overtime becomes a choice you make on purpose instead of a surprise when payroll runs. Some states go further with daily overtime, which kicks in once someone works more than 8 hours in a day no matter what the weekly total is, so in those states the length of each shift matters as well.

What is the difference between a work schedule and a timesheet?

A work schedule looks forward: it is set in advance and says when each employee is supposed to work. A timesheet looks back: it records the hours each person actually worked, is filled in during or after the shift, and is what payroll runs on. Ideally the two match. Where they do not, the gap is useful, because setting the plan next to the record shows where overtime keeps building up, where people are often absent, and which shifts regularly run over. That is the reason scheduling and time tracking are most useful when they are linked.

Make HR the easy part of running your business

Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.

  • 7-day free trial
  • No credit card required
  • Cancel anytime
4.7 on G2300+ companies trust FirstHR