A catering order form is the one page everyone works from: the client who signs it, the cook who preps from it, and the driver who loads from it. It has thirteen parts. The client and a day-of contact. The date and three times: arrive, serve, clear. The venue, including where to unload and what its kitchen has. The guest count and the day the final count is due. The service style. The menu with portions a guest. Dietary needs and allergies by headcount. Equipment, staff, the price, the deposit and balance, what happens to leftovers, and signatures. Portions are the part most forms leave out, and they're what turns an order into a prep list. Below are the parts, three events, and a file.
The short version
- Three times, not one: arrive, serve, clear.
- Ask what the venue's kitchen really has. Go and look if you can.
- A guest count, and a date after which it can only go up.
- Portions a guest for every dish, on the form.
- Dietary needs as counts, with how each is handled.
- TaroStack scales each recipe to the guest count and says what to buy. More below.
The thirteen parts
| Part | What to write |
|---|---|
| Client and contact | Who pays, and who to call on the day |
| Date and times | Arrive, serve, clear |
| Venue | Address, where to unload, ovens, sinks, refrigeration, power |
| Guests | The number quoted, and the date the final count is due |
| Service | Buffet, plated, family style, boxed, or drop-off |
| Menu | Each dish, with the portion planned a guest |
| Dietary needs and allergies | Counts, and how each is handled |
| Equipment | Chafers, serveware, plates, linens: who brings what |
| Staff | How many, for how long, doing what |
| Price | A guest, plus delivery, setup, rentals |
| Deposit and balance | Paid at booking; the balance and its date |
| Leftovers and cancelling | Who keeps leftover food; the last day to cancel |
| Signed | Client and caterer, dated |
Three events
A made-up caterer.
| Order | Event | Guests | Service | A guest | Food | Delivery, setup | Total | Deposit | Balance | Final count due |
|---|---|---|---|---|---|---|---|---|---|---|
| E-1128 | Nov 28, 6:30 PM | 60 | Buffet | $24.00 | $1,440.00 | $85.00 | $1,525.00 | $500.00 | $1,025.00 | Nov 21 |
| E-1203 | Dec 3, 12:00 PM | 25 | Boxed lunch | $16.00 | $400.00 | $35.00 | $435.00 | $435.00 | Nov 26 | |
| E-1212 | Dec 12, 7:00 PM | 40 | Family style | $38.00 | $1,520.00 | $120.00 | $1,640.00 | $800.00 | $840.00 | Dec 5 |
How the price a guest is built is in how to price catering.
Portions turn an order into a prep list
For E-1128, the form carries the portions:
| Dish | A guest | For 60 | Buy or prep |
|---|---|---|---|
| Herb roast chicken, cooked | 6 oz | 22.5 lb | About 34 lb raw, bone in |
| Roasted vegetables | 4 oz | 15 lb | |
| Rice pilaf | 5 oz | 18.75 lb | |
| Rolls | 1.5 | 90 | 8 dozen |
| Brownies | 1 | 60 | 66, for the ones that break |
Without the portion column, "chicken for 60" is whatever the cook on Thursday thinks it is. The raw weight depends on your own yield for the cut: this kitchen gets about two-thirds of a bone-in bird as cooked meat. Buffets take more than plated service, because guests serve themselves.
The final count
The count on the form is a promise in one direction. This caterer's rule: the final count is due a week before, it can go up after that if the kitchen agrees, and it can't go down. Food is ordered on the final count, so that's the number billed. Put the date on the form and in the client's calendar.
Dietary needs
Write them as counts and as a plan, not as a list of words.
| Need | Count | How it's handled |
|---|---|---|
| Vegetarian | 4 | Stuffed squash, on the buffet, labeled |
| Celiac | 1 | Plated in the kitchen first, covered, named |
| Tree nut allergy | 1 | No nuts on this menu; brownies made without walnuts |
The celiac guest's plate is made before the buffet goes out, with clean tongs, because a shared buffet can't be kept free of crumbs. Labels on the buffet do the rest. The food safety side of carrying and holding food is in HACCP plan for catering.
Get the template
Download the catering order form template. Two sheets and a read-me: an event log where food total, total, balance and the final-count date work themselves out, and the thirteen parts as an event order to print and sign. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. What to pack is in catering inventory checklist.
Where this stops working
Three events in a fortnight share one walk-in and one supplier order. The forms say chicken for 60, short rib for 40 and turkey for 25, on three pages. Somebody adds them up by hand, on the day the order is due, and the count for the 28th changed that morning.
How TaroStack does it
TaroStack does the adding up from the recipes.
Each dish is a recipe, by weight. Chicken, pilaf, brownies, each with its yield and a scrap allowance. Record a batch for 60 or 85 guests and the amounts follow.
What could I make right now says whether what's in the walk-in covers the event.
What to buy, across events. On Growth, planning adds up what the coming orders need against what's on hand and says what to buy and by when.
Batches carry a lot and a use-by. What's cooked ahead goes into stock with its date, and the oldest is used first.
Allergens on Growth. Each dish says what it contains, down through the recipes inside it.
| The job | Three forms | In TaroStack |
|---|---|---|
| Chicken to buy for the week | Add three pages | From the orders (Growth) |
| Scale the pilaf to 85 | Multiply by hand | The recipe, scaled to the batch |
| What's already cooked, and when | Tape on a pan | A lot with a use-by |
| Which dishes have tree nuts | Ask the chef | On the item (Growth) |
Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes); planning and allergen tracking are on Growth at $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
