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
- Data model and import order
The tables behind Task Queue Management
Task Queue Management ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Queue intake and priority:
Work queues, queue tasks, Organizations, People. The queue holds priority, SLA due date, status and owner; tasks describe its individual work.
Assignment rules and ownership:
Assignment rules, source mappings, work queues. The rule belongs to an organization and may have effective dates; mappings describe source-to-target fields.
Task execution:
Queue tasks, execution attempts, operation runs, operation steps. Task outcomes sit beside run status, numbered steps and external receipts.
Independent review:
Review decisions, evidence documents, People. A decision names the queue revision and reviewer; documents keep verification attribution.
Evidence and follow-up:
Evidence documents, follow up actions, work queues. Supporting files and assigned remediation point back to the queue.
Operation trace and correction:
Operation runs, operation steps, state history, queue tasks. Preserve earlier completed work when a successor revision adds a compensating task.
Every table, by feature
- Queue intake and priority4
- Assignment rules and ownership9
- Task execution7
- Independent review6
- Evidence and follow-up6
- Operation trace and correction7
- Shared and settings1
- Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - Queue tasks
Individual tasks that make up a work queue
Linked to Work queues - Organizations
Client organizations whose work queues are managed
- People
Operators, owners and reviewers who handle queue work
Linked to Organizations
- Assignment rules
Effective policies that govern how queued work is assigned
Linked to Organizations - Source mappings
Field mapping definitions for queue intake
Linked to Assignment rules - Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - People
Operators, owners and reviewers who handle queue work
Linked to Organizations - Organizations
Client organizations whose work queues are managed
- Operation runs
Workflow-maintained durable operation runs
Linked to Work queues - Operation steps
Numbered steps inside an operation run
Linked to Operation runs - Review decisions
Independent reviewer decisions on queue revisions
Linked to Work queues, People - State history
Immutable status transition history for work queues
Linked to Work queues, People
- Queue tasks
Individual tasks that make up a work queue
Linked to Work queues - Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - Operation runs
Workflow-maintained durable operation runs
Linked to Work queues - Operation steps
Numbered steps inside an operation run
Linked to Operation runs - Execution attempts
Attempts made to execute a queue operation
Linked to Work queues - Follow up actions
Remediation actions raised against a work queue
Linked to Work queues, People - State history
Immutable status transition history for work queues
Linked to Work queues, People
- Review decisions
Independent reviewer decisions on queue revisions
Linked to Work queues, People - Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - Evidence documents
Supporting evidence attached to a work queue
Linked to Work queues, People - People
Operators, owners and reviewers who handle queue work
Linked to Organizations - State history
Immutable status transition history for work queues
Linked to Work queues, People - Queue tasks
Individual tasks that make up a work queue
Linked to Work queues
- Evidence documents
Supporting evidence attached to a work queue
Linked to Work queues, People - Follow up actions
Remediation actions raised against a work queue
Linked to Work queues, People - Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - People
Operators, owners and reviewers who handle queue work
Linked to Organizations - Operation steps
Numbered steps inside an operation run
Linked to Operation runs - Review decisions
Independent reviewer decisions on queue revisions
Linked to Work queues, People
- Operation runs
Workflow-maintained durable operation runs
Linked to Work queues - Operation steps
Numbered steps inside an operation run
Linked to Operation runs - Execution attempts
Attempts made to execute a queue operation
Linked to Work queues - State history
Immutable status transition history for work queues
Linked to Work queues, People - Work queues
Operational work queues with priority, SLA and status
Linked to Organizations, People, Assignment rules - Queue tasks
Individual tasks that make up a work queue
Linked to Work queues - Review decisions
Independent reviewer decisions on queue revisions
Linked to Work queues, People
Keys and references
Use the queue’s source record ID to trace the original request and its operation key to trace guarded work. Link tasks, decisions, documents, attempts and follow-up actions to the intended queue. A run identifies its source revision; numbered steps link to their run. Keep external receipt identity on the relevant step and the provider reference on the attempt. The review decision names both the revision and reviewer.
Queue status is separate from task outcome, review decision and run status. Read each from its own record when reconciling a case. Organization and person references keep operating responsibility explicit. State history records status transitions, actor and revision without replacing the current queue record.
Migration order
- Load Organizations, then People and Users used for access.
- Load assignment rules for each organization and source mappings that refer to those rules.
- Load work queues with stable source identifiers, owners and definitions; then queue tasks under their parent queues.
- Load historical review decisions, evidence documents, execution attempts and follow up actions with their source links.
- Load operation runs and their operation steps, then state history. Reconcile source revisions, receipt references and current queue results before opening live work.
Set up Task Queue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.