How to Build a Simple Approval Workflow Without IT Help
2026-05-03
Build a purchase request, leave application, or visitor pass approval workflow in 5 minutes. No IT help, no coding, no forms to design.

How to Build a Simple Approval Workflow Without IT Help
You need a simple approval process. Maybe for purchase requests. Maybe for leave applications. Maybe for visitor passes.
You don't need SAP for this. You don't need to raise an IT ticket. You don't need a developer.
You need 3 things: a form, an approval step, and a way to track status.
Here's how to build it yourself in under 5 minutes.
What Every Approval Workflow Needs
1. A Request Form
What information does the requester need to provide?
- For a purchase request: what material, how much, from which vendor, how urgent
- For a leave request: which dates, what type of leave, reason
- For a visitor pass: visitor name, purpose, who they're visiting, date/time
2. An Approver
Who decides? One person or multiple levels?
- Single approval: manager approves
- Two-level: manager approves, then director approves (for amounts above a threshold)
3. Status Tracking
Everyone should be able to see: is my request pending, approved, or rejected?
That's it. Form → Approval → Status. Everything else is optional.
The 5-Minute Setup
Step 1: Describe your process (30 seconds)
Go to insights.flobri.com/build and type what you need. Be specific about the form fields:
For a purchase request:
"Employee submits a purchase request with material name, quantity, estimated cost, and urgency level. Manager approves or rejects with remarks."
For a leave request:
"Employee applies for leave with leave type, from date, to date, and reason. Reporting manager approves or rejects."
For a visitor pass:
"Reception creates a visitor entry with visitor name, company, purpose, person to visit, and expected duration. The host confirms or declines the visit."
Step 2: Review the generated workflow (2 minutes)
Flobri generates:
- The stages (Request → Approval → Completed/Rejected)
- The form fields at each stage
- The transitions (Submit, Approve, Reject, Send Back)
- An approver selection field (so the requester picks who should approve)
Review the fields. Add or remove any that don't fit. Rename if needed.
Step 3: Deploy (1 click)
Click Deploy. The workflow is live. Share the link with your team.
Step 4: Use it
- Requester fills the form and submits
- Approver gets notified, sees the request, approves or rejects
- Requester sees the status update
- Dashboard shows: 5 pending, 12 approved this week, 2 rejected
No IT Needed Because:
- No database setup — Flobri creates the data tables automatically
- No form builder — the AI generates forms from your description
- No notification system — built into the workflow
- No dashboard configuration — status tracking is automatic
- No user management — add employees, assign roles, done
Real Examples
A 30-person factory set up purchase request approval in 4 minutes. Within a week, they had data showing that 40% of requests were waiting more than 2 days for approval. They added auto-escalation. Approval time dropped to 4 hours.
An HR team replaced their leave register with a digital workflow. First month: 200 leave applications processed, zero lost in the system, zero "did you approve my leave?" calls.
A plant digitized their visitor management. Security logs every visitor. Host gets notified. Visitor history searchable. Time from "visitor at gate" to "let them in": 2 minutes instead of 15.
Start Now
Pick your most annoying approval process — the one that generates the most follow-up messages.
Go to insights.flobri.com/build. Describe it in one sentence. Deploy it in 5 minutes.
Flobri lets anyone build approval workflows without IT help — purchase requests, leave applications, visitor passes, expense claims, or any process that needs a form and an approval.