01
How to read the agenda you get
Start at the top. The line above the schedule is the call the day has to make. If it is wrong, fix your description and run it again. Every block below serves that call.
Check the kind. The "Read as" menu shows which kind of retreat the tool read from your words. A board retreat, a strategy reset and a new leadership team each get different blocks in a different order. If the tool guessed wrong, pick the right one and the day is rebuilt.
Read each block as a job, not a topic. Each working block names a method and what it is done when. That line is the point. Bob Frisch and Logan Chandler, writing in Harvard Business Review in 2006, found that an agenda of time slots and topics rarely moves a team forward, and recommended a stated objective for each part of the day1.
02
How to adapt it without breaking it
- Change the times, keep the order. The early blocks surface what people know; the later ones decide. Moving a decision ahead of the input it needs means deciding blind.
- Cut a block rather than squeeze all of them. Five blocks done properly beat eight rushed ones. Frisch and Chandler found retreats most often derail because nobody limited the scope1.
- Keep the biggest call in the best hours. Mid-morning, not the last slot before drinks.
- Keep the breaks. A tired room agrees to things just to finish.
- Keep the close. The last block gives every decision an owner and a date. It is the first thing people cut and the one that matters most afterward.
03
Common retreat agenda mistakes
| Mistake | What to do instead |
|---|---|
| A list of topics and presentations | One outcome per block, and send the reading ahead so nobody presents it in the room1 |
| A dozen things to cover | One or two questions for the day, and a list of what the team will stop doing |
| The leader opens with a view | Everyone writes first; the leader speaks last. People tend to follow whoever speaks first and hold back doubts2 |
| Open discussion from the start | Time to write alone before talking, so facts only one person holds get said3 |
| Ending on "great conversation" | Every topic ends decided, parked with an owner, or openly unresolved |
The fourth row has strong evidence behind it. In a 1985 experiment by Garold Stasser and William Titus, groups given all the facts picked the best option 83% of the time. When the same facts were split among members, only 18% of groups found it, because discussion kept returning to what everyone already knew3.
04
What to do before the day
Frisch and Chandler put it plainly: a retreat's success is largely decided before it starts1.
- Write the question in one sentence and send it with the invitation.
- Send a short fact book a week ahead: the numbers the day needs, not every report written this year1.
- Collect views anonymously on that question, and share the results just before the day1.
- Book the follow-up now. Put a 30-day check in every calendar. Michael Mankins, writing in Harvard Business Review in 2004, found teams often leave with different readings of what they agreed, and some members then quietly block it4.
- Hand the file to whoever runs the day, whether that is a facilitator or your own leader.
05
The full guide for your kind of retreat
This page covers the agenda. Each kind of retreat has its own guide on who comes, how long, what to send, how to run each block and how to tell if it worked:
- Leadership offsite: the general guide, including venue, cost and a full checklist.
- Annual planning offsite: turning a year's plan into a few funded choices.
- Board retreat: directors, the executive session and the legal questions.
- Strategy reset: when the plan has stopped working and something has to stop.
- Leadership team alignment: a new or changed team agreeing how it works.
- Post-merger integration: two teams, one operating model.
Frequently asked questions
- What should a leadership offsite agenda include?
- A clear statement of the decision the day has to make, time for everyone to write before anyone speaks, one block per decision with a method that ends in something concrete, breaks, and a close where every decision gets an owner and a date. This generator lays the day out that way.
- How long should an offsite be?
- Half a day is enough for one decision. A full day fits a real plan: the problem, the choice, what it costs, what stops, and who owns each part. Two days suits annual planning or a merger. This tool makes half-day and full-day agendas; for two days, the free planner builds both days from your team's answers.
- How is this different from an agenda template?
- A template is the same for everyone. Here the kind of retreat you describe decides which methods run, in what order and for how long, using the same rules as Throughline's planner and its library of 78 methods. AI only writes the questions in your words.
- Do we need a facilitator?
- Not to use this agenda. Each block names its method and what it is done when, so your own leader can run it. If you bring a facilitator, hand them the file.
- Can I edit the agenda?
- Yes. Download it as Markdown and it opens in any editor, Notion, Google Docs or a wiki. To change it with your team's input and run it live, use the free planner.
- Is it free?
- Yes. No signup and no card.
- What is a good retreat agenda example?
- A good one reads as a route to a decision, not a list of topics. It opens with the call the day has to make, gives people time to write alone before they talk, puts the biggest decision in the best hours, and ends with an owner and a date for every decision. Frisch and Chandler, in Harvard Business Review in 2006, found that agendas of time slots and topics rarely move a team forward and recommended a stated objective for each part of the day1.
- What should I send before a corporate retreat?
- The question the day has to answer, in one sentence, and a short fact book with the numbers the day needs, sent about a week ahead. If you can, collect everyone's views on the question anonymously and share the results just before the day1.
- How many topics should an offsite agenda cover?
- One or two questions for the day. Frisch and Chandler found that retreats most often derail because nobody limited the scope, and the team goes home with a dozen next steps and no clear course1.
- Should a staff retreat agenda include team building?
- A short warm-up helps people settle, and the generated agendas include one. But if the retreat has a decision to make, most of the day should go to that decision. For a retreat whose main purpose is how a team works together, choose "New leadership team" in the tool, which builds the day around that instead.
Sources
- Bob Frisch and Logan Chandler, "Off-Sites That Work," Harvard Business Review, June 2006. hbr.org
- Cass R. Sunstein and Reid Hastie, "Making Dumb Groups Smarter," Harvard Business Review, December 2014. hbr.org
- Garold Stasser and William Titus, "Pooling of Unshared Information in Group Decision Making," Journal of Personality and Social Psychology 48(6), 1985. doi.org
- Michael C. Mankins, "Stop Wasting Valuable Time," Harvard Business Review, September 2004. hbr.org
Written by Tom Olajide, Founder. Last reviewed September 24, 2026.