> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-multi-leg-lateral-guide.md).

# Well Seeker X: Multi Leg Lateral Guide

Guides the user through setting up a multi-leg lateral well in Well Seeker X

## 1.0 – Introduction

Well Seeker X supports the management of wells containing multiple lateral legs.

A Multi-Leg Lateral is configured by designating an actual well as the motherbore and defining the number of additional lateral legs associated with the well. Each lateral is managed using its Unique Well Identifier (UWI), allowing Well Seeker X to maintain the correct relationship between the motherbore and its individual lateral legs.

Once configured, users at the rig site can create new lateral legs using the Create Sidetrack workflow. Well Seeker X automatically identifies the motherbore UWI, determines the appropriate UWI for the selected lateral leg, and creates the corresponding actual well.

Importantly, the newly created lateral is then automatically pushed from the rig's local database to the organization's remote server database.

Under the standard workflow, a new plan or lateral created at the rig exists only within the local rig database. To make this available to office-based users, the rig would need to manually export the well and send it to the office, where it would then need to be imported into the server database.

The Multi-Leg Lateral workflow removes this manual exchange. As soon as the new lateral is created at the rig, it is synchronized back to the server, providing office and other connected users with visibility of the new well without requiring any manual export, email, or import process.

This provides a consistent well structure based around the UWI while ensuring that new lateral legs created during drilling are automatically available across the organization.

## 2.0 – Configuring a Multi-Leg Lateral

### 2.1 – Designating the Motherbore

An actual well can be designated as the motherbore for a Multi-Leg Lateral from the **Actual Wellbore Properties**.

This option is only available when connected to the organization's **remote server database**.

If the well is accessed from a local database, the Multi-Leg Lateral options will be greyed out. So this is something that is setup in the office prior to the job starting.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/QmKSmEO8R9JlSja5jn2b/media/image3.png)

To configure the well:

1. When connected to the server, open the **Actual Wellbore Properties**.
2. Select the option to designate the actual well as a **Multi-Leg Lateral**.
3. Enter the number of additional lateral legs.
4. Ensure that the UWI is included in the motherbore well name using the exact required format, details of which are described in the next section.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/vEdO7llvKSGwLimAz4eS/media/image4.png)

#### 2.1.1 Unique Well Identifier (UWI)

The UWI should be appended to the end of the motherbore well name.

**Example:** 101/13-01-050-25W3/00

The /00 event code identifies the motherbore as Leg 1.

{% hint style="warning" %}
**Important: The UWI must be entered in the exact required format. Additional spaces or characters can prevent Well Seeker X from identifying the UWI when a new lateral is created.**
{% endhint %}

* **Correct:** 101/13-01-050-25W3/00

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/3EihqP8c2N1zjPOEwHn2/media/image5.png)

* **Incorrect:** 101/13-01-050-25W3 /00

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/OTjEDF6bPSjMG62Y6jb4/media/image6.png)

The incorrect example contains an additional space before /00. Although the difference may appear minor, this will prevent Well Seeker X from correctly identifying the UWI.

#### 2.1.2 – Number of Lateral Legs

The number entered in the **#Legs** field in the Actual Wellbore Properties represents the number of additional lateral legs and should **NOT** include the motherbore. The motherbore is always considered **Leg 1**, and it’s UWI should always end in “**/00**”.

For example, if the well has a motherbore and three additional lateral legs, enter **#Legs = 3.** The resulting well structure will be:

| **Leg**    | **Leg Number** | **UWI ending** |
| ---------- | -------------- | -------------- |
| Motherbore | Leg 1          | …/00           |
| Lateral    | Leg 2          | …/01           |
| Lateral    | Leg 3          | …/02           |
| Lateral    | Leg 4          | …/03           |

The number entered in #Legs determines the available options in the Leg dropdown when creating a new lateral.

## 3.0 – Creating a Lateral Leg

Once the actual well has been configured as a Multi-Leg Lateral, a new lateral leg can be created at the rig site using the Create Sidetrack workflow.

Right-click the Actual Well and select Create Sidetrack.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/RPWmJNwdqtxYyNlnA9XW/media/image7.png) ![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/vtSshX9klctAlH0pCqEL/media/image8.png)

As the motherbore is always **Leg 1**, this will not be available for selection in the dropdown. If two additional legs have been configured, the available options will be, Leg 2 and Leg 3.\
Select the leg that is being created and click **Create**.

{% hint style="warning" %}
**Note: The UWI does not need to be entered again when creating each lateral. Well Seeker X automatically extracts and validates the UWI from the parent well or a matching well plan.**
{% endhint %}

If no valid UWI can be identified from the parent well or a matching well plan an error message will be displayed.

![](https://content.gitbook.com/content/-McEwHTOM_v4MexTVGSe/blobs/eprMtLKiGGeYGZFBZUfw/media/image9.png)

New lateral legs created locally with valid UWIs will be automatically pushed to and created on your organization’s remote server database.


---

# 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://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/well-seeker-x-guides/well-seeker-x-multi-leg-lateral-guide.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.