---
title: Reviews
description: >-
  A review assesses a new process version: give feedback, comment, rate and
  recommend or reject the release.
search:
  tags:
    - konzept
    - review
    - pruefen
    - feedback
sidebar:
  hidden: true
---
Processes are not set in stone. It is worth discussing them in order to understand them better and make them better.

Process representations must keep pace with how the actual workflows in the company develop. Process Participants are more likely to accept a process and implement it with commitment if it fits the conditions they actually work under. The **Process Owners** therefore depend on input from all **Process Participants** in order to implement process goals as effectively as possible.

Questions, improvement suggestions and review assessments show where a process can be improved. On top of this come external influences, for example legal regulations and requirements or business decisions.

If only the descriptions or names of process elements need to be corrected, a revision can also be released without a review. The version number must be increased, because formal changes must be logged as well.

When a new process version is created, the aim is to take all of these influences into account. Designers can use the integrated **Modeler** to design new process versions.

In a release process, new process versions (revisions) are assessed in a review and then either rejected or published with a specific validity period.

A review can also be created for a version that has already been published — to check whether it needs to be changed or is affected by other changes.

How a review is created and completed is described under [Releasing and publishing processes](/en/processes/release-process).

You have the following options for developing processes further and improving workflows in this way:

- You can ask and answer questions for every valid process on the **Q&A** tab. This also allows you to make an improvement suggestion independently of a review.
- Details of new process versions are discussed in **Reviews**. You can be assigned as a **Review Participant**.

  In the review, the overall process and individual process elements can be commented on. A comment can be marked with a label. The **BPM Manager** defines which labels are available under **Settings** > **Manage Process Space** > **Customize** > **Review labels**.

  Finally, every **Review Participant** is asked to submit a final assessment of the process version (revision). The release can be recommended, recommended subject to conditions, or not recommended.
- As a **Designer**, you can create processes directly as a BPMN diagram with the integrated **Modeler** and add them to the Process Space as a process version (revision).

In the main menu, **Reviews** opens the page of the same name. It shows the reviews you are or were assigned to as **Review Owner** or **Review Participant**: as tiles on the **Overview** tab, and with their status on the **Ratings and progress** tab.

![Reviews page on the Overview tab: the filters on the left, on the right a tile per review with the remaining time](/blume-assets/content/content/en/media/reviews-overview.png)

## The pages of this area [#the-pages-of-this-area]

- [Using my reviews](/en/reviews/using-my-reviews-page) — the overview of your reviews with filters, sorting and progress.
- [Opening a review](/en/reviews/open-a-review) — how to get to an individual review and what awaits you there.
- [Rating a process version](/en/reviews/rating-a-process-version) — submitting the final assessment.
- [Giving feedback on a process](/en/reviews/reviewing-a-process-version) — commenting on the overall process and individual elements.

**Creating** and **completing** a review is part of the release process and is described under [Releasing and publishing processes](/en/processes/release-process).

See also: [Asking and answering questions about the process](/en/processes/understand-processes/questions-and-answers), [Creating process drafts](/en/processes/create-process-drafts)