> 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/ropa/freshness.md).

# Processing freshness

Learn how to activate and use the processing freshness option

The freshness of a processing activity shows when it was last reviewed. Once regular reviews are enabled, each review sets a next review date, and the freshness decreases as that date approaches. It is a simple way to make sure the information in your record of processing activities is reviewed regularly and stays up to date.

{% hint style="info" %}
Regular reviews are also available for other items, such as stakeholders, assets, contracts or AI systems. The common mechanism is described in [Regular review (freshness)](https://doc.dastra.eu/en/features/regular-review.md); this page details how it works for processing activities.
{% endhint %}

## Activate the processing freshness option

Processing freshness is optional and deactivated by default. It is set up for the whole workspace, in the workspace settings, under **Regular reviews**.

To open this setting from your record, click the arrow next to the **Create data processing** button, then **Set up regular review**. The menu item also shows whether the option is currently **Enabled** or **Disabled**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-190ac8444a082a3ee8fd91f7244e7fc777b797d0%2Fropa-freshness-1.png?alt=media" alt="Set up regular review in the Create data processing menu"><figcaption><p>The Set up regular review entry of the Create data processing menu</p></figcaption></figure>

In the **Regular reviews** settings:

1. Select **Processing activity** in the item type selector.
2. Turn on **Enable regular reviews**.
3. In **Define the desired frequency for each review**, enter the interval between two reviews, in years, months or days.
4. Click **Save changes**.

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

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6e7cb962621cff00269f397b9570e386fece9e4c%2Fropa-freshness-2.png?alt=media" alt="Regular reviews settings for processing activities"><figcaption><p>The Regular reviews settings for processing activities</p></figcaption></figure>

The interval applies to all the processing activities of the workspace. The next review date of a processing activity is the date of its last review plus this interval, unless a specific date was chosen during the review (see [Review a processing activity](#review-a-processing-activity)).

When you save a new interval, Dastra asks whether it should apply to the reviews already recorded:

* **Apply to all existing reviews**: the review dates already scheduled are recalculated with the new interval, which overwrites them;
* **Apply only to future reviews**: the review dates already scheduled are kept, and the new interval is used from the next review onwards.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7b06c440a1e9531c35feac7ca572f72ce3819e50%2Fropa-freshness-3.png?alt=media" alt="Apply the new interval confirmation"><figcaption><p>Choose whether the new interval applies to existing reviews</p></figcaption></figure>

{% hint style="info" %}
**Example:** you set an interval of 1 year. A processing activity reviewed on 15 January 2026 has a next review date of 15 January 2027. It is displayed **Fresh** for most of the year, **Soon out of date** during the last 10% of the interval (a little over a month), then **Outdated** once its next review date has passed, until it is reviewed again.
{% endhint %}

## Disable the processing freshness option

To deactivate the option, go back to the **Regular reviews** settings, select **Processing activity**, turn off **Enable regular reviews** and click **Save changes**.

The freshness indicators are then no longer displayed. Each processing activity keeps its review history and its last review date, which are used again if you reactivate the option later.

## Freshness indicators

Freshness is only displayed for **published** processing activities that have been **reviewed at least once**. A processing activity can be in one of the following states:

| State                     | Meaning                                                                                             |
| ------------------------- | --------------------------------------------------------------------------------------------------- |
| Fresh (green)             | The processing activity was reviewed recently and does not need immediate attention.                |
| Soon out of date (orange) | The last 10% of the interval between two reviews has started: the review should be planned.         |
| Outdated (red)            | The next review date has passed: the processing activity no longer complies with the review policy. |
| Pending review            | The processing activity is published but has never been reviewed.                                   |

A processing activity still in draft is shown as **not published** in the list, and as **Awaiting publication** on its record.

### On the page of a processing activity

On a wide screen, the freshness indicator is at the top of the right-hand panel of the processing activity page. It shows the **Freshness** bar, which shrinks as the next review date approaches, the state and its colour, a **Review** link and the number of days remaining or late.

On a smaller screen, the right-hand panel is hidden: the state (for example **Fresh**) is displayed in the header of the record, next to the **Overall progression**, **Quality** and **Sensitivity** indicators. Click it to open the **Review** window.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e7f80dd26868f09dc795628df4988d90d3e6f861%2Fropa-freshness-5.png?alt=media" alt="Freshness indicator in the header of a processing activity"><figcaption><p>On a smaller screen, the freshness indicator is displayed in the header of the record</p></figcaption></figure>

### In the list of your record

The **Last review date** column shows the freshness state of each processing activity and the date of its last review. Hover over the state to see the number of days remaining or late. This column is added to your list view when you activate the option; you can also add it to the displayed columns at any time.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FErpgSIHrtKlITaGz5qoa%2Fimage.png?alt=media&amp;token=1c02937a-aacb-48d9-9fba-5a484e334a1e" alt="Last review date column in the record list"><figcaption><p>The Last review date column</p></figcaption></figure>

You can also display the **Future review date** column, which shows the next review date recorded for each processing activity, and filter your record with the **Freshness** filter (available under **Filters**), using the values **Fresh**, **Pending** (published but never reviewed) or **Outdated**.

## Review a processing activity

You can review a processing activity at any time, without waiting for its next review date. Reviewing requires write access to the record of processing activities. Open the **Review** window:

* from the processing activity page: click the freshness indicator, the **Review** link of the right-hand panel, or **Review** in the menu next to the **Save changes** button;
* from the list: click the cell of the **Last review date** column.

To review several processing activities at once, select them in the list, then choose **Review** in **Select a batch action**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-50f8098ff766fb7ade68cdf24ffdacb938ac5331%2Fropa-freshness-7.png?alt=media" alt="The Review window"><figcaption><p>The Review window</p></figcaption></figure>

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

* **Reviewer** (required): the user who carried out the review, yourself by default;
* **Review date** (required): today by default;
* **Description of the version** (optional): a short description of what was checked or changed;
* **Date before next review**: calculated from the review date and the interval set for the workspace. To apply a specific date to this processing activity, turn on **Change the date of the next review** and select a new date (at the earliest, the next day).

Click **Review** to save. A new freshness cycle starts from the review date until the next review date.

When the window is opened for a single processing activity, the **Previous reviews** tab lists its past reviews. This tab also offers the **Delete all reviews** button, which clears the review history: once confirmed, the last and next review dates are cleared and the freshness indicator is no longer displayed. This action cannot be undone.

## Important information about how freshness works

Saving a processing activity does not count as a review: the date of the last review is independent of the date on which the record was last updated. To (re)start the freshness cycle of a processing activity, you must review it.

Moving a processing activity to the final step of its workflow can also record a review: the step change window then shows a **Review** switch, enabled by default.


---

# 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/ropa/freshness.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.
