Who Is Accountable When Things Break? Why Clear Protocols Protect a Restaurant

Everyone who has spent time working in restaurants knows the sound. A glass falls behind the bar. A stack of plates shifts inside the kitchen. Something metal hits the floor, followed by the sharper sound of ceramic breaking beneath it. For a moment, everyone notices. Then service continues. One broken glass does not destroy a restaurant. Neither does one plate, one misplaced utensil, or one pan damaged by accident. Breakage is part of any operation where people move quickly, carry hot objects, work in tight spaces, and repeat physical tasks hundreds of times.

But when things are constantly breaking, disappearing, deteriorating, or being replaced, and none answers to it, the restaurant has a different set of problems. It has a financial leak and an unaccountability problem. But first let's be clear on the fact that accountability is not the same as blame. Blame asks who was standing there when something went wrong. Accountability asks why it happened, who was responsible for preventing it, what conditions contributed to it, and what must change so it does not continue. That is a much more useful set of queries.

The Person Who ‘Dropped It’ May Not Be the Whole Problem

Imagine a busy service. Servers are clearing tables quickly because guests are waiting. The dishwashing station is full. There is not enough landing space for dirty plates, so servers begin building stacks wherever they can. Large plates go on top of small plates. Cutlery falls between them. A heavy steel pot appears on top of ceramic. Glasses are placed wherever a few empty centimeters remain. Then the stack collapses. Who is accountable? The dishwasher may say, reasonably, “I am washing as fast as I can. I cannot process more than the station allows.” The server may say, “There is nowhere else to put the dishes. I have to clear the table so the restaurant can seat the next guests.” The host may say, “We have reservations waiting. I cannot stop seating people because the dish area is full.”

At first, everyone appears to be pushing responsibility toward someone else. But perhaps everyone is describing the same problem from a different position. The station does not have enough capacity. There is not enough landing space. The racks are poorly positioned. The machine is too small. The workflow is badly designed. There may not be enough dishware in circulation, forcing the kitchen to demand the same plates back immediately. In that case, the broken plates are not primarily the result of one careless person. They are the visible consequence of an operational bottleneck. The responsibility eventually rises toward the person who has the authority to correct that bottleneck. The manager. The chef. The owner. This does not mean employees carry no responsibility. It means accountability has to follow the actual cause, not merely the final moment.

I once managed a restaurant where the dishwashing station seemed permanently behind. Every time I passed, the dishwasher was working. He did not appear distracted or lazy. He was scrubbing, rinsing, and moving continuously. Still, everything took an extraordinary amount of time. A greasy pot remained in his hands far too long. Plates needed repeated scrubbing. The station accumulated dishes faster than he could release them. For some time, I observed the person. Eventually, I stopped looking only at the person and looked more carefully at the station. I put my hand into the water. It was cold. I asked him why he was not using hot water. “There is no hot water,” he said. “Otherwise, I would.” There, that was the problem. The dishwasher was being judged for failing to move quickly through a process the restaurant had made unnecessarily difficult. Grease does not release easily in cold water. The person could work harder, move faster, and remain there longer, but the basic condition needed for the job was missing.

We installed a water heater. Within days, the entire station began to flow differently. That experience stayed with me because it reveals how easily management can mistake a system failure for an employee failure. The dishwasher was not the bottleneck. The cold water was. And the cold water was an ownership problem, because they thought they were saving money. A restaurant cannot demand a standard while withholding the conditions necessary to reach it. If you expect glassware to return quickly during service, the operation needs enough glasses, proper racks, a workable washing system, and someone with enough time to manage it.

If the bartender is expected to make cocktails, serve wine, pour beer, handle payments, replenish stock, and wash every glass by hand, delays are predictable. The bartender is not failing to multitask. The operation has assigned incompatible responsibilities to one position. If the kitchen owns four frying pans but needs twelve in active rotation, the dishwasher will constantly be interrupted by urgent demands. “I need that pan now.” The pan is washed too quickly, overheated, stacked badly, or returned before the station has handled it properly. The problem may appear to be careless dishwashing, but the kitchen simply does not own enough pans for its production. Sometimes accountability means buying what the operation needs. Sometimes it means repairing the machine the business already owns. Sometimes it means adding a shelf, changing the direction of the flow, purchasing the correct racks, creating a separate area for glassware, or assigning another person during the busiest period. Management cannot demand care while designing chaos.

Common Sense Is Not a Protocol

One of the most dangerous phrases in restaurant management is: “It is common sense.” Do not stack glasses inside one another. Do not place heavy pots on ceramic plates. Do not leave knives hidden in soapy water. Do not throw hot pans into cold water. Do not use a delicate tool for a task it was not designed to perform. All of these may appear obvious to someone with experience. They are not obvious to everyone. People arrive from different kitchens, households, countries, training systems, and levels of experience. What one person understands automatically may never have been explained to another. Common sense is not universal. It is accumulated context. If something matters to the operation, it should not depend entirely on the hope that every person will interpret the situation in the same way. Make the rule visible. Explain why it exists. Demonstrate the correct procedure.Then confirm that the person understands it. That is a protocol.

“Do not stack the glasses” is a rule. “These glasses are thin and cannot carry downward pressure. Place each glass in the corresponding rack, and when the rack is full, take it directly to the washing area” is a usable protocol. The difference is important. A rule says what not to do. A protocol shows how the work should happen instead. Restaurants put great attention into the movement of food. How ingredients enter the kitchen. Where they are stored. How cooks collect their mise en place. How a finished plate reaches the pass. How the server carries it to the guest. But the reverse journey often receives much less thought. What happens after the guest finishes? Where does the plate go? Where is it scraped? Where does the cutlery land? Where are glasses separated? Where do hot pans enter the dish area? How are delicate and heavy objects kept apart? How do clean items return to service? This reverse movement is part of the restaurant’s organizational architecture.

If it is badly designed, employees will invent their own solutions during pressure. They will put things where they fit. They will create stacks. They will place objects on the floor, on top of machines, inside boxes, or in walking paths. Then management will complain that people are careless. But improvisation is often what appears when the system has not provided an answer. Every repeated movement should have a destination. Dirty glasses go here. Ceramic plates go here. Cutlery goes here. Hot cookware enters from this side. Clean racks leave through this path. Broken items are recorded here. A good protocol removes unnecessary decisions from a busy moment. The employee does not have to invent a solution while carrying twenty kilograms of dirty dishes. The solution already exists.

Not Every Breakage Is the Same

Accountability also requires distinction. A glass can break because someone slips on a wet floor. A glass can break because the rack is damaged. A glass can break because the restaurant is using the wrong rack. A glass can break because a server stacks six of them despite repeated instruction not to do so. These are not the same event. One may be an accident. One may reveal a maintenance problem. One may reveal a purchasing mistake. One may be negligence. Treating all breakage as employee misconduct is unfair and unproductive. Treating all breakage as unavoidable is equally weak. The business needs to investigate the conditions. Was the correct procedure available? Was the employee trained? Was the equipment functioning? Was the station overloaded? Has the same behavior happened before? Was the person rushing because staffing was insufficient? Was the instruction ignored deliberately?

Only after answering these questions can management respond appropriately. Accountability without investigation becomes punishment. Investigation without consequence becomes permission. The business needs both fairness and enforcement. A protocol that no one enforces gradually becomes a suggestion. The restaurant may have a handbook. Signs may be posted. Employees may sign training documents. But if managers ignore the rules during busy service, the team quickly learns which standards matter and which ones exist only on paper. Someone has to own the protocol. 

The floor manager may be responsible for how servers clear and return tableware. The bar manager may be responsible for glassware, bottles, tools, and washing systems. The chef or sous chef may be responsible for cookware, knives, small appliances, and kitchen equipment. The stewarding supervisor may be responsible for the organization and flow of the dish station. Ownership does not mean that one person performs every task. It means someone observes the system, corrects misuse, records recurring problems, and brings unresolved needs to management.

If glasses continue breaking, someone must follow the pattern. Where are they breaking?
During which shift? In which rack? While being carried, washed, stored, or polished? Is one glass type failing more than another? Are there enough glasses for the volume of the restaurant? Without ownership, each incident remains isolated. With ownership, incidents become information. A poorly designed system does not excuse deliberate carelessness. People sometimes mistreat equipment because it does not belong to them. They throw utensils into containers. Drag equipment rather than lift it correctly. Force components that do not fit. Stack glasses to avoid making another trip. Use knives to open cans. Leave machines dirty because the next shift will deal with them. These behaviors cost money. They also affect everyone else.

A damaged pan becomes another cook’s problem. A broken blender delays prep. A missing attachment makes the machine useless. A scratched glass reaches the guest. A knife left in a sink creates a safety risk for the dishwasher. Employees need to understand that restaurant property is part of their working environment. Care is not an abstract value. It protects the tools they need to perform their jobs. Once the business has provided the correct equipment, explained the protocol, demonstrated the procedure, and made the standard clear, the employee becomes responsible for following it. Repeated disregard should have consequences. Those consequences should be clearly established, proportionate, documented, and applied according to company policy and applicable employment law. Accountability should never become arbitrary punishment or an improvised deduction decided in anger after service. The aim is correction and protection of the operation. Not revenge.

Owners sometimes purchase expensive machinery and assume the supplier’s short demonstration is enough. One employee receives the explanation. That person later teaches someone else from memory. Months afterward, the machine is being used in a completely different way. Then it breaks. A good equipment protocol should include operation, cleaning, shutdown, maintenance, and reporting. What should be checked before use? Who is authorized to operate it? How is it cleaned? Which parts are removed? What signs suggest a problem? Who is contacted when something fails? Should the machine continue running?

People often damage equipment not because they intend to, but because they do not recognize the early signs of failure. The strange sound is ignored. The loose component is tightened incorrectly. The machine is forced to continue because service is busy. A manageable repair becomes a major one. Training creates the possibility of accountability because it establishes what the employee was expected to know. A simple breakage log is enough. Over time, the log may reveal that one particular glass is too fragile for the restaurant’s volume. One rack may be causing pressure damage. One service period may have insufficient staff. One station may repeatedly mishandle equipment. Without a record, the owner only notices when supplies suddenly need to be reordered. “I bought glasses two weeks ago. How are half of them gone?”

The answer should not depend on everyone trying to remember. The business should know. This connects directly to inventory and auditing. Plates, glasses, utensils, pans, containers, and small tools may not be counted every day, but they should be reviewed with enough regularity to identify abnormal loss. Otherwise, replacement becomes an invisible operating expense. The restaurant keeps buying the same objects without ever correcting the reason they disappear.

The Accountability Circle

Consider the common cycle. The restaurant owns a glasswasher. The glasswasher breaks. No one repairs it because money is tight. The bartender begins washing glasses by hand while also serving a busy bar. Glassware accumulates. Drinks slow down. Guests complain. Glasses are stacked badly and begin to break. The owner becomes angry because replacement glassware costs money. But the broken machine remains unrepaired. The operation has entered a vicious circle. The owner may say, “The staff broke the machine, so I am not buying or fixing another one.” Perhaps someone did misuse it. But leaving the operation without a functioning solution does not punish only that person. It damages service, increases breakage, slows revenue, frustrates employees, and affects guests. Accountability has to move in both directions. Employees are accountable for caring for the resources provided. Owners are accountable for providing resources that function. Managers are accountable for ensuring that the procedures are followed and that failures are reported before they become crises. When one part refuses its responsibility, the whole system weakens.

Reverse engineer the damage. When something breaks repeatedly, work backward. Do not begin with “Who did it?” Begin with “How does this keep happening?” A pile of broken plates may lead you to insufficient dish-area space. Damaged pans may lead you to cooks overheating them or dishwashers cooling them too quickly. Cracked glasses may lead you to incorrect racks, poor storage, excessive stacking, or a glass type unsuitable for high-volume service. A broken machine may reveal missing training, deferred maintenance, unstable power, incorrect cleaning chemicals, or the wrong equipment for the workload. This is reverse engineering the loss. Start with the damage and trace the conditions that produced it. Then decide where responsibility sits. Sometimes it belongs clearly to an employee. Sometimes to a manager. Sometimes to purchasing. Sometimes to the design of the operation. Often it is shared. That is why accountability is not always a straight line. It is a chain.

The goal is not a restaurant where everyone is afraid to touch anything. Fear makes people hide mistakes. Someone breaks a glass and quietly throws it away. A machine begins making a strange sound and no one reports it. A server conceals a damaged tray because they expect punishment. That culture makes accountability harder. The better culture is one where accidents can be reported honestly, negligence is addressed consistently, and recurring system failures are corrected by management. People should know: If something breaks accidentally, report it. If equipment is malfunctioning, stop and report it. If the station cannot handle the volume, raise the issue. If someone repeatedly ignores a protocol, the manager will intervene. If the operation has not provided the right means, ownership will be expected to respond.

This creates a culture of care rather than secrecy. Care for the tools. Care for the people using them. Care for the money invested in the business. Care for the flow that allows service to happen.Restaurants lose money when things go unaccounted for. Not only through major theft or spectacular equipment failure, but also through the daily erosion of objects. A glass here. Two plates there. A pan was damaged. A machine neglected. A stack of containers missing. A station slowed because something was never repaired. Each event appears small. Together, they become a significant cost.

The answer is not to demand that everyone “be more careful.” Carefulness needs support. Clear protocols. Proper training. Adequate equipment. Enough space. Defined responsibility. Regular inventories. Maintenance. Documentation. Fair consequences. Managers willing to enforce the rules. Owners willing to correct the operation. This is what accountability looks like in practice. It asks the employee to respect what has been provided. It asks the manager to notice what is happening. It asks the owner to provide the conditions under which the standard can be met. And when something goes wrong, it asks a better question than: “Who can we blame?” It asks: “What failed here, who had the ability to prevent it, and what must we change before it happens again?” That question protects more than the plates and glasses. It protects the restaurant from repeating the same loss while pretending every incident was unavoidable.

Renato Osoy - Chef | Founder

Making a great dish doesn't have to be complicated—it's really about knowing how to unlock the potential of your ingredients.

My goal with Culinary Collector is simple: to bridge the gap between the professional kitchen and your table. Drawing on my training at Le Cordon Bleu and my Guatemalan roots, I propose culinary ideas as departure points that help you build depth in every dish. Whether it's a new technique or a recipe for Adobo Negro, I want to give you the 'secret sauce' that makes your guests ask, 'How did you make this?'

https://www.culinarycollector.com/atelier
Previous
Previous

Why Failed Recipes Are the Key to Creative Mastery

Next
Next

Where the Restaurant Leaks: How Systems and Audits Protect Your Business