Buffets with several alternatives, plated meals, shared tables, finger-food/canapé plans, family celebrations, community events, school/community planning where local requirements are handled separately, and small catering jobs where the organiser already knows the portion assumptions they want to use.
RecipeWanted Resources
Guests + visible assumptions → menu quantities
Party & Catering Quantity Planner
Plan menu quantities for parties, buffets, community events and small catering using guest groups and assumptions you can actually see and change. Calculate direct mass/volume/count requirements, purchase quantities after a known usable-yield percentage, package ceilings and exact RecipeWanted recipe scale factors without pretending one appetite or waste allowance fits every event.
Editable assumptionsGuest groupsPackage planningNo universal portion claims
Interactive ResourceRuns without sending your entries to RecipeWanted.
Quick start
Before you start
Turn guest counts and explicit, editable menu assumptions into deterministic direct-food quantities, purchase quantities, package ceilings and recipe scale factors.
Know the guest/group counts and decide the portion basis for each menu item. For direct items, provide a per-person amount and unit. For a recipe item, provide the original recipe serving yield or import a published RecipeWanted recipe with a clean numeric serving yield.
Weighted guest equivalents, expected participating equivalents, base target, contingency-adjusted target, purchase quantity after known usable yield, optional package count and recipe scale/whole-batch ceiling. Every layer is shown separately.
Weighted guest equivalentsPer-item base targetContingency targetPurchase quantityPackage ceilingRecipe scale factorBrowser-local saved planCopy/CSV/Print
Examples for home cooking and teaching
Choose a relevant example and check the assumptions before using it in your kitchen or lesson.
Buffet with two mains
Give each main its own participation percentage instead of assuming every guest takes a full portion of both. The planner shows exactly how that choice changes the totals.
Mixed appetite groups
Create separate guest groups and enter your own relative portion factor for each. RecipeWanted does not assign a universal “adult” or “child” multiplier.
Known trimming/prep loss
If you have a dependable usable-yield percentage for an ingredient or prepared item, enter it to convert the edible target into a purchase quantity. Leave yield at 100% when you do not know it.
Use this againChange attendance, participation assumptions, pack sizes, known usable yield or recipe choice while keeping the rest of the event plan.
Save one quantity plan locally in this browser, reload it or delete it. My Resources may only detect that the known key exists; guest counts and menu quantities are not copied into a central visitor profile.
Trust & safety at a glance
Use the result for the decision it was built to support
A calculated quantity means the entered assumptions produce that arithmetic result. It does not prove the assumption is suitable, that every guest will eat that amount, or that the event will have zero shortage/waste.
Quantity planning from visitor-controlled assumptions5 subject references · Reference register provided below; no current review date is asserted for this route.
Estimate menu quantities and recipe scaling from guest counts and assumptions the visitor explicitly enters.
Not a nutrition prescription, appetite guarantee, allergen assessment, school/care compliance calculator, food-safety approval, waste guarantee, stock-control audit, pricing engine or legal catering standard.
Quantity arithmetic is general. Food-safety, licensing, school/care requirements, allergens and commercial catering obligations depend on the food, venue, people served and applicable local rules.
Guest-group labels/counts/factors, menu-item assumptions and saved plans stay in the browser. Optional RecipeWanted recipe import reads already-public Recipe Index serving metadata; aggregate analytics receives only allowlisted action counts. Affiliate, sponsor, Resource Card and analytics state cannot change guest factors, portion assumptions, yield, contingency, package maths or recipe scale factors.
When to stop and verify:For regulated catering, school/care settings, allergy-safe service, specialist diets or safety-critical storage/holding, verify the actual menu/process and appropriate official or professional guidance separately.
Privacy scope: this describes the working-data behaviour of this Resources tool only. Site-level cookies, analytics, consent and other storage/access technologies remain governed by RecipeWanted’s wider privacy/CMP configuration and applicable law.
Source scope: external authorities and specialist references support specific information; linking to them does not mean they have reviewed, approved or endorsed RecipeWanted.
How this Resource reaches its result
MethodDeterministic transparent-assumption quantity planner
Guest-group equivalents are the sum of group count × visitor-entered relative portion factor. Each menu item applies its own participation percentage and per-person amount. Optional contingency multiplies the target; optional known usable-yield divides the edible target into a purchase quantity; optional same-family package size is rounded up with a ceiling. Recipe mode divides contingency-adjusted target servings by the known original recipe yield.
Can it be reproduced?Deterministic under this version
The same guest groups, menu item assumptions, unit family, participation, yield, contingency and package/recipe yield values produce the same plan under the V16.7 quantity contract.
Evidence5 registered references · RecipeWanted review UNREVIEWED
The calculations are explicit ratio, percentage and unit-family arithmetic. Recipe serving integration comes only from the existing published RecipeWanted Recipe Index when a serving yield parses as one unambiguous positive number. RecipeWanted deliberately does not claim universal catering portions.
IndependenceNo paid or analytics influence over the result
No runtime AI, commercial inventory, sponsor state, grocery pricing feed or aggregate analytics signal can alter the quantity maths. No runtime AI predicts appetites, portions, yields, participation, waste or quantities.
Uncertainty stays explicit: Actual consumption, appetite, menu popularity, leftovers, trim/cook loss and package availability vary. The planner exposes those as editable inputs or leaves them unresolved; precision in the arithmetic does not create certainty in the assumptions.
Evidence reference: RWRES-1BB08EF83E8DCB68 — a RecipeWanted integrity/reference fingerprint for this release evidence set, not certification or third-party endorsement.
Report a factual or method concern if a source conflicts with the tool, a calculation appears wrong, or a boundary needs review.
Transparent quantity planning
Plan for the people and menu you actually expect
Party quantity charts often hide assumptions about appetite, menu choice and waste. This planner shows those assumptions separately. You decide the relative guest factors and per-item assumptions; RecipeWanted performs the arithmetic and keeps each layer visible.
Describe the guest groups
Start with one group at factor 1.00 or split the event into groups with different relative portion factors you choose. The factor is relative to your own base portion, not an age or nutrition rule.
Describe each menu item
Choose direct quantity or recipe mode. Direct items need a per-person mass, volume or count. Recipe items need a known original serving yield.
Make uncertainty visible
Participation is the share of guests expected to take an item; contingency is your extra margin. Usable yield is the proportion left after preparation. Leaving yield at 100% applies no loss allowance—it does not prove that nothing will be lost. Check these assumptions before buying.
Use the result downstream
Take an exact recipe scale factor to Recipe Scaler, the purchase quantities to Recipe Cost Calculator, and the final menu into Cooking Timeline Planner.
Party & catering workspace
Build a quantity plan from visible assumptions
No menu item has a hidden default portion. The starter row is intentionally blank apart from 100% participation/yield so the plan cannot look authoritative before you enter a real assumption.
1 · Event context
What a relative portion factor means
1.00 means one base portion-equivalent under your assumptions. 0.60 means you expect that group to average 60% of the base amount; 1.20 means 120%.
RecipeWanted does not pre-fill “children”, “adults”, “athletes” or other demographic multipliers. If you choose to split groups, you own the factor and can see it in every saved/exported result.
2 · Guest groups
Weighted guest equivalents = guest count × your factor. Keep one group at 1.00 when everyone should use the same base assumption.
3 · Menu items
Participation is the percentage of weighted guest equivalents expected to take that item. This is especially useful when several alternatives are offered.
Optional RecipeWanted integration
Import a published recipe serving yield
634 indexed RecipeWanted recipes currently expose a single parseable serving yield. Importing only fills the recipe name, URL and original yield; your guest participation and contingency assumptions remain yours.
Enter guest counts and at least one real menu assumption, then build the plan.
| Item | Role | Participation | Base target | With contingency | Purchase / scale target | Package / batch note | Assumptions |
|---|
Read the result correctly
The result has four different quantity layers
Keeping these layers separate is more useful than showing one apparently precise shopping number.
Base target
Weighted participating equivalents × your per-person amount. This is the clean arithmetic target before contingency or prep loss.
With contingency
Your base target after the event or item-specific contingency percentage. A 10% contingency is only 10% because you entered 10%.
Purchase quantity
For direct items, this divides the contingency target by your known usable-yield percentage. Leave yield at 100% when you cannot defend a different number.
Package / recipe batch
A same-family pack size produces a package ceiling. Recipe mode produces an exact scale factor and separately shows the whole-batch ceiling for operations that cannot use a fractional batch.
Participation
Participation is item-specific. Two buffet mains can each be 60% if you expect overlap/choice; two plated components can each be 100% when every guest receives both.
Guest factors
Factors let you model relative serving expectations without hard-coded demographics. They are assumptions, not nutritional requirements or guarantees of appetite.
Real-world planning patterns
Use the controls to model the event you are actually running
Several buffet mains
Do not divide by the number of mains automatically. Set a realistic participation assumption for each main and inspect the combined plan.
Plated courses
When every attendee receives one portion, use 100% participation for that item. If an alternative is pre-selected, use the actual number/group instead of a vague split.
Finger food
Use count units when you genuinely know pieces per base guest-equivalent. Tool 14 will not invent “canapés per person” from event type.
Trimmed/raw ingredients
Enter a usable-yield percentage only when it comes from your own product/process or a dependable operational source. Purchase quantity increases transparently when yield is below 100%.
Pack buying
Enter the actual pack size in the same mass, volume or count family. The ceiling shows how many whole packs cover the calculated purchase requirement.
Recipe-based catering
Use a published or manual original recipe yield to get the scale factor, then use Recipe Scaler for the real ingredient quantities. Scale does not automatically change cooking time or equipment capacity.
Important boundary
Quantity maths cannot guarantee consumption, safety or zero waste
Tool 14 makes the arithmetic reproducible, not the crowd predictable. Appetite, menu popularity, weather, service style, dietary restrictions, food quality, event duration, leftovers and operational losses can all change what is actually consumed.
- No universal portion chart is applied behind the scenes.
- No adult/child factor is preselected.
- Usable yield and contingency remain explicit organiser inputs.
- Recipe scale factors change quantities only; they do not automatically scale cooking time, pan size, oven space or food-safety controls.
- Commercial content and aggregate analytics remain downstream from the quantity result.
Party quantity FAQ
Questions worth resolving before you buy or prep
Why does RecipeWanted not give me one default grams-per-person number?
Because there is no single amount that fits every food, course, guest mix or service style. Tool 14 is designed around assumptions you can see, defend and change rather than hiding a generic portion table inside the calculator.
What is a guest portion factor?
It is a relative multiplier against your own base per-person assumption. A factor of 1.00 uses the base amount; 0.70 uses 70% of it; 1.20 uses 120%. RecipeWanted does not assign those factors to demographic groups for you.
How should I handle two or three alternative mains?
Give each item its own participation percentage based on the share you reasonably expect to take it. Participation can overlap in a buffet because some people may try more than one option. The planner does not force all participation percentages to total 100.
What does contingency percentage mean?
It is an explicit extra margin applied after the base target. It can represent uncertainty or the operational buffer you choose. It is not a promise that the event will avoid shortage or waste.
What does usable yield mean?
It is the percentage of purchased quantity you expect to remain usable for the planned item after the loss you are deliberately accounting for. Keep it at 100% unless you have a known, defensible yield for the actual product/process.
Why is package count always rounded up?
A package count represents whole packs needed to cover the calculated purchase quantity, so it uses a ceiling by definition. The result also shows any calculated surplus created by that whole-pack rounding.
Can I mix kilograms, litres and pieces?
Yes across different menu items, but they remain separate measurement families. Tool 14 safely normalises g↔kg and ml↔L. It will not convert mass to volume or pieces to grams without an explicit physical relationship.
Can Tool 14 scale a RecipeWanted recipe?
It can calculate the exact scale factor from a known original serving yield and your event assumptions. Use Recipe Scaler for the actual ingredient-list transformation; Tool 14 deliberately does not duplicate that mature engine.
Does this make my catering food safe or compliant?
No. The planner does not decide allergen safety, holding/cooling limits, licensing, school/care requirements or local food-law compliance. Those require the actual menu/process and appropriate official or professional guidance.
Is my event plan saved to RecipeWanted?
Not by Tool 14. Save/Load/Delete uses one versioned browser-local key. Aggregate Resources analytics can count allowlisted actions such as calculate or export, but does not receive guest counts, menu names, portion amounts or package sizes.
Continue across RecipeWanted
Use the next route for the next question
Related Resources handle the next practical job. The ecosystem handoffs add another useful format when a visual, video, current update, longer article or wider recipe browse answers something different. Cooking Education remains the deeper teaching layer.
01Recipe Scaler
Use the exact scale factor from Tool 14 to scale the actual ingredient list; Tool 14 does not rewrite recipe ingredients itself.
Open related Resource → 02Recipe Cost CalculatorAfter quantities are known, cost the real packages and ingredient usage without Tool 14 inventing grocery prices.
Open related Resource → 03Cooking Timeline PlannerOnce the menu quantity plan is settled, schedule the preparation and service tasks using real durations.
Open related Resource → 04Meal Planning ToolsUse broader meal planning to choose the menu; Tool 14 focuses on how much of each chosen item is required.
Open related Resource → 05Meal Planning & PrepOpen the related Cooking Education route for deeper method and explanation.
06Measurements & ConversionsOpen the related Cooking Education route for deeper method and explanation.
07Storage & Food SafetyOpen the related Cooking Education route for deeper method and explanation.
08Search RecipesApply the tool or decision inside a complete RecipeWanted dish.
Legal, privacy & fair-use notice
Free Resources, with clear limits and clear data boundaries.
RecipeWanted Resources provides general cooking information, deterministic calculations, planning aids and reference tools. It is not legal, medical, dietetic, allergy, regulatory or other professional advice, and it does not replace product labels, manufacturer instructions, competent-authority guidance or qualified professional advice where those are needed.
Each tool explains how it handles your entries. This Resources analytics dataset does not retain recipe or ingredient names, pantry lists, allergy, dietary or health information, other free text, exact quantities, visitor/session/account IDs, IP addresses, user-agent strings or referrer URLs.
This Resources statistics layer is currently enabled and records only allowlisted aggregate interaction and coarse workflow/build-shape counters. Daily aggregate buckets are retained for up to 730 days. Aggregate results are for RecipeWanted/QHE internal RecipeWanted service improvement only; they are not sold or used by this layer for advertising measurement, individual profiling or cross-site tracking.
Any reasonable fair-use or availability rules for free tools are separate from privacy law. Access is not conditional on participating in Resources analytics, and “fair use” is not treated as consent or as a legal basis for collecting personal data. On instrumented Resources pages, the usage-statistics panel provides a simple, free objection control.
Wider site/infrastructure scope: ordinary hosting, security, caching, firewall, consent-management or server-log systems may process technical request information outside the Resources aggregate dataset. Those systems remain governed by RecipeWanted’s wider privacy/CMP arrangements and published privacy information. This Resources notice does not claim that every web request is anonymous.
External authorities linked elsewhere in Resources support specific facts or methods; their inclusion does not mean they approve or endorse RecipeWanted. If a higher-consequence decision is uncertain, stop and verify it with the appropriate current source.First-party usage statistics
Help RecipeWanted learn what is actually useful
Resources records aggregate usage statistics such as qualified tool views, whether a working surface is started, route-level value actions, coarse read depth, broad workflow/build-shape buckets and which non-commercial RecipeWanted handoffs are used. Build-shape signals are deliberately coarse (for example, a small/medium/large row-count bucket or a selected calculator mode): RecipeWanted does not send the recipe name, ingredient list, pantry items, allergen/dietary choices, free text or exact quantities to this analytics dataset; it does not create a visitor/session ID; and it does not store IP addresses, user-agent strings or referrer URLs in the analytics dataset.
Purpose: help RecipeWanted/QHE decide which free tools, workflows, supporting content and first-party integrations to improve next. Aggregate statistics may be reviewed internally across QHE only for that same RecipeWanted service-improvement purpose. They are not sold and are not used by this layer for advertising measurement, cross-site tracking or individual profiling. Free access is not conditional on this measurement: opting out does not disable or reduce any Resource tool.
What is counted and retained?
Allowed counters include 5-second qualified views, 30 seconds of visible engagement, 50%/90% read depth, first working-surface use, selected non-commercial feature/export/continuity actions, hub task choices, broad allowlisted workflow/build-shape buckets and RecipeWanted internal/ecosystem handoffs. Counts are merged directly into UTC daily buckets and retained for up to 730 days under the current admin setting. The only browser preference this layer writes is the first-party objection cookie after you choose to opt out; removing the objection deletes that preference. This describes the Resources aggregate dataset only; ordinary hosting, security, caching, firewall, consent-management or server-log systems remain governed separately by RecipeWanted’s wider privacy/CMP arrangements.
Privacy informationYou can object simply and free of charge at any time. The preference applies only to this first-party Resources statistics layer.
Next step
Use the tool, then get back to cooking.
Resources should remove friction around the task rather than become another layer to manage.
