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.
- Task Queue Management
- Features
- Independent review
Independent review
Make a separate decision on each queue revision with a recorded reviewer.
OverviewPending independent review×
Task Queue Management · Independent review
New
Pending independent review
Approval conditions
| Source | Source revision | Decision | Reviewer | Evidence reference | Reason | |
|---|---|---|---|---|---|---|
| WQ-95723 | 720 | Pending | ER-438 | Pending rd-497 | ||
| WQ-89117 | 950 | Pending | ER-138 | Pending rd-208 | ||
| WQ-14585 | 30 | Pending | ER-609 | Pending rd-196 | ||
| WQ-72633 | 510 | Pending | ER-381 | Pending rd-131 | ||
| WQ-59723 | 590 | Pending | ER-711 | Pending rd-390 |
6 of 6 records
ER-438Review decisions · RD-77934
PendingSourceWQ-95723
Source revision720
ReasonPending rd-497
What you can do
Keep the decision with the revision
The assignment workflow raises a pending review decision for a queue revision. The Independent Reviewer examines the work, its assignment and supporting evidence, then records an approval, return or rejection with a reason and decision date. A later correction creates a successor revision and calls for validation and independent approval again. The earlier decision remains part of the history of the earlier revision.
This separation lets an operator prepare and execute work while another person decides whether a revision is acceptable. The decision record names the reviewer and its source queue. The Queue Manager can read both the current queue status and the decision on the revision, which answer different questions. A queue marked Assigned tells the team who owns the work; an Approved decision shows who authorized that revision.
How the work is organized
Independent Reviewer decides; Queue Manager responds to a return.
- Revision-specific inbox. Review the source queue and revision identified by the pending decision.
- Evidence and reason. Record a reason and supporting reference for the decision.
- New decision after correction. Treat a successor revision as new work for the reviewer.
What to agree during setup
Choose reviewers who can judge the assignment and outcome without being the same person who prepared them. Agree which evidence is required for a normal decision and for a returned queue. Establish how quickly a pending decision should be reviewed when the queue’s SLA due date is near. The due date belongs to the queue; a pending approval should not make urgent work invisible.
Rehearse an approved queue, a returned queue and a rejected queue. Inspect the decision record rather than relying on the queue status alone. For a correction, confirm that both the original and successor revision have separate decisions and that the reviewer can see why the new revision was created.
Check the handoff on an actual case
A queue has been assigned to an operator under the current policy. Pending independent review shows its revision and named reviewer. The reviewer opens the queue, checks the organization, owner, assignment reason and attached evidence, then approves the decision with a dated reason. Reviewed queue revisions shows the result. If the reviewer returns it, the Queue Manager examines the reason and corrects the work before asking for another decision.
Later, a receipt discrepancy requires a successor revision. The prior approval remains attached to the original revision. The correction workflow adds a compensating task and raises another pending decision after validation. The reviewer assesses that revision on its own record. This prevents a previous approval from being silently reused for changed work.
What your team sees
- Pending independent review — Queue revisions awaiting a named reviewer decision.
- Reviewed queue revisions — Dated approvals, returns and rejections with reasons.
- Unverified evidence — Supporting documents still awaiting verification.
Follow the work through
Independent review follows the initial decision. Operation correction follows the new review on a successor revision.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on queue revisions
- Work queues
- Operational work queues with priority, SLA and status
- Evidence documents
- Supporting evidence attached to a work queue
- People
- Operators, owners and reviewers who handle queue work
- State history
- Immutable status transition history for work queues
- Queue tasks
- Individual tasks that make up a work queue
Who uses it
Permissions- Independent Reviewer
- , Queue Manager, Admin.
- The reviewer records the decision; the manager resolves returned work; Admin maintains reviewer identities.
Set up Task Queue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.