WORKFLOWS / MEETINGS AND FOLLOW-THROUGH
Plan an offsite around the decisions it needs to produce.
Turn the purpose of an offsite into a timed session plan, with the right preparation, activities, and decisions built in.
WHAT THIS WORKFLOW PRODUCES
An agenda with a reason for every block.
A participant agenda and a more detailed facilitator plan, both based on the same session. Each working block should lead to an answer, a decision, or a useful piece of work. In the example below the break runs 10:30 to 10:45, and the decision owner and required preparation are confirmed before the agenda is shared.
LEADERSHIP PLANNING MORNING
ILLUSTRATIVE DRAFT · 9:00 A.M. TO NOON
THE OPERATING METHOD
Understand the workflow without AI.
Start with what the group needs to achieve. Then choose the people, preparation, and activities that give them a reasonable chance of achieving it. AI is introduced only after the method makes sense on its own.
Name the outcomes
State the decisions or work products the session needs to produce.
YOUCheck readiness
Confirm who must attend, what authority they have, and what information is missing.
YOUDesign the work
Choose a suitable activity and a clear output for each block.
YOUCheck the timing
Allow time for explanation, discussion, breaks, and decisions.
YOUPrepare and confirm
Send relevant prework and review the plan with the session owner.
YOUIf the group lacks the information or authority to decide, change the session's purpose or prepare what is missing before adding more activities.
WHERE THE FACTS LIVE
Use the systems where the work already lives.
These are examples of the information needed. Travel, venue booking, catering, and spending approval remain separate arrangements. Named tools link to their pages in the library.
SESSION PURPOSE
Decisions needed, current plans, and relevant results.
PARTICIPANT INPUT
Concerns, requested topics, and preparation needs.
A form the group fills in
AGENDA AND TIMING
The working session, activities, and confirmed availability.
THREE WAYS TO RUN IT
Choose how much machine.
The AI work progresses from proposing a plan to helping edit the agenda, then investigating inputs and revising a session through connected tools. For a single offsite, Level 1 and a document are enough; Levels 2 and 3 are for people who run sessions often. The tools named are examples. Use what your organization already runs, provided the connection is supported and approved.
LEVEL 1
Build and challenge the first agenda.
Give AI the outcomes, participants, time available, and constraints. Ask it to explain the purpose of each block and identify where the plan depends on missing information.
Use this version when you are shaping the session or need alternatives to an agenda made entirely of presentations.
WHAT THIS VERSION REDUCES
Starting from an empty agenda and repeating familiar activities without considering their purpose.
WHAT A PERSON STILL DOES
What the group needs, which activities will work, and how disagreement should be handled.
MAIN LIMITATION
AI does not know the room's history or relationships unless you explain the relevant context.
Build this version, step by step 4 steps, one action each. Prompts carry a Copy button.
Give the AI a proper brief.
OUTCOMES FIRST
The decisions the session has to produce, how many people are coming, who owns each decision, the start and finish times, and any known constraints. Describe the group dynamics that matter without personal details.
Ask for a working agenda.
Draft an agenda for these outcomes. For each block, give the time, the question to resolve, the activity, and the output. Include breaks and time to agree on next steps. Flag any decision we are not ready or authorized to make.
Challenge the draft.
WHAT COULD STALL IT
- You know which block is most likely to run long.
- You know whose input is missing.
- You know what participants can prepare beforehand.
Remove any block that does not serve the session's purpose.
Confirm the plan with the session owner.
OWNER REVIEW
Go through it together, check the timings yourself, and agree how the decisions will be recorded on the day.
LEVEL 2
Build the agenda inside a planning tool.
Use SessionLab's AI assistant to help draft or refine a session. Give it selected context and edit the agenda in SessionLab, where activities and their duration sit together.
Use this version when you need a practical facilitator plan, repeated timing changes, or several session blocks to coordinate.
WHAT THIS VERSION REDUCES
Translating an idea into agenda blocks and revising activities as the plan changes.
WHAT A PERSON STILL DOES
Activity fit, preparation requirements, facilitator instructions, and what participants receive.
MAIN LIMITATION
A well-timed agenda does not establish that the group is ready to make the intended decisions.
WHY THIS TOOL
SessionLab keeps the agenda, activity instructions, and timing in a dedicated session-planning format. That is useful when a chat-generated document becomes difficult to revise or run from. The AI assistant is a paid-plan feature, and export options differ by plan.
Build this version, step by step 5 steps, one action each. Prompts carry a Copy button.
Create the session in SessionLab.
TIME AND OUTCOMES
Set the working hours and the intended outcomes. Keep the agreed purpose visible while you edit.
Give the AI assistant the context it needs.
SELECTED INPUTS
The goals, what the participants need, and any constraints on preparation. Point it at the useful session material using its context controls. It has not read your forms or your calendar unless you gave it that.
Draft or revise the blocks with the assistant.
SESSIONLAB AI
Ask for activities that produce the outputs you need, then check each block, its length, and its instructions. Swap in a quieter written exercise or a smaller discussion where that suits the group better.
Check the running order from start to finish.
THE CHECK
- The opening instructions are there.
- The transitions between blocks have time.
- The breaks are there.
- There is time at the end to agree on actions.
If the time available cannot carry the outcomes, change the plan now.
Create the participant version.
PARTICIPANT OR FACILITATOR
Use the sharing or export settings to make the participant version. Check what appears in it before sharing, so private facilitation notes stay out of the participant PDF.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
SessionLab documents its AI assistant for creating and refining an agenda with selected context. Source, checked September 6, 2026.
SessionLab documents PDF export views and customization; options differ by plan. Source, checked September 6, 2026.
SessionLab's pricing page lists the AI assistant as a paid-plan feature. Source, checked September 6, 2026.
LEVEL 3
Let an agent assemble and revise the session.
Connect Claude to SessionLab's official MCP service and, where authorized, the relevant planning documents. The assistant can search for suitable facilitation activities and work with the session's blocks. You approve the plan and control sharing.
Use this version when the session must reconcile several inputs or be revised repeatedly as plans change.
WHAT THIS VERSION REDUCES
Moving between planning documents, activity references, and repeated agenda edits.
WHAT A PERSON STILL DOES
The purpose, sensitive facilitation choices, final activities, and what is shared.
MAIN LIMITATION
These connections do not automatically give the assistant access to participant responses, every calendar, or every planning document.
TOOL OPTIONS
This version runs through SessionLab's own connection to Claude or ChatGPT, which is in beta. It does not need Make or Zapier. If collecting participant responses is a recurring chore, Make or n8n can move approved responses into the planning document; add that only when it removes a real manual step.
WHAT THE CONNECTION CANNOT DO
The connection can read and edit sessions and agenda blocks. It cannot create or update SessionLab Pages and Forms, so plan those by hand.
Build this version, step by step 6 steps, one action each. Prompts carry a Copy button.
Connect Claude to SessionLab.
CLAUDE AND SESSIONLAB
Follow SessionLab's setup instructions for its MCP connection. Look at the permission and approval settings before you use it.
Choose the planning inputs.
NAMED FILES
The current objectives, the participant responses that matter, and the known constraints. Use an approved document connection or upload the files. Do not connect systems that add nothing useful.
Ask for a readiness check and a design.
GAPS AND ACTIVITIES
Have the assistant read the inputs, point out where expectations conflict, and search SessionLab's activity library where that helps. Ask it to say why an activity fits and what it should produce.
Approve the proposed session.
THE CHECK
- The order, the timing, and the assumptions have been read.
- The one draft session the assistant may create or edit is named.
- The shared or approved version stays untouched while you experiment.
Let it make the approved edits.
AGENDA BLOCKS
Allow it to update the blocks in the draft session. Then look at the agenda itself rather than taking its description of the edits on trust.
Review, then share the normal way.
FINAL AGENDA
Confirm the plan with the owner, check the participant version, and send it out as you usually would. Invitations, rooms, and spending are separate approvals.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
SessionLab documents an official MCP connection for Claude and ChatGPT with supported session and block actions; it cannot create or update Pages and Forms, and the service is documented as beta. Source, checked September 6, 2026.
SessionLab's pricing page lists the MCP connection by plan; its help article says the connection is in beta and available on all plans while it is. Source, checked September 6, 2026.
WORKS EVEN BETTER WITH
Prepare the questions before the offsite, choose how people will contribute, and leave with a clear record of the decisions.
Written Brief Meeting → | Decision Log → | Liberating Structures →