How to Pick a Date for a Team Offsite Everyone Can Make
Your offsite has a budget, a rough agenda and a venue shortlist. What it does not have is dates. So the venue holds a room for ten days, two people say they will check and get back to you, and the hold quietly expires. Knowing how to pick a date for a team offsite is the thing that unblocks everything else: the venue, the flights, the catering headcount, the agenda you have not written yet.
This post is only about the dates. Not icebreakers, not seating plans. Just the question of which two or three consecutive days your whole team can actually be in one room, and how to settle it in about a week instead of a month.
Dates come before the venue, not after
The venue is "the container for everything you're going to do on the offsite", and SessionLab's offsite guide recommends scoping potential venues 6 to 9 months in advance, then pinning them down once the participant number and scope are decided. That is a long lead time, and it only works if you know the dates. WhenNOT's own team retreat date planner puts the order plainly: choose retreat dates before you choose the venue.
This is also why Q4 is when Q1 offsites get stuck. The start of a new financial year or quarter is one of the moments SessionLab names as worth acting on for an offsite, so it is reasonable to expect other teams are eyeing the same January and February weeks, with the same half-answered thread.
Why "what dates work for you?" gets eleven answers and no date
Ask fourteen people when they are free and you get fourteen essays. "Most of January works except maybe the week of the 25th?" "I can do anything after the 3rd, though I might have a client thing." "Whatever everyone else picks." Availability is open-ended, so people answer with ranges and caveats, and none of those answers combine into a decision.
Flip the question. Ask people to cross out the days they CAN'T make. That list is short, specific and memorable: the conference, the half-term week, the surgery, the wedding in Lisbon. Nobody needs to compare their answer to anyone else's. A WhenNOT poll works this way on purpose. People mark their conflicts, the poll ranks the windows with the fewest conflicts first, and a maybe counts as half a conflict so hedging does not quietly sink a good window.
The retreat planner describes the same move: give your team a range of possible offsite dates and ask when they cannot attend. It is a smaller ask, and it is the only version of the question that produces an answer you can act on.
Set a window wide enough to contain a real answer
Before you send anything, decide the outer edges. Avoid known company deadlines and blackout periods before sending the poll, and start with several weeks so there is room for leave, client commitments and travel. Three or four weeks of candidate days is usually right for a two-day offsite. Two weeks is a trap: you will get one surviving window and it will be the week your CFO is in Singapore.
If you want the longer version of how to bound a window and weigh competing constraints, our guide to the event date selection process covers the decision-making side.
Decide how many days in a row you are actually asking about
An offsite is not a set of free dates. It is a block. The duration you ask about is the number of consecutive calendar days, not a collection of separate dates. A two-day offsite with a travel day on each end is a four-day block, and you should ask for four. Weekdays are usually the default, and arrival and departure days belong in the duration if travel means teammates need those days free too.
Be honest about the consecutive part, because the tool will be. If Tuesday is excluded, a multi-day poll will not join Monday and Wednesday into a two-day window. That is correct behavior and it saves you from booking a venue for a split that does not exist.
The arithmetic a group chat cannot do
Here is the failure nobody catches by eye. A Monday with three free people and a Tuesday with three free people do not necessarily make a workable two-day event. If they are different three people, your two-day offsite has nobody who can attend both days.
A multi-day scheduling poll checks whether each individual can attend all consecutive days before counting them. Set how many days you need and collect the conflicts that rule out each possible window. That is the whole job, and it is the job a spreadsheet of ticks reliably gets wrong.
Worked example: 14 people, two days, early 2027
Say you are organizing a two-day offsite for a 14-person team, and leadership wants it locked before the end of the year so the venue can be booked.
Set up the poll
Range: Wednesday 20 January 2027 to Saturday 13 February 2027. Weekdays only. Duration: 2 days in a row. That is three and a half working weeks of candidate windows, which is enough room to survive one bad week.
You create the poll, invite the team by email, and drop the link in the channel with one line: "Cross out the days you can't make. Takes a minute. I need this by Friday." Creating the poll is free: create a poll, share the link and collect the days people can't make.
Let people prefill from their calendar
A participant can connect Google Calendar or Microsoft 365 and Outlook, and their busy times get crossed out for them, editable before they send. This is where a lot of the accuracy comes from, because people remember the conference and forget the two days of interviews.
It also means the marks in your teammates' calendars matter. In Outlook you set an appointment's availability with the Show As box: Free, Working Elsewhere, Tentative, Busy or Out of Office. In Google Calendar you can change the visibility of individual events to control what others can find, and Google notes that for someone with "Make changes (see private events as free/busy)" access, a private entry marked Busy shows as a busy block while one marked Free is hidden. A travel day someone has blocked as Free will not cross itself out. Worth one line in your message: "If your calendar says Free for travel days, mark those by hand."
Read the results
By Friday, 13 of 14 have answered. The heatmap makes week one dead on arrival: a sales conference on 26 to 28 January takes out six people, so every window touching Monday 25 to Friday 29 January collapses. Nobody had to argue about it.
The ranked windows come out something like this:
- 9 Feb to 10 Feb: 13 of 14 available for both days
- 10 Feb to 11 Feb: 12 of 14
- 2 Feb to 3 Feb: 11 of 14
- 27 Jan to 28 Jan: 5 of 14
Windows are ranked by people available for the entire window, then by earliest start date, and overlapping windows stay visible so you can compare them. Tuesday 9 and Wednesday 10 February wins: every one of the 13 who answered can make both days, and the one person who has not answered is on parental leave anyway.
Check the people who actually have to be there
The ranking gives each person equal weight. Your facilitator does not have equal weight. If a facilitator or a particular team must be present, review their response explicitly before making the final choice, and review missing responses and essential attendees before committing to a venue or announcing the dates. One person outstanding is fine unless that person is running the strategy session.
Finalize, then call the venue
You finalize the poll on 9 to 10 February. Everyone gets an email with a calendar file and an Add to Google Calendar link, so everyone can put the dates in their own calendar in one click instead of retyping them by hand. Now you have something to say on the venue call, and now the logistics clock can start: a pre-offsite survey for dietary, travel, accessibility and room needs goes out 1 to 3 months in advance, which only makes sense once the dates exist.
Travel days and distributed teams
If people are flying in, agree on the calendar dates at the destination, then confirm flight arrival and departure dates separately with each attendee. The poll settles which days the offsite occupies; it does not settle whether Marek lands at 23:40. Keep those as two conversations.
If your team is spread across time zones and you also need to pick a start time for day one, the same crossing-out logic applies to hours instead of days. We cover that in scheduling across time zones. And once the dates are fixed, the rest of the build-out is a normal project: our guide to planning a corporate retreat picks up from there.
Four mistakes that cost you a month
- Asking for availability instead of conflicts. Long answers, no decision.
- Asking about single days when you need a block. You will discover the split only after the deposit clears.
- Offering a window too narrow to survive one conference. Give it three or four weeks.
- Waiting for 14 of 14. Set a deadline, finalize on the best window, and tell the stragglers what was chosen.
FAQ
How far ahead should we run the date poll? Early enough that the venue search still has room. If venues want to be scoped 6 to 9 months in advance, the date poll runs before that, not after.
How long should the poll stay open? Five working days is plenty for a team of 14. Say the deadline in the first message and send one reminder on day four.
What if no window gets everyone? Take the best window and handle the exceptions individually. A two-day offsite with 13 of 14 beats a perfect window in April.
Can we include a weekend? Only if the team agreed to it first. Weekday-only is the safer default for an offsite people are being asked to attend as work.
Do people need accounts to answer? No. They open the link, cross out their days and send.
Find the date everyone can make: create a free group poll on WhenNOT - nobody needs an account to answer.