# Server section chart template: sections, a fair rotation and the cut order

*Guides · Mays Team · July 5, 2026*

![Mays cover card: Server section chart template: sections, a fair rotation and the cut order — One floor plan, one sheet a shift, and a rotation nobody has to argue about](https://mays-uploads.s3.us-east-2.amazonaws.com/site/blog__server-section-chart-template-restaurant__cover.90f6297ba1.png)

Ask servers what makes a shift go wrong and the section comes up fast: one person gets the six-top by the window and the booths, another gets the two-tops by the kitchen door, and the host keeps seating the server who's standing closest. Nobody planned it that way. It just wasn't written down.

A section chart fixes that with two pieces of paper. One is the **floor plan**: every table numbered and grouped into sections for each number of servers. The other is the **section sheet** for the shift: who has which section, when they break, what sidework they own and the order they're cut. This post gives you both, plus a rotation rule and a seating tally for the host.

## Part 1: number every table

Before sections, tables need numbers that never change. Number them in the order a guest walks through the room, and write the seat count next to each one.

| Table | Seats | Where it is | Notes |
| --- | --- | --- | --- |
| 1 | 2 | Window, front left |  |
| 2 | 2 | Window |  |
| 3 | 4 | Window, front right |  |
| 4 | 4 | Center | Pushes together with 5 for an 8-top |
| 5 | 4 | Center |  |
| 6 | 6 | Booth, back left |  |
| 7 | 6 | Booth, back right |  |
| 8 | 2 | Near the kitchen door |  |
| 9 | 2 | Bar side |  |
| 10 | 4 | Patio | Patio open: \[seasonal / weather\] |
| … | … | … |  |

Total seats: \[count\]. Write the push-together pairs in the notes, so a [large party](https://www.mays.app/blog/large-parties-groups-cafe-restaurant) doesn't leave someone's section half empty.

## Part 2: the section chart

Draw one layout for every number of servers you staff. Most rooms need three: slow, normal and busy. Balance each section on **seats**, not tables, and give everyone one or two "good" tables (the window, the booths) and one or two tough ones (by the door, by the kitchen).

| Servers on | Section 1 | Section 2 | Section 3 | Section 4 |
| --- | --- | --- | --- | --- |
| 2 | Tables 1, 2, 3, 4, 5 (\[18\] seats) | Tables 6, 7, 8, 9 (\[16\] seats) | — | — |
| 3 | Tables 1, 2, 3, 8 (\[10\] seats) | Tables 4, 5, 9 (\[10\] seats) | Tables 6, 7 (\[12\] seats) | — |
| 4 | Tables 1, 2, 3 (\[8\] seats) | Tables 4, 5 (\[8\] seats) | Tables 6, 8 (\[8\] seats) | Tables 7, 9 (\[8\] seats) |
| Patio open | Add table 10 to section \[ \] |  |  |  |

The bracketed seat counts are the example room above; replace them with yours. How many tables one server can carry depends on your menu, your steps of service and whether food is run by someone else, so set the sizes from what your best shifts looked like, then adjust after a few weeks of watching where people fall behind.

Rules worth writing under the chart:

- **Each section is next to its own service station** where possible, so nobody crosses the room for water.
- **The closing section is the one nearest the station that closes last**, so the closer isn't the person furthest from the dish pit.
- **When a section is closed**, its tables are blocked off at the host stand, not just left unseated.

## Part 3: the nightly section sheet

Print one per shift and fill it in before the [pre-shift huddle](https://www.mays.app/blog/pre-shift-huddle-agenda-template). It's the page the host, the servers and the manager all read.

---

**\[Restaurant name\] — Section sheet**

Date: \[date\] · Shift: \[lunch / dinner\] · Manager on duty: \[name\] · Layout: \[2 / 3 / 4 servers\]

| Section | Server | In | Break | Sidework owned | Cut order | Out |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | \[name\] | \[4:00\] | \[6:30–7:00\] | \[Lemons, iced tea\] | \[1st\] |  |
| 2 | \[name\] | \[4:00\] | \[7:00–7:30\] | \[Silverware rolls\] | \[2nd\] |  |
| 3 | \[name\] | \[4:30\] | \[7:30–8:00\] | \[Station restock, closing station\] | \[Closer\] |  |
| Float / bar | \[name\] | \[5:00\] | \[—\] | \[Runs food, buses\] | \[3rd\] |  |

- Large parties tonight: \[time, size, table, section\]
- 86'd items / specials: …………………………
- Closed sections or tables: …………………………
- Who covers a section on break: Section 1 → \[name\], Section 2 → \[name\], Section 3 → \[name\]

Manager sign-off: ………………………… Time: ……………

---

Some notes on the columns:

- **Break.** Stagger them so two neighboring sections are never both off the floor, and name who covers. Check your state's meal and rest break rules before you set the times.
- **Sidework owned.** One line per person, from your [sidework checklist](https://www.mays.app/blog/server-sidework-checklist-template), so running and closing duties follow the section.
- **Cut order.** Decide it before service, not at 8:45 when the room empties. The first cut takes no new tables after \[time\] and finishes their checkouts; the closer is last.

## Part 4: rotate sections fairly

Write the rule down and post it next to the chart. Two common ones:

1. **Rotate weekly.** Section numbers move up by one each week: whoever had section 1 has section 2 next week, and section 3 wraps back to 1.
2. **Rotate by shift.** Keep a small log of who had which section each shift and give the next good section to whoever has had it least.

| Week of | Section 1 | Section 2 | Section 3 | Closer |
| --- | --- | --- | --- | --- |
| \[date\] | \[name\] | \[name\] | \[name\] | \[name\] |
| \[date\] | \[name\] | \[name\] | \[name\] | \[name\] |
| \[date\] | \[name\] | \[name\] | \[name\] | \[name\] |

Whatever you pick, apply it to everyone. If a section is given as a reward or a training step, say so on the sheet; unexplained favorites are what make a section chart feel unfair. Our post on fair scheduling (coming Nov 8) has the same idea for closes and weekends.

## Part 5: the host's seating tally

Even sections only help if seating is even. Give the host a tally at the stand and have them seat in turn, skipping a server who's just been triple-sat.

| Time | Section 1 | Section 2 | Section 3 | Notes |
| --- | --- | --- | --- | --- |
| 5:00–6:00 | ✓✓ (6 guests) | ✓ (4) | ✓✓ (5) |  |
| 6:00–7:00 |  |  |  |  |
| 7:00–8:00 |  |  |  |  |
| Total guests |  |  |  |  |

Count guests, not tables: two two-tops and one four-top are the same load. When a server is in the weeds, the host skips them for one turn and tells the manager, rather than quietly sending everyone elsewhere for the rest of the night.

## When the plan changes mid-shift

- **A call-out.** Switch to the next smaller layout before the doors open rather than leaving a section uncovered. See our [call-outs post](https://www.mays.app/blog/call-outs-without-burning-out-your-team).
- **A rush.** Open the closed section only if someone can take it without dropping their own; otherwise use a wait list.
- **A cut.** The cut server closes their open checks and transfers any table that's still mid-meal to a named server, at the table, so the guest knows who's looking after them.

## Your section chart checklist

- \[ \] Every table numbered, with seats and push-together pairs
- \[ \] A layout for each number of servers, balanced on seats
- \[ \] Closing section next to the last station to close
- \[ \] A section sheet printed for every shift, with breaks, sidework and the cut order
- \[ \] Break cover named for every section
- \[ \] The rotation rule written down and posted
- \[ \] A seating tally at the host stand

## Where Mays fits

Mays doesn't have a floor plan, table numbers or a section assignment, so the chart and the nightly sheet stay on paper or a screen at the host stand. Around them:

- **The section on the shift.** In the **New shift** dialog on the web schedule, put the section in the shift's **Label**, for example *Section 2* or *Closer*. Staff see the label and the shift's **Notes** in the app, so they know their section before they arrive. (The dialog also has a **Station** field, but the app doesn't show it to staff, so use **Label**.) See [Building the weekly schedule](https://www.mays.app/help/scheduling/build-the-schedule).
- **Changes reach people.** Publishing a changed or removed shift tells the people on it. See [Publishing the schedule](https://www.mays.app/help/scheduling/publish-the-schedule).
- **The chart where staff can find it.** Put a photo of the floor plan and the rotation rule in a **Knowledge Base** folder shared with the front of house. See [Your knowledge base](https://www.mays.app/help/knowledge-training/knowledge-base-basics).
- **Sidework that follows the section.** Build the running and closing sidework as a checklist template and give a single task to one person with **Assign to person (optional)**, or assign the template to the server role so anyone on shift can pick tasks up. See [Creating a checklist template](https://www.mays.app/help/tasks-checklists/create-a-checklist-template).
- **A call-out.** **Find cover** ranks who could take the shift by their availability, time off and other shifts. See [Find cover](https://www.mays.app/help/scheduling/find-cover).

## Even sections, fewer arguments

Number the tables, balance sections on seats, write the cut order before service and rotate by a rule everyone can read. The host seats in turn and counts guests, not tables. Then the section chart stops being a nightly negotiation and becomes the first thing people check when they walk in.

[**Start your free trial**](https://go.mays.app/register): 30 days, every module, no card needed. Or [book a walkthrough](https://www.mays.app/book?from=blog-server-section-chart-template-restaurant) and we'll set up your schedule labels and sidework checklists with you.

## Related help articles

- Scheduling: [Building the weekly schedule](https://www.mays.app/help/scheduling/build-the-schedule) — Build a location's week on the web — add, move, copy and edit shifts, add open shifts, and keep an eye on time off, availability and labor cost while you work.
- Scheduling: [Publishing the schedule and notifying staff](https://www.mays.app/help/scheduling/publish-the-schedule) — Your team only sees a week once you publish it. Check the warnings, choose who gets notified, publish — and republish, undo or clear a week when plans change.
- Tasks & checklists: [Creating a checklist template](https://www.mays.app/help/tasks-checklists/create-a-checklist-template) — Build an opening, closing or cleaning checklist once as a template — groups, tasks and answer types — and Mays turns it into your team's task list in the app.
- Scheduling: [Finding cover for a shift](https://www.mays.app/help/scheduling/find-cover) — Someone can't make their shift? Open it in the Mays app, see who's free, then assign it, offer it to the team, or ask the best matches if they can take it.
- Knowledge & training: [Your knowledge base](https://www.mays.app/help/knowledge-training/knowledge-base-basics) — Keep your SOPs, recipes and policies in one place. Admins and managers build folders of articles and documents on the web; the whole team reads and searches them in the app.

Canonical: https://www.mays.app/blog/server-section-chart-template-restaurant