Full-service restaurant kitchen porter - banquet breakdown and reset SOP - forty minutes from last guest to next-available room, four parallel lanes (leftovers, ware, linens, floors), and a reset is not a reset until it is signed off
You are the kitchen supervisor of a full-service restaurant. Write "banquet breakdown and room reset" as an archivable standards document, executed by kitchen porters and cleaners, with the shift lead as acceptor. Context: the restaurant takes banquets; a lunch banquet often precedes dinner service or a second event, and the window between is tight. Total reset target: [40] minutes (measured in this house - do not borrow another restaurant's number with different rooms and staffing).
1. Four parallel lanes (not four sequential steps - all four start at once; that is the only way [40] minutes works)
1. Leftovers and waste lane
- Takeout boxes: quantities confirmed with the host [30] minutes before the banquet ends, so packing starts the moment it ends - no counting boxes while the clock runs
- Staff-meal rules (red line, set strict by the house): cold dishes never kept; hot dishes more than [2] hours off the line never kept; opened whole fish and large roasts never kept - the exact limits are set by the house and printed here; porters do not make in-the-moment "looks fine" calls
- Waste poured by category, solids and liquids separated per house rules; the grease trap takes liquids only
2. Ware lane
- Scrape plates before they reach the dishpit - every soupy rack delivered at rush is dishpit capacity burned
- Plates, bowls, and glassware in separate racks; glassware is hand-washed, never racked through the machine; breakage logged on the spot as found (feeds the breakage audit)
3. Linens and tabletop lane
- Tablecloths, napkins, and chair covers bagged by type and counted - bag count and piece count on the bag label, for reconciling with the laundry; "about two bags" is not a count
- Lazy Susan dismantled and wiped; tabletops run scrape, wipe, then sanitizer - three steps in order
4. Floors and restoration lane
- Sweep then mop; oil spots treated separately, not smeared across the room; tables and chairs returned per the room diagram posted inside each door
- Climate, lights, AV off-checked; lost items photographed and reported, never pocketed or "held at the desk"
2. Handback acceptance (fixed)
- A reset is judged "ready for the next event", not "looks clean": the shift lead runs the room checklist - settings complete, floor free of grease, no odors, equipment restored, linens counted - and signs; the signature timestamp is the reset completion time
- An unsigned room is not reset, and the floor may not book it into the next event - this clause gets copied to the floor manager
3. Staffing
- One owner per lane (roles may double up), standing on their lane [10] minutes before the end - the reset starts when guests stand up, not when the room empties
Red lines (own section):
- Staff-meal limits are never relaxed on the spot - relaxed once, the rule is gone
- Glassware never goes through the machine
- Lost items are never self-disposed: photo, report, hand in
Output format: sectioned, archivable document, one section per lane; each section ends with a one-line "what the shift lead checks"; red lines in bold. Include a blank reset timing sheet template (start and end time fields per lane).
Why it is written this way
The failure mode of breakdown is working in sequence: clear all the food, then all the dishes, then linens, then floors - an hour gone, with dinner guests waiting. Four parallel lanes are the skeleton of this SOP: one owner per lane, all four starting the moment guests rise. That is also why staffing happens ten minutes early: the enemy of a reset is not the workload, it is the blank minute after the room empties when nobody knows what to touch.
"Ready for the next event" replaces "looks clean" as the handback standard because the second cannot be accepted or rejected: a mopped-but-greasy floor and a wiped-but-missing-spoon table both "look clean". The signature turns handback into a timestamped event - whether lunch-to-dinner works is read off the signature time, not off vibes - and copying "no signature, no next booking" to the floor manager is what gives the rule teeth.
The staff-meal limits are a red line that cannot be relaxed on the spot because that is a food-safety authority question: a porter has no mandate to make the house's safety calls, and "looks edible" discretion is exactly where incidents enter. The house sets the rule in advance (no cold dishes, a hard hour limit); porters execute a rule, not a feeling - rules can be strict, discretion always drifts loose.
Counting linens into labeled bags and logging breakage on the spot are small moves that feed the sister processes: the bag labels settle laundry disputes without opening bags, and the breakage log flows straight into the breakage attribution audit. Breakdown is the weakest link in the building's data chain - the moment people are most exhausted and most tempted to skip is exactly the moment the raw data every later audit needs is being produced. Embedding the logging into the SOP, instead of hoping someone "writes it down later", is what keeps the chain intact.
Variables
| Variable | Notes |
|---|---|
| Reset duration target | Minutes from last guest to signed handback - measured here; room layout, staffing, and dishpit capacity differ, so do not import a number |
| Staff-meal cutoff | Hours off the line within which hot food may feed staff - the house food-safety rule, set strict |
| Takeout confirmation point | How long before the end the box count is confirmed with the host - avoids counting boxes during breakdown |
| Lane staffing table | Who owns each lane (roles may double) - standing on lanes ten minutes early, written into the shift habit |