> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daysync.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule & Travel Items

> Go deep on the day schedule: schedule items, custom fields, drag-and-drop editing, drive items with custom vehicle profiles, and flight lookup by flight number.

[https://www.tella.tv/video/vid\_cmuv1xtcp000406p016dz7uew/embed?b=0\&title=1\&a=1\&loop=0\&t=0\&muted=0\&wt=1\&o=1](https://www.tella.tv/video/vid_cmuv1xtcp000406p016dz7uew/embed?b=0\&title=1\&a=1\&loop=0\&t=0\&muted=0\&wt=1\&o=1)

The schedule is where every tour day comes together. This guide goes item by item: **schedule items**, **drives** and **flights**. It covers how to create each one and the finer details that make them useful on the road.

> **[Schedule items](#schedule-items)**
>
> Events, notes, tags, attachments and custom fields.

> **[Drives](#drive-items)**
>
> Routes, drive times and vehicle profiles.

> **[Flights](#flights)**
>
> Look up flights by number, including multi-leg.

***

## Schedule items

A schedule item is the basic building block: something that needs to happen, and when.

### What an item can hold

| Field | Notes |
| - | - |
| **Title** | What's happening, e.g. *Load in to venue* or *Dinner: all team*. |
| **Notes** | More detail on what needs to be done. |
| **Start time** | Required. Inherits the day's time zone automatically. |
| **End time** | Optional. Leave it off for open-ended items like *Load in*, or set **All day**. |
| **Location** | Optional. Search for a place or pick the day's venue, and view it on a map (on mobile too). |
| **Tags** | Label who or what it's for, e.g. *Band* or *Support*. |
| **Attachments** | Upload files from your computer, such as a venue tech pack or a menu screenshot. |
| **Custom fields** | Add as many as you like (see below). |
| **Visibility** | Everyone on the tour, or restricted to specific people or groups. |
| **Status** | Confirmed or unconfirmed. |

### Create one

**1. Pick the day**

Open the day in the sidebar, e.g. your pre-production day.

**2. New item**

Click **New item**, or press <kbd>N</kbd>.

**3. Fill it in**

Title (*Dinner: all team*), start and end time (*5pm–6pm*), and a location (search *Shortcross Pizza, Brunswick*, then click the map to check it's the right spot).

**4. Add the extras**

Notes, tags, attachments and custom fields as needed. Set visibility if it's not for everyone.

**5. Confirm it**

Mark it **confirmed** once it's locked in.

### Custom fields

Custom fields let you add any information to an item, with no limit on how many.

> **Loading dock location**
>
> Add a **Loading dock** field and paste a dropped-pin link from Google Maps. The crew gets the exact pin on the item.

> **Wi-Fi details**
>
> *Wi-Fi: Yes*, plus the network name and password, so nobody has to ask.

> **Vehicle details**
>
> Plate numbers, driver contacts or pick-up bays on drive items.

### Move and resize on the fly

* **Drag** an item to a new time on the calendar.
* **Drag its edge** to make it longer or shorter.
* Hold <kbd>⌘</kbd> and press <kbd>↑</kbd> / <kbd>↓</kbd> to nudge an item earlier or later.

Changes save live as you make them.

### Notifying people

Turn on **Notify members** when you save, and everyone who can see the item gets a notification. If the item is visible to everyone on the tour, everyone is notified.

> [!TIP]
>
> Don't notify on every small tweak, or people start tuning notifications out. For a change that matters, post a [bulletin](https://docs.daysync.com/how-daysync-works#bulletin) pointing to the item, or mention it in tour chat.

***

## Drive items

Drive items tell everyone how long it takes to get from A to B, and route it properly for your vehicle.

### Create a drive

**1. New drive**

Press <kbd>N</kbd> and use <kbd>⌘</kbd> + <kbd>←</kbd> / <kbd>→</kbd> to switch to **Drive**.

**2. Departure and destination**

Pick where you're leaving from. The day's venues and stays are listed for quick selection. Then choose where you're going.

**3. Let it calculate**

Daysync works out the drive time, e.g. *17 minutes*.

**4. Set the departure time**

Choose when you leave, then **auto calculate** to set the arrival time (e.g. *4:00 → 4:17pm*). Leave a buffer before whatever's next.

### Custom vehicle profiles

The default vehicle is a **car**. If you're driving a van, splitter, truck or bus, add a vehicle profile so routes only use roads your vehicle can actually take.

**1. Add a vehicle**

On the drive item, add a new vehicle, e.g. *Splitter*, and set its type (e.g. **Van**).

**2. Enter its specs**

**Height** (e.g. 2.8 m), **width**, **length** (e.g. 7 m), **weight** (e.g. 4 t) and **average speed** (e.g. 95 km/h).

**3. Set route preferences**

Choose whether to avoid **tolls**, **highways** or **tunnels**.

**4. Select and recalculate**

Select the vehicle on the drive and **auto calculate** again. The route and time update for that vehicle.

> [!NOTE]
>
> Avoiding tolls and highways can make a big difference to the route and drive time. Allow them again and Daysync may find a faster route, e.g. via a tollway. Your saved vehicles are available on every drive.

Drive items also support **travel notes**, **reminders** (e.g. *5 minutes before departure*), **custom fields** (plate numbers, driver details) and **confirmed / unconfirmed** status.

***

## Flights

Flights work much like drives, with one big advantage: you can **look them up by flight number**.

**1. New flight**

Press <kbd>N</kbd>, then hold <kbd>⌘</kbd> and press <kbd>→</kbd> until you reach **Flight**.

**2. Search the flight number**

Enter it, e.g. **QF1**. Daysync pulls in the scheduled flight: departure time, airports and route.

**3. Pick the legs**

For multi-leg flights, add the **whole journey** or **just one leg** (see below).

**4. Check the day**

Make sure the flight is on the right day. Long-haul departures can fall on the following day.

**5. Save and confirm**

Airline and flight number are filled in for you. Edit anything you need, assign the flight to the people on it, save, and mark it **confirmed**.

### Multi-leg flights

Some flight numbers cover more than one leg. **QF1**, for example, flies Sydney → Singapore Changi → London Heathrow under the same number.

* Only going as far as Singapore? Add **one leg**.
* Going all the way? Add the **entire journey**, and Daysync shows every stop.

***

> **[AI Import & templates](https://docs.daysync.com/guides/ai-import-and-templates.md)**
>
> Build days from documents, then reuse them.

> **[Managing personnel & permissions](https://docs.daysync.com/guides/managing-tour-personnel.md)**
>
> Aim items at exactly the right people.


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