Our meal planning methodology explains recipe selection, portion bounds, grocery weights and browser-only storage. The planning tools reuse the food and recipe calculations documented in our nutrition methodology. This page explains the additional selection, transfer and grocery rules.
Meal planning methodology: one set of source weights
First, multiply each ingredient’s nutrients per 100 g by edible grams ÷ 100. Next, divide a recipe batch by its stated yield before applying a portion factor. Protein blocks divide protein grams by 7; available-carbohydrate blocks divide max(total carbohydrate minus fiber, 0) by 9; total-fat blocks divide fat grams by 3. The separate historical added-fat equivalent divides fat by 1.5. The tools calculate counts before display rounding.
Selection and target differences
Supported durations are 1, 3 or 7 days, with 2–6 eating occasions daily and a selected target of 1–40 blocks. Equal protein-target allocation is an organizational convention, not a validated eating schedule. A seeded recipe sequence makes the same input and seed repeatable. Vegetarian metadata and every excluded food ID constrain candidates. Explicit meal categories are strict filters; slot categories are preferences, with fallbacks disclosed.
Each recipe portion must stay within 0.25–4 times one serving. Scaling by protein changes all ingredients and all nutrient counts. The daily comparison reports protein, available-carbohydrate and total-fat differences separately. A difference within 0.10 blocks in all three is only a numerical comparison, not a claim of adequate energy, micronutrients or medical suitability. The tool does not invent food substitutions or hidden balancing ingredients.
Exact transfers and groceries
A recipe ingredient transfers as its exact food identity and unrounded gram weight. Grocery totals add those weights across the current plan; different food IDs never merge merely because names are similar. For consistency with the existing calculator convention, ounces use 28.3495 g per ounce. Cups and other household units require the particular food’s documented gram weight. Without verified yield data, the tool cannot convert edible cooked quantities to raw purchasing weights. Check the preparation labels, food packaging and your own pantry.
Local state and privacy
The tools work without an account. Your browser processes current edits. Optional saved planning state uses local browser storage only when you enable it; use the clear controls to remove it. Shared devices may expose saved preferences to later users. Storage failure does not prevent temporary use. Recipe, meal and target transfers contain food quantities or a selected public block target, never body weight or body-fat inputs. Public query parameters can appear in browser history and ordinary hosting logs. Downloads stay on the device you choose.
Boundaries and sources
The tools organize reference estimates. They do not assess allergies, nutrient adequacy, medical conditions, pregnancy, eating disorders or sports requirements. We do not claim clinical validation for any generated schedule. Review the medical disclaimer, research standards and the selected evidence library. Source links and preparation states remain available in the food reference.