> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/performance-report/work-area-performance-report/closure-feature.md).
# Closure Feature
### Overview
The **Closure Feature** allows users to close a reporting period within the Work Area Performance Report (Work Area PR).
Once a reporting month is closed, the system locks the reporting period to help preserve operational records and prevent further updates or modifications.
The Closure Feature is managed through the Comments window within the Work Area PR.
> Note: The Closure Feature is only available within the Work Area Performance Report.
### How to Close A Record
1. Open the **Work Area Performance Report**
2. Select the required block
3. Toggle on the "Close this Operation" to close the block
4. The operation will be in grey color with a small number, indicating that they're closed.
### How to Close The Entire Day
1. Open the **Work Area Performance Report**
2. Select the required date
3. Toggle on the "Close this Day" to close the entire day's operations
4. The entire operation of the day will be in grey with a small number, indicating that they're closed.
### How to Close The Entire Month
1. Open the **Work Area Performance Report**
2. Click the **Comments Icon** located in the report header
3. Toggle on the "Close this Month" to close the entire month's operations
4. The entire operation of the month will be in grey with a small number, indicating that they're closed.
---
# 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.didge.io/home/performance-report/work-area-performance-report/closure-feature.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.
