> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/contracts/review.md).

# Regular review of documents

Regular review sets a review date on your documents and lowers their freshness as that date approaches. It helps you reread your contracts and policies before they go out of date. The principle, the statuses and the display rules are described in [Regular review (freshness)](https://doc.dastra.eu/en/features/regular-review.md). This page shows where to find it in the **Contracts & policies** module.

## Turn on regular review

In the record, click the arrow on the right of the **Create a document** button, then **Set up regular review**. The entry shows whether review is **Enabled** or **Disabled** for documents, and opens the regular review settings of the workspace. It is available to users with the advanced configuration permission.

The frequency you define there applies to all documents.

## Review a document

Once review is on, each document record shows the freshness indicator in the shortcuts menu (see [Structure of a document](https://doc.dastra.eu/en/features/contracts/structure.md)). It is active only for published documents. As long as the document is not published, the indicator stays greyed out.

Click the indicator to open the **Review** window. In the **New review** tab, choose the **Reviewer**, the **Review date** and, if needed, a description. Dastra calculates the **Date before next review** from the workspace frequency. You can replace it with a specific date using **Change the date of the next review**. The **Previous reviews** tab keeps the history.

When a document becomes outdated, its owner receives an email.

## Record a review when a document becomes active

When regular review is on, moving a document to a workflow stage whose internal status is **Active** opens the **Switch workflow stage** window with a **Review** switch, turned on by default. Keep it on and click **Validate**: Dastra changes the stage and records a review at the same time.

* The reviewer is you, and the **Review date** is today.
* The **Date before next review** is calculated from the workspace frequency.
* The text you write in the version description is kept as the description of the review.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a256bc85c0dbf7482b6f5a0ed28aaf9174e4ea06%2Fv3-improvements-contracts-1.png?alt=media" alt="Switch workflow stage window with the Review switch"><figcaption><p>The workflow stage window with the Review switch</p></figcaption></figure>

The window appears when you change the stage from the document page and from the **Workflow** column of the list. The review updates the dates of the last and the next review of the document and appears in the **Previous reviews** tab. Turn the switch off if the stage change should not count as a review.

If the stage changes but the review cannot be saved, a message asks you to record it again from the **Review** window.


---

# 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://doc.dastra.eu/en/features/contracts/review.md?ask=<question>&goal=<user_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.
