1. Content Management System
  2. Features
  3. Review
Feature · Review

Review

Make the editorial decision attributable to a person and revision.

OverviewReview inbox
Content Management System · Review

Review inbox

Approval conditions

New
SourceSource revisionReviewerDecisionEvidence reference
CI-19132570PendingER-995
CI-93833390PendingER-134
CI-19654660PendingER-874
CI-37677340PendingER-122
CI-72374790PendingER-938
6 of 6 records
ER-995Review decisions · RD-86870
Pending
SourceCI-19132
Source revision570
Example screen with sample data

What you can do

Make the editorial decision attributable to a person and revision

A review decision links a reviewer to a content item and a source revision. The decision can remain pending or be recorded as approved, returned or rejected, with a date, reason and evidence reference. This gives the operator a clear response to act on and gives the editorial lead a way to distinguish approval from an item merely moving across a board.

How the work is organized

  • Open the source. The reviewer compares the pending decision with the linked item revision and evidence.
  • Decide independently. Approval, return or rejection belongs to the reviewer of that specific revision.
  • Explain a return. The reason stays on the decision so the operator can prepare a corrected source.

What to agree during setup

Agree who can review each class of content and how independence is checked. The assigned reviewer should not be the person who prepared the same revision. Define what a return reason must explain and what evidence must accompany approval. A returned decision should lead to a fresh source revision before another approval decision is taken.

The team should rehearse its access rules with an operator, reviewer and administrator. Use an item from one organization and confirm that each person can see the record needed for their part of the work. Decide who resolves an ambiguous result and which person makes the final editorial decision.

Check the handoff on an actual case

For a public announcement, the operator submits the current revision. The reviewer checks the supporting document and category definition, then returns it with a reason when a source reference is stale. The operator corrects the material and sends the new revision. Only an approval of that revision supports moving the item toward scheduling; the earlier returned decision remains part of the audit trail.

Before calling the handoff complete, compare the item status with its linked evidence and decision. The next person should be able to find the reason for the current state without relying on a message outside the record. If work must go back, assign a named person and preserve the previous outcome. Use the item number in the handoff so the recipient opens the same record, and check that the source revision still matches the decision under discussion.

What your team sees

  • Review inbox — Find pending decisions and open the source revision before deciding.
  • Content Items Workspace — Inspect the selected item with its revision strip, decisions, state history and operation trace.

Follow the work through

Follow the editorial handoff and use the data model to check how the records connect.

What it keeps track of

Data model
Review decisions
Independent reviewer decisions recorded against an exact source revision.
Content items
Editorial content items tracked through revision capture, independent review and publication.
Content revisions
Observation-level revision, document and line detail captured against a content item.
Evidence documents
Uploaded and verified supporting documents and source evidence.
People
Staff, officers, reviewers and assigned team members.

Who uses it

Permissions
Content Management System Reviewer
, Content Management System Operator.

Set up Content Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started