Restaurant manager duties and SOPs: opening, service and closing checklists

Restaurant manager duties boil down to running three checklists well: opening, service, and closing. Restaurants that write these down as SOPs (standard operating procedures) instead of relying on memory cut service errors, speed up training, and run consistently whether or not the owner is on the floor.

A restaurant without written SOPs runs on whoever happens to be working that shift. When your most experienced manager is off, standards slip. New hires guess at what “done” looks like. Health inspectors find inconsistencies that a checklist would have caught. Writing down what already works in your head is the fastest operational upgrade most independent restaurants never get around to making.

Key takeaways

• Main solution: Written opening, service, and closing checklists with a named owner and sign-off for each item
• Expected result: Fewer service errors, faster new-hire training, consistent standards across shifts
• Time to implement: 2-4 hours to draft your first full set of checklists
• Cost: Free (a shared doc, printed sheet, or your task-management tool)

Before you start

Before writing SOPs, get clear on what a manager is actually responsible for. It’s a longer list than most new managers expect.

Core restaurant manager duties:

What you’ll need to build your SOPs:

• A list of every station that opens and closes (host, bar, kitchen, floor, office)
• 30 minutes with your longest-tenured staff at each station to capture what they actually do
• A shared place to store and update the checklists (printed binder, shared doc, or your team’s task tool)

Step 1: Build the opening checklist

Opening sets the tone for the entire shift. A rushed, incomplete open creates problems that surface all night.

What to do:

1. List every task that must happen before doors open
2. Assign each task to a station, not a person
3. Order tasks by dependency (you can’t stock the bar before unlocking the walk-in)
4. Add a sign-off column

Sample opening checklist:

Reviewing the reservation book is the single highest-leverage opening task. Knowing tonight’s covers, large party bookings, and any special requests before service starts lets you staff and stage the floor correctly instead of reacting in real time. A reservation system you can check from anywhere makes this a five-minute task instead of a phone call to the office.

Step 2: Build the service checklist

Service isn’t a single checklist you complete once. It’s a set of standing checks a manager runs throughout the shift.

What to do:

1. Define check-in points across the shift (pre-peak, peak, post-peak)
2. Assign a manager or shift lead to own floor visibility
3. Build a lightweight incident log for guest issues
4. Set escalation rules so staff know when to pull in a manager

Standing service duties:

Guest issue escalation: Give staff a clear rule for when to get a manager, rather than leaving it to judgment under pressure: any complaint about food quality, billing, or a guest asking to speak to a manager gets escalated immediately. Comps and refunds route through the manager on duty.

Step 3: Build the closing checklist

Closing is where SOPs matter most, because it’s unsupervised more often than opening or peak service.

What to do:

1. Split the closing checklist by station
2. Set a hard sequence for cash-out and lockup
3. Require sign-off per station before anyone leaves
4. Build in a manager’s final walkthrough

Sample closing checklist:

Handle headcount fluctuations from the day’s covers, not guesswork. If you know tomorrow’s reservation load before locking up tonight, tomorrow’s prep list and schedule write themselves. This is also where checking for tomorrow’s large party bookings matters most: those need advance prep the regular closing checklist won’t catch on its own.

Step 4: Train staff on the SOPs

A written checklist nobody follows is worse than no checklist, it creates false confidence that things are covered.

What to do:

1. Walk new hires through each checklist during onboarding, station by station
2. Have an experienced staffer shadow-train, not just the manager
3. Post checklists somewhere visible, not buried in a binder nobody opens
4. Spot-check compliance for the first 2-4 weeks after any SOP change

Training approach by checklist:

Step 5: Build in accountability

Checklists without follow-through drift within weeks. Build a light verification layer so standards hold.

What to do:

1. Require initials or a digital check-off per completed item
2. Have a manager spot-check 2-3 items per shift, not the whole list every time
3. Review sign-off records weekly, not just when something goes wrong
4. Address gaps immediately, in private, without public callouts

Common mistakes to avoid

Writing checklists too long to actually finish

A 40-item closing list gets rushed or skipped under time pressure. Trim to what actually matters and split by station so no one person owns an impossible list alone.

No sign-off or accountability

A checklist without a name attached to each task becomes optional. Add initials or a digital check-off so completion is visible and attributable.

Treating SOPs as a one-time project

Menus change, equipment changes, staff turn over. An SOP written two years ago and never revisited stops matching reality. Review core checklists quarterly.

Manager doing everything personally instead of verifying

If the manager personally executes every closing task, the restaurant can’t run without them. The manager’s job is to verify the system works, not replace the team that should be running it.

Skipping the reservation book at open and close

Checklists focused only on physical setup miss the biggest variable in tonight’s service: how many covers and what mix of parties are actually booked. Build the book review into both the opening and closing routine.

How to measure success

Track these over the first month of running written SOPs:

Tools that help

Written checklists work on paper, but the reservation-book review at the center of your opening and closing routine works best with a system your whole team can see.

Shared reservation access lets any manager or shift lead check tonight’s or tomorrow’s book from a phone, without calling the office or digging through a paper diary.

Guest notes and history attached to bookings surface VIP details and past issues automatically, instead of relying on a manager remembering.

Table and floor visibility shows the manager what’s happening in real time during the service checklist, without walking every section constantly.

If your current setup makes checking the book a chore, look for a system that puts these three things in one place rather than spread across a phone, a paper diary, and a manager’s memory.

Staffing and pay questions the checklists surface

Two duties above deserve their own deeper guide because they carry real legal and financial weight beyond a simple checklist item:

• Staffing the shift correctly. Deciding how many servers, cooks, and hosts to schedule against tonight’s forecast covers is its own discipline. See restaurant staff scheduling for how to build a rota around demand instead of guesswork.
• Handling tips correctly. Cash-out and closing duties often include verifying tip pool distributions. Get this wrong and you carry real legal exposure. See tip out and tip pooling for how tip pools actually work and what US labor law requires.

The bottom line

Restaurant manager duties are really systems management: build the opening, service, and closing checklists once, train the team on them, and verify they hold. Start with the reservation book at open and close, since it drives staffing and prep more than any other single input. Write the checklists down this week, assign owners, and review them quarterly.

Related guides: Restaurant staff scheduling | Tip out and tip pooling | Large party bookings