Friday at 3:30 pm, the dinner rush is coming, someone calls out, and the paper schedule is taped to a fridge that half the team never looks at. I’ve seen that movie too many times.
Teams Shifts restaurants is the setup I recommend when you want one place for schedules, shift swaps, and time off, right inside Microsoft Teams. It’s not a restaurant labor-forecasting tool, but it does the day-to-day work well, especially for multi-location shops and busy managers who don’t have time to chase texts.
Below is how I set it up for restaurant owners, GMs, and scheduling managers, with the exact roles, locations, swap rules, and request flows that keep coverage tight.
Why I like Shifts for real restaurant scheduling
Restaurants don’t fail at scheduling because managers don’t care. They fail because the schedule lives in too many places.
Shifts fixes that by putting schedules where your team already is, on their phones. Staff can see their shifts, request an open shift, submit a swap, and request time off without a separate app login. Managers can approve requests and keep an audit trail, which matters when expectations get fuzzy later.
For the manager who’s also handling inventory and a broken ice machine, that’s a win.
Before you start: licensing, access, and the right Team
Shifts works inside Teams, so the foundation is your Microsoft 365 setup.
- Confirm users are licensed for Teams
- Microsoft 365 admin center > Users > Active users > select user > Licenses
- If you need a reference point for how access and licenses are managed, Microsoft’s overview is here: Manage user access to Microsoft Teams
- Make sure you’re scheduling inside the correct Team
- In Teams, Shifts attaches to a Team. If you create a Team called “Downtown Restaurant,” that’s where the schedule lives.
- My rule: one Team per location for most restaurants. For small groups with two nearby locations and shared staff, you can still keep one Team and use locations (more on that below).
- Have IT enable Shifts if it’s missing
- Teams admin center policies can hide apps. This guide is the right starting point: Manage the Shifts app for your organization
If you want Shifts available everywhere and consistent, I also follow Microsoft’s approach for admin deployment: Deploy and manage Shifts to your Frontline teams in Teams Admin Center
Set up your restaurant structure: locations, groups, and roles
A good Shifts build starts with the same question you ask on a prep list: “Where does everything go?”
In Shifts, your structure usually looks like this:
- Locations: your stores, or service areas if you’re one store with zones.
- Groups: departments (Front of House, Kitchen, Bar, Catering).
- Roles: job assignments (Server, Expo, Line Cook).
Here’s a simple model I use a lot:
| Location | Group | Roles I set up |
|---|---|---|
| Downtown | Front of House | Host, Server, Busser |
| Downtown | Kitchen | Prep Cook, Line Cook, Dish |
| West End | Front of House | Host, Server, Barback |
| West End | Bar | Bartender, Barback |
Step-by-step: create the schedule, then build groups
- Teams > your location Team > Shifts
- Shifts > Create schedule (first time only)
- Microsoft’s walkthrough is clear if you want screenshots: Create a team schedule in Shifts
- Shifts > Settings (or More options) > confirm basics like week start day
- Shifts > Add group (Front of House, Kitchen, Bar)
- Inside each group, add your roles
Permissions: don’t let “everyone edits” become your problem
I keep scheduling power limited.
- Team Owners: usually GM, AGM, ops leader
- Schedule Managers (if you use them): trusted leads who can edit schedules but shouldn’t control the whole Team
Microsoft documents the manager permission model here: Manage Shifts permissions for frontline managers
Build shifts and open shifts without losing coverage
Once your groups and roles exist, building shifts is fast, but the settings determine whether it stays fast.
Step-by-step: add shifts the “restaurant way”
- Teams > Shifts > Schedule
- Pick a group (Kitchen, Front of House)
- Select a day and time block > Add shift
- Set:
- Role (Line Cook, Server)
- Start and end
- Unpaid break if needed
- Notes (like “Close, clean fryers”)
Microsoft’s how-to is here: Add shifts to the schedule in Shifts
Best practices I use to prevent overtime and protect minors
- Cap swap approvals when hours spike: If someone is already at 38 hours, I deny swaps that push them into OT, even if the trade “seems fair.”
- Use role discipline: Don’t schedule a minor into roles that violate your local rules (late hours, bar work). Shifts won’t enforce every labor law for you, so your role setup needs common sense.
- Set availability expectations: I tell staff, “Shifts shows what you’re scheduled, not what you wish you were scheduled.” Availability belongs in your process, not in last-minute swap chaos.
Shift swaps, offers, and approvals that don’t wreck the floor
Swaps are where many restaurants either build trust or create drama. My policy is simple: staff can request, managers approve, and approvals require a coverage check.
- Teams > Shifts > Requests
- Review:
- Swap request (A trades with B)
- Offer request (A gives up, someone else claims)
- Open shifts requests (staff asks to pick up)
Microsoft’s end-user flow is explained well here: Request open shifts, swap or offer shifts in Shifts
Swap approval rules I stick to
- Same group first: A server swap stays in Front of House, not a jump into Expo unless that person is trained.
- Role match: Line cook swaps with line cook, not prep, unless you want to re-write the whole day.
- Coverage before courtesy: I check the full schedule view before approving. If it breaks the close, it’s a no.
- Time window: I recommend “no swap requests inside 12 hours” unless a manager overrides.
For shared employees across stores, Shifts can also support picking up work at another location via open shifts. Reference: Request an open shift at another location in Shifts
Time off requests that reduce call-outs
Time off is easier when it’s boring. Shifts makes it boring in a good way.
Step-by-step: set the request flow
- Teams > Shifts > Settings
- Confirm time off and request settings (approval on, who can approve)
- Teams > Shifts > Requests to approve or deny
Microsoft’s manager guide is here: Manage shift requests and time off in Shifts
For staff training, I send this link so requests come in correctly: Request time off in Shifts
My best practice: require a short note on time off requests (vacation, appointment, school event). It cuts down on back-and-forth.
Troubleshooting: when staff can’t see Shifts, locations, or notifications
When someone says “Shifts isn’t working,” it’s usually one of these.
Staff can’t see Shifts at all
- Teams mobile > profile icon > Settings > check you’re signed into the right account
- Confirm the app isn’t hidden by policy (Teams admin center). Use: Manage the Shifts app for your organization
They’re in the wrong Team or wrong location
- Teams > Teams list > make sure they joined the correct location Team
- Shifts doesn’t “float” across Teams unless you set up cross-location options intentionally
Managers can’t edit schedules
- Confirm they’re an owner or assigned properly for Shifts. Start here: Manage Shifts permissions for frontline managers
No notifications for swaps or time off
- Teams mobile > Settings > Notifications > Shifts
- On the phone: Settings > Apps > Teams > Notifications enabled
- If it’s still stuck, I’ve seen good tips in Microsoft Q&A threads like this one: Problem with Microsoft teams shift notifications
How I tie Shifts into a restaurant IT plan (so it stays reliable)
I treat scheduling as part of your broader Small Business IT plan, not a random app. If you’re planning an Office 365 Migration, I map Shifts and identity to your Cloud Infrastructure, Secure Cloud Architecture, and Cloud Management so it stays stable on busy weekends. For shops that still depend on older Data Center Technology, I focus on Infrastructure Optimization and uptime, because your managers can’t wait on slow logins.
On the floor, Restaurant POS Support and Kitchen Technology Solutions have to work alongside Teams, so I lock down shared tablets with Endpoint Security and Device Hardening, backed by Cybersecurity Services. When you want Innovative IT Solutions without surprises, I show up as a Business Technology Partner with Tailored Technology Services and Technology Consulting, including Managed IT for Small Business, IT Strategy for SMBs, real Digital Transformation, and Business Continuity & Security.
Conclusion
If your schedules live in texts, photos, and memory, you’re paying for it in call-outs and manager stress. With Shifts, I can set clear locations, groups, roles, and rules so swaps and time off don’t break coverage. Start small, lock down permissions, and keep approvals consistent. When you’re ready, I’ll help you make Teams Shifts restaurants part of a bigger, safer operations plan.
Discover more from Guide to Technology
Subscribe to get the latest posts sent to your email.