> 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/comment-feature.md).
# Comment Feature
### Overview
The **Comments Feature** allows users to add operational comments directly within the Work Area Performance Report (Work Area PR).
This feature provides additional operational context and supports communication, verification, and record tracking within a selected reporting period.
Comments are linked to the selected reporting month and can be used to document operational notes, verification updates, or compliance-related observations.
> Note: The Comments Feature is only available within the Work Area Performance Report.
***
### Purpose
The Comments Feature helps users:
* Record operational notes
* Document verification activities
* Provide additional compliance context
* Support operational communication
* Track observations and follow-up actions
* Maintain visibility of operational updates within reporting periods
***
### Common Use Cases
The Comments Feature may be used to:
* Record verification confirmations
* Document operational observations
* Add compliance-related notes
* Track follow-up activities
* Provide management updates
* Record exceptions or operational issues
Example:
* “Verified”
* “Equipment repaired”
* “Follow-up required”
* “Cleaning completed after inspection”
***
### Accessing the Comments Feature
1. Navigate to the required reporting month
2. Click the **Comments Icon** located in the report header
3. The Comments window opens
4. Type the comment, then click the "Add Comment" button to save.
---
# 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/comment-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.
