How to Plan a Company Offsite Agenda

The cardinal sin

Somebody has spent real money getting fourteen people into the same building. Flights, accommodation, a venue, three days of salary. The instinct — an honourable one — is to extract every hour of value from that investment.

So the agenda fills. Sessions from 08:30 to 18:00, dinner with a speaker, an optional early-morning activity that is not really optional. Every hour accounted for, nothing wasted.

And it produces a tired team that could have had the same meetings over video.

The mistake is treating the offsite as a container for meetings. The meetings are not the reason it is worth flying people in — you can do meetings from anywhere, and you have been doing them from anywhere all year. The reason is the unscheduled adjacency: the walk to dinner where two people from different teams finally understand what the other actually does, the conversation that continues after a session ends because nobody had to click "leave meeting".

That is the product. The sessions are the scaffolding around it. An agenda packed to 95% has scheduled the scaffolding and eliminated the product.

The shape of a three-day offsite

Two nights, three days is the format that works most reliably. Here is the weighting:

Two things fall out of this immediately.

Day one is not a working day. People arrive between 11:00 and 17:00 depending on where they flew from. Scheduling a workshop that requires full attendance is scheduling a workshop that half the group will miss. One opening session that works with stragglers, dinner, and something unstructured is the right weight.

Day three is not a working day either. Checkout is at 10:00, someone has a 14:00 flight, and the collective attention span is already at the airport. Use it for synthesis — what did we decide, who owns what, when does it happen — and finish by lunch. An offsite that ends at 16:00 on departure day ends badly.

Which means a three-day offsite contains one real working day. Plan accordingly, and put the session that matters most on the morning of day two.

Session length, honestly

Ninety minutes is the ceiling. Sixty to seventy-five is better for anything requiring active participation.

This is not a comfort preference. Sessions beyond ninety minutes do not get more done — they get the same amount done with degraded attention, and they degrade the following session too. A three-hour strategy block feels productive to the person running it and is experienced as an endurance event by everyone else.

If a topic genuinely needs three hours, split it: ninety minutes, a real break, then ninety minutes with a different format. Discussion then, say, small groups. The break is not lost time; it is where half the actual thinking happens.

Real breaks are 20–30 minutes. A ten-minute break is a queue for the bathroom. Fifteen is a queue for coffee. Twenty-five is a conversation, which is the thing you flew everyone in for.

The 30% rule

Roughly a third of the waking agenda should be unstructured. Written into the schedule as blocks, not left as accidental gaps.

Writing it down matters more than it sounds. An agenda with a visible "16:00–18:00 — free" block gives people explicit permission to use it. The same two hours left blank reads as an oversight, and the most senior person in the room will fill it with an impromptu session by about 16:20.

What goes in unstructured time is not your concern, and that is the point. Some will work. Some will sleep. Some will have the conversation that turns out to be the whole reason the offsite paid for itself. You cannot schedule that, and attempting to is how it gets crowded out.

The failure modes

Four, in rough order of how often I see them.

No stated purpose. "Team offsite" is not a purpose. An offsite to set next year's priorities, an offsite to integrate a team after an acquisition, and an offsite to reward a hard year are three different agendas, and trying to be all three produces a mediocre version of each. Pick one, say it out loud in the invitation.

Optional activities that are not optional. If the CEO is at the 06:30 run, it is not optional, and people who would rather sleep now have to weigh career risk against exhaustion. Either make it genuinely optional — which means the CEO occasionally skips it — or schedule it and own that.

No decisions. A strategy offsite that produces "alignment" and no written decisions with owners and dates has produced nothing durable. The day-three synthesis session exists specifically to force this, and it should end with a list on a screen that everyone has seen.

Dietary and accessibility handled late. This is logistics, not agenda, but it sinks more offsites than any agenda flaw. Ask at invitation, confirm two weeks out, and tell the venue in writing.

Who should build it

The person building the agenda should not be the person presenting most of it. Those are different jobs, and combining them is why the agenda ends up optimised for the presenter's material rather than the group's attention.

HR and people teams usually end up owning offsite logistics, and the highest-leverage thing to own alongside it is the shape — the session lengths, the break lengths, the free blocks, the one real working day. Content owners will always want more time than the agenda has. Somebody has to hold the line on behalf of the room's attention, and it should be someone with no session to protect.

One practical note: the agenda will change during the offsite. A session will overrun, weather will move something outdoors indoors, an unplanned conversation will deserve an extra hour. A shared live schedule that everyone can check on their phone beats a printed pack that was wrong by the first afternoon.

Adaptable structures sit in the corporate template collection. For a single-day session, the workshop agenda builder is a closer fit than a multi-day retreat format.