Fifteen Meals in Nine Days: How to Plan Sukkot Hosting Without Losing Every Afternoon

SheetSage Design · Updated August 2026

People ask how many meals Sukkot is, and the honest answer is that nobody counts until they are already behind. So here is the count for 5787, in civil dates: Sukkot begins on Friday evening, September 25, 2026. Two nights and two days of Yom Tov. Then Chol HaMoed from Monday September 28 through Friday October 2. Then Shemini Atzeret on Saturday October 3 and Simchat Torah on Sunday October 4.

That is nine days, and every one of them has a meal on it. In the example plan we built, it comes to fifteen festive meals — with a different number of people at the table on almost every one of them, and the food carried outside for most of them.

Rosh Hashanah, two weeks earlier, is hard because five or six meals arrive back to back with no shop in between. Sukkot is hard for a completely different reason: it is not intense, it is long. The failure mode is not one panicked Friday afternoon. It is nine of them.

Start by counting the meals, not the dishes

Almost everyone plans a holiday dish-first: what am I making, what else am I making, is that enough. At nine days that breaks down, because the same dish shows up at four different meals at four different guest counts and you lose track of what you have actually committed to.

Count meals first. Write one row per meal with four things on it:

• The date.
• The serving time.
• How many people.
• Whether it is in the sukkah.

That last column looks trivial and turns out to be the most consequential one on the sheet — more on that below.

One scheduling note worth knowing before you build the plan: the shape of Sukkot moves from year to year, and 5787 is one of the tighter ones. The first day of Yom Tov is itself Shabbat, and the next Shabbat in the sequence is Shemini Atzeret. That changes which meals you are able to cook for and which ones have to be finished in advance, and it is exactly the kind of thing that is obvious in September and invisible when you are copying last year's list.

The guest count is the number that moves everything

Every family recipe is written for some base number of servings, and no meal ever matches it. Sixteen on the first night, ten on Monday, eighteen on Simchat Torah. Fourteen guests on a recipe that serves eight is 1.75 batches — which means 1.75 times every single ingredient, and then the whole thing again at a different multiple for the next meal.

Do that for a dozen dishes across fifteen meals and you have done well over a thousand multiplications by hand. Most people do them twice, because they did not trust the first pass.

The structural fix is to write each recipe down once, at its own base servings, with its ingredients per batch — and then let something else carry the guest count through. Build the recipe library once and it is reusable forever; the per-meal work drops to picking rows from a list.

The shopping list stops being one trip

At one dinner you can hold the shopping list in your head. At fifteen meals you cannot, and the classic legal-pad method — go dish by dish, write what it needs, then merge the duplicates — quietly fails in both directions. You buy four separate bags of onions and you forget the eggs.

A generated list fixes both halves. Built from the menu, ingredient by ingredient, across every recipe at every meal, it merges everything into one line per ingredient. To take real figures from our example data: round challah sits on eleven of the fifteen meals, at four different guest counts, which merges into 20.25 batches, 162 servings and 40.5 lb of bread flour — one line. Kosher salt turns up in 23 recipes. Yellow onions in 12. Lemons in 9, which is 105.75 of them.

Two more things a list like that should do:

• Subtract your pantry, not your recipes. What you already have at home comes off what you buy and never off what the recipes need, or the quantities silently go wrong at the second meal.
• Sort itself by your own store. Not by category — by the departments of the shop you actually walk, in the order you walk them. Produce, then bakery, then deli, then the back of the shop. It is the single change that takes the most minutes off the trip.

The problem that only Sukkot has: the walk

Here is the one that no general holiday planner accounts for, because it does not exist at any other festival. The food is cooked in a kitchen and eaten in a sukkah, and the distance between them is part of the plan.

The kugel that came out perfect at 7:00 PM is lukewarm by the time it has crossed the yard and been served. Everyone knows this happens. Almost nobody plans around it, because it does not feel like a planning problem — it feels like bad luck.

It is a scheduling problem, and it has two halves:

Half one: every course needs a leave-the-kitchen time

If the meal is served at 7:15 PM and the carry takes twelve minutes, the food has to leave the kitchen at 7:03 PM. That is a real deadline, it is earlier than the one you were working to, and it should be written down next to the dish rather than discovered while people are already sitting down.

Half two: some dishes should not be the ones going out hot

Soups and stews survive the trip. Anything crisp does not. So mark each recipe once — does this hold its heat on the way out, yes or no — and then any dish going out hot that you marked as one that does not survive gets flagged before you commit to it.

In our example data, eleven of the fifteen meals are in the sukkah, fourteen dishes go out hot, and seven of them get flagged. The interesting part is that the same roasted cauliflower served indoors is not flagged at all. Same recipe, same oven, different answer — because the walk is different.

Make-ahead is a fortnight, not an afternoon

The thing that makes Sukkot survivable is that most of the cooking does not have to happen during Sukkot. But "make it ahead" is useless as advice unless the make-ahead work has dates on it.

In our example plan the make-ahead list runs 46 dishes across sixteen days — Thursday September 17 through Friday October 2. And note where that range ends: it runs into the festival, because a real Sukkot plan includes the cooking you do on Chol HaMoed for the nights that come after. Treating the holiday as a wall you cook up to and then stop is what produces the Thursday-night panic in the middle of the week.

Sort that list by date, mark what freezes and what only keeps a couple of days, and the plan becomes a calendar instead of a wish.

The oven is booked twice, not once

The classic Friday-afternoon failure is four dishes wanting the oven at four different temperatures in the same hour: the brisket at 325°F, the kugel at 375°F, the chicken at 400°F, the roasted vegetables at 425°F. At Sukkot that afternoon happens more than once — before the first night, and again before Shemini Atzeret.

The only way to see it in advance is to run the clock backwards: give each dish its prep time, cook time, rest and oven temperature, and work back from when you need to be out of the kitchen. Done properly it produces an actual schedule — cholent on at 7:00 AM, brisket at 12:45 PM, kugel at 3:25 PM, root vegetables at 4:10 PM, out of the kitchen by 5:45 PM — and the collisions show up while you can still move a dish. Our example run finds twelve of them across the nine days.

Price it before you shop, not after

Fifteen meals is a genuinely large grocery bill, and it is one people are surprised by every year because it arrives in three or four separate trips that never get added together.

Setting a price per unit once, on the ingredients you already typed, gets you the whole thing before you leave the house. In the example data that is $2,163.50 of food, of which $26.59 is already in the kitchen, leaving $2,136.91 to spend — against a $1,800 budget, which reads 118.7% and over by $336.91. Broken out by aisle: Produce $667.95, Meat and Poultry $598.25, Dry Goods and Baking $281.21, Canned and Jarred $219.86, Deli $116.89.

The useful figure is not the total, though. It is cost per guest-seat — $10.58 across 202 seats in the example — and the most expensive single meal, which is the first night at $285.61 for sixteen people, $17.85 a head. Knowing which meal is the expensive one is what lets you change it while there is still time to change it.

The checklist

Whatever you build it in, a Sukkot plan that survives contact with the week has six parts:

1. A meals table — date, serving time, guest count, and in-the-sukkah yes or no.
2. A recipe library written once, at base servings, with prep, cook, oven temperature, and whether it holds its heat on the way out.
3. A merged shopping list, scaled to the guest counts, minus your pantry, sorted by your own aisles.
4. Carry-out times for every course at every meal that is outside.
5. A make-ahead list in date order, running from two weeks before through Chol HaMoed.
6. A cost line per ingredient rolling up to per dish, per meal and per guest.

Doing it without a legal pad

None of those six is hard on its own. What is hard is doing all six at once, for fifteen meals, while the guest counts keep changing.

Our Sukkot & Ushpizin Hosting Planner is that system already built: eighteen meal rows covering the first night through Simchat Torah, a recipe library that scales itself to whatever guest count you type, a shopping list that writes and re-sorts itself, a cooking timeline that runs backwards from the time you set with an oven-clash alert on the row, an Out To The Sukkah panel with a leave-the-kitchen time for every course, and the whole run costed against your own budget. Nine tabs, one file, Google Sheets and Microsoft Excel, instant download, no subscription. Turn the sukkah column off after the festival and it is a Shabbat planner for the rest of the year.

If it is Rosh Hashanah you are staring down rather than Sukkot, the same system without the sukkah logistics is our Jewish Holiday & Shabbat Hosting Command Center — and if what you actually still need is the cards, we have a printable Rosh Hashanah set you can print at home the same night.

This is a planning and organizing tool, not halachic guidance and not a substitute for it. It does not rule on what may be cooked, warmed, carried or prepared, on eruv tavshilin, on kashrut, or on where and when you must eat, and it does not calculate candle-lighting times or any other zman — you type your own local time in. The ushpizin names in the file are editable labels, not a ruling; customs differ on the order, the spelling and the practice. For anything halachic, ask your rabbi. Every quantity, price, time and temperature quoted above comes from the example data included in the file and is an editable placeholder — not a recommendation, not a market price, and not a forecast of what your own Sukkot will cost. Dates given are the civil dates of Sukkot 5787.

← All guides · Browse the templates →