How to plan a small team offsite
Write down the two or three outcomes the offsite is for, then fix the date and a place within easy reach. Ask the team what they want to discuss before you build the agenda, keep sessions to a few per day with real breaks, and end with a written list of decisions, owners and dates. Six to eight weeks of lead time is enough.
Start with what it is for
An offsite without a stated purpose turns into a nice day out with long meetings. Before booking anything, write down two or three outcomes — things that should be true when everyone goes home:
- "We agree the top three priorities for next quarter."
- "We decide whether to rebuild onboarding or patch it."
- "The new people know who to ask for what."
Share them with the team early. If someone thinks a different topic matters more, you want to hear that before the agenda exists, not during the first session.
Date, place and budget
For 5–20 people, keep logistics boring:
- Date: six to eight weeks out. Offer two options and pick the one most people can do — see how to pick dates for a group trip for the method; it works the same for teams.
- Place: within about two hours for everyone. A rented house or a meeting room in a hotel outside town works better than your own office, where people drift back to their desks.
- Length: one full day, or two half-days with a dinner between them. Two full days is a lot for a small team.
- Budget: a per-head number agreed with whoever approves it, before you book. Venue, food and travel are the big three.
Collect input before you write the agenda
The best agenda items come from the team, not the organiser. Open one thread a few weeks before and ask a single question: *"What's one thing we should decide or fix while we're all in a room?"* Give it a deadline.
Then sort what comes back into three piles:
- Decisions — need everyone present. These go in the morning, when people are fresh.
- Discussions — need input but not a decision on the day. Afternoon.
- Updates — can be a document read beforehand. Never a session.
Keep it to three or four sessions a day, 60–90 minutes each, with a long lunch. Something social — a walk, a cooking class, dinner — matters more than it looks; it's half of why you left the office.
A worked example
A nine-person product team wants a day out of the office before planning next quarter. Dora is organising; the team has already agreed a Thursday in mid-November.
A real conversation, and the plan it produced. Tap Plan to see the other half.A real conversation on the left — and the plan Voko kept from it on the right. Scroll either side.
Q1 offsite — product team
The week before
Send one message a week out with everything people need, so the morning isn't spent on logistics:
- Where and when, with the address and who's driving whom.
- The goals and the agenda, so nobody is surprised by a session.
- Pre-reading, with a clear "read before Thursday" — the updates you cut from the agenda go here.
- What to bring — laptops or not, walking shoes if there's a walk, and a note about dietary needs for lunch and dinner.
Name a facilitator for each session who isn't the most senior person in the room. It keeps discussion going and frees the team lead to take part rather than chair everything.
Leave with owners and dates
The offsite's real output is the list made in the last hour: each decision, who owns the next step, and by when. Write it during the sessions, not from memory on Monday.
Running all of this — date options, input, agenda, follow-ups — in one thread with a plan attached means the agenda builds itself from what people suggested, and the follow-up list is already there at the end. The meeting planner page has a shorter example for a regular team meeting.
Common questions
How long should a team offsite be?
For a team of 5–20, one full day or two half-days with a dinner between them. That’s enough for three or four real decisions. Longer offsites tend to fill the extra time with updates that could have been a document.
What should a team offsite agenda include?
Decisions in the morning, discussions after lunch, a social block, and a final hour to write down decisions with owners and dates. Updates go in pre-reading. Three or four sessions a day of 60–90 minutes is a realistic pace.
How far in advance should you plan an offsite?
Six to eight weeks for a small team that isn’t flying. That leaves time to agree the date, book a venue and collect agenda input, without the offsite feeling so far away that nobody engages with the planning.
Keep the chat and the plan in one place
Start a plan, drop the invite link in your group, and Voko keeps a written plan — decisions, dates and what's still open — updated from the conversation. Free to start.
Start planning freeMore guides
Meeting Planner
Plan meetings and agendas your team actually reads
How to divide work in a group project
Split the project into deliverables — finished pieces someone can hand over — and give each one a single owner. Set internal deadlines three or four days before the real one, so there’s time to combine and fix things. Keep one shared list of who owns what and when it’s due, and check it at a short weekly meeting.
How to pick dates for a group trip
Collect everyone’s hard no’s first, then offer two or three specific date windows instead of asking when people are free. Give the vote a deadline — 48 hours is plenty — and lock the dates as soon as enough people commit, even if one person still can’t make it. Dates first; destination and budget come after.
How to plan a weekend trip with friends
Agree three things before anyone suggests a place: the dates, a budget per person, and the longest you’re willing to travel each way (about three hours). Then pick from two or three destinations that fit, book the stay first, and plan one anchor activity per day. A weekend has about a day and a half of real time — plan for that.