Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- OKR Tracking System
- Identity source
- Outcome source
- Document source
OKR Tracking System connects owned objectives to dated key results and the work that supports them. A delivery lead names an objective, organization, owner and schedule.
Objectives in one list
Check-in Reviewer inspects the workflow decision on a Submitted entry with positive hours.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep each objective tied to an organization, a named owner and the dates for its work.
Objectives
| Objective code | Objective | Status | End date | Progress against target | |
|---|---|---|---|---|---|
| OBJ-2026-Q4-01 | Reduce customer onboarding time | Planned | 12 Oct | 18 of 25 days saved | |
| OBJ-2026-Q4-02 | Improve first-contact resolution | Active | 18 Oct | 72% against 80% target | |
| OBJ-2026-Q4-03 | Launch regional partner portal | At risk | 04 Nov | 3 of 4 partner milestones done | |
| OBJ-2026-Q4-04 | Increase renewal confidence | Completed | 03 Nov | 14 of 20 interviews complete | |
| OBJ-2026-Q4-05 | Shorten monthly close cycle | Planned | 24 Oct | Close time down to 6 days |
Give every result a dated owner and an outcome that can be reviewed.
Key results
Connect assigned tasks to work packages and follow their status on a board.
Tasks
| Task key | Title | Work package | Assignee | Due date | Status | |
|---|---|---|---|---|---|---|
| TASK-2026-1041 | Map current onboarding handoffs | Renewal research sprint | Amina Bello | 14 Oct | Blocked | |
| TASK-2026-1042 | Publish support response playbook | Onboarding workflow discovery | Hana Park | 12 Oct | Blocked | |
| TASK-2026-1043 | Review partner portal prototypes | Onboarding workflow discovery | Daniel Okafor | 13 Oct | Blocked | |
| TASK-2026-1044 | Interview ten renewing customers | Help center refresh | Priya Nair | 17 Oct | Blocked | |
| TASK-2026-1045 | Automate invoice exception review | Support playbook rollout | Elena Ruiz | 31 Oct | Blocked |
Record dated hours against objectives and route submitted entries through a decision.
Approval conditions
| Check-in number | Check-in date | Team member | Project | Task | Hours | |
|---|---|---|---|---|---|---|
| CI-74452 | 19 Oct | Nadia Petrova | Increase renewal confidence | Test mobile checkout errors | 13 | |
| CI-51238 | 21 Oct | Daniel Okafor | Launch regional partner portal | Test mobile checkout errors | 11 | |
| CI-57724 | 28 Oct | Nadia Petrova | Launch regional partner portal | Publish support response playbook | 12 | |
| CI-97886 | 02 Nov | Mateo Silva | Improve first-contact resolution | Map current onboarding handoffs | 6 | |
| CI-63319 | 31 Oct | Nadia Petrova | Shorten monthly close cycle | Document release readiness checks | 16 |
Put raised issues and project risks in front of the people who own them.
Operation receipts
| Receipt number | Operation type | Reference | Occurred at | Result | Actor | |
|---|---|---|---|---|---|---|
| OR-81602 | Project Created | Check-in 2026-10-02 | 27 Oct | Failed | Nadia Petrova | |
| OR-71123 | Work Package Created | Review 2026-10-09 | 27 Oct | Failed | Mateo Silva | |
| OR-37995 | Task Created | Decision 2026-10-16 | 03 Nov | Failed | Linh Tran | |
| OR-57193 | Task Status Changed | Approval 2026-10-23 | 21 Oct | Failed | Priya Nair | |
| OR-11882 | Time Entry Submitted | Update 2026-10-30 | 14 Oct | Failed | Linh Tran |
Use the review queue and recorded decisions to inspect work requiring attention.
Tasks
| Task key | Title | Work package | Priority | Due date | Status | |
|---|---|---|---|---|---|---|
| TASK-2026-1041 | Map current onboarding handoffs | Help center refresh | Low | 28 Oct | Backlog | |
| TASK-2026-1042 | Publish support response playbook | Help center refresh | Medium | 22 Oct | In progress | |
| TASK-2026-1043 | Review partner portal prototypes | Renewal research sprint | High | 19 Oct | In review | |
| TASK-2026-1044 | Interview ten renewing customers | Finance close automation | Critical | 18 Oct | Blocked | |
| TASK-2026-1045 | Automate invoice exception review | Release process improvement | Low | 30 Oct | Done |
Objective to reviewed result ships ready to use. One step needs a named approval before the work moves on: Approve check-in (Check-in Reviewer).
Name the owner, organization and dates.
Add dated checkpoints under the objective.
Connect work packages and assigned tasks.
Inspect at-risk work, blockers and risks.
Submission triggers the check-in approval decision.
Record the key result outcome and objective status.
Open any objective to see its blockers, the roles that work on it, its process stages and its approvals on one page.
Objective, Organization, Owner and Start date.
Each line is linked to this objective.
Admin, Delivery Lead and Project Manager, each with their own permissions.
Set objective and Set key results, with the role that acts.
Approve check-in, with who decides.
Reduce customer onboarding time · Active
| Blocker key | Blocker | Project |
|---|---|---|
| BLK-2026-018 | Partner API access still pending | Improve mobile checkout completion |
| BLK-2026-019 | Support staffing gap on weekends | Raise self-service adoption |
| BLK-2026-020 | Billing data export is delayed | Launch regional partner portal |
Signed in as Check-in Reviewer
| Decision | Approver | |
|---|---|---|
| Approve check-inSubmission triggers the check-in approval decision. | Check-in Reviewer |
Everyone opens OKR Tracking System to the work that is theirs. Pick a role to see what it starts with.
Maintains users, reference records and access for the operating team.
Owns objective direction and reviews progress and evidence across the organization.
This is the first screen this role sees.
Objectives · Delivery Lead
Plans work against objectives and follows exceptions through review.
This is the first screen this role sees.
Objectives · Project Manager
Updates assigned work and submits dated check-ins.
This is the first screen this role sees.
Tasks · Team Member
Inspects check-in approval outcomes and follows failed attempts to their source.
This is the first screen this role sees.
Check-ins · Check-in Reviewer
| Check-in number | Check-in date | Team member | Project | Task | Hours | |
|---|---|---|---|---|---|---|
| CI-74452 | 19 Oct | Nadia Petrova | Increase renewal confidence | Test mobile checkout errors | 13 | |
| CI-51238 | 21 Oct | Daniel Okafor | Launch regional partner portal | Test mobile checkout errors | 11 | |
| CI-57724 | 28 Oct | Nadia Petrova | Launch regional partner portal | Publish support response playbook | 12 | |
| CI-97886 | 02 Nov | Mateo Silva | Improve first-contact resolution | Map current onboarding handoffs | 6 | |
| CI-63319 | 31 Oct | Nadia Petrova | Shorten monthly close cycle | Document release readiness checks | 16 |
Triages raised blockers and follows their status to verification.
This is the first screen this role sees.
Blockers · Blocker Owner
Questions to ask about outcomes, workload, exceptions and recorded decisions.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 29 | ||
| Active | 11 | 38% | |
| On hold | 4 | 36% | |
| At risk | 1 | 25% |
Sample counts per stage
Group Objectives by Owner and Status, with key results beneath each objective.
Compare Pending, Met and Missed results by target date and Owner.
Compare start date, end date, estimated hours, actual hours and logged hours by Objective.
Group Tasks under work packages and compare their Status and percent complete.
Show team members with weekly capacity hours, assigned estimate hours and assigned task count.
Compare check-ins by check-in date, team member, Hours and Status.
Review Blockers by Severity, raised date, Owner and Status.
Review Risks by Probability, Impact, risk rating, Owner and Status.
Review operation receipts by operation type, Result and occurred at.
See how OKR Tracking System fits your kind of team.
Each stage of objective to reviewed result names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare objective reviews and find the records behind exceptions.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 13 tablesStart with one team and one process, then add the rest once the basics are running.
Add organizations and team members, then agree who changes objective and key result status.
Create an active objective, dated key results, work packages and assigned tasks.
Submit a positive-hour check-in, set a blocker with severity to Open and inspect the decisions and receipts.
Open Review Queue, follow overdue work and compare task, result and risk records.
Add more objectives after the pilot team can explain each status and responsible owner.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure OKR Tracking System for your business. Begin with one active objective, a dated key result, its owner and a small set of linked tasks.
Each key result links to one objective and can name an owner and target date. Review its outcome on the result record.
Put tasks in work packages linked to the objective. Use the task board and blocked task list to follow assignments.
The result owner and delivery lead should agree on the review decision and record Met or Missed on the key result.
Setting an issue Open triggers triage when severity is present. The workflow writes an operation receipt.
A team member submits positive hours. Submission triggers the approval workflow, which records the decision and receipt. The Check-in Reviewer inspects the outcome.
Risks link to an objective and carry probability, impact, owner and mitigation. Open and monitored risks can be reviewed beside the work.
It brings overdue milestones and tasks, fixed but unverified issues and leading open risks into one actionable page with owner and direct record path.
Record attachments hold a parent record ID, file name, URL and kind for supporting material.
Operation receipts show the operation type, result, actor and reference. Open the source record before retrying the action.
Start free, then use Proto to change fields, steps and approvals before your team goes live.