> 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.7-level-6-actual-well.md). # 6.7 - Level 6: Actual 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. An actual well represents a well that has already been drilled or is currently being drilled. It is constructed using recorded surveys, as opposed to a planned well, which is constructed using planning tools. Surveys are added to the actual well by right clicking on it and selecting **Insert New Survey**. Additionally, whenever a planned well is created, a planned wellbore is automatically created on the level below it. The actual well level is made up of two components - the Actual Well Properties and the Actual Wellbore. **Use the navigation tree on the left to view the page for each component, or follow the links below:** * [**Actual Well Properties**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/6.7.1-actual-well-properties.md) **-** Where the user defines configures various properties of the actual well. * [**Actual Wellbore**](/introduction/innova-engineering-manual/well-seeker-x-manual/6.0-well-seeker-x-database-structure/6.7-level-6-actual-well/6.7.2-actual-wellbore.md) **-** A representation of the full well path from surface to TD, constructed from the surveys entered at Survey Level. --- # 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.7-level-6-actual-well.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.