The Catering Manager Who Saved the Whole Event (While I Was in Denial)

The email came in at 10:47am on event day. The subject line was “Dietary flag for tonight’s dinner” and the sender was Marisol, the venue catering manager at a Tampa conference property I’d worked with twice before.

I had 180 people arriving at 6pm. I was in setup mode. I almost skipped the email.

I didn’t, because Marisol was not the type of person who sends non-urgent emails on event days. She had been doing this job for 11 years. She was not a hand-holder. When she flagged something, it was real.

Her email was two paragraphs. She had been doing a final review of the BEO against the dietary restriction list from registration. She noticed that three attendees had listed a tree-nut allergy under “severe.” The salad course I had approved included candied pecans. The pecans were added as a finishing touch by the executive chef after I signed the original BEO; they weren’t in the version I had reviewed. The addition got a verbal go-ahead from someone on my team but didn’t get captured in a BEO amendment. Nobody caught it for six weeks.

She was already in the kitchen changing the salad when she sent the email.

My first response was wrong

I called her back within two minutes. My first instinct, and I’m not proud of this, was to ask if the pecans were really a problem. I was in event-day brain, which means I was pattern-matching toward “things are fine” and away from “things need to change.” I asked her how she was sure it was tree nuts and not peanuts. I asked if the pecans were on the surface where they could be removed. I was doing the mental gymnastics that planners do when a problem arrives at the wrong time.

She was patient. She explained that for severe tree-nut allergies, “removing the pecans from the plate” isn’t a fix because cross-contact during plating creates the same risk as ingestion. She was already making a substitution for all 180 plates because she couldn’t guarantee separate plating lines in the kitchen that evening. The substitution was roasted pumpkin seeds. It would cost $180 in ingredient overage.

She was right about everything. I agreed to the substitution in about 90 seconds and felt embarrassed that I’d taken 90 seconds to agree.

What she actually caught

The BEO I signed in May listed the salad as “mixed greens, shaved fennel, citrus vinaigrette.” No nuts anywhere in that description. Marisol’s team had received an updated menu document in early June, six weeks before the event, when the chef decided to add texture to the salad. The addition went through their internal food prep documents but didn’t formally amend the BEO.

The original BEO was the contract document. The updated menu was an operational one. They diverged. Nobody reconciled them against the dietary restriction list.

Three attendees had listed their allergy as severe. One of them was a senior partner at the healthcare consulting firm I was working with. She carried an EpiPen. She would have used it. The other two listed their allergies as medical, not preference. This wasn’t a case of someone who avoids nuts when convenient.

Without Marisol’s review, 180 plates would have gone out with tree nuts on them. I would have been the person who signed the BEO that allowed it.

The protocol change that came out of that day

I made three changes to how I manage dietary restrictions. None of them are complicated. All of them are things I should have been doing before.

The first: I compare the final operational menu document against the dietary restriction list myself, within 48 hours of the event. Not just the BEO. The actual plated menu as described in the kitchen’s service doc. If those two things don’t match, I ask the question before I’m four hours from service.

The second: I stopped allowing verbal approvals for menu changes. Any change to food after BEO signature requires a written amendment, even a one-sentence email. If the chef wants to add a garnish, that garnish goes through me in writing before the event. This sounds like bureaucracy. It is bureaucracy. It also prevents the situation where one person verbally approved a pecan addition and nobody else knew.

The third: I started sending a personal email to every attendee who listed a severe allergy, 72 hours before the event, confirming we have their restriction on file. Most reply with confirmation. Occasionally one corrects their original submission. One person, at a finance client event in 2024, replied to say she had been diagnosed with a second allergy after filling out the registration form. I would not have known otherwise.

What the relationship made possible

Marisol sent that email because she felt ownership over the event. She had worked with me twice. She knew I was serious about the details, and she knew I would want to know. She didn’t have a contractual obligation to reconcile the kitchen’s working menu against my registration data. That was a decision she made because she cared about the outcome.

I’ve worked with a lot of banquet hall and hotel and resort catering teams over eight years. The ones who send that kind of email are the ones who consider themselves co-owners of the event, not executors of a signed document. That distinction isn’t about venue tier. I’ve had it at mid-level properties and missed it at expensive ones.

The venue did not charge me for the substitution. Marisol told me later that the $180 ingredient cost was absorbed because the error originated in their internal process. I offered to cover it anyway. She declined.

That’s the kind of relationship worth protecting. After the event I wrote a detailed note to her director, not a generic thank-you, but a specific account of what she caught and what the outcome would have been. Catering managers get complaints when things go wrong. They rarely get documented credit when they prevent the wrong thing from happening.

The conference centers in Florida I work with most frequently all have someone like Marisol on staff. Finding that person during the site visit, not just assessing the room, has become part of my evaluation process.

What does your dietary collection process look like right now? There’s a specific 3-field format that gets the information catering teams actually need. Happy to walk through it if you’re planning a seated event above 80 people.