Control Patterns

Approval chains

Structured sequences of sign-offs required before a decision is finalized, with each approver adding authority based on the decision's scope, risk, or value.

Why it matters

High-stakes decisions shouldn't rest on a single person's judgment. Approval chains distribute responsibility, ensure the right people have visibility, and create accountability at each level. AI can accelerate the preparation for each approval, but the chain itself must remain human.

Where it shows up

finance

Reporting packs require analyst review, then controller review, then CFO sign-off. Each level reviews different aspects — accuracy, narrative quality, strategic alignment.

hr

Compensation changes require manager proposal, HR review, department head approval, and budget validation. Each step checks different criteria.

procurement

Vendor selections above threshold require procurement lead recommendation, business owner approval, and finance sign-off. The chain lengthens with contract value.

Common mistakes

  • Creating approval chains so long that they become bottlenecks and get circumvented
  • Not defining what each approver is actually responsible for checking
  • Allowing AI to auto-approve at any level without explicit human action
  • Failing to handle the delegation/absence case when an approver is unavailable

Signals that a workflow needs this pattern

  • The decision commits the organization to spending above a defined threshold
  • Multiple stakeholders or departments are affected by the outcome
  • The decision has compliance or regulatory implications
  • Historical incidents have occurred because a single person made a decision that needed broader input