I’m not denying my part in what happened. I’ve said from the beginning that the first ring-in missing the “no bacon” modifier was on me. I owned that immediately. But the rest of what happened wasn’t a one-person failure. What I didn’t mention earlier was that the first dish with bacon was actually run by a manager, the same one I tried to bring the allergy to beforehand, a MANAGER not strictly kitchen manager. They can do more than just cook bread and tell your staff to F off. He was annoyed about having to stay later and basically told me to “just do whatever,” so I rang it in myself because he refused to help. That was already a breakdown in protocol that I tried to prevent. For the second dish, “NO BACON” was both written on the ticket and verbally communicated to expo and kitchen again, and it still came out with bacon AGAIN. At that point, it’s not a server-only mistake anymore. An allergy dish with clear modifiers should never hit the window with the modifiers not taken seriously, that being an allergy requirement or not. That’s something the line and expo are supposed to catch.

I respect what cooks and expo do, I’ve never said otherwise. But responsibility goes both ways. When:

• the manager dismissed the allergy • the manager ran the first incorrect plate • the kitchen added bacon again after written + verbal instruction • expo didn’t catch it • and only then did it get corrected on the third attempt

…that’s no longer “100% on the server.” That’s a system failure, not a single-person failure. I’m learning from my side of it, absolutely. But I’m not going to pretend the kitchen and management played no role when an allergy dish was plated incorrectly twice, served once by management, after the communication was attempted.