Overview
Every one-pager follows a planning lifecycle with four statuses:
Not started → In progress → Pending approval → Approved
Status badges appear on the one-pager detail screen and in the tree view so everyone can see where each one-pager stands. Some status changes happen automatically (for example, when you start editing), while others require a deliberate action (requesting or granting approval).
Status meanings
| Status | Badge | What it means |
|---|---|---|
| Not started |  | The one-pager exists but no work has been done yet |
| In progress |  | The owner is actively working on the content |
| Pending approval |  | The owner has requested approval; waiting for the supervisor to review |
| Approved |  | The supervisor has reviewed and approved the content |
Automatic status changes
In three situations the status changes on its own, without anyone clicking a button:
-
First edit or accepting a propagation — A "Not started" one-pager moves to "In progress" as soon as the owner begins editing or accepts cascaded content from a parent one-pager.
-
Editing an approved one-pager — If anyone edits the content of an "Approved" one-pager, it automatically reverts to "In progress". This prevents stale content from staying marked as approved. The owner will need to go through the approval flow again.
-
Receiving new propagated changes — When a parent one-pager pushes new changes down to a child that is "Pending approval" or "Approved", the child reverts to "In progress". This ensures that new upstream changes are incorporated before the one-pager can be considered complete.
Requesting approval
When you have finished filling in your one-pager, you can request approval from your supervisor by clicking the 
button next to the status badge.
Before requesting approval, four content conditions are checked. These are shown as advisory suggestions in a tooltip when you hover over the button:
- Ambition is filled in — The ambition field should not be empty
- Every pillar has at least one initiative — No empty pillars
- Every initiative has a goal — Each initiative should have its success criteria defined
- No pending incoming propagations — All cascaded changes from the parent one-pager should be accepted or rejected first
These conditions are advisory only — the button is always clickable. The tooltip helps you understand what might still need attention, but does not prevent you from submitting the request.
Approving or rejecting
Once an owner requests approval, the one-pager enters the "Pending approval" state. Two roles can act on it:
- Supervisor — the owner of the parent one-pager in the hierarchy
- Admin — any user with enterprise admin permissions
For top-level (L0) one-pagers that have no parent, only an admin can approve.
The supervisor or admin sees two buttons next to the status badge:
— marks the one-pager as approved. The same advisory suggestions tooltip is shown on hover so the approver can check content completeness before approving.
— sends the one-pager back to "In progress" for rework
After rejection, the owner can continue editing and request approval again when ready.
Revoking approval
Once a one-pager has been approved, the approval can be revoked by clicking the 
button next to the status badge. This sends the one-pager back to "In progress".
Revoking approval is useful when content needs to be revisited — for example, if strategic priorities have changed or if the approval was granted prematurely. After revoking, the owner can make changes and request approval again.
Admin approvals tab
Enterprise admins have access to a dedicated Approvals tab in the organization admin section. This tab provides a hierarchical tree view of all one-pagers with their current statuses, allowing admins to:
- Approve or Revoke individual one-pagers
- Approve all linked — approve an entire subtree of one-pagers at once
- Revoke all linked — revoke approval for an entire subtree at once
This gives admins a centralized overview of planning progress across the entire organization.
Status badges in the tree view
The tree view shows a compact status badge on each one-pager node. This gives supervisors and admins a quick overview of planning progress across the hierarchy — at a glance you can see which teams haven't started, which are working, which are waiting for review, and which are done.