Excel Meal Prep Template: Plan Meals, Shop Smarter

How-to basics · Updated November 19, 2026

Yes. An Excel meal-prep template can combine a weekly meal plan, recipe quantities, and a grocery list in one workbook. For a useful starting point, create three sheets—MealPlan, Recipes, and Shopping—and connect them with a few formulas so planned servings scale ingredient amounts automatically.

What a meal-prep workbook should do

A meal-prep spreadsheet is most useful when it answers practical questions at a glance: What are you eating each day? Which dishes can be prepared ahead? What ingredients do you need, and in what quantities? A calendar alone can answer the first question, but it will not reliably create a shopping list or adjust a recipe when the number of portions changes.

Excel does not require a special meal-planning feature. You can build a flexible template in a blank workbook, or look in Excel’s template gallery for a starting point and adapt it. The three-sheet design below keeps the schedule, recipe data, and shopping totals separate. That separation makes the workbook easier to update than a single large grid with repeated recipe details.

  • MealPlan: the dates, meals, recipe names, and servings you intend to make.
  • Recipes: one row per ingredient in each recipe, including the recipe’s batch size.
  • Shopping: a list of ingredients and quantities to buy, grouped by matching ingredient and unit.

The template can be as simple or detailed as your routine requires. You do not need to schedule every meal, track calories, or cook everything on one day for the workbook to be worthwhile.

Set up the weekly meal plan

On MealPlan, enter these column headings in row 1: Date, Meal, Recipe, Servings, Prep notes. Add one row for each meal you plan to prepare. For example, Monday lunch might be a lentil soup for two servings, while Tuesday dinner might be a roasted vegetable bowl for four. Use consistent recipe names, because the ingredient calculations depend on matching those names to the Recipes sheet.

Turn the plan into an Excel table: select the heading row and the rows beneath it, then choose Insert > Table and confirm that My table has headers is selected. Tables make it easier to sort or filter the plan and generally extend formatting and formulas as new rows are added. On Windows, Ctrl+T is a shortcut for creating a table; on Mac, use Command+T. The ribbon path works across both desktop platforms, though exact labels can vary slightly by release.

Enter actual dates rather than relying only on weekday names. Dates make it easier to plan across month boundaries and to see which meals belong to a particular week. The Meal column can distinguish breakfast, lunch, dinner, or snacks. Prep notes can record tasks such as thawing a container overnight, cooking grains in advance, or packing a sauce separately.

For a short plan, ordinary cells are enough. If you prepare food on a repeating schedule, you can add a Week of column or duplicate the table for another week. Avoid typing a long range of future dates unless you will maintain it; an out-of-date schedule is less useful than a small plan that reflects what you actually intend to cook.

Record recipes so servings can scale

On Recipes, use these headings: Recipe, Ingredient, Amount per batch, Unit, Batch serves, Planned servings, Amount needed. Each ingredient in a recipe gets its own row. If a chili recipe serves four and uses two cans of beans, enter Chili, kidney beans, 2, cans, and 4 in the first five columns. Add separate rows for tomatoes, onions, and the other ingredients. Keep units consistent for a given ingredient; do not mix grams and cups in the same total.

The Planned servings column can add up the servings assigned to each recipe on MealPlan. With recipe names in Recipes!A2:A200, and names and servings in MealPlan!C2:C36 and MealPlan!D2:D36, enter this in Recipes!F2:

=SUMIF(MealPlan!$C$2:$C$36,A2,MealPlan!$D$2:$D$36)

For example, if Chili appears twice in the meal plan, once for four servings and once for two, the formula returns 6 on each Chili ingredient row. Copy the formula down the Planned servings column. The references with dollar signs stay fixed as the formula is copied, while A2 changes to the recipe name on each row.

To calculate the amount needed, put this formula in Recipes!G2, assuming the per-batch amount is in C2, planned servings in F2, and the batch yield in E2:

=C2*F2/E2

For the example of two cans of beans in a four-serving batch and six planned servings, the result is 3 cans. Copy the formula down. If a recipe is not scheduled, Planned servings is zero and the calculated amount is zero. If you would rather keep unscheduled recipes out of view, filter the table to show only rows with planned servings above zero.

This simple scaling assumes ingredient quantities change in direct proportion to servings. That is a helpful shopping estimate, not a guarantee that every recipe scales perfectly: pan size, cooking time, seasoning, and ingredient behavior can change with batch size. Treat salt, spices, and other seasonings as quantities to check while cooking rather than blindly relying on a scaled number.

Build a consolidated grocery list

On Shopping, enter Ingredient, Unit, and Total needed in columns A, B, and C. List each ingredient and unit combination once—for example, rice with grams, and olive oil with milliliters. The unit matters: a total of 500 grams cannot be meaningfully combined with a quantity measured in cups without a conversion.

With the ingredient and unit in Shopping!A2 and Shopping!B2, and the recipe ingredient, unit, and calculated quantity in Recipes!B2:B200, Recipes!D2:D200, and Recipes!G2:G200, enter this formula in Shopping!C2:

=SUMIFS(Recipes!$G$2:$G$200,Recipes!$B$2:$B$200,A2,Recipes!$D$2:$D$200,B2)

Suppose two scheduled recipes each require rice, one at 250 grams and one at 150 grams. If both rows use the ingredient name Rice and the unit g, the result is 400. Copy the formula down for each ingredient-unit pair. SUMIFS adds quantities only when both the ingredient and unit match, so Rice measured in cups remains separate from Rice measured in grams.

You can type the unique ingredient list manually for a small plan. For a larger one, use a PivotTable to summarize the Recipes data: select the ingredient rows, choose Insert > PivotTable, then place Ingredient and Unit in Rows and Amount needed in Values. Check that the Values field is summarized by Sum. A PivotTable is a useful alternative when you want to refresh a summary after changing recipe quantities, but it may need refreshing to reflect edits. The formula-based Shopping sheet updates when its source values change.

Make the template practical to use

A spreadsheet should reduce decisions, not create extra recordkeeping. A few careful design choices make the workbook easier to maintain:

  • Use one spelling for each recipe and ingredient. “Chicken breast” and “chicken breasts” may be treated as different entries in a summary.
  • Choose useful, consistent units such as g, kg, ml, cans, or pieces. Convert quantities yourself when you need a common unit; Excel will not infer that a cup equals a particular number of grams for every ingredient.
  • Keep notes for substitutions or pantry stock separate from calculated totals. If you already have one can, record that separately and subtract it from the amount to buy rather than changing the recipe’s base quantity.
  • Use filters on the tables to show a particular date range, meal type, or recipe. Filters help manage information without deleting rows.
  • Print the Shopping sheet or view it on a phone while shopping. Before printing, use File > Print to check page orientation and scaling; a wide sheet may otherwise be split across pages.

You can also use Data > Data Validation to restrict entries such as Meal to a short list of choices. This reduces accidental variations like “Lunch” and “Luch.” If you add conditional formatting to flag meals that need advance preparation, keep the rule visually simple and confirm that it still makes sense when dates or rows change.

Common problems and how to prevent them

The most frequent calculation issue is a recipe name that does not match. If MealPlan contains “Veggie bowl” but Recipes says “Vegetable bowl,” SUMIF will not treat them as the same recipe. Copying recipe names from a consistent list, or using a drop-down list, helps prevent this. A zero planned-serving result can also mean the recipe is genuinely not scheduled, or that a name contains an extra space or spelling difference.

A second issue is mixing units or ingredient descriptions. A shopping formula can add two entries called “tomatoes” in “each,” but it cannot decide whether “one can tomatoes” should be combined with fresh tomatoes. Use distinct ingredient labels when the form matters, such as canned tomatoes and fresh tomatoes, and keep the unit descriptions consistent.

Check the recipe yield before trusting scaled quantities. If Batch serves is blank or zero, the scaling formula cannot produce a meaningful amount. Enter a positive serving count for every recipe row, then check a small worked example manually. Also confirm that the formula ranges cover all of your rows; if the plan grows beyond row 36 or the recipe table beyond row 200, extend the ranges or convert the source ranges to Excel tables and update the formulas accordingly.

Finally, a grocery estimate is not an inventory system. It does not know what is in your refrigerator, whether a package size matches the calculated amount, or whether an ingredient will spoil before use. Review the list before shopping, account for pantry staples and package sizes, and avoid treating a decimal quantity such as 0.4 of a package as a literal purchase instruction.

Meal prep, storage, and food safety

A meal plan can include storage notes, but a spreadsheet is not a substitute for safe handling guidance. Keep perishable ingredients refrigerated promptly, use clean containers, and follow current food-safety recommendations for cooking, chilling, storage times, and reheating. Needs differ by food and circumstance, so consult a reliable public health or food-safety authority for specific temperatures and time limits rather than relying on a generic cell in a template.

It can help to add columns for Cooked on, Stored in, or Use first, but only if you will keep them current. Labeling containers with the dish and preparation date can make leftovers easier to identify. Plan meals in an order that uses more perishable ingredients earlier when appropriate, and leave room in the notes for freezing or thawing instructions specific to your recipe.

Costs, nutrition, and other optional fields

For a basic template, ingredient quantities are enough. If you want a rough food-cost estimate, add a price-per-unit column to a separate ingredient or pantry list, then calculate an estimated recipe or shopping cost using quantities that share the same unit. Prices change, package sizes differ, and a store’s sale price may not match your estimate, so treat the result as a planning aid rather than an exact bill.

Nutrition tracking is another optional layer, not an automatic property of a meal plan. Values depend on specific products, ingredient amounts, and serving sizes. If you choose to record nutrition information, use a consistent source and distinguish estimates from verified product-label values. Do not let extra columns make the core plan so cumbersome that it stops being updated.

When Excel is a good fit—and alternatives

Excel suits people who want control over their own layout, need to adapt a plan to unusual schedules, or already use spreadsheets. A workbook can work offline in the desktop app, support formulas and tables, and be reused week after week. Microsoft 365 users can also store and share a workbook through OneDrive, subject to their account and sharing settings.

A dedicated meal-planning app may be more convenient if you want built-in recipe importing, nutrition databases, automatic store lists, or household collaboration without setting up formulas. A paper planner can be faster if your meals rarely change and you prefer not to maintain digital records. The best choice depends on whether flexibility, automation, or simplicity matters most to you.

Frequently Asked Questions

Does Excel have a free meal-prep template?
Excel may show relevant files in its template gallery, but available templates can change. You can also create the three-sheet workbook described above in a blank file and save it as a reusable template or workbook.

How do I make a grocery list from an Excel meal plan?
Store each recipe ingredient on its own row, calculate the amount needed for planned servings, then summarize matching ingredient and unit pairs with SUMIFS or a PivotTable. Check names and units so unlike items are not combined.

Can Excel scale recipe servings automatically?
Yes, if you record each ingredient’s amount per batch, how many servings that batch makes, and the servings planned. Multiplying the base amount by planned servings and dividing by batch yield gives a proportional estimate.

Can I use the same meal-prep workbook every week?
Yes. Duplicate the plan rows for a new week or update the dates and servings. Keep recipe quantities in the Recipes sheet, and check that the formula ranges include any new rows.

Is Excel better than a meal-planning app?
It depends on your needs. Excel is flexible and customizable, while an app may provide recipe import, built-in nutrition information, and shopping features with less setup. Neither option removes the need to review quantities, substitutions, and food-safety practices.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.