Operations

Multi-level approval workflow

Approvals depend on amount, department, substitutes and escalation rules that are enforced through manual chasing.

Business problem

Approvals depend on amount, department, substitutes and escalation rules that are enforced through manual chasing.

What teams see

  • Work waits between receive approval request and validate authority.
  • Owners reconstruct status from Microsoft Teams and Microsoft 365.

Why it happens

  • No shared state spans Microsoft Teams, Microsoft 365, Database.
  • Decision and exception rules are applied inconsistently.

Why it becomes expensive

  • Capacity is consumed by coordination and rework.
  • Late exceptions weaken visibility and service quality.

Business outcomes

  • Shorter record final outcome cycle
  • Fewer handoff and missing-information exceptions
  • Clear ownership from receive approval request to record final outcome
  • Inspectable decisions and recovery

Measurable KPIs

  • Turnaround time: Elapsed time from receive approval request to record final outcome.
  • Manual intervention rate: Share of items needing a person outside defined review conditions.
  • Exception age: Time unresolved exceptions remain without a completed action.
  • Successful completion rate: Share of valid workflow items completing without terminal failure.

How the workflow works

  1. Receive approval request — Accept and identify the multi-level approval workflow trigger. Microsoft Teams
  2. Validate authority — Execute validate authority with validated sample data and an auditable result. Microsoft Teams
  3. Evaluate amount threshold — Execute evaluate amount threshold with validated sample data and an auditable result. Microsoft 365
  4. Select approval chain — Execute select approval chain with validated sample data and an auditable result. SEIDO Review Queue
  5. Request decision — Execute request decision with validated sample data and an auditable result. SEIDO Review Queue
  6. Handle delegation — Execute handle delegation with validated sample data and an auditable result. Microsoft 365
  7. Escalate expiry — Execute escalate expiry with validated sample data and an auditable result. Database
  8. Record final outcome — Execute record final outcome with validated sample data and an auditable result. Microsoft Teams
  9. Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store

Integrations and ownership

  • Microsoft Teams: Provide workflow input
  • Microsoft 365: Lookup and update context
  • Database: Receive controlled outcome

Human responsibility: Operations manager

Failure and recovery

Microsoft Teams is temporarily unavailable.

Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.

Required data for validate authority is malformed or missing.

Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.

The trigger or provider event is delivered more than once.

Return the existing execution identified by the idempotency key and do not repeat downstream business actions.

The human decision expires before completion.

Escalate to the configured substitute, retain the original request and record both expiry and reassignment.

When not to build this

  • Monthly volume is too low to justify integrating Microsoft Teams, Microsoft 365, Database.
  • An existing configured platform already handles multi-level approval workflow with adequate ownership and reporting.
  • Reliable source data or supported API access is unavailable.
  • No business owner has authority to define the decision and exception rules.

Related workflows