An employee schedule maker is a tool that turns your team, your roles and your shift times into a weekly staff schedule you can share, check and change in one place. It does not decide your staffing levels for you, and it does not replace your judgement about availability, skills or rest. It gives you a clear grid to work in, so the week is built once and read the same way by everyone. This guide shows you how to pick a maker, set it up, build a week with it, and check the week before you publish it.
Quick steps:
- Pick a maker type that fits your team size and how often the week changes.
- Set up roles, shift blocks, availability and time off before you place any names.
- Fill the hardest shifts first, then the rest of the week.
- Check coverage, availability, double bookings and hour totals for every person.
- Publish the week in one place and tell the team where to find it.
- Handle every change in the maker, so no one works from an old copy.
What an employee schedule maker is, and what it is not
A staff schedule maker is any tool built to hold a week of shifts in a grid: people down one side, days across the top, and a shift in each cell. Some makers are paper grids or spreadsheet templates. Some are free online tools that build the grid for you. Some are part of a scheduling app that also handles requests, clock-ins and messages. The grid is the common part. What changes is how much work the tool does after the grid is built.
The table below sets out the four maker types most small teams meet, what each one gives you, and where each one stops.
| Maker type | What you get | What it does not do | Best for |
|---|---|---|---|
| Paper or whiteboard grid | A week everyone can see on the wall, with no setup and no login | No copy for staff at home, no hour totals, no record when the week is wiped | A very small team in one room with fixed hours |
| Spreadsheet template | A grid you can copy each week, with hour totals you can add yourself | No shared live version, no request handling, no automatic check for double bookings | A small team that is happy to keep the file and send it out each week |
| Free online schedule maker | A grid in a browser, often with export to PDF or a file, and no account in some cases | Usually no time-off requests, no swap approval, no time clock, and no live update to staff phones | A small team that needs a tidy week, printed or sent out, and little else |
| Scheduling app with a maker built in | A grid plus publishing to staff, time-off and swap requests with manager approval, open shifts, a time clock and team messaging | It still needs your inputs: roles, shift blocks, availability and time off must be entered correctly | A team that changes often, works across locations or roles, or needs requests and hours in the same place |
A maker will not fix a week built on guesswork. If availability is out of date, if no one has written down which shifts need a trained person, or if the week is published late, the grid will look tidy and still cause problems. The maker organises the information. You still supply the information, and you still check it.
That distinction matters when you read maker pages that promise a finished schedule in minutes. A finished grid is not the same as a workable week. A workable week is one where every shift has the right person, every person can actually work the shift, every day meets its minimum cover, and no one is booked beyond the hours you agreed with them. The rest of this guide is built around that test.
Pick the right staff schedule maker for your team
Start with your week, not with a feature list. Work through four points before you pick a tool, and the choice gets much shorter.
First, count the people and locations in the week. A maker that works for six people in one shop may not work for thirty people across two sites, because the grid gets hard to read and the changes get hard to track. Second, note how often the week changes after it is published. If swaps and call-outs are rare, a printed grid may be enough. If they happen every week, you need a version staff can see updated, not a photo of an old printout. Third, list what else has to live with the schedule. Time-off requests, swaps, clock-ins and messages are separate jobs. If you already handle them somewhere else and that works, a simple maker may be enough. If they live in group chats and get lost, a maker that stands alone will not solve that part. Fourth, note who reads the schedule, and on what. Staff who are rarely at a desk need a version they can open on a phone. Staff who work in one building may be fine with a wall copy, as long as changes reach them too.
Use the decision table below to narrow the choice.
| If this is true | A maker of this type fits better | Why |
|---|---|---|
| One location, under ten staff, fixed hours, rare changes | Paper grid or spreadsheet template | The week is simple, and a heavier tool adds setup without adding value |
| One location, weekly changes, staff need a copy at home | Free online maker with PDF or file export | Staff get a readable copy, and you keep a file for the week |
| Frequent swaps, call-outs or time-off requests | Scheduling app with a maker built in | Requests and changes stay with the schedule, with approval recorded |
| Two or more locations, or roles that must not be mixed | Scheduling app with locations and positions | The grid can be split by location and role, so a person is not booked where they cannot work |
| Hours must feed into timesheets or payroll checks | Scheduling app with a time clock and timesheets | Planned hours and actual hours sit side by side, instead of being rebuilt by hand |
| Staff have no regular desk access | A maker staff can open on a phone | A wall copy alone leaves mobile staff guessing about changes |
Once you have a shortlist of one or two types, test a maker with one real week before you commit to it. Build next week in it, using real names, real roles and real availability. Then check five things about that test week: you can read every day at a glance; you can spot a gap without counting by hand; you can change one shift without redoing the whole week; staff can open the result without asking you for a copy; and you can find the approved version a week later. If any of those checks fails, that maker will cost you time every week, even if it looked good on its sales page. Note the results, and compare makers on the same test week, not on different weeks.
Calendza is mentioned here only because it is relevant to the choice: it is a scheduling app of the last type in the table, with a maker built in. The rest of this guide works with any maker type, and the template below works on paper, in a spreadsheet, or in an app.
Set up your maker before you build the week
Most maker weeks go wrong before any name is placed. The setup takes about twenty minutes for a small team, and it saves a rebuild later. Work through the setup in this order, and do not skip a step because the week looks urgent.
- Write the week dates and the opening hours for each day. Include work outside opening hours, such as opening checks, prep and closing, because those hours need people too.
- List every role that appears in the week, using the titles your team recognises. Keep the list short. A role that no one understands will be filled by the wrong person.
- Define a small set of shift blocks and reuse them every week. A shift block is a named shift with fixed start and end times, such as Early, Mid or Close. Three or four blocks are enough for most small teams. More blocks make the week harder to read.
- Set a minimum and a target headcount for each day, by role where it matters. The minimum is the fewest people you can run with. The target is the level you want when the week goes well.
- Collect availability in writing, with days and times, not vague notes. Record the difference between cannot work and prefer not to work, because you will treat those two cases differently when a gap appears.
- Record approved time off and fixed commitments before you build. Time off agreed after the week is built forces a change, and changes made late are where double bookings creep in.
- Write down your own house rules for the week, in plain words. Examples of house rules are a weekly hour cap you have agreed with staff, a rest gap between a late finish and an early start, and a rule that a shift needing a trained person is only filled by someone trained for it. Keep the list to the rules you will actually check.
Here is a copy-paste setup sheet. Fill it once, keep it with the maker, and update it when roles, hours or availability change.
WEEK SETUP SHEET Week starting: _______________ Opening hours by day: _______________ Roles in this week: _______________ Shift blocks (name, start, end): _______________ Minimum cover by day and role: _______________ Target cover by day and role: _______________ Availability on file for each person (days and times): _______________ Approved time off this week: _______________ Fixed commitments (classes, second jobs, agreed limits): _______________ House rules to check before publishing: _______________
A note on rules that come from law: scheduling rules on hours, breaks, overtime and notice vary by country, state and locality, and they change. This guide gives general planning help only. If a rule affects pay, hours or a legal limit in your area, check the current local law or ask a professional before you rely on it. Do not treat a house rule in this guide, such as a 40-hour weekly cap used in the example below, as a legal requirement. It is a planning choice for that example, stated so the example can be checked against it.
Copy-paste weekly schedule maker template
Use this template as your maker grid. Copy the table, fill in your team and your week, and keep the same layout every week so staff learn to read it at a glance. The template has a row for each person, a column for each day, a total-hours column, and two check rows at the bottom: one for daily cover, and one for notes and changes.
| Employee | Role | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Total hours |
|---|---|---|---|---|---|---|---|---|---|
| Daily cover (people on duty) | |||||||||
| Notes and changes |
Fill the template in this order, because the order prevents the most common errors.
- Write the week dates across the top, and the shift block key underneath the table. The key lists each block name with its start and end times, so a cell that says Early means the same thing every day.
- Fill approved time off and fixed commitments first, marking those cells as Off. A day marked Off cannot be filled later by accident.
- Fill shifts that need a specific skill or qualification next. These are the hardest cells to fill, so they get first choice of people.
- Fill the busiest days next, then the quieter days. If you fill quiet days first, you may find no one suitable left for the busy day.
- Add up each person's hours as you go, and write the total in the last column. Do not wait until the end, because a person over their agreed hours is easier to fix while other cells are still open.
- Count daily cover for each day and write it in the cover row. Compare it with the minimum and target you set in the setup sheet, and fill any day below minimum before you publish.
- Write the publish date and the place staff will find the week in the notes row, and leave the notes row open for changes. Every change after publishing goes in the notes row and in the cell, so the week and its change history sit together.
Shift key for the template. Adapt the names and times to your own business, and keep the same key every week.
SHIFT KEY Early: start ____ end ____ Mid: start ____ end ____ Late: start ____ end ____ Close: start ____ end ____ Off: not scheduled Open shift: unfilled, available for eligible staff to claim with manager approval
A template on its own does not check anything. The next two sections show the template filled in for one illustrative week, and then the check that catches the errors in that week before it reaches staff.
Build a week with the maker: a worked example
The example below is illustrative only. It is not a real business, and the names, days and times are made up to show how the maker, the setup sheet and the check work together. The business is a small pet grooming salon, open Monday to Saturday from 9:00am to 6:00pm, closed on Sunday. The team has seven people. The salon's own house rules for this example, stated so every decision below can be checked, are: no one is scheduled on a day or at a time they are marked unavailable; no one exceeds 40 scheduled hours in the week; every open day needs at least two groomers, and Saturday needs three; every open day needs at least one bather and one receptionist; a grooming shift is only filled by a trained groomer.
Shift blocks for this example are: Early, 8:30am to 4:30pm; Late, 10:00am to 6:00pm; Day, 9:00am to 5:00pm. Bathers and receptionists work the Day block unless a different time is stated. Availability and time off for this example are: Maya has approved time off on Wednesday; Jordan, a part-time student, is unavailable on Tuesday and Thursday before 1:00pm, and unavailable on Friday; all other availability is as shown by the Off cells in the table.
Here is the finished week in the maker template, with shift blocks in each cell and totals in the last column.
| Employee | Role | Mon | Tue | Wed | Thu | Fri | Sat | Total hours |
|---|---|---|---|---|---|---|---|---|
| Maya | Lead groomer | Early | Early | Off | Late | Early | Late | 40 |
| Tom | Groomer | Late | Late | Early | Early | Off | Early | 40 |
| Priya | Groomer | Early | Off | Late | Early | Late | Late | 40 |
| Sam | Bather | Day | Day | Off | Day | Day | Off | 32 |
| Jordan | Bather | Day | 1:00pm to 6:00pm | Day | 1:00pm to 6:00pm | Off | Day | 34 |
| Alex | Receptionist | Day | Day | Off | Day | Day | Off | 32 |
| Dana | Receptionist | Off | Off | Day | Off | Off | Day | 16 |
Check the week against the stated rules, one rule at a time. Groomer cover by day is: Monday 3, Tuesday 2, Wednesday 2, Thursday 3, Friday 2, Saturday 3. Monday to Friday meet the minimum of 2, and Saturday meets the higher minimum of 3. Bather cover is at least 1 every day: Monday Sam and Jordan, Tuesday Sam plus Jordan from 1:00pm, Wednesday Jordan, Thursday Sam plus Jordan from 1:00pm, Friday Sam, Saturday Jordan. Reception cover is at least 1 every day: Alex Monday, Tuesday, Thursday and Friday, and Dana Wednesday and Saturday. Hour totals are Maya 40, Tom 40, Priya 40, Sam 32, Jordan 34, Alex 32 and Dana 16. No one exceeds the 40-hour cap in this example, and Jordan's Tuesday and Thursday shifts start at 1:00pm, after the morning unavailability ends, and Jordan is not scheduled on Friday, when Jordan is unavailable.
Two fixes were made during the check, and both show why the check matters more than the first draft. The first draft put Maya on Wednesday, but Maya has approved time off that day, so Wednesday was changed to Off and Priya and Tom cover grooming that day. The first draft also put Jordan on Tuesday from 9:00am, but Jordan is unavailable on Tuesday before 1:00pm, so that shift was changed to 1:00pm to 6:00pm, which is 5 hours, and Jordan's week total is 8 plus 5 plus 8 plus 5 plus 8, which is 34 hours. Without those two fixes, the week would have looked complete in the grid and failed on the day. That is the difference between a maker that holds a week and a maker week that has been checked.
Check the week before you publish it
Run this check on every week, in this order, before anyone outside the maker sees it. The check takes about ten minutes for a small team, and it catches the errors that cause most midweek changes.
- Coverage: for each day, count people on duty by role and compare the count with the minimum and target from the setup sheet. Fill any day below minimum now, not on the day.
- Availability: for each person, compare every scheduled shift with their availability on file. A shift that starts before a person is available, or falls on a day they cannot work, must move.
- Time off: confirm every approved time-off day shows as Off, and that no one was added back in to fill a gap on their time-off day.
- Double bookings: confirm no person appears twice on the same day in overlapping shifts, and no person is booked at two locations at the same time.
- Skills: confirm every shift that needs a trained person, a licence holder or a key holder is filled by someone who meets that need.
- Hours: add up each person's week and compare it with the hours you agreed with them. Move or split a shift if the total is over the agreed cap, and note the change.
- Rest gaps: where your house rules include a rest gap between a late finish and an early start, check those pairs by their actual start and end times. A close followed by an early open the next morning is the pair most often missed.
- Readability: read the finished week as a staff member would. Check that each person can find their days without asking, and that shift names, times and the publish place are clear. If not, fix the layout before publishing, because staff will ask you the same questions all week.
If a check fails, fix the week in the maker and run the failed check again, plus the checks that touch the same people or days. A fix that moves one person can break cover on another day, so a single changed cell deserves a fresh count for that day. Do not publish a week with a known gap and a plan to fix it later, because staff plan around the published version, and a gap found by staff feels like a broken promise, even when the fix is quick.
Publish, share and handle changes
Publishing is a routine, not a single click. Use the same routine every week, so staff know when and where to look, and changes do not depend on who happens to be on duty that day.
- Pick one publish place and use it every week. It can be an app, a shared file, a printed copy on the wall, or a message with a file attached, but it must be one place, not several.
- Pick one publish day and time each week, and keep to it. Staff with childcare, classes or a second job plan around the publish day, so a week that appears on different days each week is hard to plan around.
- Publish the full week at once, with the shift key attached. A week published in parts leaves staff guessing about the days not yet shown.
- Send one short message when the week is live, telling staff where to find it and what changed since the last week, if anything changed.
- Record every change after publishing in the maker and in the notes row, and tell the people affected directly. A changed cell with no message will be missed by the person whose shift changed.
- For a gap after publishing, post the shift as an open shift where eligible staff can claim it, with manager approval before the schedule changes. Do not offer cover to the same people every time by private message, because that hides the offer from others who could have taken it and it leaves no record.
Here is a copy-paste publish message you can use each week. Fill in the week dates and the publish place, and keep the wording the same so staff recognise it.
Hi team, the schedule for the week starting [date] is now live in [publish place]. Please check your days and let me know by [day and time] if anything clashes with availability you already gave us. Changes after today will be posted in the same place, and I will message anyone whose shift changes directly.
When a swap is requested after publishing, apply the same discipline as the pre-publish check: the replacement must be trained for the role, available at that time, inside the agreed hour limit, and approved by a manager before the schedule changes. A swap agreed between two staff members but never entered in the maker is not a swap yet, because the rest of the team still works from the old version. The shift swap policy guide linked at the end of this post sets out a full set of swap rules you can copy, including notice periods and approval steps.
Mistakes that make a schedule maker useless
Most maker problems are habits, not tool problems. The table below lists the mistakes that turn a good grid into an unreliable week, what each one causes, and the fix that prevents it.
| Mistake | What happens | Fix |
|---|---|---|
| Copying last week without checking availability or time off | Staff are booked when they cannot work, and the week is rebuilt midweek | Run the setup sheet and the pre-publish check on every week, even a week that looks the same as last week |
| Keeping the maker and a group chat as two versions of the week | No one knows which version is current, and changes get lost between the two | Pick one publish place, and treat a change as real only when it is in that place |
| Recording availability as vague notes, such as usually free on weekends | The maker fills shifts with guesses, and staff decline shifts they never agreed to | Record availability with days and times, and separate cannot work from prefer not to work |
| Ignoring hour totals until the end of the week | One person is over their agreed hours, and fixing it means moving several other shifts | Add hours as you fill the grid, and check the total column before you publish |
| Publishing late, often the night before the week starts | Staff cannot plan, cover is hard to find, and swaps pile up in the first days | Fix a publish day each week, and publish earlier than feels comfortable, even if one cell is still open |
| Using a different layout, shift name or publish place each week | Staff misread the week, miss a shift, or look in the wrong place for changes | Keep the same template, the same shift key and the same publish place every week |
| Letting one person hold the whole maker in their head | No one else can build or fix the week, and a holiday or sick day stops the process | Write the setup sheet down, keep the shift key with the template, and show one other person how the check works |
If your maker week keeps failing in the same way, fix the habit in the table first, before you buy a different tool. A new maker with the same habit will produce the same week, with a different layout.
When to move from a maker to a scheduling app
A simple maker stops being enough when the work around the grid takes more time than the grid saves. Use the signs below to judge that point honestly, rather than by how busy the week feels in a single bad week.
| Sign | What it looks like in practice | What an app adds |
|---|---|---|
| Requests live outside the maker | Time-off and swap requests arrive by text, and approvals are hard to find later | Requests in the app, with manager approval and a visible decision |
| Changes happen daily | The printed or file version is out of date within a day, and staff ask you which version is right | One live version, updated for everyone when a shift changes |
| Cover is hard to find | Finding cover means calling down a list, and the same people get asked first every time | Open shifts that eligible staff can claim, with manager approval |
| Hours are rebuilt by hand | Planned hours in the maker and actual hours worked are compared by hand at the end of the week | A time clock that turns clock-ins into timesheets in the same place |
| Messages and schedules live apart | Schedule talk is spread across personal chats, and new staff miss the history | Team messaging next to the schedule, for direct messages, groups and company updates |
| Locations or roles keep getting mixed | Staff are booked at the wrong site or in a role they are not trained for | Locations and positions in the app, so the grid can be split by site and role |
Move when two or more of those signs are true most weeks, not just in one busy week. A single busy week can be fixed with a better check or an earlier publish day. A pattern across several weeks means the work around the grid has outgrown the grid. When you test an app, test it on the same jobs that strain your maker: one swap, one time-off request, one open shift, and one timesheet check at the end of the week. If the app makes those four jobs easier for staff as well as for you, it has earned a longer trial. If it only makes the grid prettier, keep your maker.
Related reading: if you want the full step-by-step process behind building a week, the guide to scheduling employees for a small business covers it in detail. If you are choosing the tool itself rather than the method, the guide to an employee shift schedule app explains which features matter and how to run a first week in an app. If swaps are the job that strains your week most, the shift swap policy guide gives you a copy-paste policy and approval rules.
Frequently asked questions
What is an employee schedule maker?
An employee schedule maker is a tool that holds a week of shifts in a grid, with people, roles, days and shift times in one view. It can be a paper grid, a spreadsheet template, a free online tool, or part of a scheduling app. The grid is the core part. What differs is whether the tool also handles publishing, requests, clock-ins and messages, or leaves those jobs to you.
What is the difference between a staff schedule maker and scheduling software?
A staff schedule maker builds and holds the week. Scheduling software usually includes the maker plus the work around it: publishing to staff, time-off and swap requests with approval, open shifts, a time clock with timesheets, and team messaging. A maker alone is enough when the week rarely changes and requests are few. Software fits better when changes, requests and hours need to stay together every week.
How do I make a weekly staff schedule with a schedule maker?
Set up roles, shift blocks, availability and time off first, then fill the hardest shifts first, then the busiest days, then the rest. Add hour totals as you go, count daily cover against your minimum, and run the pre-publish check for availability, double bookings, skills and hours. Publish the full week in one place on the same day each week, and record every later change in the same place.
Can I use an employee schedule maker for free?
Yes, in the sense that paper grids and spreadsheet templates cost nothing but your time, and some online makers offer a free version with a grid and export. A free version usually stops before requests, swaps, clock-ins and live updates to staff. Check what the current free version actually includes before you build your process around it, because free limits differ between tools and change over time.
How far in advance should I publish a weekly staff schedule?
Publish on the same day each week, and as early as you can manage, so staff can plan childcare, classes, transport and a second job around it. Many small teams aim for at least one week ahead, and some areas have rules that require more notice, which vary by locality. If you cannot publish a full week early, publish the firm days first in the same place and mark the rest clearly as not yet final, rather than leaving staff with no version at all.
Calendza handles this specific task by keeping the maker and the work around it in one place. You build the week with drag-and-drop scheduling, publish it in bulk when it is ready, and staff check it, request time off or a swap, pick up open shifts, clock in and message the team from the same workspace. It is in free early access with no credit card required, so you can test a real week in it before you decide. Start at calendza.com.
