> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/tracking/dry-hire.md).

# Dry hire

Dry hire is a term used for jobs that are for equipment hire and any related drop-off/pick-up tasks only. Dry hire jobs are created and managed in the [Tracking System](/tracking.md), not on eBoard, and appear on the **Dry hire** tab of the [Jobs list](/tracking/jobs-list.md).

Adding a dry hire job is available to a [User](/eboard/resources/user.md) with access level permissions higher than [Basic User Plus](/getting-started/user-access-levels.md#basic-user-plus).

## Add a dry hire job

1. In Tracking, click **Jobs**, then **Add a dry hire**.
2. Fill in the details below. Fields marked \* are required. **Save** stays greyed out until they're all filled in.
3. Click **Save**.

| Field                                             | Notes                                                                                                              |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Client**\*                                      | Choose one of your [clients](/eboard/resources/clients.md).                                                        |
| **Start date**\*                                  | When the hire starts.                                                                                              |
| **End date**\* / **Ongoing**                      | When the hire ends. If you don't know the end date yet, tick **Ongoing**.                                          |
| **Location**\*                                    | Where the equipment is going.                                                                                      |
| **P/O number**                                    | The client's purchase order number, if there is one.                                                               |
| **Your reference**\*                              | Your reference for the job.                                                                                        |
| **Quote reference/rate**                          | The quote or agreed rate, if there is one.                                                                         |
| **Hire items to be collected/delivered**          | Notes about the equipment being hired.                                                                             |
| **Contact**                                       | Pick one of the client's contacts to fill in the contact details. If the client has no contacts, enter them below. |
| **Contact person**\* / **Contact phone number**\* | Who to contact about the hire.                                                                                     |
| **Contact email**                                 | Optional.                                                                                                          |

Once saved, the job appears on the **Dry hire** tab with the status **Pending**. Open it to see its [details](/eboard/calendar/job-details.md), where you can add equipment and tasks, record a client sign-off and create invoices.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.roaddirect.co.nz/tracking/dry-hire.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.