> ## Documentation Index > Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt > Use this file to discover all available pages before exploring further. # Run of Show > Build the minute-by-minute flow of a gig — songs, announcements, breaks, and notes in ordered sections — with autosave, conflict handling, and a print-ready export. The **Run of Show** is the minute-by-minute plan for a gig: the songs, announcements, breaks, and cues in the order they happen, grouped into named parts of the night. It lives at the top of the gig's **Details** tab so it's the first thing you and the crew see, and it's built to be edited live — right up to (and during) the show — with everything saving as you go. Run of Show is gated by the **run-of-show** feature. Where it isn't enabled, a gig still has the simpler [day-of timeline](#the-day-of-timeline) described below. If you expect Run of Show but don't see it, [contact support](mailto:support@soundcheck.live). ## How it's organized A run of show is a list of **sections**, and each section holds ordered **items**. * A **section** is a stretch of the night — *Cocktail Hour*, *Dinner*, *Main Set*. Give it a name so the crew can follow along, and add an optional heads-up note for that stretch. * An **item** is a single cue within a section. Every item has a type: | Item type | Use it for | | ---------------- | ----------------------------------------------------- | | **Song** | A number from the setlist or song library. | | **Announcement** | A spoken moment — a toast, an MC intro, a dedication. | | **Break** | A pause — set break, dinner, changeover. | | **Note** | Anything else the crew needs to know at that point. | Each item can carry timing, free-text notes, and its own attachments (a chart, a lyric sheet, a cue card). ## Building the run of show On the gig's **Details** tab, find the **Run of Show** panel and choose **Edit**. Choose **Add section** and name each part of the night. Drag sections to reorder them. Inside a section, choose **Add item** and pick its type. For a **Song** item, pick from the picker (see [Relationship to setlists](#relationship-to-setlists)); for the others, give it a title. Drag items into the right order, add timing notes, and attach any files an item needs. Choose **Done** to leave edit mode. Your changes were already saved as you worked (see below). Toggle **Show durations** to display each item's length and see the run's timing build up as you add cues. ## Autosave and editing safely You don't press Save. As you edit, Run of Show **autosaves** in the background, showing its state — *Saving…*, *Locked in*, or *Save missed* with a **Retry** — so you always know your work is captured. If a save can't complete, Soundcheck warns you before you navigate away rather than losing the edit. ### When two people edit at once Run of Show is often touched by more than one person around show time — a coordinator and a music director, say. If the run of show changed somewhere else while you were editing, Soundcheck detects the conflict and offers to **merge your edits** on top of the newer version instead of silently overwriting. You'll see a heads-up — *"Updated elsewhere. Your edits merged in; give the show flow a quick scan."* — so you can double-check the order. If you'd rather not merge, the save pauses and you can reload when ready. ## Templates Most orgs run the same shapes of night over and over — a wedding reception, a corporate dinner, a festival slot. **Templates** let you save that shape once and reuse it, so a new gig starts from a real rundown instead of an empty page. Templates live under **Run of Show** in the sidebar, and they belong to your organization — everyone who can manage gigs sees the same library. Template names are unique per organization (case-insensitively), so you can't end up with two *Wedding Reception*s. ### Creating a template Two ways in: * **New Template** on the templates page creates an empty template and drops you straight into the editor to build it out. * **Save from a Gig** — open a gig whose run of show you like, then choose **Save as Template** from the Run of Show section's **⋯** menu. It copies every section, item, song, and attachment as it stands. Saving from a gig flushes any pending edits first, so the template always captures what you actually see — not a half-saved draft. ### Editing a template Opening a template gives you the same editor as a gig's run of show — same sections, items, item types, songs, attachments, drag-to-reorder, and autosave. The difference is that a template has a **name** and **description** at the top instead of a gig, and no gig date. You can also rename a template (or edit its description) from the **⋯** menu on the templates page without opening it. ### Applying a template to a gig From a gig's Run of Show section, choose **Apply Template** (or **Use Template** on an empty run of show), pick one, and confirm. Applying **replaces** the gig's entire run of show, so if there's already content there you'll be asked to confirm explicitly. Times are re-anchored to the gig rather than copied literally: * If the gig has a **start time**, the whole rundown shifts so it begins at that time, keeping the original spacing between items. A template built around a 6 PM show applied to a 7 PM gig moves everything an hour later, including anything that runs past midnight. * If the gig has **no start time**, times are kept exactly as saved in the template. * If the gig has **no date at all**, times can't be placed on a day, so items come across **without** times. Set the gig's date first if you need the timings. The apply dialog spells out which of these will happen before you confirm, and the gig's own date is never changed by applying a template. Applying is a full replace, not a merge — it does not add to what's already there. Templates with no sections or items can't be applied over an existing run of show, so a stray empty template can never wipe a gig's show flow. ### Deleting a template **Delete** on the templates page removes the template only. Gigs that already had it applied keep their run of show untouched — applying copies content rather than linking to it. ## Relationship to setlists Song items and [setlists](/features/setlists/overview) share one song library. When you add a **Song** item, the picker offers the songs from the gig's linked setlists plus your organization's song library, so the run of show and the setlist stay in sync rather than drifting into two different song lists. You can also add a new song to the library right from the picker while you build. Think of it this way: the **setlist** is *what you're playing*; the **run of show** is *everything that happens, and when* — with the songs slotted into their place in the night. ## Exporting When you need a run of show on paper — for the stage, the sound board, or the client — choose **Export** to open the export builder. You control: * **Which fields** appear: time, item-type label, instructions, notes, and attachments. * **Type**: font family, font size, and text alignment. * Your organization's **logo** on the header (on plans that support branded documents). A live preview shows the printable document as you adjust it, and your choices are remembered for next time. ## The day-of timeline Alongside (or instead of) Run of Show, a gig's **Details** tab includes a lighter **Timeline** section — a simple list of day-of segments with a name, start and end time, and notes: ``` 2:00 PM - Load-in begins 3:00 PM - Sound check 6:00 PM - Doors open 7:00 PM - First set (45 min) 9:00 PM - Load-out ``` Add items, drag to reorder, and edit inline. It's the quick option when you just need load-in through load-out and don't need the full section-by-section run of show. ## Attachments Gig files — contracts, stage plots, tech riders, venue maps, promo materials — live on the gig too. Upload them to the **Attachments** section on the **Details** tab (drag-and-drop or browse), add a description, and the whole assigned team can view and download them, on web and on mobile. Already have the paperwork as a PDF or forwarded email? [AI file ingestion](/features/ai/file-ingestion) can read it and propose the schedule, crew, and money for you. Need a signature? Send it for [e-signature](/features/contracts/overview) without leaving the gig. Individual **Run of Show items** can also carry their own attachments, so a chart or cue card sits right on the cue it belongs to rather than in a general pile. ## Related The song library Run of Show pulls from. The tabbed gig detail this lives in. Turn paperwork into a schedule automatically.