How to Make a Shift Schedule: A 7-Step Small-Team Workflow

A workable shift schedule starts with coverage, not employee names. Write down when the business needs each role, collect availability, assign people to those coverage blocks, check the totals, and publish one approved version. That order prevents most of the rework that sends managers back into the schedule on Sunday night.

If you searched for a shift schedule maker, the grid is only part of the job. A useful tool should help you see uncovered roles, overlapping shifts, weekly hours, and the version staff should follow. The method below works in a spreadsheet, a paper template, or an employee shift schedule maker.

The fictional six-person café roster below shows what the method produces for one five-day operation. It is not a staffing standard for a full-service restaurant. Replace its roles, hours and availability with your own, then check the provincial employment rules that apply.

How do you make a work schedule for six employees?

List the coverage the business needs, collect all six employees' recurring availability and one-time exceptions, assign trained openers and closers first, then fill general shifts. Review every day for uncovered roles and every employee for weekly hours, difficult turnarounds, and availability conflicts before publishing one dated version.

You can do this free in the Maxuod Shift public scheduler: add up to six guest employees, build the current week or one of the next four weeks, watch totals update, and download the finished PDF without an account. The tool does not choose coverage, approve an exception, or replace local employment-rule review.

1. Collect four inputs before opening the schedule

Start with operating hours, required roles, employee availability, and expected demand. If one of those inputs is missing, the first draft is guesswork.

Operating hours need a little padding. A store that opens at 9:00 may need an opener at 8:30. A restaurant that closes at 10:00 may still need a closer after the last customer leaves. Put prep, handoff, cleanup, and lockup inside the shift instead of treating them as invisible time.

Availability should have a deadline and one source. A manager who reads one request in a text, another in email, and a third on a sticky note is already maintaining three schedules. Record recurring limits separately from one-week exceptions.

Demand does not need a complicated forecast. Mark the two or three periods where being short would hurt most: lunch, delivery arrival, Friday close, or Monday intake. Those periods get coverage first.

2. Build coverage blocks before assigning names

Draw the work the business needs without thinking about who will do it. A simple coverage map can be enough.

Coverage blocks expose the hard part early. If Saturday close needs three people and only two available employees can close, changing names around the grid will not solve it. You need a different operating plan, a trained backup, or an availability conversation.

Managers often begin with last week's roster because it feels faster. Use last week as a reference, not a template. This week's leave, bookings, deliveries, and training needs decide the coverage.

3. Assign shifts in dependency order

Fill the hardest roles first. Start with required leads, licensed or specially trained positions, solo openers, and closers who hold keys. General service shifts come later because more employees can usually cover them.

Then check the handoffs. A close should have a named owner. A busy block should not lose both experienced employees at the same time. A new employee should know who is responsible for training. These dependencies are easy to miss when the only visible information is a row of names.

I prefer assigning the least flexible work first and leaving one or two ordinary shifts open until the shape of the week is clear. It gives the manager room to balance hours without breaking a critical coverage block.

4. Run three checks before calling the draft finished

First, scan vertically by day. Every opening, rush, close, and required role needs an owner. Second, scan horizontally by employee. Look at weekly totals, consecutive days, close-to-open turns, and unusually long shifts. Third, compare the draft with the original availability record.

The weekly total is a planning signal, not a payroll calculation. Overtime and premium-pay rules differ across countries, states, provinces, industries, and employee classifications. Do not assume that staying below one round number makes the schedule compliant.

The Canadian Centre for Occupational Health and Safety identifies long work hours and insufficient rest between shifts as work-related fatigue factors. A schedule can cover every station and still need revision if the same person closes late and opens early. Check rest and workload as well as the total; a fatigue review is not a medical assessment or a legal-compliance result.

5. Test the week with one realistic scenario

Consider a separate, fictional seven-day restaurant. Friday close requires one lead and two servers. Avery is the only available lead. Luis and Quinn can both serve, but Luis is already scheduled for five days and Quinn has a Saturday opening shift.

The first draft assigns Avery, Luis, and Quinn. Coverage passes. The employee scan does not. Luis's sixth day needs review, and Quinn has a tight close-to-open turn. The manager has four honest choices: move Saturday open, ask another trained employee to close, reduce Friday operating requirements, or accept the assignment after checking the applicable rules and speaking with the employees.

The schedule maker did not make the decision. It made the conflict visible while the manager still had options. That is the standard to use when comparing tools.

A worked weekly schedule for six café employees

Each full shift spans 8.5 hours. For this illustration only, it includes a 30-minute unpaid meal period with no work duties, giving 8 planned paid hours. A lunch shift contributes 3 hours. Weekly totals are Devon 24, Jo 16, Mina 16, Eli 19, Noor 14 and Sam 6: 95 planned paid hours altogether. Paid breaks, interrupted meals or different local rules would change that total.

The lunch relief person must be trained to cover either station, not just carry drinks. In this illustration, the lead takes a meal at 12:00 and the full-day barista at 12:30, each for 30 minutes, while the other two employees cover service. If relief cannot cover the lead’s responsibilities, the roster fails even though its headcount and arithmetic look right. Québec’s meal-period guidance, for example, distinguishes a duty-free meal from one that must be paid because the employee remains at the station; do not export that rule to every province.

Availability is an explicit assumption: both leads can cover their assigned full days, Mina is available Monday and Tuesday, Eli Wednesday to Friday, Noor Monday, Tuesday and Friday, and Sam Wednesday and Thursday. If Sam cannot reach the café before noon, Wednesday and Thursday no longer have the promised 11:30 relief. Rebuild those blocks rather than quietly accepting the conflict.

To test this in Maxuod Shift, enter the six employees and the listed shifts, then use a 30-minute unpaid-break input only where that treatment is appropriate. Compare the resulting planned hours with 95. The public scheduler shows time totals; it does not certify the assumed qualifications, break treatment or actual attendance. A free account saves the checked week, while the payroll provider still determines final pay from approved worked hours.

6. Separate four-week planning from weekly shifts

A weekly view is better for detailed shift work. It leaves room for start and end times, roles, breaks, notes, and daily coverage. Use it for the version employees actually follow.

A monthly view is useful one level earlier. It should show vacation, training, recurring unavailable days, major events, weekend ownership, and which manager owns each week. It becomes hard to read when exact start times, role notes, and handoffs are squeezed into the same small calendar cells.

Use the month as a control board and the week as the schedule. The monthly work schedule maker guide explains that boundary, while the four-week planning view keeps constraints and publication status together.

For recurring coverage, choose the pattern that matches the operating problem. The alternating-weekend roster balances weekend duty across four weeks. The night shift template covers one fixed-night position and documents the cross-midnight handoff. The 12-hour 2-2-3 rotation and 8-hour 24/7 rotation solve continuous-coverage jobs.

Build a four-week board before filling four schedules

A useful four-week board is small enough to scan in one meeting. Give each week four lines: demand markers, approved constraints, the person or team responsible for weekend coverage, and the publication state. Do not copy a complete shift roster into the board.

Start with constraints that affect more than one week: approved leave, recurring availability, a holiday, a planned event, or a rotation handoff. Then build week one in detail. Before publishing, compare it back to the board and label its state. Repeat for week two only when its inputs are stable enough to review.

This prevents a forecast from looking like a promise. Employees can see the approved weekly schedule, managers can prepare for later constraints, and a change to week four does not create three unnecessary corrections to weeks that were never final.

7. Publish one version and record what changed

A schedule is not published when the manager finishes editing. It is published when staff can find the approved version, understand when it takes effect, and know how changes will be handled.

Give the schedule a week label and a publication time. If a shift changes, update the shared version and record who approved it. Sending a corrected screenshot to one employee while leaving the old file in the group chat creates two valid-looking schedules.

After the week starts, keep scheduled hours and actual hours separate. Nova Scotia’s employment-records guidance, for example, requires records of hours and wages and at least 36 months of retention after the work. That is a Nova Scotia example, not one national retention rule. The eight-week history on a Free account is not a substitute for the employer’s required payroll records.

Choose the shift schedule maker that matches the job

Maxuod Shift's public scheduler works without signup for up to six employees and can export a PDF. A free registered account supports up to 12 active employees at one location with eight weeks of history. Maxuod Shift does not run payroll, remit taxes, or guarantee legal compliance. Those boundaries matter when a search result calls a tool free employee shift scheduling software.

Turn checked coverage into the week staff can follow

A blank calendar records assignments. Maxuod Shift carries the draft through the manager handoff: add employees, enter shift times and roles, watch scheduled-hour totals change, review the whole week, then export the approved schedule as a PDF.

For a one-off schedule, use the online shift schedule maker. For recurring weeks, a free account keeps the employee list and recent schedule history together. The manager still owns availability, coverage decisions, local rule checks, and any change made after publishing.

That division is deliberate. The tool handles repeated schedule math and a clean handoff. The manager handles the judgment calls that depend on the business, the employee, and the jurisdiction.

Source notes and limits

The revised examples use Nova Scotia’s employment records, Québec’s worked-time and meal-period guidance, and CCOHS’s Fatigue guidance. The provincial examples do not establish a uniform Canadian rule.

These sources and the schedule/export boundaries were checked on October 2, 2026. The roster and availability are fictional teaching inputs, not customer results or a certified staffing plan. This is operational guidance, not legal, payroll, tax or medical advice. Check current rules for the place where each employee works.

A five-minute publish check

Before sending the schedule, confirm that every required role has an owner, each assignment matches availability, weekly totals and difficult turns have been reviewed, the week and version are labeled, and staff know where future changes will appear.

Then publish it. A schedule that survives those checks is ready for employees; a prettier grid with an uncovered close is not.

FAQ