> ## 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.

# Importing a schedule

> Bring a schedule you already have into Run of Show: paste text, upload a PDF, Word, Excel or CSV file, paste key times from a call sheet, paste a set list, or review a timeline a client sent from the portal.

Most schedules start life somewhere else: a planner's email, a venue's PDF, a production spreadsheet, a call sheet. You don't have to retype them. Run of Show reads the text, shows you what it found, and lets you choose which rows to keep before anything is added.

![Paste into Run of show dialog with a file upload and a box to paste a schedule](https://mintcdn.com/soundchecklive/DQsOfwUk5leizXB5/images/run-of-show/paste-data-light.png?fit=max\&auto=format\&n=DQsOfwUk5leizXB5\&q=85\&s=72b1215eadbcb1e6a32697890a47d90e)

This page covers every way in:

| You have | Use | Where |
| - | - | - |
| A schedule as text, or a PDF, Word, Excel, CSV or text file | **Paste data** | Above the **List** grid |
| A call sheet with load in, doors, curfew and so on | **Paste key times** | Next to **Paste data** |
| A set list | **Paste data** in the **Setlist** view | The **Setlist** view |
| A timeline a client sent from the client portal | **Review** on the notice | The **List** view, or the **Run of Show** card on **Overview** |

> [!NOTE]
>
> Imports only add rows. They never delete or overwrite what's already in the run of show, and everything you add autosaves like any other edit, with **Undo** available.

## Pasting or uploading a schedule

**1. Open the dialog**

Open the gig's **Run of Show** tab, switch to the **List** view, and choose **Paste data** above the grid. The **Paste into Run of show** dialog opens.

**2. Add the text**

Paste the schedule into the box. Or, under **Upload a timeline**, choose a file. Soundcheck reads the file and puts its text in the box, so you can check and fix it before going on.

**3. Map it**

Choose **Map into Run of show**. An AI model reads the text and turns it into rows with times and names. Nothing is saved yet.

**4. Pick the rows**

Tick the rows you want to keep. Untick anything you don't want, such as a header line or a row from someone else's part of the day.

**5. Fill**

Choose **Fill**, which counts what you ticked, such as **Fill 12 values**. Only ticked rows are added. They autosave like any other edit.

> [!NOTE]
>
> The AI only proposes rows. It never writes to the run of show on its own: you tick what to keep, and nothing is added until you choose **Fill**.

### Files you can upload

| File type | Notes |
| - | - |
| PDF | The text in the PDF is read. |
| Word (.docx) | The document's text is read. |
| Excel (.xlsx) | Only the **first sheet** is read. Move the schedule to the first sheet before uploading. |
| CSV (.csv) or TSV (.tsv) | Read as text rows. |
| Text (.txt) | Read as is. |

Files can be up to **8 MB**. Older Word (.doc) and Excel (.xls) files and images aren't accepted: save them as .docx, .xlsx or PDF, or copy the text and paste it. A scanned PDF with no text in it has nothing to read.

> [!TIP]
>
> Because the file's text lands in the box before mapping, you can clean it up first: delete a cover page, a contact block, or a second schedule that isn't yours. Cleaner text maps to cleaner rows.

### What to check in the review

* **Times.** Make sure each row's time came across the way the source meant it, especially around midnight.
* **Duplicates.** If part of the schedule is already in the run of show, untick those rows so you don't add them twice.
* **Row names.** Each ticked row becomes an item with that name. You can rename items later in the grid.

### A schedule dated for another day

A row whose date falls outside the gig's dates is left out, and the dialog names it after **Fill**. This happens when you paste a schedule from another gig or from a copy of this one that moved to a new date.

When none of the dated rows fall on the gig, and moving them all by the same number of days fits every row onto it, nothing is added yet. The dialog says **Nothing added yet**, shows the schedule's date next to the gig's date, and offers **Move them to** the gig's date, such as **Move them to Jun 14**. Choose it to add the rows on the gig's dates, with their times kept.

If only some rows are outside the gig, the rows on the gig are added and the stray rows are listed as left out. They're never moved.

After **Fill**, the rows are ordinary items. Move them into sections, link them, add people, and set key times as you would for anything you typed. See [Building and editing](https://docs.soundchecklive.io/features/gigs/run-of-show/building.md).

## Pasting key times

A call sheet usually lists the handful of times everyone needs: crew call, load in, soundcheck, doors, show, curfew, load out. **Paste key times** sets those on the gig in one step.

**1. Open it**

In the **List** view, choose **Paste key times** next to **Paste data**.

**2. Paste the call sheet**

Paste the lines with times and names.

**3. Review**

Each name on your organization's key time list (**Settings → Labels → Gigs → Key times**) becomes that key time on the gig. Any other name is marked **New**.

**4. Apply**

Confirm. Matched names set the key time. Rows marked **New** are added as plain items, so nothing you ticked is lost.

Two rules to know:

* **A key time already set on that day is not overwritten.** The row is added as a plain item instead, and the dialog says so.
* **New names don't create key times.** To make a new name a key time for every gig, add it to your key time list first, or open the new item and pick a key time for it. See [Key times](https://docs.soundchecklive.io/features/gigs/run-of-show/key-times.md).

> [!TIP]
>
> If a paste marks a name you expected to match as **New**, check its spelling against your key time list. "Doors open" and "Doors" are different names unless your list has both.

### Organizations still on the older timeline

If your organization hasn't [switched to Run of Show](https://docs.soundchecklive.io/features/gigs/run-of-show/timeline-switch.md), **Paste data** sits on the gig's **Key times** card instead. There, a new name is marked **New key time**:

* An owner or admin who saves it adds it to the organization's key times and sets it on the gig.
* For anyone else, the dialog lists it as not applied.

A key time that is already set is never overwritten by a paste.

## Pasting a set list

In the **Setlist** view, **Paste data** adds a pasted set list as sets, in the order you pasted them.

* A title that matches a song in your library is added as that song.
* A title that isn't in your library is marked **New**. Saving adds the song to the library and to the set.

This is the fastest way to turn a band's emailed set list into sets you can time and print. See [Setlists](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists.md).

## Timelines from clients

Clients can send you their timeline from the [client portal](https://docs.soundchecklive.io/features/client-portal/overview.md), with **Share your timeline** on the **Schedule** card of the event's **Overview**. When they do:

1. Soundcheck emails you a link to the gig's run of show.
2. The **List** view shows a notice naming who sent it.
3. The **Run of Show** card on the gig's **Overview** tab shows the same notice, listing each file, who sent it, and when.

From either notice:

* **Review** opens the **Paste into Run of show** dialog with the client's text filled in. From the **Overview** card, **Review** first opens the **Run of Show** tab. Map, tick and **Fill** as above.
* **Dismiss** sets the timeline aside without adding anything. From the **Overview** card you can dismiss without leaving **Overview**. When several timelines are waiting, each file has its own **Dismiss**.

When you review a client's timeline, the dialog has no **Upload a timeline** field, so you can't replace the client's text with another file by mistake.

Both notices show only to people who can edit the gig or its run of show. The client sees whether each file they sent is still waiting, was added, or wasn't used.

> [!TIP]
>
> Review client timelines before the final walkthrough. A client's timeline often carries moments only they know about, such as a surprise toast or a late vendor arrival. If a moment shouldn't reach the client again, mark the item **Surprise** after you add it.

## Other ways in

* **Bulk imports.** A [Universal Event Format](https://docs.soundchecklive.io/features/imports/universal-event-format.md) import can carry run of show templates and each gig's key times.
* **Flex.** Flex quotes set load in, show and load out. See [Times that fill in on their own](https://docs.soundchecklive.io/features/gigs/run-of-show/key-times/synced-times.md).
* **AI assistants.** An MCP client can write a run of show. See [AI assistants and MCP](https://docs.soundchecklive.io/features/gigs/run-of-show.md#ai-assistants-and-mcp).
* **Other rundown tools.** Soundcheck doesn't import from or export to Shoflo, Rundown Studio, Stagetimer or show-control software today. Export a PDF or spreadsheet from that tool and use **Paste data**. See [Switching from another tool](https://docs.soundchecklive.io/features/gigs/run-of-show/switching-tools.md).

## Related

> [card] [Building and editing](https://docs.soundchecklive.io/features/gigs/run-of-show/building.md)
>
> Work with the rows you imported.

> [card] [Key times](https://docs.soundchecklive.io/features/gigs/run-of-show/key-times.md)
>
> How key times and rows relate.

> [card] [Setlists](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists.md)
>
> Sets, saved setlists and the Setlist view.

> [card] [Troubleshooting](https://docs.soundchecklive.io/features/gigs/run-of-show/troubleshooting.md)
>
> When an import doesn't look right.


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