> 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/calendar/linked-jobs.md).

# Linked jobs

A "linked job" (a.k.a. "split job") is a separate set of job details that relates to an overall [eBoard](/eboard.md) job. Therefore, an [eBoard](/eboard.md) job can consist of multiple linked jobs.

Any linked job on the [Calendar](/eboard/calendar.md) is denoted by a "1/2", "2/2" etc. next to the job number.

When you create a linked job, you can change any of the details in that linked job without affecting other linked jobs that are related to the overall [eBoard](/eboard.md) job. Therefore, each linked job can have its own specific details and instructions relating to the overall job.

Note that Job Type, Billing Information and Job Documents all relate to the overall job and cannot be changed via a linked job.

Any [Tracking](/tracking.md) task or resource use recorded under linked jobs (e.g. time, equipment) are common to the overall [eBoard](/eboard.md) job when you view the job in [Tracking](/tracking.md). This means that all charges for the overall job can be collated into a single invoice.

If you wish to invoice a job separately, but use the same or similar information stored in another [eBoard](/eboard.md) job, then you can use the "Copy Job" function in the [eBoard](/eboard.md) job view to create an entirely new job.

### Examples of use

* The same job, but different details/instructions on different dates.
* The same job on the same day at two (or more) different times.
* A job that has different stages, where traffic management closures, labour quantities etc. change for each stage.
* A job where the site is unattended on weekends, and therefore requires no staff and reduced traffic management closures.


---

# 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/calendar/linked-jobs.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.