1. OKR Tracking System
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Use the review queue and recorded decisions to inspect work requiring attention.

OverviewMy Tasks
OKR Tracking System · Review and evidence

My Tasks

Tasks

New
Task keyTitleWork packagePriorityDue dateStatus
TK-663Backlog tsk-748WP-4794Low20 OctBacklog
TK-959In progress tsk-466WP-9722Medium14 OctIn progress
TK-380In review tsk-965WP-5951High11 OctIn review
TK-771Blocked tsk-606WP-2960Critical10 OctBlocked
TK-192Done tsk-724WP-7183Low22 OctDone
6 of 6 records
TK-663Tasks · TSK-55899
Low
TitleBacklog tsk-748
Work packageWP-4794
Due date20 Oct
StatusBacklog
Example screen with sample data

What you can do

Bring the next action to one place

The Review Queue is an actionable page for overdue milestones, overdue tasks, fixed but unverified issues and leading open risks. Each item shows an owner, age and a direct path to its record. Review decisions hold a subject, decision, reviewer and date. Operation receipts record the operation type, reference, result and actor. Attachments can hold a file URL and kind against a named parent record.

The queue is a starting point for investigation. It does not replace the task, blocker or risk record. Open the direct path, inspect the current owner and status, then record the next action where the team will find it on the following review. Keep failed receipts visible until their source is understood.

How the work is organized

  • Open the queue. The Delivery Lead starts with the owner, age and direct path of an actionable item.
  • Inspect the source. The Project Manager checks the task, blocker or risk before assigning follow-up.
  • Read the evidence. A reviewer compares decisions and operation receipts with the source record.

What to agree during setup

Agree who clears each queue item and when to record a review decision. Set a consistent subject reference for decisions and a parent record convention for attachments. Keep receipt results visible during pilot reviews so failed attempts are investigated. Rehearse an overdue task, a fixed issue awaiting verification and a failed operation. Have each owner follow the queue path and record the next action on the original item.

Check the handoff on an actual case

At a weekly review, the delivery lead opens Review Queue and follows a fixed issue that still needs verification. The blocker owner inspects the original issue before marking it verified. A failed operation receipt is a separate signal to examine the attempted action, while a recorded review decision shows who decided and when. The team follows the direct record path instead of relying on a copied status in meeting notes. The Project Manager checks the fixed issue again after verification. The Admin follows the failed receipt to its reference and confirms that a later successful action has separate evidence.

What your team sees

  • Review Queue — Overdue work, unverified issues and open risks with a path to each source record.
  • Failed Operations — Failed attempted actions with type, reference, actor and time.

Follow the work through

What it keeps track of

Data model
Review decisions
Recorded approval decisions on delivery subjects.
Operation receipts
Evidence that a delivery operation was executed.
Record attachments
Files attached to delivery records.
Blockers
Defects and change items raised against project work.
Tasks
Individual pieces of work assigned to a delivery team member.
Risks
Project risks with probability, impact, owner and mitigation.
Objectives
Engagements delivered for an organization, with budget and schedule.

Who uses it

Permissions
Delivery Lead
, Project Manager, Admin.
The Delivery Lead runs the review, the Project Manager follows source work, and the Admin checks failed operation evidence.

Set up OKR Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started