# Tracked Fields (/docs/bookings/tracked-fields)



A **tracked field** is something you want your team to write down when a booking starts, when it ends, or both. You define the fields yourself: an odometer reading for a rental car, engine hours for a jet ski, the fuel level at handover, whether the equipment came back clean, the number of fish caught on a charter.

Tracked fields are for record keeping. A value never changes a price, a balance, availability or a payment, and customers do not see them.

Nothing changes until you add a field. With no fields set up, bookings have no Records tab and equipment pages have no Records section.

What a field is [#what-a-field-is]

You set up each field once per location, under **Location Settings > Tracked Fields** (click your name in the top right, then **Location Settings**).

| Setting          | What it does                                                                                                                |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Name**         | What staff see beside the box, for example "Odometer".                                                                      |
| **Type**         | **Number**, **Text**, or **Yes / No**.                                                                                      |
| **Unit**         | Number fields only. Shown after the value: mi, km, %, h. Optional.                                                          |
| **Recorded on**  | **The booking** (one value for the booking) or **Each equipment instance** (one value for each unit the booking takes).     |
| **Recorded**     | At the start, at the end, or at the start and the end.                                                                      |
| **Required**     | Marks the value as required on the booking until it is filled in. It is a reminder: it does not block a save or a check-in. |
| **Only goes up** | Number fields only. Warns staff when a value is out of line. See [Only goes up](#only-goes-up).                             |
| **Applies to**   | All activities, or the activities you choose.                                                                               |

The **Type** and **Recorded on** are chosen when you add the field and cannot be changed afterwards. To change them, add a new field.

Setting fields up needs the **Company Settings** permission. Everyone at the location can see the list.

On the booking, or on the equipment [#on-the-booking-or-on-the-equipment]

* **The booking** suits a value that belongs to the trip: fish caught, a staff note, whether a deposit envelope was handed over.
* **Each equipment instance** suits a value that belongs to the physical unit: an odometer, engine hours, a fuel level. The reading is stored against the unit, so the unit keeps one history across every booking it goes on, whichever activity booked it. This needs [equipment instances](/docs/equipment/instances).

A start value and an end value are one field recorded twice, not two fields. Set **Recorded** to **At the start and the end** and the booking shows the difference between the two (the distance driven, the hours run).

Choosing activities [#choosing-activities]

**All activities** asks for the field on every booking at the location, including activities you add later. **Chosen activities** asks for it only on the activities you tick. The list has a search box and **Select all**, and after a search the button selects just the matches, so a fleet with one activity per car does not mean ticking a hundred boxes.

Cloning an activity carries over the fields that were chosen for it.

Order, archive and delete [#order-archive-and-delete]

* Use the arrows to set the order the fields appear in on a booking.
* Deleting a field that has no records removes it.
* A field that has records is **archived** instead. Its records are kept and stay visible on the bookings and units that hold them, and it is no longer asked on bookings. Open **Archived** at the bottom of the list to restore it.

Recording on a booking [#recording-on-a-booking]

A booking has a **Records** tab when a field applies to its activity, or when a value was already recorded on it.

1. Open the booking and choose the **Records** tab.
2. Fill in the boxes. Fields recorded on the booking are listed under **This booking**. Fields recorded on equipment are listed once for each unit, under the unit's name.
3. Select **Save**.

Only the boxes you changed are saved. Values you typed and have not saved yet are kept while you work on the booking: you can open another tab, take a payment or start the timer and they are still in their boxes when you come back. They are kept in your browser only until you save or select **Discard**, so save before you close or refresh the dashboard.

Type a number the way your company writes numbers. A thousands separator is optional, so `12,120.5` and `12120.5` are the same reading. When you type one with separators, the box shows how it was read before you save. If a box holds something that is not a number, it is marked and nothing is saved until you fix it.

For a unit, each field shows the **last reading**: the unit's most recent value from before this booking. A number recorded at the start and the end shows the **difference** as soon as both are filled in.

To correct a value, change it and save. To remove a value, empty its box and save. For a Yes / No field, select the chosen answer again to take it back, then save. Under each saved value you can see who saved it last, and when.

Saving values needs **Bookings: Edit**. Team members with **Bookings: View** can read them.

Which unit [#which-unit]

A field recorded on equipment is asked for the units the booking actually took.

* **One of a kind.** When you own one of an item and it has one instance in service (a specific car), the booking asks for that unit straight away. Saving its first value also assigns the unit to the booking.
* **Several units.** When you own several (six jet skis), choose the unit first: select **Choose a unit** on the Records tab and pick it by name or serial number. This is the same assignment the [Check In](/docs/bookings/check-in) tab makes with **Assign a unit**, so a unit chosen in either place shows in both. A booking that took two units asks until two are chosen.
* **Wrong unit.** Select **Remove unit** to take a unit off the booking again. This is offered while nothing is recorded on it. Clear its values first if there are any.
* **No instances.** Equipment with no instances set up records nothing, and the tab says so. Add instances under the equipment's **Settings > Instances** to record on it.

A unit that has records on a booking cannot be unassigned from that booking, and an instance that has records cannot be deleted. Mark it [out of service](/how-to/equipment/mark-out-of-service) instead and its history is kept.

<Callout type="info">
  Putting a unit on a booking from the Records tab, by choosing it or by saving its first value, is the same as assigning it on the Check In tab. If the activity's check-in flow has an **Equipment assigned** requirement on a stage that advances automatically, the booking can move to its next stage when the unit goes on.
</Callout>

Only goes up [#only-goes-up]

Turn **Only goes up** on for a number that never falls, such as an odometer or engine hours. Staff then get a notice after saving when:

* an end value is below its start value, or a start value is above its end value
* a value is below the unit's reading before it
* a value is above the unit's reading after it (when you fill in an older booking late)

The notice names every value that is out of line. It never stops a save: the value is stored, and the notice stays on the screen so the typo can be fixed.

What stays visible [#what-stays-visible]

Nothing that was recorded is hidden later:

* Values recorded under a field that was archived, or that is no longer chosen for the activity, stay on the booking. They can be corrected or cleared, and no new ones are asked.
* If equipment is swapped off a booking after values were recorded on its unit, the unit stays listed with those values, marked **No longer on this booking**.

A unit's history [#a-units-history]

Open **Equipment**, the equipment item, **Settings > Instances**, and the instance. Its **Records** section shows:

* **The current value** of each field, with the date it applies to.
* **The history**, newest first: each value, the booking it was taken on (a link to that booking) and whether it was the start or the end reading, and who saved it. The newest 50 are listed; select **Show more** for older ones.

Opening an instance's page needs **Resources: View**.

The history is in the order the readings apply, not the order they were typed in. A value sits at the start or the end of its booking, so filling in last week's return reading today puts it in last week. The one exception is a return reading entered while the booking is still running (an early return): it sits at the time it was entered. If a booking is rescheduled, its readings move with it.

Times are shown in your own time zone.

An entry outside a booking [#an-entry-outside-a-booking]

For a reading taken with no booking, such as after a service or a drive between bookings:

1. On the instance's **Records** section select **Add Entry**.
2. Choose the field if there is more than one, enter the value, and select **Add Entry**.

The entry is recorded as of now. Entries made outside a booking can be corrected or deleted from the history with the pencil and bin buttons. A value taken on a booking is corrected on that booking's **Records** tab.

Adding and correcting entries here needs **Resources: Edit**.

Examples [#examples]

| Business               | Field               | Type                     | Recorded on             | Recorded      |
| ---------------------- | ------------------- | ------------------------ | ----------------------- | ------------- |
| Car rental             | Odometer            | Number, mi, only goes up | Each equipment instance | Start and end |
| Car rental             | Fuel level          | Number, %                | Each equipment instance | Start and end |
| Any rental             | Condition           | Text                     | Each equipment instance | Start and end |
| Jet ski or boat rental | Engine hours        | Number, h, only goes up  | Each equipment instance | Start and end |
| Fishing charter        | Fish caught         | Number                   | The booking             | End           |
| Any rental             | Returned clean      | Yes / No                 | Each equipment instance | End           |
| Anyone                 | Staff handover note | Text                     | The booking             | Start         |

Good to know [#good-to-know]

* Tracked fields are separate from the [custom fields](/docs/activities/creating-activities#custom-fields) customers answer at checkout. Tracked fields are filled in by staff and are never shown to customers.
* Photos and documents do not go in a tracked field. Record damage on an [incident](/docs/incidents) linked to the unit.
* An entry made outside a booking is recorded at the moment you add it. It cannot be dated in the past.
* A number can be negative. An iPhone's number keypad has no minus key; enter a negative value on a computer or an Android phone.

Related How-To Guides [#related-how-to-guides]

* [Track Mileage on Rental Vehicles](/how-to/equipment/track-mileage)
* [Add an Equipment Instance](/how-to/equipment/add-instance)
* [Mark an Equipment Instance Out of Service](/how-to/equipment/mark-out-of-service)
