Approval workflows that people actually follow

Every finance leader has inherited an approval process that looks reasonable on paper and falls apart in practice. Requests sit untouched for days. Managers approve things they never read. Employees learn to route around the system entirely. The problem is rarely the people. It is the design.

Start with the decision, not the hierarchy

The instinct when designing approvals is to mirror the org chart. A request travels up the reporting line until someone senior enough signs off. This feels safe, but it confuses authority with relevance. The person best placed to judge whether a purchase makes sense is usually the one closest to the work, not the one highest on the chart.

A better starting point is the decision itself. Ask what actually needs to be verified before money moves: is the amount within budget, is the vendor approved, is the expense category allowed. Once you know what the approver is checking, the right approver becomes obvious.

Set thresholds deliberately

Not every expense deserves the same scrutiny. A team lunch and a new server contract should not travel the same path. Thresholds let you match the level of review to the level of risk.

• Auto approve small, routine expenses that fall inside a known budget.
• Route mid sized requests to the direct manager who owns the budget line.
• Send large or unusual requests to finance for a second look.

Make the fast path the default

The single biggest predictor of whether a workflow survives is speed. If approvals are fast, people use the system. If they are slow, people find workarounds, and your control evaporates. Design for the common case first. The exceptions can wait.

Controls that slow everyone down to catch a rare problem usually cost more than the problem they prevent.

Close the loop

Finally, tell people what happened. An approval that disappears into silence feels broken even when it worked. A simple notification, an updated status, a clear reason for a rejection. These small signals are what make a process feel trustworthy, and trust is what keeps people inside the system instead of around it.