Approvals out of email and chat: how to set up an approval workflow
Vetrox · Published
The short answer
Write down which requests need approval and who approves each one, up to what amount. Give every request a form that collects what the approver needs, a route that follows those rules, a deadline with reminders and a stand-in for when the approver is away. Keep each decision with the record it approves, so anyone can see later who approved what, when, and on which version.
Why approvals get lost in email and chat
An approval given in an email or a chat is a message, not a record. It sits in one person's inbox or sinks under a busy thread, the thumbs-up may be on an older version of the amount, and when the approver is on leave the request simply waits. A year later, nobody can find who said yes, to what, or when.
Email also makes approvals easy to fake. The Australian Cyber Security Centre (ACSC) warns that small businesses are often targeted by business email compromise because payment approvals and account changes may rely on trust and email communications (opens in a new tab).
An approval workflow deals with both: every request goes to the right person under rules you set, and every decision is stored with the record it belongs to. The six steps below apply whichever tool it runs in.
Six steps to an approval workflow
- 1
List what needs approval
Purchases, expense claims, leave, refunds, supplier changes
- 2
Write down who approves what
By role and amount, and nobody approves their own request
- 3
Give each request a form
Required fields and the documents the approver needs
- 4
Choose where it runs
A tool you already have, or the system that runs the work
- 5
Set deadlines and stand-ins
Reminders, a hand-over when time runs out, cover for leave
- 6
Keep the decision with the record
Who approved what, when, and which version
Step 1: List what needs approval
Start with the requests that need a yes before anything happens. In most businesses it is the same short list:
- purchases and purchase orders
- expense claims
- leave, and changes to working hours
- refunds and credit notes
- new suppliers, and any change to a supplier's bank details
- contract changes and variations
- access to systems and data, such as a new login to the accounting software.
For each one, write down how it is asked for today, who says yes and how long that usually takes. The list shows where people spend their time chasing.
Not everything needs approval. A limit below which routine purchases need no sign-off keeps people from waiting on decisions nobody needs to make. Keep approvals for requests that spend money, commit the business or give someone access.
Step 2: Write down who approves what
For each type of request, write the rule as one sentence: who approves, up to what amount, and when a second person has to approve as well. For example: purchases go to the requester's manager, and above a set amount they also go to finance.
Name roles, not people: “the requester's manager”, “finance”, “the operations manager”. Rules written against roles keep working when someone changes jobs or leaves.
Then add two rules that stop most problems:
- nobody approves their own request: when the requester is also the approver, it goes to the next person up
- the person who adds a supplier or changes their bank details is not the person who approves paying them.
Both come from separating duties. The Commonwealth Fraud Prevention Centre, which helps Australian Government agencies counter fraud, recommends splitting a process between several people (opens in a new tab) so one person cannot do every step, for example by not letting the same person maintain supplier records and also process invoices. Its advice on approval workflows (opens in a new tab) is to let the system send each request to the appropriate decision-maker: payment requests to the right approver, higher-value claims to a specified one.
Step 3: Give each request a form
An approver should be able to decide from the request alone, without a follow-up question in chat. So each type of request gets its own form, with required fields such as:
- what it is for, in a sentence, and which job, project or client it belongs to
- the amount, the supplier and the date it is needed by
- the documents the approver has to see, such as the quote, the invoice or the contract
- what the next step needs, such as the account code finance will use.
The same fields make a better record. The Australian Taxation Office (ATO) says a business record generally needs the date, amount and description of the transaction, and its purpose (opens in a new tab). A form that asks for those from the start means the record is complete on the day the request is approved, instead of pieced together later from emails.
Step 4: Choose where it runs
With the rules and forms written down, check the tools you already have against them before anything is built:
- Lark Approval (opens in a new tab) handles leave, business trips, reimbursements and other requests. An administrator designs the forms and the steps, and each step's approver (opens in a new tab) can be the requester's manager at a chosen level, a department supervisor, a role or a named person, with conditional branches for different cases and a setting for when the approver and the requester are the same person.
- Microsoft Teams has an Approvals app (opens in a new tab) available to all Teams users, and team owners can create approval templates for the teams they own.
- Google Workspace's approvals (opens in a new tab) are for documents in Drive, such as a contract, on Business Standard and higher.
- Accounting, HR and job management software may have its own approval step for bills, expense claims or leave. When the record already lives there, approve it there.
How Lark, Slack and Google Workspace differ on approvals is covered in a separate guide.
A built-in approval is enough when the request stands on its own, like a leave request. A custom workflow earns its place when the approval is a step inside your own process: a job that cannot start until a variation is approved, an order that waits on a credit check, a request that needs figures from two systems before anyone can decide. Then the approval belongs inside the system that runs that work, so a yes moves the job to its next stage.
Step 5: Set deadlines and stand-ins
Set the order of approvers on each route: one after another when each needs to see the previous decision, or at the same time when they only need to agree. Then give every step three settings:
- a deadline, with a reminder before it and the request passing to someone else after it
- a stand-in who approves while the approver is on leave, so requests do not wait for them to come back
- what a rejection does: a reason is required, and the request goes back to the requester to fix, not into a new email chain.
Some deadlines are set by law. An employer who receives a request for flexible working arrangements (opens in a new tab) has to respond in writing within 21 days, saying whether it is approved or refused. A refusal has to give the reasons, and can only be made on reasonable business grounds. A request like that cannot be left waiting in an inbox.
Reminders and hand-overs are the kind of work worth automating: nobody should have to remember to chase an approval.
Step 6: Keep the decision with the record
Store each approval with the thing it approves: the purchase order, the expense claim, the leave record. Keep who asked, who approved at each step and when, their comments, and the version of the amount and documents they saw.
If the amount or the documents change after a yes, the request goes back for approval. Google Drive works this way for files: if an edit is made, every reviewer has to approve the latest version again (opens in a new tab).
The record also has to last. The ATO says most business records must be kept for five years (opens in a new tab), stored in a way that protects them from being changed, and notes that the Australian Securities and Investments Commission (ASIC) requires companies to keep records for seven years. A yes in a chat thread is hard to find a year later, and nothing ties it to the amount it approved.
Payments and bank details: check by phone
In business email compromise, criminals pose as a business, supplier, customer or staff member to get money sent to them, sensitive information shared or payment details changed, sometimes from a real email account they have broken into. The ACSC advises caution with unexpected requests involving payments or bank account changes, and verifying unusual requests through a trusted channel, such as a known phone number (opens in a new tab), not contact details given in the email.
Build that check into the workflow:
- a change to a supplier's bank details is its own request, never a note on an invoice
- it cannot be approved until someone records that they phoned the supplier on a number already on file
- an urgent request to pay a new account gets the same check, however senior the sender seems.
Start with one type of request
Do not move every approval at once. Pick the request people chase most, often purchases or expense claims, move it to the new workflow, and after the first month look at what its records show: how long approvals take, where they wait, and which requests come back for missing information.
Then adjust the form or the route and move the next type across. Make it clear the old way has stopped: once a type of request has moved, a request sent by email gets a link to the form instead of a yes.
Where Vetrox fits
Vetrox is an Australian IT company that builds approval workflows into custom systems for businesses across Australia, and sets up Lark Approval for teams that work in Lark. Each request goes to the right person under your rules: who approves which amounts, what needs a second signature and who stands in when someone is away. Approvers can act from their phone or a Lark message, the documents travel with the request, and an audit trail shows who approved what and when. If the approval feature in a tool you already have covers it, we will say so on the first call.
Sources
- Australian Cyber Security Centre: Small business cyber security handbook, Common cyber threats to small businesses (published 7 October 2026) (opens in a new tab)
- Commonwealth Fraud Prevention Centre: Segregation of duties (opens in a new tab)
- Commonwealth Fraud Prevention Centre: Approval workflows (opens in a new tab)
- Australian Taxation Office: Overview of record-keeping rules for business (updated 18 June 2026) (opens in a new tab)
- Lark Help Center: Get started with Approval (updated 16 December 2025) (opens in a new tab)
- Lark Help Center: Admin | Set up an approver step (updated 2 February 2026) (opens in a new tab)
- Microsoft Learn: Manage the Approvals app in Microsoft Teams (opens in a new tab)
- Google Workspace Admin Help: Manage Approvals (updated 26 October 2026) (opens in a new tab)
- Fair Work Ombudsman: Flexible working arrangements (opens in a new tab)