How it works
From fragmented requests to a clear record
The whole workflow is designed so a principal can process a typical decision in under ninety seconds.
- 01
A staff member creates a decision request
Title, one-sentence summary, category, deadline and priority — then the options, the costs, the risks and the supporting documents.
- 02
They state a recommendation
What they recommend, why, what the alternatives are, and what happens if no action is taken. The principal never starts from a blank page.
- 03
Optional internal review
The request can route through the chief of staff first, so only complete, well-formed decisions reach the principal.
- 04
The principal receives a decision card
Everything needed to act in 30–90 seconds: the ask, the recommendation, the cost, the deadline, the risk and the consequence of delay.
- 05
One-click decision
Approve, reject, request changes, defer to a date, or delegate to a trusted colleague — with an optional note. High-value approvals can require explicit confirmation.
- 06
The team is notified
The requester sees the outcome immediately, in the app and by email. Nothing is lost in a thread.
- 07
Approved work is tracked
Approved decisions move to In Progress and are marked complete when done — so approvals become outcomes.
- 08
The record is permanent
Every submission, edit, comment, decision and delegation is stored in an immutable audit history and included in reporting.