Approval workflows
Approvals are how Rival keeps a human on the consequential decisions while letting everything else run. An approval is a checkpoint: the work pauses, a person reviews what’s about to happen, and only their yes lets it proceed.
Routing
Section titled “Routing”An approval has to reach the right person. Routing sends each request to whoever should decide — a manager, a department lead, a finance approver — based on what the action is and who it belongs to. Good routing is what keeps approvals from piling up on one overloaded person.
Escalations
Section titled “Escalations”When an approver doesn’t respond, or a decision exceeds their authority, the request escalates — moving up to someone with the standing to decide. Escalation paths keep work from stalling and make sure big decisions land with the right level of the organization.
Types of approval
Section titled “Types of approval”- Risk-based — higher-risk actions require sign-off; low-risk ones flow through. Match the friction to the stakes.
- Department — route approvals to the owning team. See Teams & departments.
- Financial — actions above a spending threshold require a financial approver.
Configuring approvals
Section titled “Configuring approvals”Admins define where approvals are required and how they route. The art is calibration: too many approvals and people route around the system; too few and control is theater. Put them where the consequences are real.
A quick example
Section titled “A quick example”A procurement workflow auto-handles orders under $500. Between $500 and $5,000 it routes to the department lead; above $5,000 it escalates to finance. One workflow, three levels of oversight — and nobody reviews a $40 order.