The order is confirmed for 180 guests. You plan a five-percent service buffer, and the braised-beef recipe yields 24 portions. The calculator says 7.875 batches. The prep crew still needs to know how many pots to make.

Guests scale portions. The kitchen cooks batches.

Set the portion requirement first

Keep the guaranteed guest count and any planned buffer separate. That lets the quote retain its real head count while production shows why it is preparing more.

For this illustrative event:

Guaranteed guests = 180
Service buffer = 5%

Required portions = 180 × 1.05 = 189 portions

The five-percent buffer is an example, not a universal recommendation. Use the policy, service style, guarantees, and risk your business has deliberately chosen.

Convert portions into recipe batches

The established braised-beef recipe yields 24 portions:

Batches required = required portions ÷ portions per batch
189 ÷ 24 = 7.875 batches

The kitchen can prepare eight complete batches. It cannot prepare 7.875 validated batches on purpose.

If the braise is produced only as a complete validated batch, round the production quantity up:

Production batches = 8
Finished portions = 8 × 24 = 192
Planned cushion = 192 − 189 = 3 portions

Do not hide the three portions by changing the guest count to 192. They are a production remainder, not twelve additional customers.

Scale the ingredients from the batch

Suppose one batch uses:

18 lb raw beef
3 qt stock
2 lb onions

Eight complete batches require:

Raw beef: 8 × 18 lb = 144 lb
Stock:     8 × 3 qt  = 24 qt
Onions:    8 × 2 lb  = 16 lb

This is the prep requirement. It should remain connected to the recipe version and yield that produced it.

Turn batches into equipment runs

If the kettle safely holds two recipe batches, the board should not list one enormous eight-batch task:

8 recipe batches ÷ 2 batches per kettle run = 4 kettle runs

The prep plan can now say:

Braised beef: 4 kettle runs
Each run: 2 recipe batches / 48 portions
Total: 8 batches / 192 portions

Equipment capacity, cooling space, cook time, and staffing may create different operating units for different dishes. The batch rule belongs to the kitchen’s actual method, not to a universal multiplier.

Let the shopping list round separately

The kitchen needs 144 lb of raw beef, but the supplier sells 40 lb cases:

Cases required = 144 lb ÷ 40 lb = 3.6 cases
Cases to order = 4

Purchased quantity = 4 × 40 lb = 160 lb
Quantity above prep need = 160 lb − 144 lb = 16 lb

The shopping list says four cases. The prep list still says 144 lb. Do not tell the crew to prepare all 160 lb merely because buying rounded to a whole pack. The remaining 16 lb needs its own stock or future-use decision.

Give the crew the executable plan

The complete path is:

180 guests
→ 189 planned portions
→ 8 recipe batches
→ 4 kettle runs
→ 144 lb raw beef for prep
→ 4 × 40 lb cases to buy
→ 16 lb remains outside this prep plan

Each arrow crosses a real operating boundary. Keep those boundaries visible, and tomorrow’s board can show four full kettle runs and three planned spare portions instead of a mystery fraction copied from a calculator.