The Kitchen Timeline for a Catered Event

The two events I remember most vividly both went wrong for the same reason: the food was ready, and then it wasn't. First time, we plated forty covers twenty minutes early because the room was ahead of schedule — and then the speeches ran long, and forty plates sat under lamps drying into leather. Second time, the opposite: the venue kitchen had two induction points instead of the four on the site sheet, regeneration took twice as long, and I sent the first course fifteen minutes late to a room that had already finished its wine.

Neither was a cooking problem. Both were timing problems. A catered event isn't a menu you execute; it's a schedule you execute, and the menu is the easy part. Get the schedule wrong and it doesn't matter how good the lamb is.

Plan the event kitchen schedule backwards, not forwards

The anchor is service time — the moment the client's run sheet says the first course is served. Call it 20:00. Everything in your event kitchen schedule is a negative offset from that number. You do not think "we arrive at 14:00, then what?" You think "plates leave at 20:00, so what has to be true at 19:55, 19:30, 18:00, 15:00, and the day before?"

That's the whole discipline. The buffer is not optional and it is not the same for every task. A cold canapé can be plated with a ten-minute buffer. A regenerated braise that has to come up through the danger zone needs a buffer measured against a safety clock, not just against how long the oven takes. More on that below, because it's the part most people get wrong.

Work each block backwards and write down the clock time. When you're done you have a spine. It will look roughly like this for a 120-cover plated dinner at 20:00, cooked off-site and regenerated at the venue:

Those numbers are a starting point, not gospel — a 300-cover buffet regenerates differently from a 40-cover tasting menu. But the shape holds for almost any job.

The prep-day / event-day split

The single biggest lever you have over event-day stress is how much work you move to the prep day. The rule I use: anything that doesn't degrade in 24 hours gets done the day before. Anything that must be fresh, hot, or crisp at the moment of service stays on the event day. Everything else is negotiable and you push it earlier if you can.

Goes on the prep day

• Braises and stews. They're better the next day anyway. Cook, cool correctly, chill, portion cold. You'll regenerate on site.
• Stocks, sauces, dressings, purées. All hold. Sauces split into service-size containers so you're not decanting from a 5-litre pot at 19:45.
• Butchery and portioning. Trim, weigh, portion, tray up. Doing this on site with one sink and a folding table is how people cut themselves.
• Baking and pastry bases. Sponges, tart shells, most components of a plated dessert.
• Mise for cold courses. Pickles, cured elements, anything in a marinade.

Stays on the event day

• Regeneration of hot food (never fully cook off-site if you can regenerate — a re-heated-from-cold braise beats a four-hours-in-a-cambro braise).
• Anything fried, seared à la minute, or crisp.
• Final dressing of salads and leaves.
• Plating and garnish.
• Sauce finishing — mounting butter, adjusting seasoning, correcting consistency after travel.

Building the safety clock into the timeline

This is the part that turns a nice-looking schedule into a safe one. Hot food that leaves temperature control is on a clock whether you're watching it or not. Under the US FDA Food Code — and mirrored in most national codes — time/temperature control for safety food sitting in the danger zone (roughly 5–60°C / 41–135°F) is limited: broadly, food held between those temperatures should be used or discarded within four hours if you're using time as your control, and a stricter two-hour reading is the practical target caterers plan to.

The way this bites a caterer: the clock doesn't start when service starts. It starts when the food leaves proper temperature control — the moment it comes out of the hot-hold or off the heat and starts drifting. If you plate 120 covers and the last one isn't eaten until 90 minutes after the first left the pass, that last plate has been ticking the whole time.

So you build the window into the schedule as a hard boundary, not a hope:

Concretely, for the 120-cover dinner: if the room finishes the main around 20:45 and I want a two-hour planning margin, nothing hot can come out of temperature control before 18:45. That's why regeneration is scheduled at 19:00, not 17:30 "to be safe" — earlier is less safe here, because it starts the clock too soon. The intuition that "ready early = good" is precisely backwards for hot-hold food.

Practical tactics that keep you inside the window:

• Regenerate in waves for big numbers. Don't bring 120 covers up to temperature at once and hold them. Bring up enough for the first 40, then the next, so the tail of the room gets food that only just left the oven.
• Hot-hold at true temperature, and log it. A cambro or bain that reads 63°C+ is holding, not drifting; the four-hour clock is for food out of temperature control. Know which regime each item is in and record the reading.
• Cold courses have the same clock in reverse. A seafood starter plated and left on a pass table is drifting up into the zone. Plate late, or plate onto chilled bases.
• When in doubt, the clock wins. Food that has been out too long gets binned. Build the cost of that risk into your quote, not into a gamble at the pass.

The run of show is one document, and everyone reads it

A run of show for catering is the master timeline that ties your kitchen schedule to the room's schedule and the client's schedule. The client's planner has their own run sheet — arrivals, speeches, first dance, cake. Yours has to interlock with theirs. The failure mode I opened this piece with — plating early into a room that ran long — is a run-of-show failure: my kitchen timeline wasn't married to the room's.

A workable run of show has, in one place:

• Clock column — every entry pinned to a real time, sorted top to bottom.
• Kitchen actions — regen start, plating start, course away, in your language.
• Room actions — doors, seated, speeches, service cues, from the planner's sheet.
• Owner — who is responsible for each line. "Course two away — Ahmet." No orphan tasks.
• Contacts — the planner's mobile, the venue duty manager, your driver.

The point of writing it down isn't bureaucracy. It's that on the night, adrenaline erases your plan. A printed run of show on the pass is the thing you glance at when the room is loud and someone's asking a question and you can't remember whether the fish is meant to go before or after the toast. It's also the document you hand your commis so they can act without asking you every ninety seconds.

Load-in, setup, and the reconnaissance that saves the night

Load-in is where off-site catering is won or lost, because it's the part you can't fully control from your own kitchen. The venue kitchen is never quite what the site sheet said. Fewer power points. A combi that's actually a domestic oven. No hot water. A twenty-metre carry from the loading bay to the prep area, up a ramp, in the rain.

The defence is a site visit — or at minimum a hard phone call — before the day, and a load-in schedule that assumes friction. My load-in block is always at least 30 minutes longer than the drive-and-unload maths says it should be, because it never goes to the maths. Order matters too: equipment out first so there's somewhere to put the food, cold chain into a running fridge fast, and only then the ambient stores.

Once you're in, setup is its own mini-timeline: power on and ovens preheating before anything else, because a cold combi coming up to 180°C is 20 minutes you don't get back at 19:00. Fridges loaded and confirmed reading temperature. Stations built in the order you'll work them. Bins and a wash point identified. Then, and only then, do you start final prep.

Plating cadence: the beat of service

For a plated event, service isn't one moment, it's a rate. 120 covers don't leave the pass simultaneously; they leave at a cadence, and your plating line has to sustain that cadence without either stalling or racing ahead of the room.

If the planner wants all 120 mains down inside 12 minutes so the room eats together, that's 10 plates a minute. A single pass can't do that — you build a line: platers, sauce, garnish, wipe-and-away, and you count the hands against the rate. If four platers can dress two plates a minute each, that's your 8–10. If the maths doesn't reach the rate, either the line grows or the room's expectation gets managed before the night, not discovered at it.

The cadence also feeds back into the safety clock: the faster the room eats, the shorter the drift window on the last plate, which is another reason to plate late and fast rather than early and slow.

Breakdown is on the timeline too

The night isn't over when the last plate goes. Breakdown is a scheduled block, not an afterthought, and it's the part your tired brain wants to skip. Hot equipment has to cool before it's packed. The venue wants its kitchen back by a contracted time — often with a penalty attached if you overrun. Leftover food is a food-safety decision, not a "shove it in a coolbox and sort it tomorrow" decision: what was held hot and has now been out too long gets binned, full stop; what stayed properly chilled can go home under the cold chain.

A realistic breakdown block for the 120-cover job is 60–90 minutes: strip stations, bag waste, wipe down, cool and pack equipment, walk the space with the venue manager, load the van in reverse order (first thing you'll unload tomorrow goes in last). Put it on the run of show with a clock time and an owner, or it sprawls to 1am and your staff cost quietly doubles.

Where the timeline connects to the rest of the plan

The kitchen timeline doesn't stand alone. It sits between two other documents. Above it is the banquet event order — the client-facing contract of what's happening, how many, what's agreed. Your timeline has to honour the BEO's guest count and service times exactly; if the BEO says 120 at 20:00, your schedule anchors to 120 at 20:00. Below it is the prep list — the granular, sequenced tasks that make each timeline block real. The timeline says "17:30, final prep"; the prep list says what "final prep" is, in order, by station.

The point

A catering event timeline is not a nice-to-have you write up if you have time. It is the job. The cooking is the part you already know how to do; the reason experienced caterers stay calm on the night isn't that they cook faster, it's that they scheduled backwards from the pass, split the work honestly between two days, and built the safety clock into the plan so holding never breaks the rule by accident.

Write the run of show. Pin every line to a clock time and an owner. Anchor it to the pass and let the safety window set your hard boundaries. Then, on the night, you're not improvising — you're reading.

"The food was ready twenty minutes early. That was the problem, not the solution."

Every caterer learns that sentence once, usually the hard way. Build the timeline properly and you learn it on paper instead.