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
- Data model
The tables behind OKR Tracking System
OKR Tracking System ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Direction
Organizations and Objectives carry the owning context; key results carry dated outcomes.
Delivery
Work packages group Tasks, while team members provide named owners and assignees.
Time and exceptions
Check ins record work; Blockers and Risks preserve issues and exposure.
Evidence
Review decisions, operation receipts and record attachments preserve decisions, attempted actions and linked files. Users carries app identities.
Every table, by feature
- Objectives and alignment4
- Key result checkpoints3
- Work packages and tasks4
- Check-ins and approvals6
- Blockers and risks5
- Review and evidence7
- Shared and settings1
- Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Organizations
Client and internal business organizations that projects are delivered for.
- Team members
Delivery staff with role, practice and weekly capacity.
- Key results
Dated checkpoints a project must meet.
Linked to Objectives, Team members
- Key results
Dated checkpoints a project must meet.
Linked to Objectives, Team members - Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Work packages
Groupings of work inside a project.
Linked to Objectives, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Objectives - Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Check ins
Hours booked by a team member against a task and project.
Linked to Team members, Objectives, Tasks - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Objectives - Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Objectives - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Blockers
Defects and change items raised against project work.
Linked to Objectives, Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Objectives, Team members - Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Objectives - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Record attachments
Files attached to delivery records.
Linked to Team members - Blockers
Defects and change items raised against project work.
Linked to Objectives, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Objectives - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Objectives, Team members - Objectives
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members
Keys and references
Each key result references an objective. Each work package references an objective, and each task requires a work package. A task can also reference the objective directly. A check-in requires a team member and objective; its task link is optional. Blockers and risks require an objective through their Project reference. Review decisions can link to an objective; operation receipts link an actor and textual reference. Attachment parents are named by parent type and record ID.
Migration order
- Import Organizations, team members and Users with stable identities.
- Import Objectives with organization and owner references.
- Import key results and work packages under their objectives.
- Import Tasks, then dated check ins, Blockers and Risks.
- Import review decisions, operation receipts and record attachments after their subjects exist.
Set up OKR Tracking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.