Review

A review is a structured check of the visible contents of a base — the entries in its blocks. The goal is traceability before release, audit, or publication.

Goal

deliberately check content before binding steps
record a review status and comments per entry
see open and critical items in one place
keep an immutable review report after completion

What is reviewed

Reviews cover the business entry content of blocks (what users see and maintain in the data).

Out of scope:

schema modeling itself (blocks and columns)
comparison against a Baseline
push or team diffs

Review work mode

Besides Model and Maintain data, there is a Review work mode (see Work modes). It is not toggled with the Model / Maintain data switch; you start and stop it from the Review page in the navigation (next to History).

While a review is active:

schema and entry content are write-protected in the block view through the working UI
in entry detail you set a status and an optional comment per entry

You can pause a review: you can work again in Model or Maintain data mode; you can resume later.

Participants and reviewers

Many participants can take part. Some are marked as reviewers. At least one reviewer is required. At start you also capture title, reason, and optionally planned dates and notes.

Review report

Completing a review produces a report with metadata, summary, status overview, and checked or open items. The report is stored in the organization context and is immutable afterwards. Previous reviews for the same base remain listed on the Review page — a history of review documents, not a base version bump.

Distinction

	Review	Baseline	Push
Purpose	content check with status and comment	mark a binding full state	share working state with the team
Read-only	in the block view while review is active	marked state immutable	no
Result	review report	baseline mark	updated main
Plan	Cloud (Enterprise where agreed)	depends on environment	Cloud