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
- Follow-up
Follow-up
Assign correction work without losing earlier decisions.
OverviewPublished record×
Content Management System · Follow-up
New
Published record
Content items
| Number | Name | Publication date | Completed at | Published URL | Published item count | |
|---|---|---|---|---|---|---|
| CI-10931 | Item 605 | 17 Oct | PU-298 | 7 | ||
| CI-28979 | Item 666 | 25 Oct | PU-271 | 15 | ||
| CI-62889 | Item 173 | 27 Oct | PU-512 | 14 | ||
| CI-81360 | Item 252 | 14 Oct | PU-909 | 10 | ||
| CI-58569 | Item 375 | 27 Oct | PU-298 | 27 |
6 of 6 records
Item 605Content items · CI-10931
Publication date17 Oct
Published URLPU-298
Published item count7
What you can do
Assign correction work without losing earlier decisions
A follow-up action records the correction or outstanding request against the content item and keeps its assignee visible. It has an assignee, due date, status and resolution. State history links changes to the item and the actor, while the prior revision and review decision remain available. This is useful when content has been published and the team must explain how the next revision relates to the earlier result.
How the work is organized
- Assign the action. A correction has a source item, named assignee, due date and current state.
- Preserve the old result. Capture changed content as a successor revision with its own review decision.
- Close with evidence. Record the resolution after checking the corrected destination.
What to agree during setup
Agree which situations need an action, who owns the correction and what a completed resolution must say. A superseded publication can require a compensating action at the destination. Record that work explicitly, then seek independent review of the successor revision. Keep the previous link and result reference available for reconciliation.
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
Imagine a published item contains an outdated instruction. The operator creates an action for the responsible person, sets a due date and records the source item. A new revision captures the corrected text and supporting evidence. The reviewer decides on that revision. The assignee then records the destination correction and closes the action with a resolution. The state history shows who moved the item through its states.
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
- Open corrections — See assigned actions that remain open or in progress.
- 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- Follow up actions
- Assigned outstanding actions, corrections and outstanding requests for a case.
- 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.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- State history
- Immutable workflow-written status transition history for each case.
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.