Skip to content

FlexApp vs email and spreadsheets for approvals: a side-by-side comparison

Compare email and spreadsheet approvals with a workflow platform such as FlexApp on control, audit trail, reporting and cost, and see when switching pays off.

By FlexApp Product Team Published 3 min read

Most organisations did not choose email and spreadsheets as their approval system. They simply started there, because the tools were already on every desk. This guide compares that way of working with a workflow platform such as FlexApp, so you can judge when it is time to move a process on.

The short answer

Email and spreadsheets are fine for occasional, simple requests. A workflow platform pays off when a process has regular volume, more than one approval step, rules that must be applied every time or audit requirements.

Side-by-side comparison

Email and spreadsheetsFlexApp
Submitting a requestFree-form email or a copied template; details often missingA structured form with required fields, calculations and attachments
RoutingThe requester decides who to email and forwards it onRouted automatically by amount, department, company or project
Policy rulesDepend on people remembering themApplied by the approval route every time
Where is my request?Ask around or search inboxesStatus visible to the requester and approvers at any time
Approving away from the deskPossible by email, without the full contextMobile approval with the form, history and attachments
Audit trailScattered across mailboxes and file versionsA record of who did what and when, kept with the request
ReportingSomeone compiles a spreadsheet by handDashboards and reports built from the request data
Changing the processTell everyone and hope they follow itUpdate the form or route once in a no-code designer
Extra software costNoneLicence and setup, quoted per organisation

Where email and spreadsheets work well

  • Low volume: a handful of requests a month.
  • One decision-maker: the request goes to one person and stops there.
  • No audit pressure: nobody will later ask who approved what and why.
  • Temporary processes: a one-off project that ends in weeks.

In these cases the cost and effort of any new system may outweigh the benefit.

Where they break down

Requests get lost

An approval sitting in someone’s inbox is invisible to everyone else. Reminders depend on the requester chasing, and holidays or job changes leave requests stranded.

Rules are applied inconsistently

Amount limits, extra approvers for certain cost centres or a finance check before payment are easy to forget when each request travels by email. Exceptions become normal without anyone deciding they should.

There is no single record

The latest version of a spreadsheet, the approval email and the supporting document often live in three places. Pulling them together for an audit or a dispute takes time.

Reporting is manual

Questions such as “how long do purchase approvals take?” or “how much did each department claim this quarter?” need someone to compile data by hand, so they are rarely asked.

What changes with a workflow platform

  1. One form per request type, so every request arrives complete.
  2. Automatic routing to the right approvers, including delegation when someone is away.
  3. Visible status for requesters and managers.
  4. Mobile approval with the full request in front of the approver.
  5. A complete record of each decision, stored with the request and its documents.
  6. Reports and dashboards from the same data, without retyping.

FlexApp also includes 45 ready-made approval processes for everyday requests, such as leave, expenses, purchase requests, company seal usage and system access, and every one can be tailored to your policies.

How to decide

Score each of your email or spreadsheet processes against four questions:

  1. Does it run every week or more often?
  2. Does it need two or more approvers or departments?
  3. Are there rules such as amount limits or required checks?
  4. Would you need to prove later who approved it?

A process with two or more “yes” answers is usually a good first candidate to move onto a workflow platform. Start with that one, measure how long it takes before and after, and expand from there.

F

About the author

FlexApp Product Team

Product & Solutions, FlexSystem

The people who design, build and deploy FlexApp for organisations across Hong Kong and Greater China — workflow architects, solution consultants and engineers.

Frequently asked questions

Is email good enough for approvals?

For occasional, single-step requests in a small team, yes. Once requests are frequent, need several approvers, follow rules such as amount limits, or must be auditable, email makes it hard to know where each request is, who approved it and whether policy was followed.

Can we keep using Excel alongside FlexApp?

Yes. Data captured in FlexApp forms can be exported to Excel, and reporting and spreadsheet tools can connect to it. Most organisations stop using spreadsheets as the system of record but keep them for analysis.

How do we move an existing email or spreadsheet process into FlexApp?

Start with one high-volume process. Many common requests, such as leave, expenses and purchase requests, are already among FlexApp's 45 ready-made processes, so the work is mainly adjusting the form and approval route to your policy.

See FlexApp running your process

Tell us about one process you want to fix. We will show it working in FlexApp in a 45-minute demo.