> For the complete documentation index, see [llms.txt](https://ontime.gitbook.io/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ontime.gitbook.io/v2/features/import-events-from-excel.md).

# Import events from Excel

![Template sheet](/files/EQZIleIDfeTanZ0HGd2v)

You can import an Excel file containing your rundown. See [the template from the above screenshot ](https://docs.google.com/spreadsheets/d/1TYZhAELRFQa_2QBO8Q651fMHdem6AXmFLjEDoksJd8Y/edit?usp=sharing)

Ontime allows importing rundown and project data from a spreadsheet.\
For a successful import, there are a few conventions to follow

1. Ontime reads a single worksheet
2. The name of the worksheet and columns is given in the app on import
3. Ontime creates an event for every row on the table
4. All fields in an event (row) are optional. Missing data will be defaulted if needed
5. Time fields not provided will be calculated at import. The times can be either an Excel time field or a short text entry as described in the docs eg: `00:10:15` or `10h15`
6. Any text under a field named **Is Public** will make the event public. We show this as a toggle for simplicity
7. See below the expected data types of the rundown data

### Project data

{% hint style="info" %}
The project data can be defined in the sheet. These fields must have their data on the cell to its right (see screenshot or template)
{% endhint %}

| Field Name          | Data type |
| ------------------- | --------- |
| Project name        | Text      |
| Project description | Text      |
| Public URL          | Text      |
| Backstage URL       | Text      |
| Public Info         | Text      |
| Backstage Info      | Text      |

### Rundown

{% hint style="info" %}
Field names are not case-sensitive. Meaning: both **Event Title** and **event title** would be recognised on import
{% endhint %}

| Event Field | Data Type                                             | Notes                              |
| ----------- | ----------------------------------------------------- | ---------------------------------- |
| Cue         | Text                                                  |                                    |
| Time start  | Excel time \| Text                                    |                                    |
| Time End    | Excel time \| Text                                    |                                    |
| Duration    | Excel time \| Text                                    |                                    |
| Title       | Text                                                  |                                    |
| Subtitle    | Text                                                  |                                    |
| Presenter   | Text                                                  |                                    |
| Note        | Text                                                  |                                    |
| Timer Type  | 'count-down' \| 'count-up' \| 'time-to-end \| 'clock' |                                    |
| End Action  | 'none' \| 'stop' \| 'load-next' \| 'play-next'        |                                    |
| Colour      | Text                                                  |                                    |
| Public      | Text                                                  | any text means the event is public |
| Skip        | Text                                                  | any text means the event is public |

### User Fields

{% hint style="info" %}
There are ten custom fields available.

These can have any name, the names are given to Ontime on import
{% endhint %}

|       |      |
| ----- | ---- |
| user0 | Text |
| user1 | Text |
| user2 | Text |
| user3 | Text |
| user4 | Text |
| user5 | Text |
| user6 | Text |
| user7 | Text |
| user8 | Text |
| user9 | Text |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ontime.gitbook.io/v2/features/import-events-from-excel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.