The Catering Enquiry Form: 7 Fields That Prevent Endless Back-and-Forth

"Hi, do you cater weddings? How much?"

Every caterer knows this enquiry. It is friendly, it is real, and it cannot be answered. So the reply is a list of questions, the client answers half of them, and five emails later you still cannot price it.

The fix is not a longer form. It is the right seven fields.

Why short enquiries cost you work

A thin enquiry does not save the client time. It moves the work to you and adds days to the conversation. Every extra round of clarification is another chance for the client to book whoever replied with a price first.

A good enquiry form does two things:

1. It collects exactly what you need to give a useful first reply.
2. It stays short enough that people finish it.

These seven fields do both.

The 7 fields

1. Event date

If you cannot do the date, nothing else matters. Put it first. Allow "flexible" or "not sure yet" as an option so early-stage planners do not abandon the form.

2. Venue or location

Travel time, kitchen access, load-in and whether you need to bring equipment all change the price. A town or venue name is enough at this stage.

3. Guest count

Ask for a number, and say that an estimate is fine. "About 120" is far more useful than a blank.

4. Event type and service style

A wedding, a corporate lunch and a birthday party are priced differently, and so are plated, family style, buffet and drop-off. Use a dropdown for event type and simple choices for service style.

5. Budget range

This is the field people are most nervous about, on both sides. Two things make it work:

• Offer per-head ranges rather than an empty box. Nobody wants to be the first to name a number, but most people will pick a range.
• Say why you are asking. A one-line hint such as "so we can suggest a menu that fits" makes it feel helpful rather than salesy.

Set the ranges to match your real pricing, and include one option above your usual range so higher-budget clients can say so.

6. Dietary needs and allergies

Do not stop at a yes/no checkbox. Ask how many guests are vegetarian, vegan, gluten-free, or have allergies, and which allergies. It shapes the menu from the first draft and shows the client you take it seriously.

7. Must-haves

One open question: "Is there anything you already know you want?" This is where you learn about the family recipe, the timing constraint or the dish they will judge you on. It is often the most useful answer on the form.

What to leave off

Everything that can wait until after the first proposal: colour schemes, full run-of-show, how they heard about you, and long free-text "tell us about your event" boxes that nobody knows how to fill in. You can ask those once the client is engaged.

Contact details (name, email, phone) obviously stay — but keep them to three fields.

Forms vs a chat

A form collects details. It does not reply, ask a follow-up question, or notice that the guest count is missing.

That is why some caterers put a chat on their website that asks these same seven questions one at a time, in plain conversation, at any hour. Collaborative Kitchens AI does this: it asks for the date first, then venue, guest count, style, budget and dietary needs, and puts the lead and the whole conversation into one pipeline. You can try it on a real enquiry.

Whichever you use, the rule is the same: get the details that decide the price in the first exchange. For the rest of the process, see how to respond to catering enquiries faster.

Checklist

• ☐ Event date (with a "flexible" option)
• ☐ Venue or location
• ☐ Guest count (estimates welcome)
• ☐ Event type and service style
• ☐ Budget as per-head ranges, with a one-line reason
• ☐ Dietary needs and allergies, with numbers
• ☐ Must-haves