The contract said sixty. You ordered for sixty, set sixty chairs, and put three servers on the floor for the rehearsal dinner. Forty-six people walk in.
You just paid for fourteen plates nobody ate, plus a server you didn't need on a Friday in July. Flip it the other way and it's worse: the host swore it was forty, eighty show up, and your line is slammed while the back half of the room waits for entrees that aren't coming fast enough.
The booking was the easy part. The hard part is the week before, when the final count, the two vegetarians, the one serious shellfish allergy, and the question of who's actually paying all live on your phone as texts you half-remember. You chase the host the night before, catch them at nine, and scribble the number on the back of the kitchen printout. Then you hope.
Why the night-before scramble happens every time
Hosts aren't trying to make your life hard. They just don't know their own number until late. People RSVP to them, not to you, and half of those land in the last week. The groom's aunt cancels, two coworkers decide to come, the kid count changes twice.
So the information you actually need shows up in a trickle, right when you have the least time to go collect it. You're running other events, prepping, and ordering against a deadline from your purveyor. Nobody sits down to call the host until it's almost too late, and by then you're guessing on the stuff that costs the most to get wrong: food quantity, labor, and dietary needs.
A short automated sequence fixes the timing problem. Automated here just means you set it up once and your system sends the texts on its own, on the dates you pick, without anyone remembering to do it.
The three texts that do the chasing for you
You don't need the count ten times. You need it three times, spaced so each one asks for what the host can actually answer that week. Each text is short and carries a link to a quick form (a web page with a few boxes to fill in), so the host taps it from their phone in under a minute.
- Three weeks out: "Hi Sarah, looking forward to the Hydrangea Room on the 12th. Rough head count and any allergies so far? No need to be exact yet." This one sets the ceiling and surfaces the serious allergies early, while you can still plan the menu around them.
- One week out: "Getting close. Can you confirm your count and anything new on dietary needs?" This is the planning number, the one you order and schedule staff against.
- Two days out: "Final count for Saturday? Also, arrival time, and who should we hand the bill to at the end?" This locks it, and it quietly solves the payment question before the end of the night instead of after.
Each reply drops straight into one record for that event. The host does the work of answering on their own schedule, usually at a red light or on the couch, and you stop being the one placing calls at nine at night.
Keep the form short or they won't finish it
The fastest way to break this is to ask for too much. A host staring at fifteen fields on their phone closes the tab. Ask for what the kitchen and floor genuinely need and nothing else.
- Head count, with a spot for kids if that changes your pricing or seating.
- Allergies and dietary needs, in plain boxes: shellfish, nuts, gluten, vegetarian, vegan. Leave room for "other" so nobody writes a paragraph in the wrong place.
- Timing: arrival, when they want food out, any toast or cake moment the floor should know about.
- Billing: one check or split, and the name of the person settling up.
Pre-fill the date, room, and host name so they're not retyping what you already know. The whole thing should feel like confirming, not filling out paperwork.
One place your kitchen and floor actually read
A count does you no good if it lives in your texts and the chef's number lives on a sticky note. The point of the sequence is that every answer lands in a single event record you can print or pull up on a screen: count, allergies, timing, billing, all current as of the last reply.
Make that record the one source everyone trusts. The expo station sees the three allergies flagged in bold. The floor lead sees the 6:30 arrival and the cake at eight. Whoever's closing knows the bill goes to the best man, not the bride's father who left at ten.
When the number changes, and it will, it changes in that one place and nowhere else. No more three versions of the count floating between a text, a printout, and somebody's memory.
Where this won't save you
Automation chases, it doesn't decide. If a host ghosts all three texts, you still have to pick up the phone, and you should, because a host who won't confirm two days out is a host whose count you can't trust anyway. The sequence just makes that the rare exception instead of every event.
It also won't fix a soft cutoff policy. If your contract doesn't say when the final count locks and what happens if more show up, the form only collects numbers you can't hold anyone to. Decide your rule first (we usually see the final count lock 48 hours out, charged whether they show or not), then let the two-days-out text put it in writing.
And it won't read minds about a guest who arrives with an allergy the host never mentioned. You'll still train the floor to ask at the table. The sequence cuts the surprises down, it doesn't erase them.
Worth setting up this week
You can have the bones of this running before your next weekend of events. Start small.
- Pull your next three booked parties and write down how you got each final count. If the honest answer is "a phone call the night before," this is for you.
- Write the three texts in your own voice. Keep them to two sentences each, and put the link right there.
- Build one short form: count, allergies, timing, billing. Five fields, not fifteen.
- Pick where the answers land (one printable event sheet) and name who reads it in the kitchen and on the floor.
- Set your final-count cutoff in writing and match the two-days-out text to it.
It's a small state, and the Newport function season is short and loud. You shouldn't spend the best Fridays of the summer guessing at a number you could have locked on Thursday. If you'd rather hand the setup to someone, that's the kind of thing we wire up for local spots in an afternoon.