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.
- E-library / Digital Repository
- Features
- Tasks and corrections
Tasks and corrections
Assign outstanding work while retaining earlier decisions and revisions.
OverviewMy production tasks×
E-library / Digital Repository · Tasks and corrections
New
My production tasks
Production tasks
| Source | Task | Due date | Status | Resolution | |
|---|---|---|---|---|---|
| CI-93513 | TSK-751 | 15 Oct | Open | RSL-190 | |
| CI-89614 | TSK-132 | 10 Oct | In progress | RSL-984 | |
| CI-96044 | TSK-628 | 12 Oct | Completed | RSL-695 | |
| CI-61390 | TSK-247 | 15 Oct | Open | RSL-177 | |
| CI-41880 | TSK-937 | 07 Oct | In progress | RSL-184 |
6 of 6 records
TSK-751Production tasks · PT-56110
OpenSourceCI-93513
Due date15 Oct
ResolutionRSL-190
What you can do
Turn a return into assigned work
A returned review decision should lead to a named action. The operator creates a production task against the content item, assigns it to a person and sets a due date. Open and in progress distinguish newly assigned work from work under way. Completed records the finished correction and its resolution; Cancelled preserves a task that no longer needs action. The task stays attached to the item so a reviewer can see why the next revision changed.
Corrections matter even after an item has been delivered. A successor revision carries the changed material through review while the earlier revision, its decisions and its execution evidence remain in the history. When a delivery is superseded, the team needs an explicit compensating task. That task states what must be addressed at the receiving end; changing the item status alone would leave an ambiguous external outcome.
How the work is organized
- Every correction has an owner. A task names who will resolve the outstanding request.
- Prior evidence stays available. The earlier review and delivery trail explain what is being corrected.
- Successors get reviewed. A new revision waits for an independent decision on the changed content.
What to agree during setup
Agree which review outcomes create tasks and who assigns them. Define reasonable due dates for missing files, incorrect references and post-delivery changes. A task resolution should say what changed and point to the updated material; a bare Completed label is not enough for a later reviewer. Decide which changes are minor edits to a draft and which require a successor revision, especially when a decision or delivery already exists.
Agree how a superseded delivery is communicated through the delivery connection. The task should identify the action and responsible person. Rehearse a returned item, a rejected requirement and an already delivered item whose evidence needs replacement. Keep the original source reference and decision reason available while the successor is prepared.
Check the handoff on an actual case
A reviewer returns an item because its attached file has the wrong document date. The operator creates an Open task for the assigned person with a due date. That person obtains the replacement. The operator records the resolution and completes the task. The operator updates the content revision and submits it again. The reviewer sees the earlier return, the completed task and the new evidence before recording a decision for the successor. If the original had already been delivered, another task records the required compensation.
What your team sees
- Open production tasks — Outstanding corrections with assignee, due date and status.
- My production tasks — Assigned work and the resolution recorded by its owner.
- Submitted revisions — Successor content awaiting an independent check.
Follow the work through
Correction and supersession traces the successor. Evidence review covers a replacement file.
What it keeps track of
Data model- Production tasks
- Assigned outstanding tasks, corrections and outstanding requests for a content item.
- Content items
- Content items submitted for a project and tracked through draft, review, approval and delivery.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Content files
- Uploaded and verified supporting documents and source evidence.
- State history
- Immutable workflow-written status transition history for each content item.
- People
- Staff, officers, reviewers and assigned team members.
Who uses it
Permissions- Digital Repository Operator
- Assigns and resolves tasks; Digital Repository Reviewer decides the successor revision; Digital Repository Administrator reviews project context.
Set up E-library / Digital Repository your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.