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.
- OKR Tracking System
- Features
- Key result checkpoints
Key result checkpoints
Give every result a dated owner and an outcome that can be reviewed.
OverviewKey Results At Risk×
OKR Tracking System · Key result checkpoints
New
Key Results At Risk
Key results
Pending3
KR-449OBJ-9695
22 Oct
KR-314OBJ-6047
07 Oct
KR-551OBJ-4042
21 Oct
Add
Missed3
KR-554OBJ-5755
06 Oct
KR-211OBJ-2972
07 Oct
KR-875OBJ-5717
22 Oct
Add
What you can do
Turn an objective into checkpoints
Each key result has a name, target date, status and notes. It links back to one objective and can name a team member as owner. Pending, Met and Missed are the available outcomes. The objective carries a key result count and progress text that can help the lead orient a review. The result record remains the place to inspect its target date and the notes behind the outcome.
The target date makes a pending result actionable. An owner can open the result, read its notes, and compare the linked objective with current work before recording an outcome. That same record remains available at the next review, so the team can see which checkpoint was decided and when it was due.
How the work is organized
- Link the objective. Each result belongs to the objective whose outcome it helps the team review.
- Set a target date. The owner uses the date and notes to prepare an outcome decision.
- Record the outcome. The Delivery Lead checks the result before it moves from pending to met or missed.
What to agree during setup
Agree how to phrase a key result so the owner can make a clear met or missed decision. Set target dates before work starts, name the owner, and decide what notes should accompany an outcome change. Review the objective link when importing earlier checkpoints. Rehearse a pending result whose target date is near and another whose date has passed. Ask the Delivery Lead to explain the evidence for each outcome before recording it.
Check the handoff on an actual case
For an objective due at the end of a quarter, the lead records a key result due earlier and assigns an owner. The owner sees the checkpoint as pending while tasks are still in progress. At the review, the owner reads the task state and notes, then marks the checkpoint met or missed. The lead can compare that result with another pending result before deciding whether the objective needs attention. The Delivery Lead records the decision on each result and checks whether the objective status still reflects the work. The owner updates notes on the same result so the next review has its context.
What your team sees
- Key Results At Risk — Pending and missed checkpoints with owner and target date.
- Key Result Outcomes — Met and missed results ready for review.
Follow the work through
What it keeps track of
Data model- Key results
- Dated checkpoints a project must meet.
- Objectives
- Engagements delivered for an organization, with budget and schedule.
- Team members
- Delivery staff with role, practice and weekly capacity.
Who uses it
Permissions- Delivery Lead
- , Project Manager.
- The Delivery Lead records the outcome with the result owner; the Project Manager supplies the state of supporting work.
Set up OKR Tracking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.