---
title: "Workbench"
description: "Your role-aware landing page — a live view of what needs your attention across every engagement."
version: "en"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.kliper.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Workbench

The **Workbench** is where you land when you sign in — a single, role-aware home that pulls together what needs your attention across all your engagements. Everything on it is computed from your real data; there are no placeholder numbers.

> **Note**
>
> What you see is scoped to **your workspace and your role**. Managers and admins see org-wide activity; assessors and reviewers see the work assigned to or shared with them.

## The stat strip

A row of headline numbers across the top, each drawn from live data:

| Stat | What it shows |
|---|---|
| **Engagement** | The active engagement in context |
| **Progress** | Overall completion across its assessments |
| **Reqs drafted** | Requirements drafted today / this week |
| **Open gaps** | Count of open gaps |
| **Awaiting client** | Open evidence requests waiting on the client |
| **Cortex queue** | Items waiting in the Cortex review queue |
| **QA review** | Requirements awaiting your review — reviewers only |
| **Days to deadline** | Days remaining against the LOE dates |

> **Note**
>
> The **QA review** tile appears only for reviewers (admin / manager / QA) and **escalates by state** — quiet when the queue is clear, blue when items are waiting, amber within two weeks of the QA milestone, and red once it has passed.

## Priority queue

The main panel lists **what to work on next** — requirements needing testing-procedure review, evidence to chase, and gaps to resolve — ranked by priority. Columns are **sortable**, and filtering to **All assessments** or a single one is a dropdown at the top.

The footer line is **tab-aware** — it shows the shape of whichever tab you're on, right where the work is:

| Tab | Footer shows |
|---|---|
| **All** | Estimated time-to-clear and average per item |
| **TP review** | Flags · drafts · time-to-clear |
| **Evidence** | Awaiting · changes requested · to verify · overdue |
| **Gaps** | Critical · high · medium · low |

## Coverage & evidence

The coverage card has a **Coverage \| Evidence** lens toggle, plus a grid / by-requirement view switch:

- **Coverage** — a heatmap of the defined-requirement set colored by finding (in place, partial, gap, N/A). The by-requirement view groups cells under each requirement with a per-group in-place %.
- **Evidence** — the same heatmap, but each cell is an **evidence request** colored by status (pending client, submitted, changes requested, accepted). It answers *which requirement areas are blocked on client evidence*.

Switch **assessments** with the dropdown in the card header, and click any cell for a popover that deep-links to the requirement. **Open gaps** are broken down by **real risk severity**, so the highest-risk gaps surface first.

## Active engagement & Next up

- **Active engagement** — the engagement you're currently working, with its framework, progress, and a **QA milestone** bar.
- **Drafting pace** — requirements drafted in the last 7 days with an up / down trend versus the prior week, and an honest projection: at this pace you land *N weeks* from finishing, compared against the QA milestone (on track / past).
- **Next up** — your upcoming calendar events, pulled from [Tasks & Calendar](/operations/tasks-and-calendar).

## Recent activity & team presence

- **Recent activity** — a live feed of what's happening across the org (created records, evidence, approvals). Filter it by **All / You / Cortex**. **Show all** reveals the rest inside the card with internal scrolling; a separate **expand** icon grows the card to full length.
- **Team presence** — who's **online right now** and where they're working, updated live across the organization.

## Gap registry

Gaps are tracked in a persistent **registry** with stable IDs, so a gap keeps its identity across sessions. Each gap can carry an **owner** and an **ETA**, making the Open-gaps view an actual worklist rather than a snapshot.

## Get started checklist

New organizations see a **Get started** card that tracks real setup progress — add your first client, create an LOE and assessment, connect your tools, and invite your team. It reflects actual completion and disappears once you're set up.

> **Tip**
>
> The Workbench is the fastest way back into flow: the Priority queue and Recent activity both deep-link straight to the requirement, evidence request, or assessment they reference.

Source: https://docs.kliper.dev/operations/workbench/index.mdx