Workflow design

Designing approval workflows reps don't route around

May 12, 2026 · 5 min read

Every workaround is a design review you didn't schedule. When reps quote at 9.9% to dodge the 10% threshold, email the VP directly instead of submitting, or keep a shadow spreadsheet of "pre-approved" prices — they're telling you exactly where your workflow costs more than it protects. Here's how to design chains that get followed.

Principle: the compliant path must be the fastest path

Reps optimize for deal velocity, always. If the sanctioned route takes two days and the workaround takes two hours, the workaround wins regardless of policy. So the design target is not "prevent violations" but make compliance faster than evasion. Everything below serves that.

The ladder, and why each rung exists

Four mechanics that keep chains fast

  1. Auto-approval SLAs. Pending >24h at manager tier? Auto-escalate, don't auto-approve — but tell the requester exactly where it sits and who's next. Silence is what breeds workarounds.
  2. Approve from the notification. Every click between "saw the request" and "approved" costs hours of latency at scale. One-tap approval with quote context inline.
  3. Parallel where possible. Legal review and finance review of the same quote rarely depend on each other. Sequential-only chains double latency for ritual's sake.
  4. Reasons on both sides. Requester explains the discount; approver's decision is logged with identity and timestamp. Symmetric accountability keeps the ladder honest in both directions.

The metric that tells you it's working

Watch approval latency by tier and the distribution of requested discounts. A healthy system shows discounts clustering just under thresholds less over time, not more — because the ladder is cheap enough to climb honestly. And when the audit trail shows every decision, quarter-end reviews take an hour, not a week.

The threshold ladder in this post is Glime's default configuration — see an approval chain live in the sandbox.