Local events: the match night nobody told the kitchen

At half past six on an ordinary Wednesday, the door opens and does not stop. Forty people arrive in twenty minutes, most of them wearing the same football shirt. There is a big match on the screens in the bar next door and at the stadium across town, and half the neighbourhood has decided to eat first. Nobody told the kitchen. Prep runs out by eight, the grill falls behind and the regulars who booked a quiet dinner wait an hour for their mains. Local events change a service more than almost anything else, and they are almost always known in advance.

A restaurant's normal patterns, the busy Saturdays and quiet Tuesdays, are easy to see in its own numbers. What its numbers cannot see coming is the concert at the arena, the conference at the hotel, the school holiday, the festival in the square or the road closure that keeps everyone away. Each can double a quiet service or empty a busy one, and each can be planned for, if someone has written it down.

This guide covers what counts as a local event, the three kinds that most often transform a service, how to build a local events calendar once and keep it, and how to use it in forecasting, pacing, menus and staffing. Every venue and figure in it is an example.

Local events catch kitchens out because they sit outside the venue's own records. The forecast looks at recent weeks and bookings, and on a normal Wednesday both point to an ordinary night. The match, the concert or the conference is happening somewhere else, so nothing in the venue's own numbers warns of it.

The information usually exists: fixtures are published months ahead, concert venues list their shows, schools publish term dates. The problem is that nobody at the restaurant is looking. A simple calendar, checked every week, closes that gap.

A local event is anything outside the venue that changes how many guests come, or when. Sports matches, whether at a nearby ground or on screens. Concerts, theatre and shows nearby. Conferences and exhibitions. Markets, fairs and festivals. Public holidays, religious festivals and school holidays. University term dates. Major roadworks or transport changes.

Some events bring guests; some keep them away. Both matter for the forecast, and both belong in the calendar.

Events that bring guests are the ones most venues think of first. A match brings fans who eat before or after. A show nearby brings a rush before curtain-up and sometimes after. A conference brings groups looking for dinner. A festival brings visitors who would never otherwise walk down your street.

The effect depends on the venue: its distance from the event, its style and its guests. A bar with screens near a stadium may be transformed by a match; a quiet fine-dining room across town may barely notice it. That is why your own records of past events matter.

Some events take guests away. A big match can empty a restaurant whose regulars are all watching at home or in a bar. A road closure or a transport strike can keep guests from reaching you. A major event elsewhere in the city can draw your usual crowd away for an evening.

These are easy to forget because nothing happens: the room is simply quieter than expected. Put them in the calendar too, so the kitchen does not prep for a busy night that never comes.

Three kinds of event most often turn an ordinary service upside down. The big match, which brings a rush at a fixed time or empties the room, depending on the venue. The show nearby, which brings an early rush of guests who must leave by a set time. And holidays and school breaks, which change the whole pattern of the week, sometimes for days at a time.

Each needs a slightly different response, from menus to pacing to staffing. The sections below take each in turn.

A big match can bring a wave of guests at once, usually in the hours before kick-off and sometimes after the final whistle. Fans want to eat quickly, often in groups, and they want to be finished in time to watch. If the venue shows the match, it may be full for the whole game, with guests who order drinks more than food.

Know which matches matter to your guests: the local team, the national team, the biggest finals. Fixtures are published well in advance, so they can go in the calendar months ahead, with the kick-off time noted.

Theatres, concert halls and arenas create a rush before the show, of guests who want to eat and leave by a fixed time, and sometimes a second rush afterwards. Pre-show guests need fast service and a reliable finish; a late main course that makes them miss the curtain is a disaster.

Note the start times of shows nearby, and expect early tables to want to be away on time. A short pre-show menu and a clear promise of the time they will be finished turns the rush into a strength.

Holidays change trade for days at a time. A public holiday can turn a weekday into something like a weekend, school holidays can bring families at lunchtime and empty the office crowd, and religious festivals can change when and how people eat for weeks. University terms can transform venues near a campus.

Put every holiday and school break in the calendar, and look at how the same holidays went last year. Their effect is usually repeatable, which makes them among the easiest events to forecast once you have seen them once.

Build the calendar once, then keep it up to date. Start with the events you already know affect your venue: the stadium, the theatre, the school holidays. Add the dates for the coming months, with times where they matter. Then add the events you discover as the year goes on.

Keep it simple: a shared document or a shared calendar the team can see, with each event's date, time, what it is and a note of what it did last time. The aim is a single place to look, not a complicated system.

Most local events are published in advance. Sports grounds and leagues publish fixtures. Theatres, concert halls and arenas list their shows. Councils publish markets, festivals, roadworks and road closures. Schools and universities publish term dates. Conference centres and hotels publish their events.

Make a short list of sources for your area and check them once a month. Sign up to newsletters from the venues nearby. Ask regulars and neighbouring businesses, who often know about events before they are widely advertised.

One person should keep the calendar, with a backup. Usually it is the manager who does the weekly forecast, because they will use it most. Their job is to add new events as they appear, check the sources monthly and note what each event did after it has happened.

The rest of the team can help. A chef who hears about a festival, a server who knows a regular group is coming for a conference, a host who notices a cluster of bookings on one date: each should tell the person who keeps the calendar.

The calendar only helps if it is read. Make it part of the weekly forecast: before writing down the covers for each service, look at the calendar for the coming week and note any events. Then adjust the forecast for each one.

Look further ahead too, a few weeks at a time, for events that need preparation: extra staff to book, a special menu to plan, stock to order. A big match in three weeks is easy to prepare for; one discovered the day before is not.

Local events are one of the four inputs in demand forecasting, alongside recent weeks, bookings already made and the time of year. They are often the input that explains the biggest misses, because recent weeks and the season cannot see a one-off event coming.

When you check a forecast afterwards, look first at the services with the biggest misses and ask whether an event explains them. Our guide to demand forecasting without a data scientist covers how events fit with the other inputs.

How much to adjust the covers forecast for an event depends on what that event has done before. If last season's home matches added around thirty covers to the early evening, add about thirty for the next one. If a concert at the arena usually fills the pre-show slots, forecast those slots as full.

Where there is no history, make a cautious estimate and note it as a guess. After the event, record what actually happened. After two or three of the same kind, the adjustment becomes reliable.

The most valuable part of the calendar is the note of what each event did: covers compared with a normal night, when the rush came, what guests ordered, how long they stayed. These notes turn a list of dates into a forecasting tool.

Compare each event with an ordinary night of the same kind, such as a normal Wednesday dinner. Over a year, you will know which events matter to your venue and which make no difference at all, so you can stop worrying about the second kind.

Event nights often bring guests in a rush, all wanting to eat at once. Pacing covers, spreading arrivals so the kitchen is not hit by every table at the same moment, matters more than ever. Stagger booking times, limit how many tables arrive in each slot and hold back walk-ins until the kitchen has room.

A kitchen that receives forty covers in twenty minutes will struggle however well it is prepped. One that receives them over an hour can cope. Our guide to pacing covers so the kitchen never drowns covers how to spread a busy service.

A shorter menu can help on event nights. Fewer dishes mean faster service, less waste and a kitchen that can keep up with a rush. A pre-show or pre-match menu of a few dishes that can be cooked quickly, at a fixed price, suits guests who are in a hurry and helps the kitchen.

Plan the menu with the kitchen, using what past events showed about what guests ordered. Make sure the prep covers the expected rush, with a buffer for the dishes that sell fastest.

Event nights need the right number of people at the right time. A rush before a show needs extra hands early in the evening; a match night may need extra bar staff during the game. Book extra staff as soon as the event is in the calendar, because other venues will be looking for them too.

Brief the team on what to expect: when the rush will come, what guests will want and how the night will run. Our guide to scheduling from forecast, not from memory covers building a rota from the forecast.

The point of the calendar is that the kitchen is never surprised. Tell the kitchen about every event that will affect a service, at the weekly forecast and again at the briefing on the day: what the event is, when guests will arrive, how many extra covers to expect and what they are likely to order.

A kitchen that knows a match is on can prep more of the quick dishes, set up the grill early and plan breaks around the rush. A kitchen that finds out at half past six can only react.

Event nights often bring more walk-ins than usual, as guests decide on the spur of the moment to eat before the show or the match. Decide in advance how many tables to hold for walk-ins and how many to release for bookings.

Look at the bookings already made for an event date, and compare them with past events. If the book is filling faster than usual, the night may be bigger than expected; if it is slow, guests may be planning to walk in. Either way, the calendar tells you to look.

Some local events come round every year: a festival in the same week, a series of matches through the season, the school holidays, the Christmas markets. They become part of the venue's seasonal trade, and their effect can be planned months ahead.

Put recurring events into the yearly calendar alongside the seasons, and look at how they went last year when you plan. Our guide to seasonal trade: mapping your own restaurant year covers how to build the yearly map.

Events are also a reason to talk to guests. A pre-show menu promoted to guests who opted in, a post about showing the big match, a note on the website about opening early before the concert: each turns an event from a surprise into an opportunity.

Promote only what the venue can deliver well. A pre-show promise of "out in time for curtain-up" is valuable only if the kitchen and the floor can keep it on a busy night.

Events sometimes change: a match is rescheduled, a concert is cancelled, a road closure is moved. When you hear about a change, update the calendar at once and tell the team, especially the kitchen, so prep and staffing can be adjusted.

Keep an eye on the sources in the days before a big event, so a change does not catch the venue out. A rescheduled match that nobody noticed is just as damaging as one nobody knew about.

Neighbouring businesses often know about events first: the hotel knows about the conference, the bar knows about the match screening, the theatre knows about the extra matinee. Ask them to share what they hear, and share what you hear in return.

A small network of local businesses that swap event news is one of the best sources a calendar can have, and it builds goodwill on the street at the same time.

Event nights can be hard on regulars. A guest who booked a quiet dinner on a match night may find the room loud and busy, and the service rushed. Where you can, warn regulars when they book: "It will be lively that evening, with the match on next door."

Some regulars will move to another night; others will enjoy the atmosphere. Either way, they appreciate knowing, and are less likely to be disappointed.

An invented bistro near a theatre and a football ground keeps being surprised by busy and quiet nights. The manager builds a local events calendar: the ground's fixtures, the theatre's shows with their start times, the school holidays and the council's list of markets and road closures. She checks the sources monthly and reads the calendar at every Monday forecast.

After each event, she notes what it did. Home matches add about thirty early covers; theatre nights fill the six o'clock tables; a road closure halved a Thursday. The kitchen now knows about every event a week ahead, the bistro runs a short pre-theatre menu and staggers its early bookings, and the big surprises stop.

servearound keeps no calendar of local events, so the events calendar in this guide is yours: a shared document or the team's own calendar. What it can do is reflect an event in the book: booking rules set the times offered for each shift and the minimum notice, each table's rules set whether it can be booked online, and a booking can be moved to another table or time. There is no limit on covers per time slot, so pacing on an event night is set by which booking times each shift offers.

Reservation analytics show covers by day and hour for any range of dates, so last year's match nights and concert evenings can be looked up and compared with ordinary nights, and the reservations screen shows the bookings already made for an event date. See the reservations module and Analytics.

Anything outside the venue that changes how many guests come or when: matches, shows, conferences, festivals, holidays and road closures.

For most venues, big matches, shows nearby and holidays or school breaks.

Fixtures lists, theatre and venue listings, council notices, school and university term dates and conference centres.

The person who does the weekly forecast, with a backup.

By what similar events did before. Where there is no history, estimate cautiously and record the result.

Stagger booking times, offer a short menu and promise guests they will be away on time.

Yes. Matches, road closures and big events elsewhere can keep guests away.

At the weekly forecast, and again at the briefing on the day.

Local events change a service more than almost anything else, and most are published in advance. Build a local events calendar once: matches, shows, conferences, markets, festivals, holidays, school breaks and road closures, with dates, times and a note of what each did last time. Give one person the job of keeping it and read it at every weekly forecast.

Use it to adjust the covers forecast, to pace bookings so the kitchen is not hit all at once, to run a short menu on rush nights, to book extra staff early and, above all, to tell the kitchen in good time. Note what every event did afterwards, so next year's calendar is a forecasting tool rather than a list of dates.