> 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/eboard/dashboard/dry-hire-misc.md). # Dry hire and Misc The **Dry Hire** and **Misc** tabs of the [Dashboard](/eboard/dashboard.md) list jobs of those types. * **Dry Hire**: equipment hire jobs. These are created in the Tracking System with **Add a dry hire** (see [Dry hire](/tracking/dry-hire.md)). * **Misc**: jobs with the **Misc** job type, for work that doesn't involve TTM. When you book a Misc job, the form leaves out the TTM-specific fields (see [Book a job](/eboard/book-a-job.md)). Tick **Include complete jobs** to show finished jobs as well. The columns are **Created / Booked**, **Start Date**, **Job No.**, **Your Ref**, **PO No.**, **Client**, **Principal** (Misc only) and **Location**. ## Job actions The job's **⋮** menu has **View Job**, **Email** and **View In Tracking**. On the **Dry Hire** tab it also has **Mark Job as Ready To Invoice**, which puts the job on the **Ready to be invoiced** tab of the Tracking [Jobs list](/tracking/jobs-list.md). --- # 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/eboard/dashboard/dry-hire-misc.md?ask=&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.