Complete Guide to Vegan Meal Planning with Notion

Most meal-planning advice tells you to "just plan your week." The hard part isn't the intention — it's that planning, shopping, and cooking live in different places, so the effort never compounds. You plan in your head, shop from a half-remembered list, and rediscover on Tuesday that you have no idea what you meant to cook.

This guide builds a meal-planning system in Notion where those three things connect. Plan once, and the grocery list and the week's cooking fall out of it automatically. I'll walk through the full build, the order to do it in, and the mistakes that make these systems collapse.

The three databases

A working system is three linked databases, no more:

1. Recipes — your library of what you can cook.
2. Meal Plan — which recipe is assigned to which day.
3. Grocery List — what to buy, derived from the plan.

The magic is in the links between them. But links only help if the pieces underneath are solid, so build them in order.

Step 1: The Recipes database

Start here, even though planning feels more urgent. A meal plan with no recipes to draw from is just an empty calendar.

Give each recipe these properties:

• Meal type (Select): breakfast, lunch, dinner, snack
• Cook time (Number, minutes)
• Effort (Select): low / medium / project
• Main ingredient (Multi-select): tofu, lentils, chickpeas, etc.
• Servings (Number)

In the page body of each recipe, list the ingredients. For the automation later, the cleanest approach is to make each ingredient a sub-item or a row in a related Ingredients database — but if that feels heavy, a plain text ingredient list works for a manual grocery list too. Start simple; you can upgrade later.

Seed it with 15–20 recipes you actually cook. Don't try to import 200 at once. A system you trust with 20 beats a system you abandon with 200.

Step 2: The Meal Plan database

This is where you assign recipes to days. Properties:

• Date (Date)
• Meal (Select): breakfast / lunch / dinner
• Recipe (Relation → Recipes)
• Servings needed (Number) — useful if you're cooking for more than yourself or batch-cooking

The key property is the Recipe relation. Instead of typing a meal name, you link to an actual recipe in your library. That link is what lets everything downstream work.

Create a calendar view for the at-a-glance week, and a filtered list view showing just the next 7 days for quick planning. I plan on Sunday using the list view, then glance at the calendar during the week.

Step 3: The Grocery List

This is where the system pays off. There are two ways to build it, depending on how much setup you want.

The simple version

Make a Grocery List database with:

• Item (Title)
• Section (Select): produce, pantry, plant proteins, plant milks, frozen, etc.
• Got it (Checkbox)

Use a board view grouped by Section so it matches the store layout. After you plan the week, you copy ingredients from your assigned recipes into this list. It's manual, but it's one focused pass, and the section grouping means you walk the store once.

The connected version

If your recipes use a linked Ingredients database, you can relate ingredients to the Meal Plan and build a grocery view that surfaces exactly the ingredients for this week's planned recipes, grouped by section. Plan the week and the shopping list assembles itself.

My honest advice: ship the simple version first. Live with it for two or three weeks. Only build the connected version once you're sure you'll keep planning — the automation is only worth it if the habit is real.

The weekly rhythm

The system is only as good as the routine around it. Mine:

1. Sunday, 15 minutes: Open the Meal Plan list view. Pull dinners for the week from the Recipes database, favoring the Weeknight filter (low effort, under 30 minutes) on busy days and one "project" recipe for the weekend.
2. Build the grocery list from those recipes (manual copy or auto-view).
3. Check the pantry, tick off what you already have.
4. Shop once.
5. Cook from the calendar during the week — no decisions left to make at 7pm.

The entire point is to move all the deciding to Sunday, when you have the bandwidth, so weeknights are just execution.

Where these systems break

Having rebuilt mine twice, the failure modes are predictable:

• Over-engineering before you've used it. People spend a weekend wiring up rollups and formulas, then never plan a single week. Build the minimum, use it, then add.
• Too many properties. Every field you add is a field you have to fill in. If you never filter by it, delete it.
• Trying to plan a whole month. Plans decay. A week is the right horizon; anything longer is fiction you'll rewrite.
• No capture habit. If new recipes don't easily make it into the library, the planner slowly runs dry. Set up the web clipper and the mobile share sheet on day one.

Start this week

Don't build all three databases tonight. Build Recipes, add 15 meals you actually make, and plan one week with a plain list. That's enough to feel the difference. Add the Meal Plan calendar next week, the grocery automation the week after — only if the habit stuck. The system that survives is the one you grow into, not the one you front-load.