Appearance
Workbench
Where to find it: Work & Decisions, then Workbench (/my-work).
The Workbench answers one question: what is OrviQ waiting for me to do?
The buckets
| Bucket | Contains |
|---|---|
| Awaiting acceptance | Ownership offers made to you that you have not accepted or declined |
| My reviews | Governed decisions awaiting your approval, across every module |
| My attestations | Policy attestations addressed to you (version-pinned; deep links to the Employee Policy Portal at /my-policies) |
| Returned to me | Work a reviewer returned for changes |
| Rejected assignments | Assignments you offered that were declined |
| My work | Work you own and are expected to progress |
| Delegated to me | Work delegated to you by an owner |
| Shared with me | Work shared for visibility |
| Completed | History of what you have finished |
The single-claim rule
An item appears in exactly one active bucket. If it qualifies for two, the more specific bucket claims it.
Without this, a returned item you also own would appear in both Returned to me and My work, and the counts across your buckets would sum to more than your actual workload.
The Completed bucket is history and is not subject to the deduplication that governs the active buckets.
Terminal items never appear in an active bucket
Once a requirement's demonstration is approved, or its work item is completed, it is removed from every active bucket for every role.
This extends to delegated child obligations: when a parent requirement closes, its active child cards disappear from the delegate's Workbench too. Completed retains the history.
Why this matters more than it sounds
A queue that retains finished work stops being a queue. Within a few months people learn that most items in it need no action, and the ones that do get missed.
Deep links
Every Workbench item carries a deep link to the exact record and action — not to a module landing page:
- Incidents & Findings: Links to
/incidents?id=INC-2026-0014or/findings?id=FND-2026-0032. - Policy Attestation: Links to the assigned version-pinned policy in the Employee Policy Portal at
/my-policies, preserving the exact published text and reading timestamp (opened_at). - Policy Operationalization: Links to the specific atomic statement's operationalization drawer at
/governance/policy/:pid/operationalization?statement=PST-2026-0045. - Change Impact Assessments: Links directly to the candidate assessment drawer at
/governance/change-impact?assessment_id=IMP-2026-0012for maker evaluation or checker approval. - Evidence Expectations: Links to the evidence upload drawer (
EXP-2026-0089) with pinned control and freshness expectations. - Gap Remediation: Links to the assigned deficiency in the Gap Workbench at
/governance/gaps?id=GAP-2026-0018.
Business references resolve directly. No technical identifier is ever exposed in a link a person sees.
Ownership offers
Ownership in OrviQ is an offer and acceptance handshake, not a silent assignment.
| Step | Where |
|---|---|
| An offer is made | By someone holding work.assign or obligations.assign |
| The offer appears | In the offeree's Awaiting acceptance bucket |
| The offeree accepts or declines | Requires ownership.accept |
| A decline returns to the offerer | In their Rejected assignments bucket |
An owner who never agreed to own something is not an owner in any sense a regulator would recognise. The acceptance step turns an administrative field into an accountability record with a timestamp.
What creates a Workbench task
A task is created only when OrviQ is genuinely waiting for a specific human or role to act.
| Creates a task | Does not create a task |
|---|---|
| A governed approval stage reaching your role | A collector run completing |
| An ownership offer to you | An indicator evaluating |
| Work returned to you by a reviewer | A freshness sweep running |
| A policy attestation campaign addressed to you | A regulatory source being checked |
| A policy operationalization mapping assignment | A scheduled recalculation |
A change-impact candidate assessment (IMP-) | Ingesting scanner telemetry |
| An evidence expectation requiring manual artifact upload | Background asset discovery |
| A gap remediation task from the Gap Workbench | Publishing an unchanged policy |
| An assigned obligation activity | Automated health check pass |
See Notifications for the event and notification distinction.
Working the Workbench
Start with Returned to me. Returned work has already consumed someone else's review time and is blocking a chain.
Then My reviews. Somebody else is waiting on you. Review queues are where governance chains stall.
Then Awaiting acceptance. Unaccepted offers mean work with no owner.
Then My work.
Do not use Shared with me as a queue. It is visibility, not obligation.
Permissions
| Action | Permission |
|---|---|
| View work items and personal buckets | work.read |
| Assign and reassign ownership, split obligations | work.assign |
| Act on assigned work | work.act |
| Participate in a review chain | work.review |
| Escalate within a chain | work.escalate |
| Accept or decline an ownership offer | ownership.accept |
| Attest to a policy | policy.attest |
Example
A Compliance Manager's Workbench on a Monday morning.
| Bucket | Count | Contents |
|---|---|---|
| Returned to me | 1 | A policy returned by Legal with comments |
| My reviews | 7 | 3 mapping approvals, 2 applicability decisions, 1 exception approval, 1 incident closure review |
| Awaiting acceptance | 0 | — |
| My attestations | 1 | Information Security Policy v3.1 |
| My work | 12 | Obligation activities she owns |
| Delegated to me | 2 | Covering for a colleague on leave |
| Shared with me | 5 | Visibility items |
The seven in My reviews are the ones blocking other people. The exception approval has been open six days and its requester cannot proceed. The incident closure review is holding an incident in in_review.
The twelve in My work are hers to schedule.
The ordering advice above is not stylistic. Items in My reviews have a second person waiting behind them; items in My work do not.
Troubleshooting
"An item is in two buckets." It should not be. Active buckets deduplicate, with the more specific bucket claiming the item.
"Completed work is still showing." Check whether it is in Completed, which is history, rather than an active bucket.
"I cannot accept an ownership offer." Requires ownership.accept.
"A review task went to the wrong person." Stage assignment is determined by the workflow template's role binding or resolver. See Workflow Templates.
"I never received a task for something I own." Check whether OrviQ is actually waiting on you. Automated events do not create tasks.