PortionThread field notes
How Relative Portions Become a Grocery List
Relative portions turn one familiar recipe into a grocery list by scaling the recipe to the household’s planned portions, converting ingredients into buy quantities, and recording remainders for later use. It is household math, not calorie math, and it stays separate from medication decisions.
TL;DR: Relative portions turn one familiar recipe into a grocery list by scaling the recipe to the household’s planned portions, converting ingredients into buy quantities, and recording remainders for later use. It is household math, not calorie math, and it stays separate from medication decisions.
Start with a familiar recipe and let each diner pick a relative portion. That is the whole trick. PortionThread calls a practical, non-medical way to scale one meal for different appetites, figure out package counts, and plan useful leftovers. The numbers, like 1.0, 0.75, and 0.5, simply describe the meal to serve. They are not calorie targets, medical advice, or a guess about what anyone should weigh or eat.
Use a familiar recipe as the base
The method begins with a recipe whose normal yield is already known. If the recipe normally makes four familiar portions, you have a base. Then each diner picks a relative portion for that meal, and those portions are added together into one planned total.
That is why this works as household math instead of nutrition theater. You are not starting with calories, medication, or body size. You are starting with, “How much of our usual dinner does each person want tonight?”
Worked example: turn portions into ingredient quantities
Suppose a recipe makes 4 portions.
Tonight the household chooses these relative portions:
- Person A: 1.0
- Person B: 0.75
- Person C: 0.5
Total planned portions: 2.25
Recipe factor: 2.25 ÷ 4 = 0.5625
Now scale each ingredient by 0.5625.
Example ingredient list:
- 400 g ingredient A × 0.5625 = 225 g
- 2 cups ingredient B × 0.5625 = 1.125 cups
- 1 onion × 0.5625 = 0.5625 onion
That last one is where real kitchens get slightly unglamorous. If the recipe unit and the package or measuring unit do not line up neatly, keep the calculation honest and note the unknown instead of pretending. PortionThread’s explanation is explicit here, including “Start with relative portions, not calorie targets,” and that the calculations are deterministic. Same inputs, same outputs. No mystery wizardry, just arithmetic with a spatula.
Keep full precision during calculation. Round only at the display or measuring step. That avoids little rounding errors piling up and nudging the shopping list off course.
Translate the scaled recipe into store quantities
Once each ingredient is scaled, the result becomes the buy list.
At this point, the planner should separate three things:
- The amount the recipe needs.
- The package size sold in the store.
- Any remainder after buying whole packages.
If you need 1.125 cups and the store only sells a larger container, the shopping list should say how many packages to buy and what will be left over. The remainder is not a bug. It is just the part that does not fit the package boundary.
And when a recipe unit and a package unit do not match, honest unknowns are better than neat but invented numbers. A recipe calling for two pieces cannot be safely matched to a package described only in grams without a user-supplied conversion. Kitchen math does not get better just because the spreadsheet is feeling optimistic.
Keep leftovers and package remainders useful
A good planner does not treat leftovers as accidental clutter. It assigns each remainder a next job.
That might be:
- tomorrow’s lunch,
- another planned recipe,
- or freezing.
PortionThread’s remainder guidance ties this to pantry checking before shopping and to writing down what the household will do with the extra. That means the leftover becomes part of the plan, not a sad container at the back of the fridge.
This is also where the pre-shop check matters. Look at the refrigerator, freezer, and pantry first, then decide what still needs to be bought. If a large package only looks cheaper, ask whether the household will use it in time. Cheap is great. Wasteful is just expensive with better branding.
Clarify what this method does not do
This planner should not infer food needs from Ozempic, Wegovy, semaglutide, Mounjaro, Zepbound, or tirzepatide. It should not recommend doses, calories, or treatment changes.
That boundary matters. PortionThread’s boundary guide is clear that household math and clinical decisions are different jobs. It also notes that Ozempic and Wegovy both contain semaglutide, while Mounjaro and Zepbound both contain tirzepatide, but those paired brands are not interchangeable. Use the exact medicine name on the prescription and current label when discussing care with a clinician or pharmacist. For the household side of the problem, see the GLP-1 household meal planning guide and the semaglutide and tirzepatide boundary guide. They help keep the cooking math in the kitchen and the medical math where it belongs.
One practical takeaway
Start with a known recipe, assign relative portions, scale the ingredient totals, round into package counts, and write down what the household will do with any remainder.
Sources
Put it into practice.
Practical household meal planning for people searching around Ozempic and GLP-1 routines. No calorie prescriptions, treatment plans or medication advice.
Plan a meal free ↗Keep reading
Ozempic & GLP-1 Meal Planning for a Shared Household ↗
A practical, non-medical way to scale one familiar meal for different appetites, calculate package counts, and plan useful leftovers.
Pantry Planning for Changing Appetites and Less Waste ↗
Use simple package math and a remainder plan to shop for a household whose appetites vary, including households navigating GLP-1 treatment.