> 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/regular-review.md).

# Regular review (freshness)

Activate regular review so that Dastra reminds you to review your items: processing activities, stakeholders, assets, AI systems, contracts and control points.

Freshness tells you when an item was last reviewed. When you activate regular review for a type of item, you define an interval between two reviews. Each review sets a next review date, and the freshness degrades as that date approaches. This way, you make sure the information entered in Dastra is reviewed regularly.

Regular review is available for processing activities, stakeholders, assets, AI systems, contracts and the control points of risk management, depending on the modules of your subscription. The specifics of processing activities are described in [Processing freshness](https://doc.dastra.eu/en/features/ropa/freshness.md).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FKYDm62XkVlULPbZkSb47%2Ffreshness-en.png?alt=media&amp;token=ec4ad361-1746-42ce-9ac4-53963e6a1ae1" alt="Diagram of how the freshness indicator works"><figcaption><p>How the freshness indicator works</p></figcaption></figure>

## Activate regular review

Only users with the **Advanced configuration** permission can change this setting.

1. In the left menu, click **Workspace settings**, then, under **Process**, click **Regular reviews**. You can also click **Set up regular review** in the options menu of a module list: the entry shows whether regular review is already enabled for that type of item.
2. In the selector at the top of the page, choose the type of item.
3. Turn on **Enable regular reviews**.
4. In **Define the desired frequency for each review**, enter the interval in years, months or days.
5. Click **Save changes**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f289c12c38e0580ae9433c1d92472f79c9d8b62d%2Fregular-review-1.png?alt=media" alt="The Regular reviews settings with the item type selector, the activation switch and the interval"><figcaption><p>The Regular reviews settings</p></figcaption></figure>

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6e1ca0998621c822dadefbb9d00384d16ed950ce%2Fregular-review-2.png?alt=media" alt="The list of item types for which regular review is available"><figcaption><p>The available item types</p></figcaption></figure>

The interval is the same for all items of a given type. Once you save it, Dastra asks **Apply the new interval ?**:

* **Apply to all existing reviews** replaces all the next review dates already set with new dates calculated from the new interval.
* **Apply only to future reviews** keeps the existing dates, and the new interval applies from the next review.

## Deactivate regular review

In the same settings, choose the type of item, turn off **Enable regular reviews** and click **Save changes**.

## Display freshness

Freshness is only displayed for **published** items that have been reviewed at least once.

All the items concerned have a **Last review date** column, which you can add to the columns of the list. It shows the freshness state of each item.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-668f1ab89f49e08ed477dcfc09aeec58831ad56c%2Fregular-review-3.png?alt=media" alt="A list with the Last review date column"><figcaption><p>The Last review date column</p></figcaption></figure>

On the page of a processing activity or an AI system, the right-hand panel also shows the **Freshness** bar, which shrinks as the next review date approaches. Next to the state and its color, you see the **Review** link and the number of days left or overdue.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-5eb60cfad59e5171eff621b68b5fbaca26cf9fa5%2Fregular-review-4.png?alt=media" alt="The freshness panel of a processing activity page with the bar, the state and the Review link"><figcaption><p>The freshness indicator of a processing activity page</p></figcaption></figure>

### Freshness states

| State                         | Display rule                                                                                                                                                             |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Fresh** (green)             | The item has been reviewed recently and does not need immediate attention. This state is displayed until the current date is within the last 10 percent of the interval. |
| **Soon out of date** (orange) | The item needs to be checked. This state is displayed during the last 10 percent of the interval after the last review.                                                  |
| **Outdated** (red)            | The next review date has passed: the item no longer complies with the review policy.                                                                                     |

{% hint style="info" %}
**Example:** you have set an interval of 1 year. An item reviewed on 1 January 2026 is displayed as **Fresh** until the end of November 2026, then as **Soon out of date** until 1 January 2027. After that date, it is displayed as **Outdated** until it is reviewed.
{% endhint %}

## Review an item

You can review an item at any time, without waiting for its next review date. In a list, click the cell of the **Last review date** column for the item. On the page of a processing activity or an AI system, click **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-ba9789845a515e7470cad5a2cd500ce7081aa6b7%2Fregular-review-5.png?alt=media" alt="The Review window with its fields"><figcaption><p>The Review window</p></figcaption></figure>

In the **New review** tab, fill in:

* **Reviewer**: the user who carried out the review.
* **Review date**.
* **Description of the version:** what was checked or changed (optional).
* **Date before next review**: calculated from the interval defined in the settings. To set a date specific to this item, turn on **Change the date of the next review** and choose a date (at the earliest the next day).

Click **Review** to save: a new freshness cycle starts from the review date.

The **Previous reviews** tab lists the past reviews of the item. It also offers the **Delete all reviews** button, which clears the history. After confirmation, the item is considered never reviewed, its review dates are cleared and the freshness indicator disappears. This action cannot be undone.

## Follow reviews on the dashboard

The **Record of processing activities** tile of the [dashboard](https://doc.dastra.eu/en/features/dashboard.md) shows the **Requires review** indicator: the number of processing activities to review according to the defined interval, and the number of fresh ones.

## Notifications

When an item becomes outdated, its creator and the users associated with it (for example the owners of a processing activity) are notified by email: the item has not been reviewed for a long time and it is time to refresh it.


---

# 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/regular-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.
