TL;DR:
Start from the clock: list the total minutes, then subtract breaks and buffers to see how much real content time you have.
Every session needs one owner, a length and an outcome.
Add the minutes back up. An agenda that does not total the day has a hidden overrun.
An agenda that lists six topics with no times feels fine until the day itself. The first session runs long, lunch moves, and the last speaker gets five minutes. The fix is arithmetic done in advance. A one-day event is a fixed number of minutes, and every item either fits or does not.
Start from the minutes you have
A day from 9:00 to 17:00 is 8 hours, which is 8 × 60 = 480 minutes. That number is the whole budget. Everything else, from the welcome to the last goodbye, comes out of it.
Take out the fixed things first: lunch, breaks and the opening and closing. What remains is content time. Most people overestimate it.
Before you start
Write down the outcome of the day in one sentence. A session that does not serve it is a candidate to cut.
Confirm the room or link is available for the whole day, including setup before and clean-up after.
List the sessions and who leads each.
Ask yourself what people need to eat, drink and see.
Step by step
Fix the start, end and lunch: Say 9:00, 17:00 and a one-hour lunch around the middle.
Place breaks: A short break about every 75 to 90 minutes of sitting is a reasonable rule of thumb, not a law. Adjust to your audience.
Add a buffer: One short unassigned gap, so an overrun can be absorbed without moving lunch.
Place the sessions: Heavy thinking before lunch, interactive work after it.
Assign an owner to each session: One name each, who prepares and keeps time.
Total the minutes: Add every row and compare with 480.
Worked example: a workshop agenda from 9 to 5
Time | Minutes | Block | Owner |
|---|---|---|---|
9:00 to 9:20 | 20 | Welcome and goals | Host |
9:20 to 10:30 | 70 | Session 1: where we are now | Dana |
10:30 to 10:45 | 15 | Break | |
10:45 to 12:00 | 75 | Session 2: the main problem | Lee |
12:00 to 13:00 | 60 | Lunch | |
13:00 to 14:15 | 75 | Session 3: working groups | Maya |
14:15 to 14:30 | 15 | Break | |
14:30 to 15:30 | 60 | Session 4: build a plan | Dana |
15:30 to 15:45 | 15 | Buffer (absorbs overruns) | Host |
15:45 to 16:45 | 60 | Session 5: share and decide | Lee |
16:45 to 17:00 | 15 | Wrap up and next steps | Host |
Check the sum: 20 + 70 + 15 + 75 + 60 + 75 + 15 + 60 + 15 + 60 + 15 = 480 minutes. That matches the 8 hours. Content sessions are 70 + 75 + 75 + 60 + 60 = 340 minutes. Breaks and lunch are 15 + 60 + 15 = 90. Welcome, buffer and wrap-up are 20 + 15 + 15 = 50. Then 340 + 90 + 50 = 480, so nothing is missing and nothing is counted twice.
Look at what the arithmetic tells you. Of 480 minutes, 340 are content: a little over two thirds. If a speaker asks for "another half hour", you can see exactly what it costs: the buffer disappears and the next session shrinks.
Owners, outcomes and materials
For every session, write three short lines: the owner, the outcome ("the group agrees three priorities"), and what is needed (slides, a flip chart, a shared document). The owner keeps time and decides what to cut if the session runs over. Send the owners their slot and ask them to confirm.
When the day runs late
Decide before the event what you will cut first. A good rule is to cut from the middle of a session, not from the break or the wrap-up, because tired people leave without the decisions if the end is squeezed. Tell the owners the order of cuts in advance: buffer first, then the shortest part of the most flexible session, then discussion time.
Keep one person watching the clock whose only job is to give each owner a two-minute signal. Times printed on the agenda are promises, and a visible clock makes them easier to keep.
Share the agenda
Put the agenda in a document or a page everyone can open, with the date, place, link and the owners. Send it a few days ahead, with anything people should read first. Add the day to attendees' calendars with a link to the agenda in the description.
Mistakes to avoid
Scheduling content right up to the end of the day with no buffer.
Skipping breaks to "save time". Attention drops and the time is lost anyway.
Giving a session two owners. Nobody then keeps time.
Putting the hardest session straight after lunch.
Forgetting the setup and the leftover time for questions.
Doing it faster
DuckyHelper can add up a table you have on screen when you press the key and ask out loud, as a second check on the total. The agenda itself is yours.
Frequently asked questions
How many sessions fit in a day?
It depends on how long each is and how many breaks you take. Use the 480-minute method and count.
Why include a buffer?
Because sessions run over. A buffer lets one overrun happen without pushing back lunch or the finish.
Get started
