You shop for a catering event roughly five days before it happens. Any detail your client changes after that, headcount, a dietary restriction, a venue access code, is a detail you cannot fully act on in time. Most of the chaos that shows up on-site was never a staffing problem. It was a missing field on an intake form.
Here is the exact list of fields that prevent that, and how to sequence when you collect each one.
Why "we texted about it" is not a system
Ask any caterer where their event details live and the honest answer is usually: scattered. Some in an email thread, some in a text from three weeks ago, some in the owner's head. That works until the owner is behind the cart on the day and a staffer needs to know the parking situation, the client changed the headcount and nobody updated the shopping list, or an allergy mentioned once on a phone call never made it into the kitchen prep.
A single structured intake form, filled out once by the client and treated as the source of truth, removes this failure mode entirely. It is the same discipline that lets a business run events in a city the owner has never visited: staff can execute correctly because the information exists in a system, not in someone's memory.
The event intake field list
Send this as one form, not a scattered set of emails. Every field maps to a real failure mode operators report when it is missing.
| Category | Fields to capture | What it prevents |
|---|---|---|
| Headcount and timing | Final guest count, event start and end time, service window length | Under-ordering, staffing the wrong number of hours |
| Venue access | Load-in address if different from the event address, parking instructions, loading dock or freight elevator code, day-of contact name and number | Late arrival, a driver circling the block during setup |
| Power and water | Outlet availability and amperage, distance to nearest water source, whether generators are needed | Equipment failure mid-event, a scramble for an extension cord |
| Dietary and allergies | Every restriction by name, not "some people have allergies," cross-contamination sensitivity level | The single most costly on-site mistake to get wrong |
| Weather and heat limits | Indoor or outdoor, shade availability, expected temperature | An outdoor spread in summer heat can be unsafe to leave out much past 90 minutes, so the service plan has to account for it before the day, not during it |
| Add-ons and menu changes | Any items added since the original quote, signature drink or dish requests, cake-cutting or bar-timing coordination with other vendors | Menu drift that never made it back to the shopping list |
| Staff and equipment assignment | Which cart, rig, or kit is assigned, which staff member is lead | Confusion when more than one crew is running that week |
| Payment and deposit status | Deposit received, balance due date, cancellation terms acknowledged | Awkward day-of payment conversations |
That last row deserves its own note. Deposit and cancellation terms belong on the intake form even though they also live in the contract, because the staff member executing the event should not have to go find the contract to know whether a balance is outstanding.
When to send it, and when to lock it
Two touchpoints, not one.
Right after booking: send the full form. This is when you capture venue access, dietary restrictions, and anything that needs lead time, like a specialty ingredient order or a rental request.
Five to seven days before the event: send a short confirmation version, three or four fields only, to catch last-minute changes: final headcount, any new dietary notes, and a confirmation that access and timing have not shifted. This is your real shopping deadline, so anything that changes after this point needs a direct conversation, not a form update nobody sees.
Treat the second touchpoint as non-negotiable. Operators who only collect intake once, at booking, are the ones who show up to find the guest count is wrong or a client added a dietary restriction nobody flagged.
Where the form should live
The form itself matters less than what happens to the answers. Route submissions into whatever your team actually checks that day, whether that is a shared drive, a project management board, or a CRM record tied to the event. The event brief that reaches your staff on the day should be a summary of this data, not a second document someone has to compile by hand from the original form.
If more than one crew member touches an event, that summary should include which equipment is assigned and who the lead is. Confusion between "which cart" or "who is running this one" is a preventable failure once the assignment is written down in the same place as the rest of the event details.
FAQ
What should a catering intake form include?
At minimum: final headcount, event timing, venue access and parking details, power and water availability, every dietary restriction by name, weather and heat considerations, any menu add-ons since the quote, staff and equipment assignment, and payment status. The field list above maps each category to the specific on-site failure it prevents.
When should I send the intake form?
Send the full form immediately after booking, so you have lead time for anything that needs it, like specialty ingredients or venue coordination. Send a short confirmation version five to seven days before the event, since that is roughly when you shop, to catch any last-minute changes before it is too late to act on them.
How is an intake form different from a service agreement or contract?
The contract covers liability, deposit terms, and cancellation policy, the legal relationship. The intake form covers execution details: what your crew actually needs to know to run the event correctly. They overlap on payment status, which is why that field belongs on both, but the intake form should never be treated as a substitute for a signed agreement.
Should intake questions live in my CRM or a separate form?
Either works as long as the answers land somewhere your team checks on event day. A CRM that auto-creates a project and event brief from the form submission is the cleanest setup, since it removes the manual step of someone copying answers into a separate document. A standalone form is fine for smaller operations as long as someone owns compiling it into the day-of brief.
What is the single biggest gap operators leave out of intake forms?
The five-to-seven-day confirmation touchpoint. Most operators collect intake once at booking and never re-check it before shopping. Headcount and dietary details change constantly between booking and event day, and a form sent once weeks or months earlier cannot catch that drift.
Get the systems that stop details from slipping
An intake form is one piece of the operational stack that keeps a growing catering business from running on memory. If leads are landing but events keep hitting the same on-site surprises, that is a systems gap, not a staffing one. Visit our Website service page to see how we help caterers build the intake, booking, and event-brief workflow that scales past what one person can track by hand.