ENEnglish
Log inBook a demo
Menu

Template · Time off and attendance

Employee shift schedule template

By TapTalent Editorial TeamUpdated

In short

A shift schedule template is a weekly grid that shows which employee works which shift on each day, the hours each person is scheduled and whether coverage meets the target for every shift. This version includes shift codes, coverage targets, weekly hour totals and posting rules, with patterns for 24/7 operations.

Weekly Shift Schedule template

Download WordDownload PDF

Weekly Shift Schedule

Fill in the shift codes and coverage targets first, then assign employees. Enter one shift code per day for each employee (for example: A, B, C, OFF, PTO, TRN). Check the coverage summary before posting. Post the schedule at least [14] days before the week begins and send any later changes through the shift change process.

Schedule details

Location / site
Department / team
Week beginning (first day of workweek)
Week ending
Prepared by
Version
DraftPostedRevised after posting
Date posted

Shift codes

Shift A: name, start and end time, unpaid break (e.g. Day 7:00 AM to 3:30 PM, 30 min)
Shift B: name, start and end time, unpaid break
Shift C: name, start and end time, unpaid break
Shift D (split, mid or peak shift, if used)
Other codes in use
OFF = scheduled day offPTO = approved paid time offTRN = trainingOC = on callLOA = leave of absence

Coverage targets (people needed per shift)

Sunday: A / B / C
Monday: A / B / C
Tuesday: A / B / C
Wednesday: A / B / C
Thursday: A / B / C
Friday: A / B / C
Saturday: A / B / C
Minimum skills or roles required on every shift (e.g. one keyholder, one bilingual agent, one certified forklift operator)

Employee 1

Name and role
Shift codes Sun to Sat (e.g. OFF A A A A A OFF)
Total scheduled hours

Employee 2

Name and role
Shift codes Sun to Sat
Total scheduled hours

Employee 3

Name and role
Shift codes Sun to Sat
Total scheduled hours

Employee 4

Name and role
Shift codes Sun to Sat
Total scheduled hours

Employee 5

Name and role
Shift codes Sun to Sat
Total scheduled hours

Employee 6 (copy this block for each additional employee)

Name and role
Shift codes Sun to Sat
Total scheduled hours

Coverage and hours check

Shifts below coverage target (day and shift)
Employees scheduled over 40 hours (overtime approved?)
Employees with less than [10] hours between shifts
Total scheduled hours for the team
Budgeted hours for the week
On-call employees and contact numbers

Posting and change rules

Schedules are posted by [day] for the week starting [number] days later. Requests for time off must be submitted before the schedule is posted. After posting, shift swaps require a completed shift swap request approved by a supervisor, and the swap must not create overtime or a gap in required skills. Changes made by the company after posting will be communicated directly to each affected employee and recorded below. [Add any predictive scheduling notice or premium pay rules that apply at this location.]

Changes after posting

Change made (employee, day, old shift, new shift)
Reason
Employee-requested swapEmployee absenceBusiness needOther
Employee notified on (date and how)
Approved by

How to use this template

  1. Define each shift with its start, end and unpaid break, and give it a short code so the grid stays readable.
  2. Set the number of people needed per shift each day from your demand forecast or past volume, and note any skills that must be on every shift.
  3. Place fixed commitments first: approved PTO, training, leave and employees with fixed availability.
  4. Fill remaining shifts so each day hits its coverage target, keeping at least 10 hours between shifts and avoiding unplanned overtime.
  5. Total hours per employee and for the team, and compare the team total to the budgeted hours.
  6. Post the schedule by your published deadline and record every change made after posting, with the reason and when the employee was told.

Start with coverage, not with people

The most common scheduling mistake is starting from who wants which days. Start instead from how many people you need on each shift, then fill the grid. For a contact center that number comes from interval forecasting and Erlang math, which is what a call center capacity planning template works out. For a warehouse it comes from units per hour and expected volume. For a clinic or store it is usually a fixed minimum plus extra at peak times.

Once coverage is set, the schedule becomes a matching exercise, and gaps are visible before they become a short-staffed Saturday.

Staffing math for a 24/7 schedule

One seat covered around the clock needs 168 hours a week. At 40 hours per full-time employee, that is 4.2 people per seat before any absence, PTO or training. Add shrinkage of around 15 to 25 percent (a common planning range for hourly operations) and you need about 5 to 5.5 people per 24/7 position.

Example: a security operations desk needs 3 people on every shift, around the clock. 3 seats x 168 hours = 504 hours a week. 504 / 40 = 12.6 FTE. With 20 percent shrinkage: 12.6 / 0.8 = 15.75, so you hire and schedule 16 people, not 13.

Common 24/7 patterns:

  • 2-2-3 (Panama). 12-hour shifts; work 2 days, off 2, on 3, then the reverse. Every other weekend off. Weeks alternate between 36 and 48 hours, so every second week carries 8 hours of federal overtime unless you shift the workweek start to split the long stretch.
  • 4-on, 4-off. 12-hour shifts, simple to explain, an average of 42 hours.
  • DuPont. 12-hour shifts on a 4-week cycle with a 7-day break once a cycle. Popular in manufacturing; tough on people who dislike long stretches of nights.
  • Fixed 8-hour shifts across 5 days. Most flexible for part-time workers and easier to stay inside 40 hours, but needs more people and more handovers.

Fixed shifts generally beat rotating day-to-night shifts for health and retention. If you must rotate, rotate forward (days to evenings to nights) and slowly.

Federal law does not require advance schedule notice, but several jurisdictions do. Oregon, and cities including New York City, San Francisco, Seattle, Chicago, Philadelphia, Los Angeles and Evanston, have fair workweek or predictive scheduling laws for certain retail, food service, hospitality or warehouse employers. They typically require 14 days' notice of schedules, premium pay for late changes and a minimum rest period between closing and opening shifts. Coverage differs by city, so check each location.

A few other points:

  • Overtime is based on hours actually worked in the workweek, not the schedule. Total scheduled hours on the grid help you spot overtime before it happens, and the timesheet template shows what really happened.
  • Do not assign shifts based on age, pregnancy, religion or other protected characteristics. Religious scheduling conflicts are a common accommodation request under Title VII.
  • Minors have hour and time-of-day limits under the FLSA and state child labor laws.
  • Keep posted schedules and change records. In predictive scheduling cities they are required evidence.

Running schedules across many teams

With 30 supervisors each building their own grid, you get 30 versions of fairness. A few rules keep it under control:

  • One template, one set of shift codes and one posting deadline for every site.
  • A visible rule for weekends and holidays, such as rotating them or bidding by seniority every quarter.
  • Swaps go through a shift swap request form and are only approved if the replacement has the same skills and the swap does not create overtime.
  • Review schedule adherence and coverage gaps weekly. A shift that is always short usually has a schedule problem behind it, such as a 6:00 AM start nobody can reach by public transit.

When new hire classes start, schedule their training shifts on the same grid so the floor plan accounts for them. New agents often start on a fixed day shift during nesting before moving into the rotation.

Common mistakes

  • Building the schedule around last month's roster and not this month's forecast.
  • Clopening: closing at 11:00 PM and opening at 6:00 AM. It is unsafe, illegal in some cities and drives turnover.
  • Leaving no one with the required certification or keys on a shift.
  • Posting late, which pushes employees to call out when they cannot rearrange childcare.
  • Not counting training, coaching and meetings as scheduled time, so the floor is short every Tuesday.

Frequently asked questions

What should an employee schedule template include?

The week and location, shift codes with start and end times and breaks, the number of people needed per shift, each employee's shifts for the week, total scheduled hours per person and for the team, and space to record changes after posting.

What is the best 24/7 shift schedule?

For most teams, a 2-2-3 or 4-on, 4-off pattern with 12-hour shifts gives full coverage with fewer handovers and regular weekends off. If 12-hour shifts are tiring or unsafe for the work, use fixed 8-hour shifts across three teams instead.

How many employees do I need for 24/7 coverage?

One position covered all week needs 168 hours, or 4.2 full-time employees at 40 hours. Add your shrinkage for PTO, sickness and training, often 15 to 25 percent, which brings it to roughly 5 to 5.5 people per position.

What is a rota template?

Rota is the British term for a work schedule. A rota template is the same as a shift schedule template: a grid of employees and days showing who works which shift.

How far in advance should work schedules be posted?

Two weeks is the common standard and is required by most predictive scheduling laws. Even where it is not required, posting at least 7 to 14 days ahead cuts call-outs and makes shift swaps easier to plan.

Keep exploring

All templates