> 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-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well.md).

# 6.6 - Level 6: Planned Well

When the user right-clicks at Well level, they will be given the choice to insert a **planned well** or **actual well** below it. A planned well is a well trajectory that is constructed using planning tools, as opposed to an actual well, which is constructed using recorded surveys. Whenever a planned well is created, a planned wellbore is automatically created on the level below it.

The planned well level is made up of three components - the Plan Properties, Planning Tools and the Planned Wellbore. **Use the navigation tree on the left to view the page for each component, or follow the links below:**

* [**Plan Properties**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.1-plan-properties.md) **-** Where the user defines configures various properties of the plan.
* [**Planning Tools**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.2-planning-tools.md) **-** Where the user creates their plan points using Well Seeker X's suite of planning tools.
* [**Planned Wellbore**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well/6.6.3-planned-wellbore.md) **-** An interpolated listing of the plan.


---

# 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-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.6-level-6-planned-well.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.