Back to examples
Admin intakeIllustrative scenario

Internal approval routing

Route an internal request to the right approver and keep the decision and next step visible.

This example explains a workflow design and its controls. It does not represent verified client results. Tooling and benefits must be validated in each project's context.

Internal approval routing editorial cover

Solution example

Internal approval routing

Route an internal request to the right approver and keep the decision and next step visible.

The design connects these steps: Form → Rules → Task → Notification → Reminder → Approval → Report. Rules, exceptions and approvals are defined before external actions are connected.

Workflow map

Approval workflow from request to decision log

Every request gets an owner, a visible status and a final decision record.

Policy-based routingStart1. Receive requestForm | requester | categorySupabase2. Apply routing rulesTeam | amount | policyPython/FastAPI3. Notify approverOwner | due date | contextResend/email4. Track statusWaiting | overdue | approved5. Prepare decisionApprove | reject | reviseApproved?NoYes6b. Request revisionReason | next actionResend/email7b. Log blocked stateWaiting for requesterRetry6a. Log approvalDecision | approver | timestamp7a. Notify requesterApproved | next stepResend/emailEnd

Main database: Supabase

The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.

Tool icons

SupabasePython/FastAPIResend/email

System rationale

A lightweight approval system beats invisible chat approvals

This workflow keeps approvals simple but inspectable: every request has a rule, owner, due date, reminder path and final decision record.

Routing rules reduce ambiguity

The requester does not need to know the org chart; the workflow assigns the correct approver from category and policy.

Reminders protect momentum

Overdue work is visible before a blocked request becomes an operational surprise.

Decisions become reusable history

Approve, reject and revise decisions stay attached to the original request with reason and timestamp.

Add-ons that fit on top

Spend thresholds
Vendor approval
Access approval
Legal review lane
Slack/Teams buttons
Delegation rules
Escalation schedule
Budget owner mapping
Monthly approval report
Policy exception log

The scenario

Design scenario: Route an internal request to the right approver and keep the decision and next step visible. The starting point is a workflow with scattered information, manual steps and responsibilities that need to be made explicit.

Before implementation, we review available data, responsible owners and decisions that need approval. Understand the workflow first.

The approach

The design connects these steps: Form → Rules → Task → Notification → Reminder → Approval → Report. Rules, exceptions and approvals are defined before external actions are connected.

AI can help classify, extract or draft; sensitive actions retain human review. Clear controls at each step.

What was used

Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.

In practice, the build combined Form intake, Supabase, Python/FastAPI, Resend, Approval log. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.

Form intakeSupabasePython/FastAPIResendApproval log

Workflow design

Manual approach and proposed workflow

Manual approach

1Requester sends chat/email
2Approver unclear
3Context repeated manually
4Status checked manually
5Overdue items hidden
6Decision recorded inconsistently

Proposed workflow

1Request form
2Routing matrix
3Approval task
4Owner notification
5Reminder/escalation
6Decision log
7Requester update

Visible artifacts

  • Approval matrix
  • Request log
  • Reminder schedule
  • Decision record
  • Overdue queue
  • Requester notification examples

Controls

  • Approver rules visible
  • Overdue escalation
  • Decision audit log
  • Requester update after decision
  • Rejected/revise path records reason

What this aims to improve

The aim is to reduce manual coordination and make records, exceptions and the next action visible. Any improvement must be validated against the project's own data and operating conditions.

Project scoping establishes a baseline and success criteria so proposed improvements can be tested. Validate the benefit in context.

The workflow in one line

01Form02Rules03Task04Notification05Reminder06Approval07Report

Tooling and boundaries

The design shows how Form intake, Supabase, Python/FastAPI, Resend, Approval log can work together. Final tooling, scope and controls are agreed for each project.

Integrations need appropriate permissions, run logs and a way to review exceptions. The team should be able to understand and operate the workflow.

What this example demonstrates

Design components
  • Request form
  • Approval matrix
  • Owner assignment
  • Due-date reminders
  • Requester updates
  • Overdue escalation
  • Decision log
Intended controls
  • Approver rules visible
  • Overdue escalation
  • Decision audit log
  • Requester update after decision
  • Rejected/revise path records reason

Discuss a similar workflow.

Discuss your workflow

Free initial conversation. No obligation.

Ductio newsletter

Practical ideas for better work.

Get ideas on automation, connected systems and more reliable processes.

Ductio
DuctioSYSTEMS
Custom automation, connected systems and support for teams that need reliable, documented workflows.
Operating focus

CRM operations, reporting workflows, approvals, document handling, and AI-assisted internal tools.

Copyright © 2026 Ductio. All rights reserved.

Discuss your workflow

Free initial conversation. No obligation. We will work through the details together.

Add more details (optional)

We use these details to respond to your inquiry. Please do not include passwords or confidential business data. Privacy notice

You can also email contact@ductiosystems.com.