# Staffing for season in South Florida: from last season's covers to a head count and a hiring calendar

*Guides · Mays Team · November 18, 2026*

![Mays cover card: Staffing for season in South Florida: from last season's covers to a head count and a hiring calendar — Covers per labor hour, a head count and a hiring calendar](https://mays-uploads.s3.us-east-2.amazonaws.com/site/blog__south-florida-season-staffing-covers-headcount__cover.ba88497094.png)

Part-year residents start coming back around November, and they leave around May 15, when schools up north let out. In between, a South Florida restaurant or café can serve far more guests a week than it does in August. The schedule has to grow with them, and the people on it have to be hired and trained before the busiest weeks, not during them.

This is the first post in our series **Getting a restaurant or café through South Florida's season**. Our [snowbird season playbook](https://www.mays.app/blog/snowbird-season-south-florida-restaurants) covers the whole season in one page. This post goes deeper on one part: turning last season's numbers into how many people you need, in which positions, and when each one has to start.

*Every business number in this post is hypothetical, there to show the math. Use your own. This is general information, not legal advice.*

## Plan from covers, not only sales

Sales tell you what the season is worth. Covers tell you how much work it is. If you raised prices since last season, the same sales mean fewer guests, and fewer guests need fewer hands.

So pull two things from your POS for last season, week by week from November to May:

- **Covers** (guests served) for a table-service restaurant, or **transactions** (tickets) for a counter-service café.
- **The same numbers by daypart:** breakfast, lunch, the afternoon and dinner, whatever your day looks like.

If your POS doesn't record guest counts, transactions are the next best thing. If it doesn't split by hour, pull hourly sales for a few typical weeks and divide by your average check.

## Step 1: Find your busiest weeks

Sort last season's weeks by covers. Most South Florida operators see two peaks: the holiday weeks from Thanksgiving to New Year's, and a long run from January to March. Note which weeks they were for you, and how many covers the busiest normal week had (not a one-off event week).

**Align by weekday, not by date.** Christmas fell on a Thursday in 2025 and falls on a Friday in 2026, and so does every holiday with a fixed date. Compare the second Saturday of February with the second Saturday of February, not February 14 with February 14.

## Step 2: Set a covers-per-labor-hour standard for each position

Pick a shift from last season that went well: tickets on time, nobody overwhelmed, nobody standing around. Divide its covers in the busiest hour by the people working that hour in each position. That's your standard.

| Position | Peak hour on a good Saturday (hypothetical) | People on | Covers per person per hour |
| --- | --- | --- | --- |
| Servers | 80 covers | 4 | 20 |
| Line cooks | 80 covers | 3 | about 27 |
| Bussers and runners | 80 covers | 2 | 40 |

Your standard is yours: it depends on the menu, the layout and how experienced the team is. Don't borrow one from another restaurant.

## Step 3: Turn the peak week into hours by position

For each daypart of the peak week, divide the covers by the standard to get the variable hours. Then add the fixed hours that don't grow with guests: opening and closing, side work and prep.

Hypothetical servers, peak week:

| Daypart | Covers in the week | Server hours (covers ÷ 20) |
| --- | --- | --- |
| Lunch, 11 am to 3 pm | 1,400 | 70 |
| Dinner, 5 to 9:30 pm | 2,100 | 105 |
| Setup, side work and closing |  | 28 |
| **Total** |  | **203** |

Do the same for each position. A busy hour needs more people than an average one, so check the peak hour on your busiest day separately: if the standard says four servers and you only schedule three, the plan fails on Saturday night even when the weekly hours look right.

## Step 4: From hours to a head count

Hours don't fill a schedule; people do. To get a head count:

1. **Divide by the hours people want.** If your servers want about 30 hours a week, 203 hours is about 7 servers.
2. **Check the 40-hour line.** Planning on several people working 45 hours means paying overtime every week of the peak. Plan to stay under 40 and keep overtime for emergencies.
3. **Check availability.** Students, second jobs and trips home cut into what people can actually work in December and March.
4. **Add a buffer** for call-outs and for people who leave mid-season. Hypothetically, one extra person for every six or seven.

So 203 server hours becomes 7 servers, plus 1 for the buffer: **8**. If you have 5 now, you're hiring 3.

| Position | Peak-week hours | Hours per person | People | Buffer | Need | Have | Hire |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Servers | 203 | 30 | 7 | 1 | 8 | 5 | 3 |
| Line cooks | 157 | 35 | 5 | 1 | 6 | 4 | 2 |
| Bussers and runners | 96 | 25 | 4 | 1 | 5 | 3 | 2 |

*All numbers hypothetical.*

## Step 5: Check the hours against the budget

Multiply each position's hours by its average hourly cost, add them up and compare the total with the peak week's forecast sales times your labor target. If the plan costs more than the target allows, look at the standard and the fixed hours before you cut people: an extra hour of side work on every shift adds up fast.

Florida's minimum wage is the floor for every number in this table. FloridaCommerce says: "Effective September 30, 2026, the Florida minimum wage will be $15.00 per hour," and "The $15.00 per hour will be effective from September 30, 2026, to December 31, 2027" ([FloridaCommerce](https://floridajobs.org/florida-minimum-wage)). So there's no state increase in the middle of this season. The playbook has the tipped cash wage, and our [labor cost guide](https://www.mays.app/blog/labor-cost-percentage-weekly-review) covers budgets in detail.

## Step 6: Build the hiring calendar backward

Start from the first week you need the full crew and work back:

| Step | How long (hypothetical) | For a crew needed from December 19 |
| --- | --- | --- |
| Full crew on the schedule |  | December 19 |
| Training until they can work a station alone | 2 weeks | Start by December 5 |
| From job post to first day | 2 weeks | Post by November 21 |

If the date has passed, hire anyway and train in the slower midweek shifts. For the January to March peak, do the same again: some people you hire for the holidays will leave, and the second wave needs time to train too.

**The food handler deadline.** Florida's training law says: "Food service employees must receive certification within 60 days after employment" ([s. 509.049, F.S.](http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0500-0599/0509/Sections/0509.049.html)). A December hire needs it by February, in the middle of the peak, so book it in their first week. Our [food handler training guide](https://www.mays.app/blog/florida-food-manager-food-handler-training) covers the approved programs.

## Step 7: Re-forecast in early January

By the first week of January you have this season's own numbers. Compare the covers for each week since November with last season's same weeks, aligned by weekday.

- **Running ahead of last season?** Raise the January to March plan by the same share, and hire the second wave sooner.
- **Running behind?** Hold off on new hires and offer extra shifts to the people you have first.
- **About the same?** Keep the plan, and check it again at the start of February.

Write the plan down with its numbers. When the season ends, it's the first thing to compare against.

## Where Mays fits

- **The Forecast** (**Scheduling → Forecast**): with Square or Union connected, Mays projects each day's sales from the same weekday over the last 8 weeks, with recent weeks counting more. That makes it an in-season tool. It follows a ramp-up late and doesn't know holidays, so click a day and type your own number. Weeks more than about 8 weeks out have no projection, so plan the season from last season's POS reports.
- **Unit forecast:** with Square, pick the items that stand for your work, such as entrées or coffees, and see how many sell each hour and the peak hour. It's a stand-in for covers by hour.
- **Weekly budget** on the schedule, which turns amber when scheduled labor goes over it, and **Scheduling → Reports → Actuals**, with projected sales, actual sales and labor % by day.
- **Labor Cost** (**Insights**): the **Staffing vs Revenue Heatmap** shows each half hour of the week by labor % of revenue, so you can see where last week was over- or understaffed.
- **New hires** go in under **Locations & Users → Users → Add User**, and employees get a text with a link to the app.

Mays doesn't count covers or guests, and its forecast doesn't look back to last season. Use your POS's year-over-year reports for the season plan, and Mays for the week in front of you.

## Your season staffing checklist

- Last season's covers or transactions, week by week and by daypart
- The two peaks marked, with weeks aligned by weekday
- A covers-per-labor-hour standard for each position, from a shift that went well
- Peak-week hours by position, including fixed hours, and the busiest hour checked separately
- A head count for each position, under 40 hours, with availability checked and a buffer added
- The plan's cost checked against the forecast and your labor target
- A hiring calendar worked back from the first full-crew week, and again for January
- Food handler training booked in each hire's first week
- A re-forecast in the first week of January

## Plan the season in Mays

Forecast the week, set a budget and see where the hours went, in one app.

[**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-south-florida-season-staffing-covers-headcount) and we'll set up your schedule with you. Next in this series: hiring seasonal staff in Florida.

## Related help articles

- Scheduling: [Sales forecast and labor budget](https://www.mays.app/help/scheduling/sales-forecast-and-labor-budget) — See each day's projected sales from your POS history next to the weather, adjust the projection, and compare it with scheduled labor and your weekly labor budget.
- Scheduling: [Scheduling reports](https://www.mays.app/help/scheduling/scheduling-reports) — Ten ready-made reports on sales, labor, hours, overtime, time off, attendance, the shift pool and tips — for any date range, one location at a time, with CSV export.
- Reports & insights: [Labor cost insights](https://www.mays.app/help/reports-insights/labor-cost-insights) — Labor Cost compares staffing with sales hour by hour, scheduled hours with hours worked, and tracks labor cost as a share of sales over time. Web app, admins by default.
- 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.
- Team & roles: [Add and invite team members](https://www.mays.app/help/team-roles/add-team-members) — Add people on the web or from the app. Employees get a text with a link to the app; managers and admins get an email to set a password. Plus resending invites and checking delivery.

Canonical: https://www.mays.app/blog/south-florida-season-staffing-covers-headcount
