OKR Approval Workflows
Audience: Team Leads preparing OKRs and administrators reviewing submissions
Approval applies to a unit's work in the relevant OKR cycle. Resource Analysis (VRIO) has no separate submit/approve/reject lifecycle.
Submission and decision
- Open the cycle under Goals & Tracking → OKR Cycles.
- In OKR Tree or OKR Focus, review the unit's objectives, key results, owners/contributors and focus-area links.
- Submit the unit's work for approval. Its state moves from DRAFT to PENDING_APPROVAL.
- An authorized reviewer approves it or requests revision.
- If revision is required, address the reason and resubmit. Track the current state on the unit row.
| State | Meaning |
|---|---|
| DRAFT | Draft; not yet submitted |
| PENDING_APPROVAL | Awaiting a decision |
| APPROVED | Approved work; workflow editing locks apply |
| REVISION_REQUIRED | Returned for revision |
Closed/locked cycle or record state and company read-only restrictions also apply. Approval authority does not bypass cycle state or module entitlements.
Who can submit and approve?
- Company Admins, Strategy Managers, the relevant Group Admin and the Super Admin manage/approve units within their authorized company scope.
- A Team Lead submits or reverts to draft for their own unit or descendants covered by active ancestor leadership.
- An ordinary Team Lead cannot approve their own unit; approval requires leadership of an active ancestor unit. A root-unit leader can approve their own active root unit.
- Leadership of an inactive ancestor does not grant approval authority; an active higher ancestor is considered.
- A Member's authority to update their own progress does not make them a unit approver.
Organizational titles and application roles are different: there is no separate CEO system role. Check root/ancestor leadership assignments and the membership role.
If an approval action is missing
Check the selected company and OKR cycle, unit activity, leadership assignment and your role. The Role Guide shows the permission matrix; hierarchy, module and workflow rules apply in addition. You can inspect the unit-row state without receiving a notification; do not use approval email as the only evidence.