Approval Workflows
Audience: Admin, CEO, Strategy Manager
Page Type: Configuration Guide
Duration: 15-30 minutes
What are Approval Workflows?
Approval workflows in COS are used to control when OKR work becomes formally approved.
Current scope in product:
| Area | What Requires Approval |
|---|---|
| Phase 4 - OKR Execution | OKR submissions by org unit (cycle-level approval states) |
Important: Resource Analysis (VRIO) does not currently use submit/approve/reject status.
End-to-End Flow
1. Submit
A responsible user submits the unit's OKR work for approval. Status moves from Draft to Pending Approval.
2. Review
Approver reviews objectives, key results, and alignment.
3. Decision
Approver sets status:
- Approved
- Revision Required (returned for rework)
- Or back to Draft when needed by process/rules
4. Rework and Re-submit
If revision is required, the owner updates content and submits again.
Approval States
| Status | Meaning |
|---|---|
| DRAFT | Not submitted yet |
| PENDING_APPROVAL | Waiting for approver decision |
| APPROVED | Accepted and locked according to workflow rules |
| REVISION_REQUIRED | Sent back for changes |
Where to Monitor Approvals
Use approval-focused views in the OKR area:
- OKR → Control Center (approval and progress visibility)
- Approval Queue pages available by role/menu configuration
What you typically see:
- Org unit
- Current approval status
- Pending approvals
- Last status update time
Approval Responsibility
| Item | Required Approver |
|---|---|
| Corporate-level OKR submissions | CEO / Company Leader |
| Unit-level OKR submissions | Strategy Manager / hierarchical approver |
Exact routing follows your organization hierarchy, role assignments, and plan features.
Notifications (Approval-related)
| Event | Who Gets Notified |
|---|---|
| New OKR approval request | Approver |
| OKR approved | Submitter |
| OKR revision required / rejected | Submitter |
Notification delivery depends on user notification settings.