> 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/add-a-callout-job.md).

# Add a callout job

Use this when you're called out to a job that isn't on the Calendar yet. Open the main menu and tap **Add Callout Job**.

{% columns %}
{% column %}

<figure><img src="https://4286947481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F98XhbhrRRLsZR32fcYPt%2Fuploads%2Fgit-blob-a3f6fe669a62f22fa1e60109cc6143670b55c460%2Fmobile-add-callout-job.png?alt=media" alt="Add Callout Job" width="300"><figcaption><p>Add Callout Job</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="https://4286947481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F98XhbhrRRLsZR32fcYPt%2Fuploads%2Fgit-blob-f5ae6bd80cd8afde29d5bfcf6f1329c4171c9b8d%2Fmobile-add-callout-job-lower.png?alt=media" alt="Further down: staff, vehicles, photos and TMPs" width="300"><figcaption><p>Further down: staff, vehicles, photos and TMPs</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

1. Choose the **Client**.
2. Enter the **Location**: start typing a road or address and pick it from the list.
3. Enter a **Description of Work Activity**.
4. Under **Traffic TTM Closures** and **Pedestrian and Cyclist TTM Closures**, pick the closures from the list, or type a new one.
5. Enter the **Number of Staff Required Onsite** (it starts at 1), or tick **TBC**.
6. Add the **Allocated Staff** and **Allocated Vehicles**. You're added to the staff automatically.
7. Tap **Add photos** to add any photos.
8. Under **TMPs**, search the TMP library and add the TMP you're using, or tap **Upload TMP** to attach a PDF.
9. Tap **Save**.

The job is added to the Calendar for the office to see.


---

# 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/add-a-callout-job.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.
