Buy for Coverage
Purchase quantities that cover all highlighted cells for an ingredient, not just the first recipe that calls for it.
Select an ingredient name in the left column to reveal its usage across the week. Dashes indicate days where the item is not needed.
| Ingredient | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Spinach | Lunch | — | Dinner | Lunch | — | Brunch | — |
| Roasted Squash | Dinner | — | — | Dinner | Lunch | — | Brunch |
| Farro Grains | Lunch | Breakfast | — | — | Dinner | — | Lunch |
| Red Lentils | — | Dinner | Lunch | — | — | Dinner | — |
| Lemon | Dinner | Lunch | Dinner | — | Lunch | — | Dinner |
| Olive Oil | Lunch | Breakfast | Lunch | Dinner | Lunch | Brunch | Dinner |
| Chickpeas | — | — | Lunch | Lunch | — | Dinner | Lunch |
Most home cooks buy a full bag of greens or a large squash for a single recipe. Without a cross-reference system, the remainder often goes unused.
This table solves that by showing every touchpoint for each ingredient before you write your shopping list.
Apply these guidelines when converting the cross-reference table into a practical grocery run.
Purchase quantities that cover all highlighted cells for an ingredient, not just the first recipe that calls for it.
If an ingredient appears only once, consider swapping it for one that appears three or more times across the week.
Prep shared ingredients once during your Sunday session and portion them for each day they appear in the table.
Once ingredients are mapped, the next step is scheduling when each item gets washed, chopped, roasted, or stored. The prep timeline handles that logistics layer.