> ## 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 on show day

> Run the show live from the run of show: Follow live and the lock screen, running late and shifting times, what crew see on their phones, the guest live page, printing a backup, and an honest list of show-calling features Soundcheck doesn't have, with workarounds.

This page is about the hours when the show is actually running. It covers what Soundcheck gives you on the day, who can change what, and where it stops. If you call shows with a GO button and cue lights today, read [What show callers expect](#what-show-callers-expect-and-what-to-do-instead) before you plan your first show.

![Run of Show tab in Schedule view with timed items from load in through the sets](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/run-of-show-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=cc9b6bcb5e14471f40191c04ec4aeeed)

## Before doors: a short checklist

**1. Publish the final version**

On the web, open the gig's **Run of Show** tab, choose **Publish** in the header, leave **Notify crew** ticked, and choose **Publish now**. With **Publish before crew see changes** on, crew only see what you published. See [Publishing to crew](https://docs.soundchecklive.io/features/gigs/run-of-show/publishing-and-collaboration.md#publishing-to-crew).

**2. Have crew open the gig in the app while they have signal**

The app keeps a read-only copy of the run of show on the phone for upcoming gigs, so it still shows in a basement with no signal. See [Offline](#offline).

**3. Print a backup**

Export a PDF and keep paper at the caller's position and side stage. See [Printing a backup](#printing-a-backup).

**4. Decide who can shift times**

Only people who can edit the run of show can shift times on the day. Check that your show caller or stage manager is one of them. See [Who can change times on the day](#who-can-change-times-on-the-day).

**5. Publish the guest live page, if you use one**

Guests and vendors follow along at a short code. See [The guest live page](#the-guest-live-page).

## Follow live: now, next and the lock screen

In the mobile app, the gig's **Day sheet** shows a card with the item happening **NOW**, the time left on it, and what's **UP NEXT**. When everything has run, it says **Show complete**.

Choose **Follow live** on the card to keep following the schedule:

* On iPhone, the schedule shows on your **lock screen** (the hint reads *Shows this schedule on your lock screen*). You see the current item, its time left and what's next without opening the app. With **Publish before crew see changes** on, crew see the last published version on the lock screen, never a draft. An editor's own lock screen can show their draft.
* On other phones, the app follows the live schedule inside Soundcheck.
* **Follow live** opens 8 hours before call. Before that, the card says *Follow live opens 8 hours before call*.
* If times move later after you started following, the card says how far, such as *Moved 10 min later since you started following*.
* Choose **Stop** to stop following.

The card follows the clock. The current item is whatever the planned times say is happening now, on each phone. Nobody "advances" it. See [Timing every screen follows](#timing-every-screen-follows).

> [!TIP]
>
> The **Running late?** pill on the current item and the NOW card are on the same screen. When the show slips, the caller can shift the times from the place they're already looking.

## Running late and shifting later

Shows slip. Soundcheck moves the rest of the night for you instead of you retyping every time.

### On the phone

**1. Open the shift**

In the **Day sheet**, tap **Running late?** on the current item. Or open any item and choose **Shift times…**.

**2. Pick how much**

Pick **+5**, **+10**, **+15** or **+30**, step by one minute with the minus and plus buttons, or type a number of minutes. Negative minutes move times earlier.

**3. Pick what moves**

**This and everything after** moves this item and everything later. **Only this item** moves just this one.

**4. Confirm**

Check the preview and any warnings, then confirm. **Undo** stays on screen for about five seconds.

Items with no start time are skipped. If nothing can move by that amount, the sheet says *No timed items can move by this amount.*

### On the web

Open the **⋯** menu on the first cue that moves and choose **Shift this and later**, then **5**, **15**, **30** or **60 min later** or **earlier**. That cue and every cue after it on the same day move, **on every track**. To move only some cues, such as one stage at a festival, tick them and use **Shift** in the bulk bar. See [Shift this and later](https://docs.soundchecklive.io/features/gigs/run-of-show/linking-and-timing.md#shift-this-and-later) and [Changing several cues at once](https://docs.soundchecklive.io/features/gigs/run-of-show/bulk-actions.md).

Shifts stop at the edge of a cue's day, and a key time cue that moves takes the gig's key time with it.

### Who can change times on the day

Anyone who can edit the run of show can shift times, on the web or the phone:

* owners, admins and gig coordinators
* the gig's **Lead**
* anyone assigned **Run of show** on the gig
* anyone given **Run of show on every gig** for the organization

On the phone they also need to be **online**. The app turns editing off without a connection and says *Editing is unavailable offline. Reconnect to make changes.* See [Roles and permissions](https://docs.soundchecklive.io/settings/team/roles-permissions.md).

### When crew see the new times

> [!WARNING]
>
> **A shift on the phone stays a draft until someone publishes on the web.** The app can't publish. With **Publish before crew see changes** on (the default), crew keep the old times until an editor opens the gig on the web and chooses **Publish**. A shift never sends a notification on its own.

What to do about it on show day:

* **Keep a laptop at the production desk** signed in to the gig, so someone can choose **Publish** after each shift. Leave **Notify crew** ticked to push *Run of show updated* to crew.
* **Or turn publishing off for show day.** An owner or admin can switch off **Publish before crew see changes** in organization settings. Crew then see every saved edit as it saves. The setting covers the whole organization, so switch it back after the show if you rely on drafts. See [Publishing and collaboration](https://docs.soundchecklive.io/features/gigs/run-of-show/publishing-and-collaboration.md).
* **Tell people on comms anyway.** No screen in Soundcheck pops up when times change. Phones pick up the new times when they refresh the gig.

## What crew see on their phones

Crew read the last published version of the run of show in the mobile app:

| Where | What they get |
| - | - |
| **Day sheet** | The day's items in order, the NOW and UP NEXT card, and **Follow live**. |
| **Timeline** | The day laid out against the clock. |
| **Setlist** | The sets with their songs. |
| **My items** | A filter above the schedule that shows only the items they're on, plus key times. It opens on **All items** each visit. |
| **Your times** | Their call, start and end, the sections they work, and notes addressed to their position. |
| An item's sheet | Who's on it, with each person's department and task note. |

Editors also get a **Full** view. See [Run of Show on mobile](https://docs.soundchecklive.io/features/gigs/run-of-show/mobile.md).

## The guest live page

The [live page](https://docs.soundchecklive.io/features/gigs/live-page.md) is a public page for guests, vendors and clients, opened with a short event code. Nobody signs in. It shows the gig's status, **Right now** and **Next**, and the run of show titles and times from the **published** version. Notes, surprise cues, items for specific crew positions and crew steps such as load in and soundcheck stay off it. It refreshes every minute.

> [!NOTE]
>
> Publishing a new live page is in early access and rolling out gradually. Contact [info@soundchecklive.io](mailto:info@soundchecklive.io) to have it turned on.

On the day, a gig manager uses the **Live page** card in the app, or the **Live page** tab on the web:

* **Schedule status** tells guests you're running late: **On time**, or **Running N min late** (5 to 120 minutes on the web). While you're late, **Right now** and **Next** on the page follow the delay. Your run of show times don't change.
* **Status note** posts a short message at the top of the page, such as *Doors moved to the east gate*. **Post note** saves it and **Clear** removes it.

> [!TIP]
>
> Use one or the other for guests, not both. If you shift the run of show and publish, the live page already shows the new times. Setting **Running 15 min late** on top of that delays **Right now** and **Next** twice.

## Printing a backup

Paper is the backup on every show. Print before doors, because exporting needs a connection.

| Export | Where | Good for |
| - | - | - |
| **PDF…** | Web: **Export** → **Run of show** | The cue-by-cue sheet. Pick **Quick views** such as **No Surprises**, choose the fields, and filter **For** Sound, Band leader, Planner or Musicians. |
| **Timeline PDF** | Web export hub, or **Export Timeline PDF** in the app | One landscape page with every cue in time order. Good at the caller's desk. |
| **CSV** | Web export hub | A spreadsheet copy you can open anywhere. |
| **Day sheet** | Web export hub | One page per crew member for show day. Never includes pay. |
| **Export Setlist PDF** | App, run of show actions menu | The sets, for the stage floor. |

In the app, the run of show actions menu shows the two PDF exports to people who can edit the run of show and manage the organization's gigs, when they aren't in edit mode. Offline, they read *Needs an internet connection*. See [Exporting](https://docs.soundchecklive.io/features/gigs/run-of-show/exporting.md).

## Offline

Venue Wi-Fi drops. Here is exactly what keeps working:

* **Reading works offline.** The app saves the run of show on the phone for gigs from about four days back to a week ahead. Open the gig once while you have signal so it's saved. **Your times** is saved for offline use too.
* **Editing doesn't.** There's no offline editing and nothing queues up to save later. Shifts, edits and publishing all need a connection.
* **The web needs a connection.** There's no desktop app or local-network mode.

If the whole building goes dark on data, run from the paper backup and a phone hotspot for the one editor who needs to shift times.

## What show callers expect, and what to do instead

Soundcheck is built around the plan for the whole day and everyone in it. It isn't a cue-firing system. If you come from Shoflo, Rundown Studio, Cuez, Stagetimer or QLab, this is the honest list.

> [accordion] A GO button
>
> Soundcheck doesn't have a GO button, or any way to call a cue that advances everyone's screen. The current item follows the planned clock on each phone.
>
> **Instead:** call the show on comms as you do now, and use Soundcheck as the shared script. Keep the caller's page open on the **Day sheet** with the NOW and UP NEXT card, and shift times when the show drifts so "now" stays true.

> [accordion] Warnings and standbys
>
> Soundcheck doesn't have warning or standby states, or cue lights.
>
> **Instead:** write the standby into the cue's **Notes**, such as *Standby LX 14, SQ 7 at the end of the applause*. For a long-lead cue, add a short row a few minutes before it titled *Warning: fly cue 3* so it shows up in UP NEXT in time.

> [accordion] Current and next cue
>
> This one exists, driven by the clock rather than a caller. The app's NOW and UP NEXT card, **Follow live** on the lock screen, the **Now** marker on the web's Tracks view, and **Right now** and **Next** on the guest live page all work out the current item from the planned times.
>
> **Instead of a caller-driven cursor:** keep the times honest. A quick **Running late?** shift keeps every "now" in step.

> [accordion] Countdowns
>
> The app shows the time left on the current item in the NOW card and on the iPhone lock screen. Soundcheck doesn't have a countdown on the web, a full-screen stage or confidence-monitor timer, a speaker timer, a count-up timer, or a live over/under against plan.
>
> **Instead:** run a dedicated stage timer such as Stagetimer next to Soundcheck for the confidence monitor, and type the segment lengths from your run of show into it. Use **Max time** on a cue, such as *45–60 min*, so crew know the hard limit.

> [accordion] Cue numbers
>
> Soundcheck doesn't have cue numbers or cue IDs.
>
> **Instead:** start the row title with the number your departments use, such as *LX 14 · CEO walk-on*. It prints on every PDF and shows in every view.

> [accordion] A column per department (LX, audio, video, graphics)
>
> Soundcheck doesn't have custom columns or separate lighting, audio, video or graphics cue fields. Each cue has one **Notes** box, a **Playback** field (**Live**, **Track**, **DS iPad** or **Other**), speakers, files and people.
>
> **Instead:**
>
> * Write one line per department in **Notes**: *LX: 14 house to half. SQ: walk-on stinger. VX: logo loop to ME.*
> * Put each operator on the cue as a person with a **Department** and a **Task note**, such as *Lighting: house to half on the stinger*. They see it on their phone and in **My items**.
> * Use [tracks](https://docs.soundchecklive.io/features/gigs/run-of-show/schedule-view.md) for departments that run on their own, such as Production or Front of house.
> * Attach the cue's file, such as the lower-third spreadsheet or the video, to the row.

> [accordion] Timing that every screen follows
>
> Soundcheck doesn't have a shared show clock that a caller drives. There's no live sync between screens: each phone works out "now" from its own clock and the times it last loaded, and the web refreshes when you come back to the tab.
>
> **Instead:** treat the times as the shared truth. Shift them when the show drifts, publish on the web, and leave **Notify crew** ticked so phones get the update.
>
> If your organization is in the gig chat private preview, a message posted in the gig's chat shows on the **Follow live** card for people following, for about five minutes. That's the closest thing to a "wrap it up" flash. See [Chat](https://docs.soundchecklive.io/features/chat/overview.md).

> [accordion] Working offline
>
> The app reads offline but doesn't edit offline, and the web needs a connection. See [Offline](#offline).
>
> **Instead:** print a backup, have crew open the gig before they lose signal, and give the one person who shifts times a hotspot.

## Worked example: a corporate general session

A production company runs a 9:00 AM general session for 1,200 people: walk-in, a VOG, an opener video, the CEO keynote, a product reveal, two award presentations, and walk-out.

**1. Build it from a starter**

Start from the **General session sound** starter. It covers the audio build, presenter mics, rehearsal and two session blocks. Add rows for *Walk-in music*, *VOG: welcome and phones*, *Opener video*, *CEO keynote* and *Walk-out music*.

**2. Put the department detail on each cue**

On *Opener video*, set **Playback** to **Track**, attach the video file, and write *LX: house to half on VOG end. VX: roll opener. SQ: opener from playback*. Title it *VX 3 · Opener video* so the video operator's numbers match.

**3. Add the speaker**

On *CEO keynote*, add the CEO under **Speaker** with **20** minutes, and set **Max time** so the stage manager knows the hard stop.

**4. Protect the reveal**

Mark *Product reveal* **Surprise**. Crew still see it. When you send the client a PDF, use **No Surprises**.

**5. Hand out paper**

Export **Timeline PDF** for the caller and **PDF…** filtered **For** Sound for the A1.

**6. On the day**

The keynote runs 8 minutes long. The stage manager taps **Running late?** on the next cue, enters **8**, and keeps **This and everything after**. The producer at the laptop chooses **Publish** with **Notify crew** ticked. The VOG and award presenters see the new times on their phones. A stage timer on the confidence monitor still drives the speaker, because Soundcheck has no confidence-monitor timer.

## Worked example: a festival changeover

A festival stage runs four acts with 20-minute changeovers between them, and a hard 11:00 PM curfew.

**1. Build it from a starter**

Start from the **Festival stage** starter. It has a Main stage and a Side stage, gates, the acts, changeovers linked as segues, curfew and strike.

**2. Link changeovers to the sets**

Each changeover follows the set before it with **Segue into next**, so when a set runs long the changeover and the next set move with it. See [Linking and timing](https://docs.soundchecklive.io/features/gigs/run-of-show/linking-and-timing.md).

**3. Give each act what it needs**

Put each visiting act's tour manager on their set row with a task note. If they're on the gig in the app, they see their slot under **My items** and in **Your times**.

**4. On the day**

The second act starts 12 minutes late. On the web, the stage manager ticks the Main stage rows from that set onward and uses **Shift** → **+15** in the bulk bar. The Side stage stays where it was. (**Shift this and later** would move both stages.) The headliner now ends 15 minutes later, so the stage manager checks it against the **Curfew** key time and trims the changeover.

**5. Tell everyone**

**Publish** with **Notify crew** ticked. On the guest live page, the published times already show the shift, so leave **Schedule status** at **On time**.

> [!NOTE]
>
> Soundcheck doesn't flag that the new end time runs past curfew. Check it by eye against the curfew key time.

## Questions this page answers

* [Is there a GO button or live show-calling mode?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Does everyone's screen follow the current cue?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Who can shift times when the show runs late?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Why don't crew see the times I shifted on my phone?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Is there a countdown or a speaker timer?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Can I use cue numbers and department columns?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [What happens when the venue Wi-Fi drops?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)
* [Can guests follow the schedule without an account?](https://docs.soundchecklive.io/features/gigs/run-of-show/faq.md)

## Related

> [card] [Linking and timing](https://docs.soundchecklive.io/features/gigs/run-of-show/linking-and-timing.md)
>
> Segues, groups, Max time and shifting later.

> [card] [Publishing and collaboration](https://docs.soundchecklive.io/features/gigs/run-of-show/publishing-and-collaboration.md)
>
> Drafts, publishing and notifying crew.

> [card] [Run of Show on mobile](https://docs.soundchecklive.io/features/gigs/run-of-show/mobile.md)
>
> Every view and edit in the app.

> [card] [Live page](https://docs.soundchecklive.io/features/gigs/live-page.md)
>
> The public page for guests and vendors.

> [card] [Exporting](https://docs.soundchecklive.io/features/gigs/run-of-show/exporting.md)
>
> PDF, Timeline PDF and CSV.

> [card] [Glossary](https://docs.soundchecklive.io/features/gigs/run-of-show/glossary.md)
>
> Show-calling terms and what they map to in Soundcheck.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.