> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/manual/management/management-review/adding-a-management-review.md).
# Adding a Management Review
Add Management Review form
**Title**
A name given for the individual management reviews.
**Description**
A description within a management review refers to a narrative or summary of the current status and performance of the organisations ISMS. It provides an overview of the measures taken to protect the confidentiality, integrity, and availability of information assets, as well as the effectiveness of these measures.
**Attendees**
Attendees are the people who were present and participated in the review. This could be anyone that was present, such as staff, management, clients, or suppliers.
**Location**
The physical or virtual space where the review is conducted.
**Scheduled Date**
The specific day on which the review was or will be conducted.
---
# 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://manual.harpe.io/start/manual/management/management-review/adding-a-management-review.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.
