Approval Workflows: Design, Failure Modes & Fixes

Why Approval Workflows Matter

Every organisation runs on approvals — leave requests, expense reports, purchase orders, hiring decisions, overtime. When approvals work well, they are invisible. When they break, everything slows down. A well-designed approval workflow balances speed with control, ensuring the right people sign off without creating bottlenecks.

Common Approval Workflow Patterns

Most workflows fall into a few patterns. Choose the simplest one that meets your needs:

• Single approver — one person approves or rejects (simple, fast, but creates a single point of failure)
• Sequential — passes through multiple people in order (thorough, but slow)
• Parallel — multiple people approve simultaneously (faster for teams, but can create confusion)
• Conditional — routing depends on values (amount > X goes to VP, otherwise to manager)
• Chain of escalation — if the first approver does not act in Y days, it moves to the next level

The Four Failure Modes (and How to Fix Them)

1. The Black Hole

Requests go in and never come out. The approver is on leave, overwhelmed, or ignoring notifications. Fix: add escalation rules — if no response in 48 hours, auto-escalate to the next person. Also, let employees see the status of their request so they know it is stuck.

2. The Bypass

Employees skip the formal process and ask for approval via Slack, email, or in-person. Managers approve informally, and the system is never updated. Fix: make the formal process faster than the workaround. If approval takes three clicks in the system vs. one message in Slack, people will use Slack.

3. The Perfectionist

A workflow that requires too many approvals for routine decisions. Every leave request goes to the CEO because nobody defined thresholds. Fix: use conditional routing — low-value requests need one approver, high-value requests need more. Define thresholds clearly.

4. The Ghost Workflow

The workflow exists on paper but nobody follows it because it was designed without consulting the people who use it. Fix: involve the people who will use the workflow in its design. Test it with real requests before going live. Iterate based on feedback.

Design Principles for Approval Workflows

• Keep it simple — the shortest path that meets your control requirements is the best one
• Set clear SLAs — define how long each step should take and enforce escalation
• Provide visibility — let requesters see where their request is in the pipeline
• Enable mobile approval — most bottlenecks happen when approvers are away from their desk
• Log everything — an audit trail of approvals protects everyone

Measuring Workflow Health

Track these metrics to identify problems before they escalate:

• Average approval time — hours or days from submission to decision
• Escalation rate — how often requests need escalation to move forward
• Rejection rate — high rejection suggests unclear policies or training gaps
• Bottleneck approvers — who consistently takes the longest?
• Abandonment rate — requests that are submitted but never resolved

Key Takeaways