> 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/jobs-list.md). # Jobs list The Jobs page lists every job in the [Tracking System](/tracking.md), grouped into tabs by job type and by where the job is in the invoicing process. Access to this page depends on your [access level](/getting-started/user-access-levels.md). To open it, click **Jobs** in the Tracking navigation bar. It opens on the **Dates confirmed** tab. Click any job to open its [job details](/eboard/calendar/job-details.md), where you can see and manage its equipment, tasks, uninvoiced charges, notes and invoices. ## When jobs appear in Tracking * [**eBoard**](/eboard.md) **jobs** appear when the first task for the job is started from eBoard (for example with **Record time**), or when the job is added to Tracking from eBoard's [Dashboard](/eboard/dashboard.md). * [**Dry hire**](/tracking/dry-hire.md) **jobs** are created directly in Tracking with **Add a dry hire**. ## Job tabs | Tab | What's in it | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Dry hire** | Equipment hire jobs, with any drop-off and pick-up tasks. These are added and edited in Tracking only. | | **Dates confirmed** | eBoard jobs with confirmed booking dates. | | **TMP only** | eBoard jobs with the TMP Only job type. | | **Misc** | Jobs with the Misc job type: work that doesn't involve TTM. | | **Ready to be invoiced** | Jobs whose eBoard [job status](/eboard/calendar/job-status.md) is "Job Completely Finished (Ready to Invoice)". Filter by **Job Type** using the drop-down in the column heading. | | **Complete** | Jobs whose final invoice has been created. | ## Job information Each row shows: | Column | What it shows | | ---------------------- | ------------------------------------------------------------------------------------ | | **Job #** | The job number. eBoard jobs keep the same number in both systems. | | **Client / Principal** | The client, and the principal if there is one. | | **Bill** | Who is billed for the job (e.g. the client). | | **P/O** | The job's purchase order number, if there is one. | | **Job Ref** | Your reference number for the job. | | **Location** | The job's location. | | **Start** / **End** | The job's start date and end date. Jobs without an end date show as **Ongoing**. | | **Status** | The job's Tracking status (not shown on the Ready to be invoiced and Complete tabs). | The Tracking statuses are: | Status | Meaning | | ------------------------ | ---------------------------------------------------------- | | **Pending** | The job is in Tracking but no tasks have been created yet. | | **Scheduled** | The first task has been created for the job. | | **Active** | Equipment has been loaded onto the job. | | **Ready to be invoiced** | The job is finished and ready for its final invoice. | For all job statuses, including returned, complete and cancelled jobs, see [Job details](/eboard/calendar/job-details.md). ## Finding a job * Click a column heading to sort the list by that column. Click it again to reverse the order. * Tick **Hide future jobs?** to hide jobs that are booked to start in the future. The Tracking System is focused on "actuals" (what has actually happened) rather than scheduled jobs that haven't started yet. * Use the page controls at the bottom (first, previous, page numbers, next, last) to move through the list. ## Add a dry hire job Click **Add a dry hire**, fill in the job and contact details, and click **Save**. See [Dry hire](/tracking/dry-hire.md) for each field and which are required. --- # 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/jobs-list.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.