> 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-insert-a-missing-daily-report.md).
# Well Seeker X - Insert a Missing Daily Report
## Introduction
In some cases, a single or multiple Daily Drilling Reports (DDR) may be missing from the middle or the beginning of a well, that a user wish to add in.
When this happens, simply adding a new DDR and entering the missing date may not work. Well Seeker validates that DDR report numbers and dates remain in chronological order.
For example, if **DDR #5** is missing for **05 July 2019**, but DDRs #5 already exists for a later date, the existing DDRs must first be renumbered to create a gap for the missing report.
This guide explains how to insert the missing DDR while maintaining the correct DDR numbering and dates.
## Procedure
{% stepper %}
{% step %}
### Identify the Missing DDR
Open the Daily Reports section and identify the missing date.
In this example, the missing report is 05 July 2019.
The existing DDRs after the missing date are numbered consecutively, so a new DDR cannot simply be added as DDR #10 and assigned the missing date. WSX’s validation logic will flag this as an error and prevent a date from being saved to DDR #10 that is less than DDR #9.
{% endstep %}
{% step %}
### Renumber the Existing DDRs
Starting with the last DDR, renumber each report by +1, saving at each change.
In this example change:
* Report #9 → **Report #10**
* Report #8 → **Report #9**
* Report #7 → **Report #8**
* Report #6 → **Report #7**
* Report #5 → **Report #6**
{% hint style="warning" %}
**Important:** Change backwards from the last DDR. This prevents two DDRs from temporarily having the same number.
{% endhint %}
After renumbering, the DDR sequence should look like this, with report #5 available:
{% endstep %}
{% step %}
### Add the Missing DDR
Add a new DDR.
Set the DDR **Report #** to 5. Save the new DDR.
At this stage, do not edit the date until after the DDR has been saved with the correct report number.
{% endstep %}
{% step %}
### Set the Missing Date
After saving the new DDR as Report #5, click in the  to change the DDR date to 05 July 2019.
Save the DDR again.
The DDR sequence should now be chronological.
{% endstep %}
{% step %}
### Select the Correct BHA and Phase
If the activity for the inserted day was non-drilling, then manually update the daily activity accordingly, to the row where on bottom drilling activity resumes. Then on the first row of drilling activity select the appropriate BHA and Phase. These values should match the BHA and phase that were active for the missing day's activities.
{% endstep %}
{% step %}
### Slide Sheet
If applicable, open the relevant Slide Sheet and click in the save button. This allows the Daily Activity to update the drilling data associated with the newly inserted DDR.
{% endstep %}
{% endstepper %}
### Missing Report #1
If the missing Daily Drilling Report is **Report #1**, follow the same procedure described above, but renumber **all existing reports # by +1** until Report #1 becomes available.
Once Report #1 is available, add the new DDR as **Report #1** and enter the correct date.
### Missing Multiple Daily Reports
If **more than one day** is missing, the existing reports numbers must be increased by the number of missing reports.
For example:
* Drilling started on **01 October 2025**
* Drilling ended on **10 October 2025**
* DDRs currently exist from **Report #1 to Report #7**
* DDRs for **02, 03 and 04 October** are missing
There are **3 missing reports**, so the existing report numbers need to be shifted by **+3**. In this case, change the last existing report from **report #7** to **report #10**
The reports should then be renumbered backwards to create gaps for reports #2, #3 and #4:
* Report #7 → **Report #10**
* Report #6 → **Report #9**
* Report #5 → **Report #8**
* Report #4 → **Report #7**
* Report #3 → **Report #6**
* Report #2 → **Report #5**
* Report #1 remains **Report #1**
This creates the required gaps for:
* **Report #2 – 02 October 2025**
* **Report #3 – 03 October 2025**
* **Report #4 – 04 October 2025**
The missing reports can then be added using the available numbers following the steps explained above.
{% hint style="warning" %}
**Important:** When multiple DDRs are missing, always increase the existing report numbers by the **number of missing reports**. Work backwards from the last report to avoid creating duplicate report numbers during the renumbering process.
{% endhint %}
---
# 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-insert-a-missing-daily-report.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.
