> 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/mobile-app/job-status.md).
# Job status
Tap **Job Status** on the [job screen](/mobile-app/job-screen.md) to update the job's status from site. The screen shows the date, client and location, and three sections:
* **Job Status**: **Job Completely Finished**, **Job Ongoing - Dates Confirmed with Client**, **Dry Job Becoming Dry Hire (handover completed)** or **Job Ongoing - Dates TBC**
* **Cancellation Status**: **Job Cancelled While You Were At Base** or **Job Cancelled After Left Base**
* **Callout Status**: **Was this a Call Out Job?** or **Late Booking**
In each section, choose the option that applies. The name of the person who set the current status is shown next to it. Once an option is chosen, its follow-up appears underneath (for example, **Job Ongoing - Dates TBC** asks you to confirm the status with the client and choose one of the other options). Tick it when the action has been done. **Reset Job Status**, **Reset Cancellation Status** and **Reset Callout Status** clear a section.
Add any **Notes**, then tap **Save**.
{% columns %}
{% column %}
Job Status
{% endcolumn %}
{% column %}
Choosing an option shows its follow-up tick box
{% endcolumn %}
{% endcolumns %}
For what each status means and how the office uses it, see [Job status](/eboard/calendar/job-status.md) in the eBoard guide.
---
# 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/mobile-app/job-status.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.
