These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Content Management System
- Features
- Revisions
Revisions
Preserve the detail behind each editorial change.
OverviewRevision outcomes×
Content Management System · Revisions
New
Revision outcomes
Content revisions
| Parent | Sequence | Description | Outcome | Source reference | Source record id | |
|---|---|---|---|---|---|---|
| CI-49014 | 60 | Pending cr-499 | Pending | SR-887 | SRI-688 | |
| CI-34840 | 70 | Accepted cr-353 | Accepted | SR-799 | SRI-702 | |
| CI-88340 | 40 | Rejected cr-988 | Pending | SR-147 | SRI-245 | |
| CI-98234 | 50 | Pending cr-572 | Accepted | SR-162 | SRI-542 | |
| CI-80218 | 80 | Accepted cr-305 | Pending | SR-493 | SRI-871 |
6 of 6 records
Pending cr-499Content revisions · CR-74415
PendingParentCI-49014
Sequence60
Source referenceSR-887
Source record idSRI-688
What you can do
Preserve the detail behind each editorial change
Each revision belongs to a parent content item and carries a source record ID for the material being reviewed. Its sequence, description, source reference and document hash can tell the team which material a reviewer considered. Outcome distinguishes pending material from accepted or rejected material. Evidence documents add the dated attachment and a verifier where the editorial decision needs support.
How the work is organized
- Capture the source. Each revision keeps a source record ID and a link to its parent item.
- Compare outcomes. Sequence and outcome help the team distinguish pending, accepted and rejected material.
- Preserve evidence. A changed source gets its own revision and supporting document before another review.
What to agree during setup
Agree what counts as a new revision and which source identifier stays stable. Decide which supporting documents are required, who verifies them and how the team handles an attachment that changes after review. Keep the reviewer tied to a source revision so a later document cannot silently change the basis of an approval.
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
Consider a policy article whose source copy is amended after an initial review. The operator records a new revision rather than editing away the old outcome. They attach the updated source evidence and request another decision. The reviewer checks the revision number, source reference and evidence document before deciding. If publication already happened, an assigned follow-up can record the correction work while the earlier published record remains traceable.
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
- Revision outcomes — Compare pending, accepted and rejected source details for an item.
- 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- Content revisions
- Observation-level revision, document and line detail captured against a content item.
- Content items
- Editorial content items tracked through revision capture, independent review and publication.
- Evidence documents
- Uploaded and verified supporting documents and source evidence.
- People
- Staff, officers, reviewers and assigned team members.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
Who uses it
Permissions- Content Management System Operator
- , Content Management System Reviewer.
Set up Content Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.