Most approval processes live in email chains. Someone sends a request, a manager replies "approved" or "denied," and the record of that decision exists in an inbox that nobody else can easily find. When something needs to be audited or re-approved, you're hunting through email threads.
Airtable can replace that entirely with a structured approval workflow: one table, multiple decision points, interfaces for submitters and approvers, and a formula that tracks overall status automatically.
Build your approval process in Airtable and get decisions out of email and into a system.
Disclosure: some links in this post are affiliate links. If you sign up through them, GAP Consulting earns a small commission at no extra cost to you.
The cost of informal approvals isn't obvious until something goes wrong. A purchase gets made without sign-off because the email got missed. An approval is claimed verbally but there's no record. A workflow depends on a decision that happened weeks ago and nobody remembers the outcome.
A structured process in Airtable creates an audit trail, makes status visible without asking anyone, and keeps decision-makers accountable to a clear workflow.
The core of the system is a single table with a record for each item requiring approval. For a purchase request workflow, that means fields like: requester name, item description, amount, department, submission date, and then the approval fields.
Each decision point gets its own single-select field: Approval Step 1, Approval Step 2, Approval Step 3. Options are "Pending," "Approved," and "Denied." Each approver updates their field when they make a decision.
With individual step fields in place, an overall status formula reads all three and returns the current state of the request:
This formula runs automatically as approvers update their fields. No manual status management. No summary emails needed. Anyone can look at the record and know exactly where it stands.
Two interface views make this system work for non-technical users:
Submitter interface: A form or record creation page where employees submit requests. Show only the fields they need to fill out. Hide all the approval step fields — submitters don't need to see or interact with those.
Approver interface: A filtered view showing requests that are pending their specific step. A manager responsible for Step 2 approvals sees only records where Step 1 is "Approved" and Step 2 is "Pending" — their queue, nothing else.
This filtering prevents approvers from jumping ahead in the process and ensures each step happens in the right sequence.
Airtable's Interface access controls let you share the approver interface with specific people without giving them full base access. Each decision-maker gets a link to their filtered queue. They approve or deny records through the interface. The underlying table updates in real time.
For submitters, a shared form link lets them submit without needing an Airtable account at all.
In practice, the flow looks like: employee submits a purchase request via the submitter form → Step 1 approver (team lead) sees it in their queue, approves it → Step 2 approver (finance) sees it automatically appear in their queue once Step 1 is done, approves it → Step 3 approver (executive sign-off) approves → overall status becomes "Fully Approved."
If anyone denies at any step, the request is flagged immediately and the submitter can see the outcome without emailing anyone.
Set up an approval process in Airtable — it takes less than an hour to build and replaces years of email-based approvals.