Add the requested inputs
Use the labelled fields in the workspace above. If example values are provided, try them first or replace them with your own.
Dates & time · Free online tool
Build a timed event agenda or run sheet with changeovers, then save it as text, CSV or an iCalendar file. Turn a list of sessions into a chronological event schedule with start and finish times that is ready to copy, save as CSV or import into a compatible calendar.
Runs locally in your browser
Enter each line as activity | minutes | optional note. Changeover time is inserted between activities; the finished run sheet can be saved as text, CSV or an iCalendar file.
Use it with confidence
Use the labelled fields in the workspace above. If example values are provided, try them first or replace them with your own.
Use the main action when needed. Each activity starts when the previous activity and selected changeover finish. The schedule length is the sum of activity and changeover minutes.
Start a workshop at 09:00, add registration, welcome, three sessions and a closing block, then include five-minute changeovers.
Confirm the intended timezone after importing the calendar file, and allow extra contingency for access, speakers, audience movement, technical checks and delays that a fixed run sheet cannot predict.
A clearer answer
Enter each activity with its duration and optional operational note, choose the start time and add a standard changeover. The builder calculates each start, finish and the complete scheduled span.
Activity time and transition time remain separate, making the schedule easier to review. Keep the copy-ready run sheet, open the CSV in a spreadsheet or import the generated .ics activities into a calendar.
Six activities total 160 minutes. Five changeovers at five minutes add 25 minutes, producing a complete scheduled span of 185 minutes and a finish at 12:05 before additional contingency.
Method: Complete span = the sum of all activity durations + changeover minutes × one fewer than the number of activities.
The CSV protects formula-like text before it reaches a spreadsheet, and the calendar export converts the device-local entries into portable UTC timestamps. Before sharing, confirm the intended timezone, access, setup, accessibility, speaker availability, audience movement and contingency.
Helpful answers
Yes. Guests receive 3 runs per rolling 24 hours, verified free accounts receive 10, and Premium subscribers receive unlimited normal use.
No. This tool runs in your browser and UtilHub does not receive or store the values you enter. Your browser or device may still retain normal local history or form data.
Each activity starts when the previous activity and selected changeover finish. The schedule length is the sum of activity and changeover minutes.
Confirm the intended timezone after importing the calendar file, and allow extra contingency for access, speakers, audience movement, technical checks and delays that a fixed run sheet cannot predict.
It depends on the venue and activity. Use a realistic default, then add explicit longer setup or contingency blocks where equipment, rooms, speakers or attendees need more time.
It uses the local timezone of the device creating it. The .ics export records the corresponding UTC instants so calendar apps can display them in their configured timezone. Confirm the intended venue timezone before importing or sharing.
Yes. Build the schedule and save the .ics file, then import it into a compatible calendar. Each activity becomes a separate timed calendar event, including its operational note and any following changeover.
Yes. Save the generated CSV and open or import it in a spreadsheet. It contains the event, start, finish, activity, duration, following changeover, note and builder timezone for every row.