Monthly all-staff meeting for restaurants: 45-minute agenda template

A small team talks all day, but almost never all together. The openers never see the closers, the weekend crew hears about the new menu item from a sticky note, and the same three questions get answered five different ways. A short meeting once a month, with everyone in the room, fixes more of that than any group chat.

It's different from the pre-shift huddle (coming Nov 3), which is ten minutes about today's shift, and from the weekly manager meeting, which is the leaders only. The monthly meeting is for the whole team, about the month: what went well, what's changing, one thing to learn, and their questions.

When and how long

Once a month, on a fixed day. "The first Monday at 3 p.m." is easier to plan around than a date announced a week before.
45 minutes. Long enough for a real training topic, short enough that people don't drift.
When the café is closed or quiet. Before opening, after closing, or in a slow afternoon gap with the minimum crew covering. Nobody should be half in the meeting and half on the register.
Two sessions if you have to. If openers and closers can never meet at one time, run the same agenda twice in one week rather than leave a shift out.
Feed people. A staff meal turns a meeting into something people come to on purpose. Our employee meal policy covers how to set that up.

The time is paid

If you require people to come, it's work time. Under the federal rules, time at meetings and training "need not be counted as working time" only if four things are all true: "Attendance is outside of the employee's regular working hours", "Attendance is in fact voluntary", "The course, lecture, or meeting is not directly related to the employee's job", and "The employee does not perform any productive work during such attendance" (29 CFR 785.27).

An all-staff meeting fails at least two of those. And "voluntary" means really voluntary: attendance "is not voluntary in fact if the employee is given to understand or led to believe that his present working conditions or the continuance of his employment would be adversely affected by nonattendance" (29 CFR 785.28).

So put the meeting on the schedule, have people clock in, and pay it like any other shift. Two practical consequences:

It counts toward overtime. A 45-minute meeting can tip someone who works 39.5 hours that week over 40. Check the schedule for that week before you set the date.
It counts toward teen hour limits. Federal and state rules limit when and how long under-18s may work; a 4 p.m. meeting on a school day is part of that day's hours. Our state pages on hiring minors cover the local rules.

Before the meeting

A week ahead: confirm the date, time and place, and add it to everyone's schedule.
Collect questions. A box by the time clock or a shared chat where people can drop questions. Anonymous paper slips get you the honest ones.
Pick one training topic and the person who'll run it. Hands-on beats slides: a new drink built in front of everyone, the allergen matrix used on three real orders, the fire extinguisher pulled off the wall.
Two days ahead: share the agenda, so nobody arrives wondering if they're in trouble.

The 45-minute agenda

Copy this and keep the times.

Time	Item	Who	What it sounds like
0:00–0:05	Welcome and the month in one line	Owner or GM	"Busy month: the new cold brew sold out twice. Thanks."
0:05–0:12	Wins and recognition	Owner or GM	Name three specific things people did, not "great job everyone"
0:12–0:20	What's changing	Owner or GM	One or two changes only: a menu item, a policy, the holiday schedule
0:20–0:35	Training topic	One team member	Hands-on, with everyone trying it
0:35–0:43	Your questions	Owner or GM	Answer the collected questions first, then the room
0:43–0:45	Next month	Owner or GM	The next date, and what you'll report back on

A few rules keep it useful:

No individual criticism. If one person's work needs correcting, that's a private conversation; our guide to coaching on the floor shows how.
Specific recognition. "Maya caught a wrong milk on a tagged allergy order on Saturday" teaches the whole room something. Our post on low-cost staff recognition (coming Nov 7) has more ideas.
Answer or promise. A question you can't answer today gets a named person and a date, and goes on next month's agenda.
Leave the money talk simple. Sharing whether the month was busy is fine; reading out a P&L to the team usually isn't the point.

After the meeting

Post short notes within 24 hours: the changes, the training points, each question with its answer or the person who owes one. Anyone who missed it reads them.
Check the training stuck. A short quiz or a spot check during the next week shows whether it landed.
Do the things you promised. The fastest way to kill a monthly meeting is the same unanswered question two months running.
Ask for feedback once a quarter: one thing to keep, one to change.

Your all-staff meeting checklist

[ ] A fixed monthly day and time, 45 minutes
[ ] On the schedule as paid time, with an overtime and teen-hours check
[ ] Questions collected in advance, anonymously if possible
[ ] One hands-on training topic, run by a team member
[ ] The agenda shared two days ahead
[ ] Specific recognition; no individual criticism
[ ] Notes posted within 24 hours, with every question answered or owned
[ ] Promises followed up at the next meeting

Where Mays fits

The meeting on the schedule. Add a short shift for each person at the meeting time, so it's on their schedule and their clock-in pays it. It also counts in the schedule's OT warnings tile and, with minors' rules on, in the minors warnings. See Building the schedule.
A reminder on the day. Add the meeting as an event in the schedule's Events row. Everyone with a published shift at that location that day gets a push in the morning, which, with a meeting shift, means everyone who's coming. See Schedule events and birthdays.
Questions and notes in one place. Start a group chat for the team to drop questions, and post the notes in a Knowledge Base folder shared with everyone, readable in the app. See Group chats and Knowledge base basics.
Check the training stuck. An admin can turn the training topic into a short quiz module (the AI drafts questions from your Knowledge Base) and assign it with a due date; pop quizzes then ask people on shift a question from it. See Assigning training and Pop quizzes.

What Mays doesn't do: there's no anonymous question box and no meeting minutes template; use paper slips and a Knowledge Base article.

Make it the meeting people expect

Same day, same 45 minutes, paid, with the team's questions answered and one useful thing learned. After three months, people stop asking whether they have to come and start bringing questions.

Start your free trial: 30 days, every module, no card needed. Or book a walkthrough and we'll set up the meeting shift, reminders and notes folder with you.