Reviews and approvals
Review and approveThe video is narrated in German; you can switch on subtitles in the player. Playing the video connects to YouTube (Google). More in the privacy policy · Watch on YouTube
A review collects the decision of several people on a set of artifacts: every invited person approves each artifact, rejects it with a reason or comments on it. The results are traceable per artifact and per person.

Creating a review
Under Reviews → New review (role EDIT and above) you define:
- Scope:
- a module: all artifacts of the module except headings,
- a baseline: exactly the recorded state, which no longer changes,
- a selection of individual artifacts.
- Participants with their task as reviewer or approver. Any group member with the role COMMENT and above can take part, including customers or suppliers with comment rights only.
- Notes for the reviewers and optionally a due date.
Participants are notified in the app (and by e-mail if configured).
Deciding
Each participant decides per artifact:
- Approve,
- Reject with a short reason (required),
- Comment without deciding.
An artifact counts as approved when all participants have approved it, as rejected as soon as there is a rejection, otherwise as open.
Changes during the review: each decision refers to the version of the artifact the participant saw. If the artifact is changed afterwards, the decision is marked as outdated and must be renewed. This way nobody can accidentally approve a text they have never seen. This does not apply to a baseline review, because the state is fixed.
Closing and rework
The person who created the review, or a group admin, closes it with Close review. Optionally, ETRM sets the attribute Status: approved artifacts to “Approved”, rejected ones to “Rejected”. All participants receive a summary.
If artifacts were rejected, rework them and start another round with the same participants and the current state with New round after rework. The rounds are linked to each other.
Approving baselines
A binding state, for example a specification agreed with the customer, is recorded as a baseline and approved there. The approval contains name, function (e.g. “quality assurance” or “project management”), time and a remark. Several people can approve the same state; each person only once. Any member with the role COMMENT and above may approve.
Recommendation: First check a state in a baseline review and approve the baseline afterwards. Then it is documented that exactly this immutable state was reviewed and approved.