TripSanity › Trip templates › Team offsite agenda template
Team offsite agenda template: a 1–2 day plan that ends in decisions
This template is for the local offsite — a leadership team, a department or a project group spending a day or two in a rented room, a hotel meeting space or someone's lake house, then going home. No flights, at most one night. It is a different animal from the multi-day travel retreat: that one is built for connection, with one working session a day at most; this one is built to leave with answers. If you are planning the trip version, use the company retreat itinerary template instead.
Offsite or retreat? Pick the right agenda
| Team offsite | Company retreat | |
|---|---|---|
| Length | 1–2 days, home the same night or after one | 3–4 nights |
| Travel | Local; people drive in | Flights, lodging, airport runs |
| Built to produce | Decisions, owners, dates | Connection, plus one real working session |
| Agenda shape | Mostly working blocks, one activity, one dinner | One session and one activity a day, max; lots of free time |
| Plan ahead | 3–6 weeks | 8–12 weeks |
The two-day offsite at a glance
| Day | Shape | Why |
|---|---|---|
| Day 1 | Kickoff · context · two working blocks · activity · dinnerThe morning does the hardest thinking; the afternoon block is shorter; the activity starts when the brains are done. | Day one is for understanding the problem and generating options — not for deciding yet. |
| Day 2 | Recap · decide · commitments · done by early afternoonA fresh morning to choose between day one's options, then an owner and a date on every decision. | The early finish is the reward, and it forces the room to actually decide. |
Day 1, hour by hour
Times assume a 9:00 start at a venue people drive to. Shift the whole day if yours starts later — the lengths of the blocks matter more than the clock.
| Time | Block | Owner · output |
|---|---|---|
| 8:30 | Arrive, coffee, find the Wi-FiBreakfast out and the screen tested before anyone walks in. | Organizer. Parking and the door are in the agenda, so nobody calls from the lot. |
| 9:00 | Kickoff: why we're hereTwenty minutes, not a keynote. Read out the two or three questions the offsite has to answer, and the ground rules (laptops closed outside working blocks). | The team lead. Output: the questions written up where everyone can see them all day. |
| 9:20 | Context: where we actually areThe numbers, what changed, what customers are saying. The pre-reads carry the detail, so this is questions on the pre-read, not a slide deck. | One owner per topic, ten minutes each. Output: a shared picture of the problem. |
| 10:20 | BreakFifteen minutes, protected. | Every 90 minutes, or the second hour is wasted. |
| 10:35 | Working block 1: question oneNinety minutes. Small groups of four or five generate options, then share out and cluster them. | A facilitator who isn't the most senior person. Output: three to five real options. |
| 12:05 | Lunch — away from the roomA real lunch, not a working one, somewhere with daylight. | The hallway conversations here are half the value of the day. |
| 1:05 | Walk and talk in pairsTwenty-five minutes outside with one prompt from the morning. | The post-lunch dip is real. Don't schedule anything heavy into it. |
| 1:30 | Working block 2: question twoSeventy-five minutes, same format as the morning. | Owner named in advance. Output: options, plus what we'd need to believe for each one. |
| 2:45 | Parking lot and close-outFifteen minutes: what's unresolved, what's out of scope, what tomorrow must decide. | Facilitator. Output: tomorrow's decision list. |
| 3:30 | Team activityTwo hours of something collaborative: a cooking class, a guided hike, an escape room, a volunteering shift. | Booked weeks ahead. Name the genuine opt-out in the agenda. |
| 6:30 | Team dinnerA private room, booked under one name, with dietary needs sent to the restaurant in advance. | Work talk allowed, decisions not. Say what's covered and when the tab closes. |
Day 2: decide, commit, go home
| Time | Block | Owner · output |
|---|---|---|
| 8:30 | CoffeeA later start than day one is fine if dinner ran late — say so in the agenda the night before. | |
| 9:00 | Recap: what we learned, what we must decideTwenty minutes, read from yesterday's close-out. | Facilitator. Output: the decision list, confirmed. |
| 9:20 | Working block 3: decideNinety minutes to choose between the options: dot-vote to narrow, discuss the top two, and the decision-maker decides. | Decide in advance who has the final call. Output: the decisions, written down. |
| 10:50 | Break | |
| 11:05 | CommitmentsForty-five minutes turning every decision into an owner, a first step and a date. The parking lot gets an owner too. | The team lead. Output: the commitments list, sent the same day. |
| 11:50 | Lunch | |
| 12:45 | What we tell everyone else + a quick retroAgree the three sentences the rest of the company will hear, then ten minutes on what to change next time. | Output: the internal update, drafted in the room. |
| 1:30 | DoneSend people home early. | An early finish is remembered far longer than one more session. |
The one-day version
One question, or two small ones, fits in a single day. Keep the morning for context and options, decide after lunch, and let the activity and dinner close the day instead of opening a second one:
- 8:45 arrive and coffee · 9:00 kickoff (15 min) · 9:15 context, questions on the pre-read (45 min)
- 10:00 working block: options (90 min) · 11:30 lunch away from the room
- 12:30 walk and talk in pairs · 1:00 working block: decide (75 min)
- 2:15 break · 2:30 commitments: an owner and a date on each decision (45 min)
- 3:30 team activity · 6:00 dinner or drinks, optional and said so
Five rules that make an offsite worth leaving the office for
1. Write the outputs before the agenda
"By 1:30 on Friday we will have decided X, Y and Z." If you can't finish that sentence, you are planning a team day, not an offsite — which is fine, but plan it as one, with more activity and fewer working blocks.
2. Every block gets an owner, a format and an output
"Discuss the roadmap" is not a block. "Pick the three bets for next quarter — Maya facilitates, small groups then a dot-vote, output a ranked list" is. The owner prepares the block the week before, not the night before.
3. Don't present what could be pre-read
Send the pre-reads a week out and keep them short enough to actually be read. Replace the opening deck with "questions on the pre-read." The room is expensive; spend it arguing, not watching slides.
4. Respect the energy curve
The heaviest thinking goes first thing in the morning. Nothing demanding right after lunch. The activity goes late on day one, when people are done thinking anyway, and day two ends early.
5. End with commitments, not a good feeling
The last working block turns every decision into an owner, a first step and a date, and the commitments list goes out the same afternoon. Without it, Monday quietly erases the whole thing.
The offsite prep checklist (six weeks out to the morning of)
- 4–6 weeks: date and headcount locked; venue booked (daylight, a corner for breakouts, Wi-Fi that survives twenty laptops, parking); facilitator named; budget owner named.
- 3 weeks: the two or three questions agreed with the team lead; an owner for every block; the activity booked; a private room reserved for dinner; dietary needs collected.
- 1 week: pre-reads sent; the full agenda published, with the address, how to get into the building, parking, Wi-Fi, the dress code, the dinner details and who to call.
- Day before: supplies — sticky notes, markers, a visible timer, extension cords, the right display adapter — and a test of the screen with the laptop that will actually present.
- Morning of: changes go into the agenda, not a reply-all. A moved block should reach every phone without anyone asking where to be.
Questions offsite organizers ask
How long should a team offsite be?
One day for a single decision or a small team; two days with one night between them when you need real working time and time together. Past two days it's a retreat and needs a lighter agenda. A tight day and a half beats three loose days.
What's the difference between a team offsite and a company retreat?
An offsite is one or two working days close to home, built to produce decisions. A retreat is three or four nights with travel, built for connection, with one working session a day at most. Plan an offsite like a workshop and a retreat like a trip.
What should a team offsite agenda include?
A short kickoff naming the questions, a context block the pre-reads keep short, two or three working blocks with an owner, a format and an output, one team activity, a dinner, and a commitments block at the end. Breaks every 90 minutes and a parking lot for the good ideas that don't belong in this room.
How far in advance should you plan a team offsite?
Three to six weeks. Book the venue and the private dinner room first; set the questions and block owners about three weeks out; send pre-reads and the full agenda one week before.
What are good team offsite activities?
Collaborative, and nothing that puts anyone on the spot: a cooking class, a guided hike, an escape room, a volunteering shift, a long lunch with lawn games. Late on day one, with a genuine opt-out named in the agenda.
How should you share an offsite agenda with the team?
One link, a week ahead, that opens in any phone browser without an app or an account, with the logistics in the same place: address, building entry, parking, Wi-Fi, the dinner and who to call. If the agenda is live, a moved block reaches everyone without a reply-all. More on that in how TripSanity runs retreats and offsites.
Run your offsite on TripSanity
Tap “Use this template”, swap in your questions, owners and venue, and it becomes a live agenda with the address, parking, Wi-Fi and who-to-call on one link. No app, no accounts for the team.
Disclosure: TripSanity is our product — this template exists so you can try it with a real plan. The structure is free to use anywhere, in any tool, including a printed agenda on the table.