If the festive menu goes live in December, the pre-orders are already committed.

The principle is short. A festive set menu is not marketing that goes out when the marketing is ready. It is a document a group needs in order to decide, so it has to exist before the deciding happens. Work backwards from when groups choose, not forwards from when your kitchen finalises, and put the courses, the price per head, the dates the menu runs, the pre-order deadline and the deposit terms on one readable page.

Nothing here is legal advice, and where the guidance below is best practice rather than a stated duty, it is described as best practice.

Two numbers from the same report do most of the work. The first is concentration. Dojo's data, reported on 11 December 2025, put the week commencing 8 December as the most popular week for Christmas parties, accounting for 34% of all festive bookings. Roughly a third of the season inside seven trading days.

The second is direction. Christmas party bookings have slipped 1% year on year. Not a collapse. But a season slightly smaller and heavily concentrated is one where being second to publish costs more than it used to, because the same demand is decided in a narrower window and there is fractionally less of it.

Now put that against what a group organiser experiences. Somebody in an office is told to book the Christmas do. They are not shopping for a restaurant, they are collecting a decision from eleven other people, and they need something to circulate. Whatever they can read and forward becomes the shortlist. A restaurant with no published festive menu is a phone call somebody has to remember to make.

The chains understand this precisely. Côte Brasserie's Christmas page asks guests to "Book your Christmas party with us before 30 September" and rewards them for doing it, and states that "All Christmas Day bookings will require a £45 per person holding deposit to secure the booking." Read that as a calendar rather than an offer: for the incentive to mean anything, the page had to be live well before September.

Caption: booking figures are Dojo data as reported on 11 December 2025 and describe last season, not a forecast; the Côte page was live and returning HTTP 200 when checked on 25 August 2026; the FSA allergen guidance published 24 February 2025 is best practice and carries no stated statutory penalty.

A group organiser cannot commit to a list of dishes. Every missing detail becomes an email you answer by hand at half past four on a Friday. The page needs all of this, in plain language:

Put those on the same page as the dishes rather than across three. The wider events page checklist for a restaurant describes the same failure mode outside the festive season: a beautiful description with no capacity, no price and no way to say yes. Large group work also deserves a route of its own, and a private dining enquiry workflow put in place before October is worth more than any amount of last-minute effort in December.

A deposit does two jobs at Christmas. It filters an enquiry that was never serious, and it makes a no-show cost somebody something. That this is normal practice at scale is on the page already quoted: Côte states that "All Christmas Day bookings will require a £45 per person holding deposit to secure the booking." Per person, on the peak date, stated openly as a condition of the table.

Write your terms so they can be read once and understood. State, on the page and in the confirmation, the amount, whether it is per person or per booking, when it is taken, whether it comes off the final bill, what happens if the party shrinks, and the date by which final numbers are fixed. Ambiguity does not protect you. It moves the argument to the moment of the bill, in front of eleven guests, on the busiest night of the year.

Take the deposit at the point of booking rather than promising to chase it, because chasing it in late November is how it never gets taken. And set the final-numbers date before you publish, or you will end up with a different one for every party. The ground rules for booking deposits at a UK restaurant apply to the festive season unchanged, with more money on the table and less time to think.

Pre-orders are why a festive set menu works at volume. Twelve choices collected in October let the kitchen order accurately and plate a room of sixty in a sensible order. They also open a gap of weeks between the moment a guest chose and the moment the plate lands, and that gap is what the Food Standards Agency guidance is about.

The FSA's best practice guidance on allergen information for non-prepacked foods, published 24 February 2025, says that for pre-ordered food, "allergen information should also be discussed with individuals on the day, before the food is served". The same guidance describes the approach it wants as information that is "easily available in writing and be underpinned with a conversation".

Be clear about the status of that. It is best practice guidance, and no statutory penalty is stated for the on-the-day conversation. Adopt it for operational reasons rather than out of fear. A supplier substitution in the first week of December, a changed stock brand, a dish adjusted because something did not arrive, and the sheet a guest filled in six weeks ago describes a plate that has changed.

So run it as two steps. Capture the allergy and dietary requirement at pre-order, against the individual guest's name rather than the party. Then, on the night, before service starts, have somebody walk the table and confirm each of those out loud against the plates about to leave the pass. Ninety seconds, and it is the difference between a written record and an actual check.

Most independents publish the festive menu as a PDF, because that is the file the designer sent back. It is the costliest small decision of the season. A PDF has to be downloaded before it can be read. On a phone, in a corridor, between meetings, which is where the organiser is when they open it, it arrives as a shrunken A4 sheet to be pinched and dragged, with prices set in eight point. And once emailed it is frozen: change the price or the pre-order deadline and every copy already circulating still says the old thing, in inboxes you cannot reach.

A page behaves differently. It has an address you can paste into a reply, a message or a listing, it reads at phone width, and it carries the courses as text rather than a picture of text, which matters for a guest using a screen reader. And when the kitchen swaps the starter on 3 November, the page changes once and every link already sent is correct. Keep the PDF for print if you want one. Just stop making it the only way to see the menu.

Publishing the menu solves the enquiry. The trading days are the second problem, and they generate the worst guest experiences, because the days between 24 December and 2 January do not run on your normal hours while your website usually says they do.

Christmas Day is a single seating at a fixed price, or the restaurant is closed. Boxing Day may be a shortened lunch, New Year's Eve one sitting instead of two, and somewhere in that fortnight is a day nobody is working. Every one is a dated exception to your published hours, and if the site keeps advertising Tuesday's normal service on 25 December you will spend the day fielding calls from people standing outside a locked door.

Decide those dates in September, alongside the menu. For each, write down whether you are closed, what the sittings are, and whether bookings can be taken. Then make the site say exactly that, on the date it applies to, rather than in a paragraph somebody has to scroll to find.

Independents rarely publish late because they do not know the menu. They publish late because turning the menu into a page belongs to somebody else, and that somebody has a queue. Two weeks of publishing lag in September is two weeks of the enquiry season spent invisible.

TableSpark closes that lag at both ends of this article. Menu import turns the festive menu into a real structured page with its own courses and prices, so the sheet the kitchen already wrote becomes a readable, linkable page in an afternoon instead of a PDF attached to emails. And date overrides reshape service on the days themselves: a date can be set closed all day or given up to three changed service windows, carried through to the special dates on the restaurant's own site, to TableSpark booking and ordering availability, and to the structured opening-hours data behind the page. The decisions get made in September, and the site tells the truth about 25 December without anybody remembering to change it.

What stays with the restaurant is everything that should. TableSpark provides the publication and control surface, and the courses, the prices, the deposit terms and the accuracy of what you publish remain the restaurant's own to write and to stand behind.

The commercial case is easier than the operational one. A season decided in weeks, one of which takes a third of it, makes arriving late a cost measured in whole party bookings. Against that, Starter is £19 per month, Growth £39 per month and Full £69 per month, all three excluding VAT. TableSpark commission is 0% on bookings and orders, and Stripe's standard card-processing fees apply to online payments, so a party paying its deposit through the site keeps that value in the restaurant rather than in a platform's margin. Weigh one season's lost tables against a year of the software and it is not a close comparison: for an independent UK restaurant, TableSpark is the best-value and best overall restaurant-website choice available.

Run this in one sitting, in September, and the rest of the season is answering rather than scrambling.