---
title: "Saved shows"
description: "Save a rundown once, reuse it across rooms and events."
---

# Saved shows

A saved show is a named snapshot of a rundown, kept at the team level rather than
inside any one room. Save one from a room you have already built, then load it into a
new room or an existing one — as many times, and into as many rooms, as you like.
Loading never changes or removes the saved show itself.

Open the [Controller](controller.md) and click **Saved Shows** in the header.

## Saving the current rundown as a show

1. From a room's Controller, click **Saved Shows** in the header.
2. Under **Save current rundown as a show**, type a **Show name** (required, up to
   200 characters).
3. Click **Save as show**.

What gets saved is the structural shape of each session — **title, speaker, notes,
duration, mode, "pause before", and "this is a break"** — in running order. **Scheduled
start times and auto-start are not saved.** A saved show is reused across rooms and
events, and a fixed clock time or a "start itself" flag only makes sense for one room on
one day, so both are dropped. Loading a show always produces plain, unscheduled sessions —
the same starting point [CSV import](csv-import.md) produces.

Saving does not touch the room's own rundown. It is a snapshot, not a move.

### The free plan is capped at one saved show

**On the free plan your team can hold one saved show at a time.** Saving a second
offers an upgrade instead — the same **Upgrade to Pro** prompt the 1-room limit uses.

This is not a dead end if you want to save a _different_ show without upgrading:
delete your existing saved show from the Dashboard's **Saved shows** panel, then save
the new one. No upgrade required — you are simply back to holding one.

## Managing saved shows

Your team's saved shows are listed on the **Dashboard**, above the room grid, each
showing its name and session count.

- **Rename** — edit the name in place.
- **Delete** — asks for confirmation. Deleting a saved show never affects any room that
  already loaded it; loading copies the sessions rather than linking to the saved show, so
  the two are unrelated again the moment the load finishes.

## Loading a saved show into a room

There are two starting points:

**A new room.** On the **+ New Room** dialog, an extra **Start from a saved show**
picker appears whenever your team has at least one saved show. Leave it on **Start
blank** for an empty room, or choose a saved show to seed the new room's rundown from
it immediately.

**An existing room.** From that room's Controller, click **Saved Shows** in the header,
choose a show under **Load a saved show into this room**, and click **Load into this
room**.

> **Loading into an existing room replaces its entire rundown — it does not add to
> it, and the replacement cannot be undone.** This is the opposite of
> [CSV import](csv-import.md), which always appends. A confirmation names exactly how
> many sessions are about to be deleted before anything happens, so read it before
> confirming — there is no undo once you do.
>
> If the room was mid-show when you load, playback stops and the on-air session is
> cleared, the same as pressing **Reset**.

Loading a saved show is always safe to repeat: it never consumes, changes, or deletes
the saved show, no matter how many rooms load it or how many times.

## Exporting the current rundown as CSV

From the same **Saved Shows** page, **Export CSV** downloads the room's current rundown using the same four columns [CSV import](csv-import.md) reads — **title, speaker,
notes, duration** — so a room's running order round-trips through a spreadsheet. The
button is disabled if the room has no sessions yet.

The file it downloads is a plain CSV with a header row, not a Tamora format. That makes it
the one artefact here that travels: a producer, venue or client who does not use Tamora can
open the running order in any spreadsheet, and a rundown built somewhere else can come back
in through [CSV import](csv-import.md) using the same four columns. A saved show, by
contrast, only exists inside Tamora — it is a starting point for another room, not a
document to hand over.

## Related

- [Controller](controller.md#create-a-room) — creating a room, including the
  saved-show starting point
- [CSV import](csv-import.md) — the other way to build a rundown, and how it differs
  (always appends, never saved for reuse)
- [Team management](team-management.md) — saved shows belong to the team, so any
  member can save, load, rename, or delete one