Review requirements. Keep decisions in context.

Assign reviewers, discuss open questions beside a requirement and follow each decision in the sidebar. The document stays visible throughout the review.

Real product recording · Silent, with text hints · Fictional ECG smartwatch project and demo team.

The workflow, step by step

01 · Assign reviewers

Maya Roth and Jonas Keller review the same software requirement in the demo project. The overview shows both people and their pending decisions.

02 · Discuss questions where they belong

Work-item comments stay attached to that requirement. Document comments are available for questions about structure or the document as a whole.

03 · Track each decision

Maya’s approval appears with her name and a timestamp. While Jonas has not yet decided, Medioora shows “1 of 2 approved”.

An overview of the next review action

Filter pending, accepted or rejected reviews. Requirements without assigned reviewers remain separately visible. One approval does not replace another reviewer’s outstanding decision.

Feedback stays with the requirement

A rejection can be explained in a comment. When a work item appears in several documents, feedback remains associated with the central record. The team does not have to restart the same discussion in each document.

Questions about this feature

When is a review accepted?

When all assigned reviewers have approved. A rejection takes precedence, and pending decisions remain visible.

Are document comments and requirement comments the same?

No. General feedback belongs to the document. A work-item comment belongs to that specific record.

Continue through the workflow

Bring your requirements to the demo.

Discuss how your team could organize documents, requirements and reviews in Medioora.