Every catering job has one fixed point: the moment the first plate lands in front of a guest. Whether it's a wedding breakfast for 120, a corporate awards dinner or a milestone birthday buffet, the service time is what everyone remembers and what the rest of your day has to fit around. It's tempting to plan forwards — arrive at nine, cook at eleven, serve at two — but the realistic approach is to work backwards from that first plate, then add breathing space at every stage. The difference between a calm service and a chaotic one is rarely the cooking; it's the hour that quietly disappeared during setup.
Think of the day as a chain of dependent steps, each one needing to finish before the next can begin. A useful running order looks like this:
Once those blocks are mapped out on paper, you can see immediately where the pressure points sit. Most of them are not in the kitchen at all.
Timelines usually fail because they were built from best-case assumptions. Unloading a van for a 100-guest wedding can easily take 45 minutes if there's a lift, a long corridor and a flight of stairs in the way. Dressing a room properly takes longer than people expect — linen, cutlery, glassware, centrepieces, table numbers and water jugs all take hands and minutes.
A sensible rule is to double the time you think unloading and set-up will take, then shave it back only if you've worked the venue before. Plating is another quiet thief of time. A team of four can plate roughly 40 to 50 covers in ten minutes once they're in rhythm, but the first few plates always take longer. Allergies, dietary covers and last-minute changes eat into that window too, so build them in rather than hoping they won't appear.
Weddings tend to run on a long, formal arc. If the wedding breakfast is at 3pm, aim to arrive on site around 8am, have food delivered and the kitchen set by 10am, cooking underway by 11am, and canapés plated by 2.15pm. Speeches, photographs and late-running ceremonies are the usual culprits, so treat the stated time as the earliest possible start rather than a promise.
Corporate events are usually tighter. A drinks reception at 6.30pm with bowl food means arriving by 3pm, setting up the service station by 4.30pm, and having the first trays ready 15 minutes before guests are due. Lunches for 80 in an office or venue often need a three-hour window: one hour to set up, one to serve, one to clear.
Private parties are more relaxed but less predictable. Buffets can be set 30 to 45 minutes before guests arrive, though the kitchen still needs two to three hours on site beforehand. If there's a live band, a magician or a cake cutting, ask for the running order and work around those fixed points.
A realistic timeline includes deliberate gaps. Ten to fifteen per cent of your total on-site time should be unallocated, and it's far better placed before service than after. If you've allowed a buffer and nothing goes wrong, you've simply gained a calmer team and a chance to check the details twice.
Two buffers are especially useful: one before final cooking, so a delayed ceremony or a late guest arrival doesn't derail the kitchen, and one before clear-down, so the team isn't rushed into dropping things or overrunning the venue's departure time. Buffers at the end of the evening are worth far less than buffers in the middle of it.
Write the timeline down and share it. The venue needs to know when you're arriving and where you'll park. The client needs to know when food will appear and when the team will leave. Your own staff need their call times, breaks and stations agreed in advance.
Before the day, confirm access, power, water, waste arrangements, noise restrictions and any curfews. Ask about lift dimensions, door widths and whether there's a service entrance. Check allergen information and dietary counts at least 48 hours in advance, then print two copies of the timeline — one for the kitchen, one for the front of house — and note the venue contact's phone number on both.
A good timeline isn't a rigid script. It's a shared understanding of what happens when, which leaves everyone free to handle the small delays that always turn up. Build it backwards, pad it generously, and the service itself becomes the easiest part of the day.