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
- Evidence and follow-up
Evidence and follow-up
Verify supporting documents and assign remediation for queue exceptions.
OverviewUnverified evidence×
Task Queue Management · Evidence and follow-up
New
Unverified evidence
Evidence documents
| Source | Title | Document date | Verified | Verified by | External reference | |
|---|---|---|---|---|---|---|
| WQ-71212 | No ed-149 | 27 Oct | No | ER-459 | ||
| WQ-60974 | No ed-984 | 05 Oct | No | ER-431 | ||
| WQ-24559 | No ed-148 | 10 Oct | No | ER-858 | ||
| WQ-67440 | No ed-387 | 19 Oct | No | ER-593 | ||
| WQ-48147 | No ed-571 | 11 Oct | No | ER-339 |
6 of 6 records
No ed-149Evidence documents · ED-15205
NoSourceWQ-71212
Document date27 Oct
External referenceER-459
What you can do
Keep proof beside the queue
Evidence documents attach to a work queue and retain a title, document date, external reference and attachment. A verifying person is recorded with the verification state. That gives the Independent Reviewer and Queue Manager a clear place to inspect supporting material when deciding on a revision or investigating a receipt. Verification answers whether the document was checked; it does not itself approve the queue.
Follow-up actions capture work that still needs attention. Each action points to a source queue, names an assignee and can carry a due date, status, completion date and resolution. The task completion workflow raises receipt follow-up when required. The Queue Manager can therefore see a verified operational result alongside an open action to investigate an associated exception.
How the work is organized
Independent Reviewer checks evidence; Follow-up Owner resolves assigned actions.
- Source link. Keep every document and action attached to the correct queue.
- Named verification. Record the person who checked supporting evidence.
- Resolution trail. Close follow-up with a resolution and completion date after the issue is addressed.
What to agree during setup
Agree which supporting documents are required for assignment, execution and correction decisions. Decide whether an external reference identifies a document in another system and who is responsible for supplying the attachment. Set a review practice for items marked unverified. A document can be useful context before it has been verified, but the reviewer should know that state when making a decision.
Choose the Follow-up Owner for receipt exceptions and establish when a follow-up is due. Test the difference between a task outcome, an operation run status and a follow-up action status. Completing an action should document the resolution; it should not rewrite the underlying execution trace.
Check the handoff on an actual case
An operator completes a task, but the external receipt needs investigation. The workflow raises an action against the queue and assigns a Follow-up Owner. That person finds it in Open follow-up work by assignee, checks the operation step and external reference, and attaches supporting evidence to the queue. The Independent Reviewer verifies the document and records their identity. Once the receipt issue is resolved, the owner records the resolution and completion date on the action.
If the receipt instead shows that the effect was wrong, the Queue Manager follows the correction process. The supporting document remains linked to the same queue, while the successor revision and compensating task explain the new result. Do not clear the investigation merely to remove it from the open list.
What your team sees
- Open follow-up work — Actions still open or in progress by due date and assignee.
- Unverified evidence — Documents awaiting a recorded verification.
Follow the work through
Task completion and receipts shows where receipt follow-up starts. Operation correction shows how documented evidence supports a changed result.
What it keeps track of
Data model- Evidence documents
- Supporting evidence attached to a work queue
- Follow up actions
- Remediation actions raised against a work queue
- Work queues
- Operational work queues with priority, SLA and status
- People
- Operators, owners and reviewers who handle queue work
- Operation steps
- Numbered steps inside an operation run
- Review decisions
- Independent reviewer decisions on queue revisions
Who uses it
Permissions- Follow-up Owner
- , Independent Reviewer, Queue Manager, Operations Analyst.
- The owner resolves the action, the reviewer checks evidence, the manager decides whether correction is needed, and the analyst reads the operation trace.
Set up Task Queue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.