How to Scale a Trip Menu From 8 to 80 Without Starting Over

Every outfitter knows the drill. You build a beautiful six-day menu for a group of twelve, and two weeks out the client calls to say it’s now a group of thirty-one. Suddenly your shopping list is wrong, your batch sizes are wrong, and someone is doing arithmetic on a napkin at 10pm.

The fix isn’t a bigger spreadsheet. It’s building the menu so that headcount is an input, not something baked into every line.

Write recipes per person, not per batch

A recipe that says “serves 12” is a dead end. A recipe that says “4 oz dry pasta per person, 1.5 oz sauce per person” can be multiplied by any number. Take the time once to convert your core recipes to per-person quantities and every future trip gets easier.

Separate the menu from the group

Keep your menu as a reusable template: day one dinner is chili, day two breakfast is oatmeal, and so on. Then attach a group to it. When the group changes, the template stays the same and only the quantities move. This is the single biggest time saver for programs that run the same trips season after season.

Watch the things that don’t scale linearly

Not everything multiplies cleanly. Spices, oil, and condiments often grow more slowly than the headcount. Packaging rounds up to whole units. A good rounding rule (round up to the nearest bag, can, or case) keeps you from showing up with 1.3 jars of peanut butter.

A quick checklist

Convert recipes to per-person amounts. Store menus as templates. Set rounding rules by ingredient. Review the shopping list once with the real headcount, not the estimate.

Wholesum was built around exactly this workflow, so if you’d rather not maintain the spreadsheet yourself, that’s what the free trial is for.