Skip to main content

Triage the review queue

This page shows you how to read the Quality Review Queue and decide what each open task needs.

Who this is for

Quality Admin and Corporate Admin. Other administrators do not see this surface.

The queue is at Quality > Review queue. Open tasks land here automatically as people author content and as source documents change.

Screenshot pendingQuality Review Queue with the filter chips and a list of open tasks

The three task types

Every task in the queue is one of three types. The filter chips at the top switch between them, and each chip shows a count.

Filter chipTask typeWhat it meansWhat you do
Pending versionsversion_approvalAn author submitted a new training version. It is pending review and not live.Compare and approve or reject. See Approve content.
Outdated sourcessource_outdatedA controlled document a training relies on changed, so the training may be out of date.Open the task and record a resolution.
Recert decisionsrecert_decisionA re-certification decision is waiting for a human call.Open the task and record a resolution.

The All chip shows every open task. Use Refresh to reload the list after you act on a task elsewhere.

You only see tasks for roles you hold

The queue is scoped by role. A Quality Admin sees the tasks addressed to the Quality Admin role. A Corporate Admin sees everything. This scoping is enforced in the database, so a task you cannot act on never appears for you.

Read a task card

Each card shows:

  • The training name and version (for example v3.2).
  • A type badge (Version approval, Source updated, or Recertification decision).
  • An AI-generated badge when the pending version was drafted with AI.
  • The triggered by document, for an outdated-source task.
  • The created timestamp.
Screenshot pendinga single version_approval task card with the Compare, Approve and Reject buttons

Act on a pending version

For a Pending versions task, the card offers:

  • Open training to view the material.
  • Compare to see a side-by-side delta between the pending version and the current active version.
  • Approve and Reject.

The full approval flow, including the change rationale and the source requirement, is on its own page: Approve content.

You cannot approve your own version

If you authored the pending version, the Approve and Reject buttons are disabled and the card tells you another Quality Admin must review it. This is segregation of duties, and the server enforces it even if the buttons were somehow bypassed. See Segregation of duties.

Resolve a source-outdated or recertification task

For an Outdated sources or Recert decisions task, click Resolve. You choose a resolution and write a short reason (at least 5 characters):

ResolutionWhen to choose itEffect
Cosmetic change, no impactThe document change does not affect the training subject.The version is marked reviewed and the outdated flag clears. Campaigns can use it again.
Re-approved after reviewYou compared the content against the new document version and the training is still valid.The outdated flag clears.
Re-certify usersThe change is significant enough to warrant re-certification.The flag stays. Your next step is to create a new training version and a campaign targeted at users who already completed it.
Every resolution is recorded

Your decision and your reason are written to the audit log permanently. There is no way to undo a recorded resolution; choose the right one and document why. See Read the audit log.