> For the complete documentation index, see [llms.txt](https://brenkel-solutions-eg.gitbook.io/dp-planning-eng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brenkel-solutions-eg.gitbook.io/dp-planning-eng/planning-calibration/planning-templates/fields.md).

# Fields

A list of all header fields of the planning template.

<details>

<summary>Created at</summary>

Specifies when the planning template was created.

</details>

<details>

<summary>Created by</summary>

Specifies the name of the user who created the planning template.

</details>

<details>

<summary>Description</summary>

Specifies an explanation of the planning template.

</details>

<details>

<summary>Ending Date</summary>

Specifies the ending date for this planning template. If you are working with scheduling, this field must be filled to certify the planning template.

</details>

<details>

<summary>No.</summary>

Specifies the number of the involved entry or record, according to the specified number series.

</details>

<details>

<summary>Repetition Period</summary>

Specifies the period, that will be added at the last active day

</details>

<details>

<summary>Starting Date</summary>

Specifies the starting date for this planning template. If you are working with scheduling, this field must be filled to certify the planning template.

</details>

<details>

<summary>Status</summary>

Displays the current status of the planning template.

</details>

<details>

<summary>Template Active</summary>

Shows if the template is currently active.

</details>

<details>

<summary>Validity</summary>

Shows the current validity. More information can be found in the chapter [Scheduling](/dp-planning-eng/planning-calibration/planning-templates/scheduling.md).

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://brenkel-solutions-eg.gitbook.io/dp-planning-eng/planning-calibration/planning-templates/fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.