Weekly Work Schedule Template: Copyable Layout and Build

A weekly work schedule template is a simple grid: days of the week across the top, employee names down the left, shift times in the cells, and a daily hours column that keeps overtime from sneaking up on you. Below is a copyable example, the exact spreadsheet build, and the point where a template stops being enough.

The template's real job isn't looking organized. It's ending the "am I working Saturday?" texts, catching the 44-hour week before it happens instead of on payday, and giving you a record of who was supposed to be where. A grid that does those three things is a good schedule, whether it lives in Excel, Google Sheets, or on a corkboard. Copy the one below and you have a free weekly schedule template without handing your email address to anybody.

The standard weekly work schedule layout

Almost every weekly staff schedule uses the same structure: Monday through Sunday across the top, staff down the side, and a cell that reads "9:00-5:00" or "OFF" where they intersect. A manager scans a row to see one person's week, or a column to see who covers a given day. Here's a filled example for a five-person coffee shop:

Employee	Mon	Tue	Wed	Thu	Fri	Sat	Sun	Total
Maria (open)	6a-2p	6a-2p	6a-2p	6a-2p	6a-2p	OFF	OFF	40
Devon (close)	OFF	1p-9p	1p-9p	1p-9p	1p-9p	1p-9p	OFF	40
Jess (mid)	OFF	OFF	10a-6p	10a-6p	10a-6p	10a-6p	10a-6p	40
Sam (PT)	OFF	OFF	OFF	OFF	4p-9p	8a-4p	8a-2p	19
Priya (PT)	10a-2p	OFF	OFF	4p-9p	OFF	10a-6p	OFF	17
Daily labor hours	12	16	24	29	29	32	14	156

Two variations are worth knowing. Flipping the grid (employees across the top, days down the side) keeps things narrow enough to print in portrait, which suits crews of 3 to 8. And a shift-based layout, where rows are shifts (Open 6-2, Mid 10-6, Close 1-9) and cells contain names, answers "who's covering Friday's close?" faster than "what's Maria's week?" Restaurants and retail usually prefer it; offices rarely need it.

What should a weekly work schedule template include?

At minimum: the week's date range ("Week of June 15-21"), employee names, role or position, start and end times per day, daily hours per person, and a weekly total column. That total column is the one most free templates skip, and it's the single most valuable cell on the sheet. If you can see Devon is already at 38 hours by Friday, you know a Saturday shift means time and a half before you offer it, not after.

Useful extras that earn their space: a notes row for "training" or "covering for Dan," a daily labor-hours total across the bottom so you can sanity-check the week against your budget, and color-coding by role (register, kitchen, floor) so coverage gaps jump out. In the example above, one glance at the bottom row shows this shop is staffed heaviest Thursday through Saturday, which had better match when customers actually show up.

Leave two things off any staff schedule template. Pay rates, because schedules get posted in breakrooms and shared in group chats, and compensation is nobody's group business. And phone numbers, for the same reason. Keep the template about time and coverage only.

How to build the template in a spreadsheet

Ten minutes, four steps:

1. Row 1: the week's date range. Row 2: "Employee" in column A, Monday through Sunday in B through H, "Total" in I.
2. List employees down column A, one row each. Add a final "Daily labor hours" row at the bottom.
3. Enter shifts as text like "8:00 AM-4:30 PM," or split each day into two skinny In/Out columns if you want the sheet to do the math. With In/Out columns, daily hours is =(Out-In)*24 formatted as a number; an 8:00 AM to 4:30 PM shift returns 8.5. Sum each person's week in the Total column and each day's column in the bottom row.
4. Save this as your master, then duplicate the tab each week and rename it with the dates. Never overwrite last week. Old schedules are records you'll want if a pay dispute ever surfaces, and they're the fastest starting point for next week, since most weeks are 90% identical.

If you'd rather not build from a blank sheet, the same grid works as a template for weekly work schedule printing: set the print area to the grid, landscape orientation, and one page wide. A laminated copy and a dry-erase marker have run many good shops. The failure mode isn't the paper; it's the swap that happens by text and never makes it back to the sheet.

Prefer a longer view? Some teams keep a monthly work schedule template on a second tab, showing four or five weeks of skeleton coverage for vacations and rotations, then publish a firm weekly grid from it. Plan monthly, commit weekly. The weekly grid stays the source of truth because it matches the workweek that overtime is calculated on, and because a month of shift detail is unreadable on a phone screen anyway.

Which format: Excel, Sheets, Word, or paper?

The grid is identical in all of them. What changes is who can edit it and whether it does arithmetic for you.

• Excel or Google Sheets. The only formats that calculate. An Excel weekly work schedule template can total hours per person and per day on its own, which is the entire reason the Total column is worth having. Sheets adds live sharing, so a manager can fix Thursday from a phone.
• Word. A weekly work schedule template Word can open is fine for a fixed roster that rarely changes and mostly gets printed. It won't add anything up, so the hours math happens in your head, and that's where overtime hides.
• Printed or laminated. Post it where the team already looks. Paper wins on visibility and loses on changes, so it works best as a copy of the real file rather than as the file itself.

Free work schedule template downloads are everywhere and most are the same table with somebody's logo across the top. Before you trade an email address for one, check two cells: does it total hours per person, and does it total labor hours per day? If it does neither, a blank work schedule template you build yourself in ten minutes is better, because you'll know what every formula does. Schedule templates for work are a table, not intellectual property.

One search-result mixup worth clearing up: if you were looking for what is a work breakdown schedule, that's a project management chart that splits a deliverable into tasks, and it has nothing to do with staffing a week. Our work breakdown schedule guide covers that one.

Work backward from demand, not from people

The most common scheduling mistake is starting with who wants which shifts. Start with what each day needs instead. Sketch your week in coverage terms first: how many people must be on the floor at open, at peak, at close? For the coffee shop above, that answer might be one at 6 AM, three during the lunch rush, two through the afternoon, and two at close on weekends. Only after that skeleton exists do names go into it.

Build in overlap at handoffs. If the opener leaves at 2:00 PM and the closer arrives at 2:00 PM, the register count, the restock status, and the "watch out for table six" context all walk out the door in a fifteen-second hello. A 30 to 60 minute overlap costs a few dollars and saves the daily game of telephone. The same logic applies to open and close buffers: schedule the opener before doors open and the closer past the last sale, because setup and shutdown are work.

Then check the bottom row of your grid against reality. If Saturday does twice Monday's revenue but carries the same 12 labor hours, one of those two days is staffed wrong. This is the discipline the daily labor-hours row enforces, and it's why it belongs in the template rather than in your head. Demand-first scheduling also makes hiring decisions obvious: when the skeleton can't be filled without pushing someone past 40, that gap is a job posting, not an overtime line item.

Fixed vs rotating: pick one structure and commit

A fixed schedule gives each person the same shifts every week. Maria always opens weekdays. It's the easiest format to template because you build the grid once and edit exceptions, and employees can plan childcare, classes, and second jobs around it. The cost is fairness drift: whoever owns the permanent Sunday close will eventually resent it.

A rotating schedule cycles people through shift types, open this week, close next. It spreads the unpopular slots and cross-trains everyone, at the price of more complex planning. If you rotate, maintain labeled Week A and Week B templates and alternate them rather than rebuilding weekly. Around-the-clock operations take this further with named rotations. The 2-2-3, or Panama work schedule, puts four teams on 12-hour shifts to cover 24/7 in a two-week cycle. The DuPont work schedule stretches the same idea across 28 days and hands every crew a full seven days off inside it. A work schedule for nurses is usually three 12-hour shifts a week, and the classic firefighters work schedule runs 24 hours on, 48 off. They all template the same way: build the cycle once, label the weeks, then rotate the labels instead of rebuilding the grid. Our sample work schedules guide walks through examples by business type.

A practical middle path for most small businesses: fixed by default, rotating only the genuinely unpopular slots like Sunday closes and holiday weeks. You get the stability of fixed with the fairness of rotation where it actually matters. Neither structure is the same thing as a flexible work schedule, where the employee picks start and end times inside limits you set. That's a separate decision, and it templates differently because the cells hold ranges rather than fixed times.

The labor math your template should surface

Overtime is the number one thing a schedule template exists to catch. Under 29 USC 207, hours over 40 in a workweek are owed at time and a half, and 29 CFR 778.104 makes each workweek stand alone, so a heavy week can't be offset by a light one. That's why the per-person Total column matters at scheduling time: overtime is cheapest to fix before it's worked. A few states go further with daily rules; California owes time and a half after 8 hours in a day and double time after 12, per the California Labor Commissioner, so a single 10-hour shift there costs extra even in a 35-hour week.

Calculate work schedule cost while it's still a draft. Multiply each person's scheduled hours by their rate, sum it, and check the result against a sales forecast; most service businesses aim for labor somewhere in the 20s or low 30s as a percent of revenue. Use a work schedule calculator rather than mental arithmetic here: our free work hours calculator and overtime calculator make the per-person math instant, including the time-and-a-half scenarios you're trying to avoid.

Then close the loop after the week runs. The template says Devon works 1 to 9; only a time clock knows he actually left at 9:40 three nights running. That gap between scheduled and worked hours is exactly where surprise overtime lives, and a schedule alone can't see it. Keep your timesheet layout in the same column order as the schedule grid so planned and actual sit side by side without anyone translating between two formats.

Time-off requests and shift swaps without chaos

A template only stays accurate if changes flow through it, so set two rules and hold them. First, a request cutoff: time-off requests are due before you build the schedule, say Tuesday for a Wednesday publish. Requests that arrive after publishing become swaps, not edits. Keep a simple availability tab in the same spreadsheet (one row per person, recurring constraints like "no Sundays" plus dated requests) so you're not scheduling from memory and group-chat archaeology.

Second, a swap protocol: the two employees agree, the swap covers the same role, it doesn't push either person over 40 hours, and a manager approves it in the file before it happens. That last clause is the one that saves you. An unrecorded swap means the schedule now lies, and when someone no-shows a shift they "gave away" verbally, you have nothing. Update the cell, add a note ("Sam covering for Priya"), done.

Watch the 40-hour clause especially. A swap that looks like a simple trade can hand someone a sixth shift, and time and a half applies whether or not the extra hours were your idea. The weekly Total column recalculates the instant you edit a cell, which is precisely why swaps must be edited in and not just agreed to. Managers who skip this step usually discover the sixth shift on the payroll report, three weeks and two pay runs too late to do anything but pay it.

Posting rules, and when the template stops scaling

Publish on a consistent day with real lead time. Some jurisdictions legislate this: Oregon's predictive scheduling law requires covered retail, hospitality, and food service employers with 500 or more employees worldwide to post written schedules at least 14 calendar days in advance, per the Oregon Bureau of Labor and Industries, and cities like Seattle, Chicago, and New York have their own versions. Most small businesses aren't covered yet, but the direction of travel is obvious, and two weeks' notice is simply good practice that cuts no-shows and swap chaos regardless of law.

Whatever you publish, make one copy the single source of truth. The moment the corkboard says one thing and the group chat says another, someone works the wrong shift in good faith. That's also the honest signal you've outgrown the spreadsheet: swaps happening by text that never reach the file, employees photographing a stale printout, an hour every week rebuilding a grid that's 90% unchanged.

Scheduling software closes those gaps: the current schedule lives on every employee's phone, swaps update in real time, and scheduled shifts sit next to actual punched hours so variance is visible instead of theoretical. Kloqk pairs it with a free time clock, so the schedule you plan and the hours you pay finally come from the same place. Start with the grid above this week. When maintaining it becomes a job, you'll know exactly what to replace it with.