Finding the Hidden Overrun in a Two-Hour Workshop

This is an invented planning exercise, not a real customer event.

Background and constraints

A fictional craft host has promised a 120-minute session to 18 guests. The first draft includes all desired activities but has not allowed anyone to check whether the total fits.

Exact inputs

Start: 14:00. Available duration: 120 minutes.

Welcome | 15
Demonstration | 25
Making session | 60
Break | 15
Sharing | 20
Cleanup | 10

Actual calculated running order

Total: 145 minutes. Remaining: -25 minutes. Conflict: the entered schedule exceeds the available duration.

Planning process

The host deliberately enters the draft unchanged so the tool can expose the conflict. The 145-minute total ends at 16:25 instead of the required 16:00. Rather than removing cleanup or the break, the host revises the demonstration to 15 minutes and the making session to 45.

Result explanation

The revised two cuts remove 25 minutes and produce a 120-minute plan. The first result remains a useful record of why the change was necessary. Guests still receive a break and the host keeps time for leaving the room ready for its next booking.

Alternative

Offer the longer workshop only if the room and participants can support a 145-minute session. A smaller craft outcome is another option; rushing the same task is not the only adjustment.

Execution notes

Explain the shorter activity before invitations are finalized. An overrun warning is about the entered duration, not proof of a collision with another calendar booking.

Continue planning

Open TimeWeave

How to Plan a Themed Event from Start to Finish

Giving Tea Service Its Own Place in the Running Order

FAQ