Hosting a dinner party: menu, quantities and a cooking timeline

A menu that fits your kitchen and every guest's needs, the amounts per person, what to make ahead, and a cooking timeline worked back from the moment food goes on the table, so the oven holds one temperature at a time.

A menu that fits the kitchen Understand

A dinner party is a small event with a full plan: the guests, the menu, the shopping, the cooking, the table and the evening. The menu is where most of the plan is decided, and the kitchen limits it before taste does. The University of Minnesota's guide to quantity cooking says equipment limits the menu: with little oven space, roasts, baked potatoes and hot apple pies may all be out (University of Minnesota Extension's Planning the quantity food occasion). The University of Maryland's holiday timeline says to plan the menu around oven space and other equipment, such as slow cookers, and to check that the roasting pan fits the oven (University of Maryland Extension's 8-day holiday meal timeline).

Before choosing dishes, write down what the kitchen has.

One cooks, one is made ahead, one needs nothing

A pattern that suits a small kitchen: one dish cooks while the guests arrive, one is made a day ahead and reheated, and one or more need no cooking at the last minute (a salad, bread, a bought dessert). The pattern keeps the host's last half hour short. It is a planning habit, not a rule; a menu that needs two hot dishes at once can work with two ovens, a slow cooker or a stovetop dish. Convention

The test that matters is the oven in the last hour. List every dish that needs the oven on the day, with its temperature. If two need different temperatures in the same window, change one: move it earlier and reheat it, move it to the stovetop or the microwave, or swap it for a dish that needs no heat. The cooking timeline finds the conflict on paper, before it happens in the kitchen.

How the food reaches the table

The serving style changes what the kitchen and the table need. Minnesota's guide describes three. A plated meal (Minnesota calls it a plate meal) has each dish served onto each person's plate in the kitchen. Family style puts dishes on the table to pass, which needs extra serving pieces and food that passes easily. A buffet sets the food out for guests to serve themselves; Minnesota notes that at a buffet, portion control is lost. For six to eight people around one table, family style is common; for more people than the table seats, a buffet is. If you serve a buffet, FDA's buffet rules apply, and they are under Go deeper and in Feeding a crowd.

A full plate for every guest: diets and allergies

Ask before you plan the menu, not after. The invitation or the first message can carry the question: is there anything you do not eat, for any reason? Guests and invitations covers wording and timing. Three kinds of answer come back, and each asks something different of the menu.

• A diet by choice or belief, such as vegetarian, vegan, halal or kosher. Ask what it includes for this guest (eggs? dairy? fish? stock made from meat?) rather than assume.
• A food allergy, where a small amount of a food can cause a reaction. Ask what they avoid and how strictly.
• Other needs, such as a medical diet or a dislike. Ask what they would like you to do.

The goal is a complete plate for each guest: a main, sides and dessert they can eat, not a plate of sides around a gap. One way is a dish everyone can eat; another is a separate main for one guest, cooked on its own pan. Check the hidden ingredients: a vegetable dish made with chicken stock is not vegetarian, and a packaged meat can carry seasonings that contain allergens, as FARE's guide for hosts points out (FARE's tips for hosting with food allergies). Learn Meal Planning's People at your table covers reading labels for a household.

The major allergens and what a label tells you

FDA names nine major food allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame (FDA's Food Allergies page). The federal labeling law requires packaged foods to declare them. Two limits on labels matter to a host. FDA says the labeling law does not cover most food sold at retail or food service without a package label, such as a cake from a bakery counter or a loaf from a bakery shelf with no label. And "may contain" statements are voluntary: a package without one may still have been made on shared equipment. So for a bought dessert or bread, ask the bakery, and give the answer to the guest. Ask the authority

Cross-contact

Cross-contact is an allergen getting into a food that does not contain it, in amounts too small to see. FARE's page explains that cooking does not reduce the chance of a reaction, which is how cross-contact differs from bacteria. Its example: a knife used for peanut butter and only wiped before spreading jelly can carry enough peanut protein to cause a reaction (FARE's Avoiding Cross-Contact page). What FARE says to do, as a host can apply it:

• Wash pans, boards and utensils in hot, soapy water before you make the guest's food. Soap removes allergen protein from hands; FARE says hand sanitizer does not.
• Give every dish its own serving utensil, and keep ladles and tongs in their own dish.
• Keep the packaging, or photograph the ingredient labels, so the guest can read them.
• At a buffet, let guests with food allergies serve themselves first. At a family-style table, pass each dish to them first. Convention

Many guests with allergies will say what works for them; some will bring their own dish, which FARE suggests guests do in a separate container with its own utensil. That is not a failure of hosting. Ask whether they would like to.

How much to make

For a seated dinner, the per-person amounts below come from Iowa State University Extension's party planning post, written by one extension staff member for graduation parties (Iowa State's AnswerLine post on party food). They are one writer's planning conventions, and they are the only per-person figures we found from an extension service. Convention

Three things to know about the figures.

• The post does not say raw or cooked. Its per-person protein column gives 6 to 8 ounces; its 50-guest column gives raw meat for sandwiches and sliders. Bone and trimming add weight you do not eat. Learn Meal Planning's How much to buy explains the difference between what you buy and what you eat (the yield), and how to scale a recipe.
• A recipe's yield is another figure. If the recipe says it serves 4 and you seat 6, multiply by 1.5. Compare the result with the table; if they disagree, the recipe knows its own dish better.
• A guest who eats a different main changes the count. If one of six is vegetarian, the meat main is for five, and the dish that is their main is a main-size portion for them plus a side portion for everyone else.

The food calculator does the multiplication for a seated dinner and gives the 1 to 1.5 pound check. The turkey calculator gives the bird's weight at 1 pound per person and the thawing dates. FSIS's turkey figure is the one federal per-person amount; a practitioner figure of 1.5 to 2 pounds, for leftovers, is under Go deeper.

Make-ahead and the days before

Most of a dinner party's work can happen before the day. Two extension timelines written for holiday meals show the pattern. Maryland's eight-day timeline makes and freezes dishes four or five days ahead, thaws them in the refrigerator two or three days ahead, makes desserts, prepares vegetables and assembles casseroles the day before, and sets the table the night before. Alabama's schedule finishes the shopping and the freezer dishes on Monday for a Thursday dinner, makes sauces and vegetables and sets the table on Tuesday, and bakes and peels on Wednesday (Alabama Extension's Timing Is Everything). Both sets of days are side by side under Go deeper.

For a smaller dinner, the dinner plan's timeline starts with a few rows we use as this manual's convention: shopping two days ahead, the table set the night before, and dishes made ahead the day before. Convention

Food cooked ahead: the rules that apply

A make-ahead dish is one cooked fully, chilled and reheated before serving. FSIS's guidance sets four rules for it.

1. Cook it fully. FSIS's Cooking for Groups booklet says not to partly cook food to finish later (FSIS's Cooking for Groups booklet). Bake the casserole through on the day you make it.
2. Chill it fast. Put it in shallow containers and into the refrigerator within 2 hours of cooking. FSIS says hot food can go straight into the refrigerator; divide large amounts first (FSIS's Leftovers and Food Safety page).
3. Keep it cold. At 40°F or below. Leftovers keep 3 to 4 days in the refrigerator by FSIS's leftovers page, so a dish made the day before is well inside it. Learn Meal Planning's How long food keeps has the storage times.
4. Reheat it to 165°F. Check the center with a food thermometer. FSIS's chart gives 165°F for casseroles and leftovers (FSIS's Safe Minimum Internal Temperature Chart).

Community suppers that serve the public follow stricter make-ahead rules than these home guides; Feeding a crowd has them.

The cooking timeline, worked back from serving

A cooking timeline is a list of every kitchen task with the clock time it starts, worked backward from the serving time, the moment the food goes on the table. Alabama's schedule is the model: for a noon meal, the turkey goes in at 7:00, the side dishes follow through the morning, the turkey is checked at 11:00, the rolls bake at 11:30 as oven space frees, and the food is plated at 11:50. Tasting Table's holiday timeline puts the method in one line: count backward from when you want to sit down (Tasting Table's Thanksgiving timeline).

How to work it back

1. Write the serving time at the bottom. Then the time guests arrive. The dinner plan seeds guests at 30 minutes before serving, our convention.
2. For each dish, write its oven or burner temperature, its cooking minutes and its resting minutes. These come from your recipe. Resting time is the time a cooked dish stands out of the oven before it is cut or served; FSIS gives a minimum 3-minute rest for steaks, chops and roasts of beef, pork, veal and lamb, and recipes often give longer rests for quality.
3. Subtract. Serving time minus resting minus cooking minus preheating gives the start time. Write it as a clock time, not "about an hour before".
4. Mark the oven windows. Draw each oven step as a block from start to finish with its temperature. Two blocks at the same temperature can overlap if both pans fit. Two blocks at different temperatures cannot overlap. Where they do, move one.
5. Add the tasks that are not cooking. Emptying the oven, preheating, filling platters, dressing the salad, opening the wine.

The planner on the dinner plan page sorts your rows by clock time from the serving time in setup and flags two oven rows at different temperatures in the same window. It also seeds a row for freeing the oven for the main, our convention: empty it, set the racks, then preheat. Convention

Where the times come from

The minutes and temperatures on a timeline come from recipes. FSIS gives the safe internal temperatures, not recipe times: 165°F for all poultry, casseroles and reheated leftovers; 145°F plus a 3-minute rest for whole cuts of beef, pork, veal and lamb; 145°F for fish; 160°F for ground meat. A recipe's time is an estimate of when the dish reaches its temperature in the writer's oven. The thermometer tells you when it has reached it in yours. Test it For a roast, FSIS also says to set the oven no lower than 325°F.

Keeping food hot until it is served

Hot food stays safe at 140°F or above. FDA's buffet page says hot back-up dishes can wait in an oven set at 200°F to 250°F, and warns that some warmers hold food at only 110°F to 120°F, so check the label (FDA's Serving Up Safe Buffets page). FSIS's page on cooked dinners says it is not a good idea to keep food hot longer than 2 hours; for a meal much later, refrigerate it and reheat to 165°F (FSIS's Handling Cooked Dinners page). A warm oven holds one temperature too: a dish waiting at 200°F occupies the oven another dish might need at 425°F.

Drinks

Plan the drinks without alcohol as carefully as the wine. NIAAA's host tips say to offer alcohol-free choices such as water, juices and sparkling sodas, to serve food with drinks, and to arrange designated drivers or taxis (NIAAA's The Truth About Holiday Spirits). A pitcher of water on the table and one nonalcoholic drink chosen on purpose cover most dinners.

For buying wine, NIAAA counts a regular 750 ml bottle as 5 standard drinks (NIAAA's drinks in common containers). A standard drink of wine is 5 ounces at 12 percent alcohol (NIAAA's What Is A Standard Drink). NIAAA notes that standard drinks may not match the glasses people pour. The arithmetic shows why that matters: a 750 ml bottle holds about 25.4 fluid ounces, so it gives about 5 pours of 5 ounces but only about 4 of 6 ounces.

To estimate bottles: count the guests you expect to drink wine, multiply by the glasses you expect each to have, and divide by the pours per bottle. Those are your assumptions, and the answer is a supply estimate, not a recommendation of how much anyone should drink. The drinks calculator does the same for a longer party, with ice. Rides home, a guest who has had too much, and guests under 21 are in Feeding a crowd.

The evening and the leftovers

The plan is built so the host is out of the kitchen when guests arrive and when the food is ready. With a timeline, the last half hour is a few short trips: pull a pan, check a temperature, fill the platters. Write those trips on the run sheet if you keep one; for a dinner, the timeline can be the run sheet.

• Before guests arrive. Empty the dishwasher, clear the counter you need for platters, put out the water and glasses.
• At the table. Dishes with their serving utensils; the guest with an allergy offered each dish first, or told which dish is theirs.
• After the meal. Perishable food goes into the refrigerator within 2 hours of serving, in shallow containers, by FSIS's leftovers page. Set a timer for two hours after serving if the evening runs long. Dessert does not reset the clock for the main.
• Guests leaving. Food sent home goes in the refrigerator within 2 hours too; FDA's buffet page says the same of "doggie bags".

If a guest cancels the afternoon of the dinner, the timeline does not change; the plan for that is in The contingency plan.

See it: Marcus's dinner for six See it

Free pages that show the method: Alabama Extension's day-of schedule (a whole meal worked back to noon), Maryland's eight-day timeline (the days before), and FARE's cross-contact page (why a wiped knife is not clean).

Practice: plan one dinner on paper Practice

Minimum: a menu with each guest's needs checked against it, and a cooking timeline with clock times for one dinner. Time: about 45 minutes, plus the time for guests to answer. Materials: your recipes, the guests' answers about what they cannot eat, a food thermometer if you own one, and the dinner plan sheets (menu and timeline).

1. List the kitchen. Oven, racks, burners, microwave, slow cooker, free refrigerator space, counter, seats and serving pieces.
2. Fill the menu sheet. One row per dish: when it is made (days ahead, morning of, last hour, bought), oven or stovetop, temperature, cooking and resting minutes, how many it serves, and the major allergens it contains.
3. Check each guest's plate. Read the menu as each guest with a need would. Does each have a main, a side and a dessert? Is any allergen hidden in stock, seasoning or a bought item?
4. Write the amounts and the shopping list. Use the food calculator or the table in how much to make, and compare it with your recipes' yields.
5. Fill the timeline sheet backward from serving. Enter the serving time, then each task with its minutes before serving. Read the sorted view and fix any flagged oven conflict.

Your event Your event

Check your work Check your work

Criteria

• Did you ask every guest what they cannot eat, and how strictly for an allergy?
• Does every guest have a complete plate, with hidden ingredients (stock, seasonings, bought items) checked?
• Does every dish on the menu have its temperature and minutes, from your recipe?
• Do the amounts come from a stated figure (the per-person convention or the recipe's yield), multiplied by the people who will eat that dish?
• Does the timeline give every dish a clock start time, worked back from serving?
• Do any two oven steps at different temperatures overlap?
• Is there a time by which leftovers go into the refrigerator?

Worked example

Marcus's menu sheet has six rows, each with its temperature, minutes and allergens; the gratin row says "vegetable stock; contains milk and wheat". His timeline runs from Thursday's shopping to 9:30 pm, and its two oven windows meet at 7:05 without overlapping. His wine line says "2 bottles, 10 pours; assumes 4 drinkers, 2 glasses each". It passes. It does not yet say whether the bakery dessert works for the guest with the allergy, because the guest has not answered.

Common mistakes

• Two dishes at two temperatures in the last hour. Draw the oven windows; the overlap shows on paper.
• A vegetarian plate of sides. Give that guest a main.
• Trusting a missing "may contain". The statement is voluntary, and unpackaged bakery food has no label. Ask.
• Counting the host out. Six at the table means six portions.
• Timing by the clock alone. The thermometer says when a dish is done.
• Leaving the food out through dessert and coffee. Two hours from serving, it goes in the refrigerator.

What is still unresolved

What each guest can safely eat is settled by the guest; the questions to ask are in Guests and invitations. Food for more people than one table, or served to the public, is in Feeding a crowd. The rest of the evening, from setup to the dishes, goes on The run sheet, and the what-ifs on The contingency plan. The dates for invitations and shopping are on The planning schedule.

Knowledge check and scenario

Checklist

• Every guest has been asked what they cannot eat, and the answers are on the menu sheet.
• The menu gives every guest a complete plate, and every dish has its temperature, minutes and allergens.
• The amounts and the shopping list are written.
• The timeline lists every dish with a start time, and no two oven steps at different temperatures overlap.
• The drinks include a nonalcoholic choice, and the wine count rests on written assumptions.
• I cooked the newest dish once and put my own minutes on the timeline. (Go deeper; optional)