How to duplicate a session
Re-use an existing session's rows, timing, and assignees on another day of your event. Faster than rebuilding from scratch when Day 2 looks a lot like Day 1.
When you're producing a multi-day event, Day 2 usually looks a lot like Day 1: same general schedule, same intro music, same crew briefing, just different content blocks. Instead of rebuilding the whole thing, you can duplicate a session and use it as a starting point.
Steps
-
Open the event
Sign in at app.overture.show and open the event that contains the session you want to copy. You'll land on the event's Run of Show with a tab for each existing session across the top.
Once an event is open, every session shows up as its own tab. -
Find the session tab
At the top of the Run of Show, you'll see a tab for each session. Locate the one you want to duplicate.
The session tab strip runs across the top of the Run of Show. -
Open the session menu
Right-click the session tab (or long-press on a touch device) to open its action menu, then choose
Duplicate.
The action menu lets you rename, duplicate, or delete a session. -
Rename and reschedule
A new tab appears named
{Original} (COPY)— for example, duplicatingDay 1createsDAY 1 (COPY). Right-click the new tab and chooseRenameto give it a meaningful name (e.g. "Day 2 — Opening"), then adjust the start time. All rows, assignees, and durations come along with the copy.
The duplicate appears as a new tab — rename it to fit your schedule.
Tip
Duplicating copies row content and assignees but does not copy completion state. The new session starts fresh with every row uncompleted — exactly what you want for Day 2.
What gets copied
- All rows in the session, in order
- Row durations and timing
- Stage leader assignments
- Producer notes attached to rows
What doesn't get copied
- Row completion checkmarks (the new session starts fresh)
- Follow-ups created during the original session
- Live show-clock state
Heads up
A duplicated session is independent of the original. Edits to one don't propagate to the other. If you need shared rows across sessions, use a row template instead.