➡️
Linear • Simple
1. Sequential Approval
Approvers must approve in a specific, pre-defined order. Each approver must complete their approval before moving to the next.
✅ Pros
- Clear accountability at each level
- Simple to implement and understand
- Ensures hierarchical review
- Audit trail is straightforward
❌ Cons
- Can cause bottlenecks
- Delayed if any approver is unavailable
- No parallel processing
- Rigid structure
Best for: Hierarchical organizations, financial approvals, compliance workflows, purchase orders over certain limits.
// Sequential approval workflow
workflow: [
{ role: "Manager", order: 1 },
{ role: "Director", order: 2 },
{ role: "VP", order: 3 }
]
⇉
Fast • Collaborative
2. Parallel Approval
All approvers receive the request simultaneously and can approve independently. May require all or majority approval.
✅ Pros
- Faster processing time
- No single point of failure
- Collaborative decision making
- Works well with remote teams
❌ Cons
- Lack of clear accountability
- Potential for conflicting feedback
- May require coordination
- Can be confusing for complex decisions
Best for: Cross-departmental projects, design reviews, policy changes, committee decisions.
// Parallel approval workflow
workflow: {
type: "parallel",
approvers: ["Dept Head", "Finance", "Legal"],
required: "all" // or "majority"
}
⏭️
Smart • Adaptive
3. Conditional Approval
Approval path changes based on request attributes (amount, department, risk level). Different rules trigger different workflows.
↓
B
Path B
If amount ₹50K-5L
✅ Pros
- Optimizes approval paths
- Reduces unnecessary approvals
- Adaptive to business rules
- Efficient resource utilization
❌ Cons
- Complex to set up initially
- Requires clear business rules
- Can be confusing if poorly designed
- Harder to audit
Best for: Purchase approvals, travel requests, expense claims, vendor onboarding with tiered risk levels.
// Conditional approval workflow
if (amount < 50000) {
workflow = ["Manager"];
} else if (amount < 500000) {
workflow = ["Manager", "Director"];
} else {
workflow = ["Manager", "Director", "VP", "CFO"];
}
👥
Flexible • Scalable
4. Role-Based Approval
Approvers are determined by their organizational roles rather than specific individuals. System finds appropriate person based on role.
→
→
👤
Assign to actual person in role
✅ Pros
- Automatically adapts to org changes
- No need to update workflows when people change roles
- Scalable for large organizations
- Clear separation of duties
❌ Cons
- Requires accurate role mapping
- May assign to incorrect person if roles aren't maintained
- Less personal accountability
- Can be impersonal
Best for: Large organizations, matrix structures, IT access requests, leave approvals, standard operational requests.
// Role-based approval workflow
approvers: [
{ role: "Department Manager",
field: "department" },
{ role: "Project Manager",
field: "project_id" }
]
📈
Time-Sensitive • Backup
5. Escalation Approval
If primary approver doesn't respond within defined time, request automatically escalates to next level or alternate approver.
A
Primary Approver
24 hours to respond
→
B
If no response
Escalate after 24h
→
C
Backup Approver
12 hours to respond
✅ Pros
- Prevents workflow stagnation
- Ensures timely processing
- Automatic backup system
- Reduces bottlenecks
❌ Cons
- May bypass intended approver
- Can create confusion if primary approver responds late
- Requires careful timing configuration
- May annoy approvers
Best for: Time-sensitive requests, urgent purchases, crisis situations, critical IT changes, emergency approvals.
// Escalation approval workflow
approvers: [
{ person: "Manager", timeout: "24h",
escalate_to: "Director" },
{ person: "Director", timeout: "12h",
escalate_to: "VP" }
]
🤝
Democratic • Consensus
6. Majority/Quorum Approval
Requires a certain percentage of approvers (e.g., 3 out of 5, 51%, 2/3 majority). Common in committees and boards.
✅ Pros
- Democratic decision making
- Reduces individual bias
- Works well with committees
- Collective responsibility
❌ Cons
- Can lead to groupthink
- May delay decisions
- Individual accountability diluted
- Complex to track
Best for: Board decisions, policy approvals, hiring committees, award selections, budget approvals.
// Majority approval workflow
workflow: {
type: "quorum",
approvers: ["Member1", "Member2", "Member3", "Member4", "Member5"],
required: 3, // minimum approvals needed
quorum_type: "majority"
}
👤
Fast • Flexible
7. Any-One Approval
Only one approver from a defined group needs to approve. First available approver can handle the request.
↓
↓
✓
First to respond approves
✅ Pros
- Extremely fast processing
- No bottlenecks
- High availability
- Load balancing across team
❌ Cons
- Lack of specialized review
- May assign to less qualified approver
- No backup if all are unavailable
- Accountability issues
Best for: IT support tickets, routine operational approvals, standard purchase requests, team-level decisions.
// Any-one approval workflow
workflow: {
type: "any_one",
approver_pool: ["Manager A", "Manager B", "Manager C"],
required: 1
}
🔀
Complex • Multi-Dimensional
8. Matrix Approval
Combines multiple dimensions (department, amount, project type) to determine approvers. Used in matrix organizations.
📊
Matrix Evaluation
Department × Amount × Type
→
→
✅ Pros
- Highly precise approval routing
- Considers multiple factors
- Adapts to complex org structures
- Comprehensive review
❌ Cons
- Very complex to set up
- Hard to maintain
- Can be confusing for users
- Requires constant updating
Best for: Matrix organizations, global companies, complex projects with multiple stakeholders, research grants.
// Matrix approval workflow
matrix: [
{ dept: "Engineering", amount: ">100000",
approvers: ["Eng Director", "CFO"] },
{ dept: "Marketing", project: "Global",
approvers: ["CMO", "Regional Head"] }
]
👥➡️👤
Flexible • Backup
9. Delegated Approval
Approvers can delegate their approval authority to others temporarily (during vacations, leave, etc.).
Best for: Organizations with frequent travel, backup planning, continuity of operations.
⚖️
Fair • Balanced
10. Weighted Approval
Different approvers have different voting weights (e.g., VP vote = 3 points, Manager = 1 point).
Best for: Investment committees, strategic decisions, board votes.
🔄
Fair • Distributed
11. Round-Robin Approval
Requests are distributed evenly among a pool of approvers in rotating fashion.
Best for: Support teams, quality control, peer reviews, code reviews.
👤✅
Efficient • Trust-Based
12. Self-Approval with Limits
Employees can approve their own requests within predefined limits (amount, frequency, etc.).
Best for: Expense reports, small purchases, time-off requests within limits.
🤖
Smart • Automated
13. AI-Assisted Approval
AI analyzes requests and either auto-approves, flags for review, or recommends approval path.
Best for: High-volume low-risk requests, compliance checks, pattern-based approvals.
🔄➕
Adaptive • Comprehensive
14. Hybrid/Mixed Approval
Combines multiple methods in a single workflow (e.g., parallel within department, then sequential upward).
Best for: Complex organizations, multi-stage processes, comprehensive reviews.