A workshop agenda consists of three things: a sequence of blocks, a duration for each block, and a goal each block is meant to achieve. Everything else – method, materials, room setup – hangs off those. With all three in place you have a running order; with one missing you have a list of topics.
What belongs in an agenda
The most common draft we see is a list of headings with clock times in front of them. "9:00 welcome, 9:30 expectations, 10:00 input on conflict models." It reads like a plan, but it will not carry you through the day, because two things are missing.
Duration instead of clock time. A block lasts 45 minutes – that is a property of the block. That it starts at 10:15 is not: that follows from whatever comes before it. Write down clock times and the first rebuild forces you to recalculate everything. Write down durations and you only change the order.
The goal of the block. Not the topic, but what is different afterwards. "Conflict models" is a topic. "Participants can place their own most recent conflict in a pattern" is a goal. The difference shows the moment you have to cut something: with topics you cut by instinct, with goals you see immediately which one you are giving up.
Then come the things that concern delivery rather than dramaturgy: social form (plenary, small group, individual work), materials, and – if you work with colleagues – who runs the block.
The timing
Most running orders that reach us are generous at the front and tight at the back. There is a reasonable explanation: you design in reading order, and your energy while writing is highest at the start. The morning gets air, the late afternoon gets whatever is left.
Buffers do not belong at the end
A buffer at the end of the day buffers nothing. It sits behind every block that might overrun, and by the time you need it, it is long gone. What it actually does is this: you notice at 4:30 in the afternoon that you are forty minutes behind – at a point where nothing can sensibly be rearranged any more.
More useful is a buffer after the block that tends to overrun. Those are almost always the blocks with an open outcome: expectation rounds, case work, anything where participants talk. An input block rarely overruns – you know how long you speak.
Breaks are blocks, not gaps
Treat lunch as a gap between two blocks and you will plan it too short and put something demanding straight after it. Both come back to bite you. A break has a duration, a purpose and an effect on the block that follows – it belongs in the running order like any module.
This matters most for the block right after lunch. It is the hardest one of the day, and it is the wrong place for a long plenary input.
A grid to start from
Not a law, but a starting point for a day running from 9 to 5, to be adapted to your topic:
| Section | Duration | What for |
|---|---|---|
| Arrival | 30 min | Welcome, goal of the day, expectations. Regularly overruns – put the air here. |
| First working block | 90 min | Peak attention. The hardest topic goes here. |
| Break | 20 min | Scheduled, not "as needed". |
| Second working block | 75 min | Depth, first application. |
| Lunch | 60 min | Too long beats too short. |
| Activating block | 60 min | Movement, small groups, case work. No lecture. |
| Break | 15 min | |
| Transfer block | 60 min | Applying it to the participants' own work. |
| Closing | 30 min | Consolidation, next steps, feedback. Most often sacrificed – and least dispensable. |
The 90-minute morning block, incidentally, is not a fixed quantity. It works if you subdivide it – input, exchange in pairs, plenary. As an uninterrupted lecture it does not.
Where planning breaks
Not on the first draft. On the third.
The first draft is written in one go and holds together. Then the client comes back: half an hour less, start at 9:30 instead of 9:00, and please move feedback to day one instead of day two. Three changes – and every clock time in the document is wrong.
At this point most people do the same thing: they recalculate. Twenty minutes in which nothing of substance is produced, with an error rate you only discover in the training room. And because it is tedious, the fourth change no longer gets worked in properly – it gets kept in someone's head.
This is why Sessionario calculates the clock times itself. You give it the start of the day and the durations, drag blocks around, and everything after them moves with them. Before every change a version is saved that you can restore – which also belongs to a running order that has to survive several rounds.
When two of you plan together
As soon as a co-trainer joins, the second familiar problem appears: agenda_final_v4_MS.docx. Two versions, both edited, neither complete.
In Sessionario colleagues are invited into the same session – with roles: edit, comment, or view only. Collaboration costs nothing extra on any plan, because a running order only one person can open does not solve the actual problem.
And if you plan with an AI
Many trainers now draft the first running order in conversation with an AI. That works well – right up to the moment the finished agenda sits in the chat window and has to be retyped.
Since 1 September 2026 Sessionario can be connected once to your own Claude, ChatGPT or Grok. After that the running order is created directly in your planning rather than in a chat window. The clock times are not calculated by the AI but by Sessionario: the AI only supplies durations in minutes. How to set this up and what to watch out for is covered in Planning workshops directly in Claude, ChatGPT or Grok.
In short
- Per block: duration, goal, social form, materials – no hand-typed clock times
- Buffers behind the blocks with an open outcome, not at the end of the day
- Plan breaks as blocks, not as gaps
- Nothing frontal after lunch
- Protect the closing first instead of cutting it first
