> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-a-review-cycle.md).
# Managing a Review Cycle
Review documentation on a scheduled basis to verify its accuracy and relevance.
A **review** is a scheduled check to ensure documentation remains accurate and up to date. It helps maintain the relevance and quality of content over time.
{% hint style="warning" %}
Review is **optional** and can be configured to run periodically for specific documentation objects. The frequency and necessity depend on the nature of the content and the organization’s requirements.
{% endhint %}
***
## How to Configure & Manage a Review Cycle
In **Phase 1**, governance cycle management is not yet available in the platform. All setup and administration must be performed in EPC.
For detailed instructions on managing review cycles in EPC, refer to the following topic:
* [Review Cycle](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/7-5-review-cycle)
***
## Completing Review Tasks
While you cannot manage review cycles in the platform, you can complete review tasks assigned to you. See the guides below to get started:
---
# 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://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-a-review-cycle.md?ask=&goal=
```
`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.
.png?alt=media&token=d933eeae-cd7d-48f8-becf-d3b590bbdfe7){kind=link}
