A Chat With a Sell-By Date: Running the Office Christmas Do Group Without a January Hangover
Photo: Sahbiti, CC BY 3.0, via Wikimedia Commons
Every November, a new group appears on someone's phone. It is called something like "Christmas Do 2026" or "Works Party!!" and within an hour it has forty-seven messages, two arguments about whether the pub takes bookings, and one person asking whether their partner can come. By February, it is a searchable record of who drank what and who said the venue was "a bit naff".
The office festive do is one of the few work events where the chat matters almost as much as the night itself. Get it right and people turn up relaxed. Get it wrong and you spend January explaining a joke that landed badly in a thread with thirty people on it.
Give the group an expiry date before you give it a name
The first rule is simple: this is an event chat, not a second team channel. Name it with the year and a closing date, something like "Christmas Do 2026 (archive 20 Dec)". Pin the final details at the top. If your workplace uses a permanent tool such as Teams or Slack, create a dedicated channel rather than hijacking the one where people discuss actual work, and archive it once the last mince pie has gone.
The reason is not tidiness. It is context. A temporary chat signals that the daft stuff, the "is Darren actually coming or is he just reacting with a thumbs up", is not a permanent record. A permanent channel signals the opposite, and people behave differently when they remember their manager can scroll back to 2029.
Plus-one politics: decide the rule, then say it out loud
Nothing derails a festive chat faster than the plus-one question. It arrives early, usually from someone well-meaning, and it sits there like a parking ticket while everyone waits for a manager to answer.
So answer it before it is asked. Decide whether partners are welcome, whether they are subsidised, and what the per-head cost is. Then put that in one clear message, not in a reply buried under a poll about starters.
Script: "Quick one on partners: the room holds 30 and we have 24 on the team, so we can fit six guests. Guests are welcome at £35 a head to cover the meal. If you want to bring someone, reply to me directly by Friday 28 November and I will add them to the list. No pressure either way."
What you should not do is run a public vote on whether a specific person is invited. "Should we ask Kelly's husband?" is not a group chat decision. Invitations and exclusions belong in a private conversation with a manager, not in a thread where the person can see the poll.
The budget poll that saves three weeks of drift
Group polls are brilliant for one thing: a quick temperature check. They are terrible for anything that involves money, because half the group treats a poll as a suggestion and the other half treats it as a binding contract.
Use a poll for the broad shape of the evening: pub meal, restaurant, bowling, or "whatever is closest to the station". Then move to a form or a direct message for the details that matter, such as deposits, dietary needs and who is actually paying.
Script: "Two options for the meal: the Toby Carvery at £22 a head or the Thai place at £31. I will close the poll Wednesday at 5pm so I can book. If you vote for the Thai one, please be aware that is the price, not a guess."
Do not use emoji reactions as votes. A heart is not a yes. A thumbs up is not a deposit. Clear wording saves a lot of quiet resentment.
Dietary needs: ask once, ask privately
A group chat is the worst possible place to collect allergy information. People either overshare, undershare, or post "I'm vegan" and then spend the next two days defending it to a colleague who thinks fish is a vegetable.
Ask once, and ask people to reply to you directly. Keep a simple list. Confirm with the venue in writing. Then post a short summary in the chat that contains no names: "The venue has confirmed two vegetarian, one gluten-free and one nut allergy. If I have missed you, message me today."
That approach protects privacy and still gets the job done. It also means the person with the serious allergy is not left hoping the restaurant noticed a comment from three weeks ago.
Photos: consent before the camera comes out
This is the bit nobody wants to raise, and it is the bit that causes the most trouble afterwards. Someone takes a group photo. Someone else is mid-laugh with a mouthful of roast potato. The photo goes into the chat, then into a wider channel, then onto someone's public account, and by the next morning it has been seen by a client.
Say it early, say it lightly, and make opting out easy.
Script: "Photos on the night: I will assume yes unless you tell me otherwise. If you would rather not be in any, just reply 'no pics' to me and I will keep you out of the group shots. No explanation needed."
Then respect it. Do not post the photo anyway with a "you look fine!" caption. Do not upload anything from the night to the company intranet without asking the people in it. And if someone asks for a picture to be taken down, take it down without a debate.
Secret Santa deserves its own little room
If you are doing Secret Santa, move it to a separate thread. A £10 limit, a draw tool, and a rule that nobody discusses gifts in the main chat where the recipient can see it. It keeps the main group focused on logistics and stops the "who got Rob?" speculation from becoming a running joke that Rob reads every day.
The morning after: close it down properly
Pick a closing date and stick to it. Post the final details one last time: time, address, what is booked, how people get home, and who to ring if they are running late. Then archive the chat or hand it over to whoever is organising the next thing.
If something happened on the night that needs to be dealt with, deal with it through the proper channel. A group chat is not a complaints procedure, and a message sent at 1am is rarely the version of events you want on record.
The best festive chat is the one that gets everyone to the pub on time and then quietly disappears. Keep it light, keep it clear, and give it a sell-by date.