> 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/legacy-documentation/manuals/well-seeker-pro-1/13.0-reporting/13.14-daily-activity-editor.md).
# 13.14 – Daily Activity Editor
Only available at Actual Well level. The Daily Activity Editor allows the user to view all the daily activities for an actual well in one chronological table. The user can make edits to the activities in the table the same way they would in the Daily Reporting window.
Figure 319: Daily Activity Editor
The Daily Activity Editor can be used to check for mistakes in the daily activities. Cells will be highlighted in red if the end time/depth do not match with the start time/depth of row below. Cells in the BHA and Phase columns will also be highlighted in red if the BHA/phase is different to the ones above and below. This is usually an indicator that the user has filled in the wrong BHA/phase by mistake.
Once the user is happy with their edits, they can save them by clicking on the **Apply** button.
---
# 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/legacy-documentation/manuals/well-seeker-pro-1/13.0-reporting/13.14-daily-activity-editor.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.
