How to make a work schedule for a small business (a simple 7-step guide)

If you run a small business with shift workers, the weekly schedule is one of the most important things you produce — and often the most painful. Done well, everyone knows where to be and the floor is covered. Done badly, you get no-shows, double-bookings, and a group chat full of “who’s closing Friday?” This guide walks through a repeatable way to build a weekly work schedule that holds up.

1. Start with your coverage needs, not your people

Before you assign a single name, map what the week actually requires. For each day, write down the shifts you need filled and how many people per role at each part of the day — your open, your rush, your close. This is your demand. Scheduling people first and hoping it adds up to coverage is how gaps happen.

This also gives you something to hand a new manager. “Two on the floor from open, three from five, two to close” is a spec anyone can build against. “However Maria usually does it” is not.

2. Collect availability up front

You can’t build a workable schedule without knowing when people can work. Collect each person’s availability — including split availability for students and second-jobbers — and keep it current. The goal is to never schedule someone into a slot they already told you they can’t make. A tool that flags those conflicts as you build saves a surprising amount of rework.

Set a refresh cadence — the start of a semester, the start of a season — and ask everyone at once. Availability collected once at hire and never revisited is the quiet cause of a surprising share of no-shows.

3. Honor approved time off and requests

Approved time off should be visible while you build, not discovered after you publish. Settle time-off and day-off requests first, then schedule around them. If your process is a text-message pile, you will eventually schedule over someone’s approved day — and that erodes trust fast.

4. Build the week — and copy what repeats

Most small-business schedules are 70–80% the same week to week. Build the recurring backbone once, then duplicate it and adjust the exceptions. Drag-and-drop tools make this quick: lay down the shifts, assign by role, and only think hard about the parts that actually changed.

If you find yourself rebuilding a nearly identical week from an empty grid every Sunday, that’s the hour to get back first — before any other improvement to the process.

5. Fill the gaps with open shifts

There will always be shifts nobody is pre-assigned to. Instead of calling around, post them as open shifts that qualified team members can claim. First to claim wins, the gap closes, and you didn’t spend your afternoon on the phone. (Here’s how open shifts and publishing work in Daypart.)

6. Publish once — and notify everyone

A schedule nobody can find isn’t a schedule. When the week is ready, publish it and notify the whole team in one move — in the Activity feed, by email, or both. Everyone should be able to pull up their shifts on their phone, not squint at a photo of a printout. Avoid the screenshot-in-the- group-chat workflow; it’s where versions go to diverge.

How far ahead? Further than you probably are. The Shift Project’s 2019 survey of 30,000 workers at 120 of the largest retail and food-service firms found that two-thirds got less than two weeks’ notice of their schedules, and half of those got less than a week. Three-quarters said they’d prefer something more predictable.

Two weeks is also the number Oregon picked when it wrote scheduling into law. Its predictive scheduling rules require a written schedule at least 14 calendar days out — though only from retail, hospitality, and food-service employers with 500 or more employees worldwide, which is to say almost certainly not you. Treat it as a benchmark rather than an obligation: a six-person shop can clear a bar the biggest chains miss, and it’s the cheapest goodwill you will ever buy.

7. Make changes painless

The schedule will change after you publish — that’s normal. What matters is that swaps and pickups have a clear path. Let staff request shift swaps and trades, approve them in a tap, and make sure both sides see the update. The smoother this loop, the less it lands on you.

One rule saves most of the arguments: a change isn’t real until it’s on the published schedule. Not when it was agreed in a text, not when someone said they’d “probably” cover. If the schedule doesn’t show it, it didn’t happen — and everyone can check the schedule.

Give people enough hours, and the same hours

Coverage is your problem; hours are theirs. In July 2026, The Shift Project surveyed 9,644 hourly workers at 67 of the largest service-sector employers and found broad agreement, across every demographic and political line, on what it takes to get by: about $24 an hour and at least 40 hours a week.

Most small businesses can’t simply decide to pay that. But the hours half is partly a scheduling decision. Someone who gets 32 hours one week and 18 the next can’t plan rent around the job, and will take the first offer that’s steadier. If you can’t give more hours, give the same hours — consistency is the part that’s free.

What to write down

Keep the list short enough that you’ll actually maintain it:

• Coverage needs per day. Roles and headcount for open, rush, and close.
• Who can work which role. Not everyone is interchangeable, and this is what makes open shifts safe to hand out.
• Current availability. With a date on it, so you know when it’s stale.
• Approved time off. In the same place you build the schedule, not in a text thread.
• What changed after publishing. Swaps, pickups, and who approved them.

Do you need software, or is a spreadsheet fine?

A spreadsheet can work for a tiny, stable team. But the moment you’re juggling availability, time off, swaps, and last-minute coverage, a spreadsheet starts costing you more time than it saves — and it can’t notify anyone. If that’s where you are, a focused scheduling app is usually worth it. We compared the two in free schedule maker vs. a real scheduling app.

Daypart is a simple scheduling app built for exactly this — small teams that work shifts, in restaurants, cafés, salons, cleaning companies, and retail. You can start a free 30-day trial (no credit card) and have your first week published in about ten minutes.