Approval Workflow Engine with Escalations for Small Offices
An approval workflow engine for small offices, schools and NGOs that turns purchase requests, leave, reimbursements and document sign-offs into tracked flows with deadlines, escalations and email or WhatsApp-style reminders. A no-code automation final year project with a durable workflow runtime and an audit trail.
Intermediate
A small team, or one strong student willing to learn something new.2 semesters · 3 students
7 to ship
3 optional extrasSuggested stack
What you should ship
- A visual builder where an admin defines a form and an approval flow with sequential, parallel and conditional steps (for example amounts above a limit go to the director).
- A workflow runtime that stores each request's state in the database and survives server restarts without losing or repeating steps.
- Deadlines per step with automatic reminders, escalation to a backup approver, and out-of-office delegation.
- Approve and reject actions from a signed link in email that works without logging in, protected against reuse and expiry.
- An immutable audit trail showing who did what and when, exportable as PDF for auditors or donors.
- Versioned workflow definitions so requests already in flight finish on the old version when an admin changes the flow.
- A pilot with one real office for at least three weeks, with request volumes, approval times and user feedback reported.
If you have time left
- Outbound webhooks and an n8n or Zapier integration so approved requests trigger other systems.
- A mobile-friendly approver inbox with bulk approve for low-risk items.
- Budget checks that block a purchase request when the department budget is exhausted.
The problem: approvals that live in WhatsApp groups and inboxes
In a small office, school or NGO, a lot of work is waiting for someone to say yes. A teacher needs lab supplies, a field officer wants a travel reimbursement, a staff member asks for leave, a vendor invoice needs two signatures. Today these requests travel as WhatsApp messages, emails, and paper forms on a desk. Nobody knows where a request is stuck, approvers forget, and at audit time the organisation cannot show who approved what. NGOs that report to donors feel this most.
The steps are usually simple, but the rules are specific to each organisation and they change.
What already exists and the gap
- Kissflow is a low-code workflow platform with many templates for purchase requests, leave and expense approvals.
- Microsoft Power Automate includes approval flows, strongest when the organisation already lives in Microsoft 365.
- Zoho Creator lets teams build custom apps and workflows inside the Zoho suite.
- n8n and Zapier automate between apps, but are not designed around human approval steps with deadlines and escalations.
The gap for small organisations is a focused approvals tool with low per-user cost, email-link approvals that work for staff who rarely log in, audit exports that donors and auditors accept, and a flow builder simple enough for an office manager.
What you build
Three roles: admin, requester and approver.
- Admin builds a form (fields, attachments, validation) and a flow: steps, who approves each (a person, a role, the requester's manager), conditions on form values, parallel branches that all must approve, and deadlines.
- Requester fills the form and tracks the request on a timeline.
- Approver gets an email with the request summary and approve or reject buttons; can also use an inbox in the web app. Can delegate while away.
- Runtime moves each request through its flow, schedules reminders and escalations, and writes every event to an append-only audit log.
The technically interesting part
The hard problem is durable execution. A request might wait two weeks for an approver. During that time the server restarts, the admin edits the flow, the approver leaves the organisation, and two people click approve on the same step within a second. Your runtime must never lose a request, never skip or double-run a step, and must keep in-flight requests on the flow version they started with.
Model each workflow as a state machine stored in the database, advance it inside transactions, and run timers through a persistent job queue rather than in-memory timeouts. This is the same idea behind durable workflow engines such as Temporal, done at a scale you can reason about. Show your evaluators a chaos test: kill the server at random points while a script drives hundreds of requests, then prove every request ended in the correct state with a complete audit trail.
Signed email links are the second challenge: they must expire, work once, and not leak access to other requests.
How to evaluate it
- Reliability: zero lost or duplicated steps across at least 1,000 simulated requests with random server restarts.
- Concurrency: simultaneous approve and reject on the same step always yields one outcome and a clear audit entry.
- Pilot metrics: median time from submission to final decision during the pilot compared with the office's estimate of the old process.
- Usability: an office manager builds a new three-step flow unaided; record time and errors.
- Security: tests for link reuse, expired links and access to requests the user should not see.
Suggested plan
- Weeks 1 to 3: interview two or three offices, collect their real forms and approval rules.
- Weeks 4 to 8: workflow definition schema, state machine runtime and audit log.
- Weeks 9 to 12: form builder, requester and approver screens.
- Semester 2, weeks 1 to 4: deadlines, escalations, delegation, signed email actions.
- Weeks 5 to 8: versioning, chaos tests, PDF audit export.
- Weeks 9 to 14: pilot with one office, fixes, evaluation report.
Path to a product
Sell to schools, clinics, NGOs and small companies with 10 to 200 staff, priced per active user per month with a flat plan for NGOs. The pilot organisation is your first customer and case study. Offer ready-made templates (purchase request, leave, reimbursement, vendor payment) so setup takes an afternoon. Scale by adding integrations with accounting tools and payroll, and by partnering with firms that already sell IT services to schools.
Scope warning
Do not build a general no-code app builder or a BPMN editor. Do not add payments, payroll or accounting. Do not build native mobile apps before the web app and email approvals work well.
Learn what you need on Sefism
- Backend roadmap : queues, transactions and background jobs behind the runtime.
- Full Stack cheat sheet : forms, auth and API patterns for the builder and inbox.
- n8n Documentation : see how an automation tool models nodes, triggers and webhooks.
- Webhook.site : inspect and debug your outbound webhooks during development.
- The Mom Test : interview office managers about approvals without leading them.
Get help with this idea
Workflow engines look simple until a flow changes mid-request, so bring your versioning plan when you discuss it. If you want a second opinion on scope, stack or how to evaluate it before you pitch it to your supervisor, bring your draft proposal and we will pressure-test it together. You build it; the guidance is on the decisions.
New here? Create a free account first.
Ideas and guidance, not finished projects
These are project ideas and scoping guidance, published free for students to use as a starting point. I do not build, write, or sell final-year projects, and I do not complete coursework for anyone. Take an idea, make it yours, and build it.
Not sure this one fits you?
I help students pick an idea that matches their skills and their deadline, then scope it down until it is finishable. Guidance only, never done for you.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.