Phone approvals → clear steps
Approvals happen by phone, and nobody can tell who said yes.
Purchase requests, expenses, discounts, leave and refunds all need someone's yes. When that yes comes by phone or in a chat, requests wait on a busy manager, nobody knows where one is stuck, and months later there is no record of who approved what. An approval workflow gives every request a form, a path of approvers based on simple rules such as the amount or the department, reminders when it waits too long, and a history that shows each decision with its date and its reason.
Who this is for
- Companies where purchases need a manager's sign-off
- Finance teams chasing expense receipts
- Sales teams whose discounts need approval
- Organisations that must show who approved what
This is how it works today.
Each box is a moment where the work waits for a person. Keep scrolling and we will take out the ones a system can carry.
A purchase request today
By hand today: 5 steps
- An employee messages the manager with a requestThe request is filled in on a short form
- They call again because it has not been seenThe approver is reminded automatically
- The manager says yes on the phoneThe decision is recorded with date and reason
- Someone forwards it to finance by email
- At audit time, people search old chats
What we would build
- 01
Request forms
One short form per request type, with the fields and attachments it needs, filled from a phone or a desk.
- 02
Approval rules
Who approves depends on simple rules you set: amount, department, type. Two steps for large amounts, one for small.
- 03
Reminders and delegation
Requests that wait too long remind the approver; when someone is away, a deputy approves instead.
- 04
A full history
Every request keeps its trail: who asked, who approved or rejected, when, and why. Searchable and exportable.
- 05
A view of what is waiting
Managers see what waits on them; the owner sees how long requests take and where they get stuck.
Why it matters
Approvals by phone feel fast because each one takes a minute. The cost is in the waiting and the missing record: a purchase that holds up a site for two days because the manager was in meetings, a discount nobody remembers granting, an expense paid twice. Clear approval steps protect both sides. Employees know their request is moving and who has it; managers decide from a complete request instead of a voice note; and the company can answer an auditor or a partner with a record instead of a memory. Over time, the history also shows where requests usually wait, so the rules can be improved.
What to build first
Pick the one request type that causes the most chasing, often purchases or expenses, and build its form, rules, reminders and history first. Keep the rules simple at the start: one or two amount thresholds and one deputy per approver. Once that type runs smoothly, other requests such as discounts, leave or refunds reuse the same engine with their own forms. Approvals can then connect to the systems around them, for example creating the purchase order or the payment once a request is approved. Write the rules down with the people who approve today, so the system matches how decisions are really made.
What it takes
Effort depends on the number of request types, how complex the approval rules are, whether approvers need a phone-friendly screen or notifications, and whether approvals must create something in another system such as accounting. Most of the thinking happens before building: writing down who approves what today, including the exceptions people handle in their heads. NOVA starts with that conversation, puts the rules in writing for you to confirm, and then builds in fixed milestones you can see working each week. Once the rules are clear, building is the shorter part, and later request types are faster because the engine already exists.
See how it could look
A quick concept from the Studio, built from NOVA's templates. Your real design is made with you.
Open in the StudioWork that shows how
Questions
Can managers approve from their phone?
Yes. Approval screens are built for phones first, with a notification when something waits on them.
What happens when an approver is on leave?
A deputy you choose receives the requests, and the history shows who approved on whose behalf.
Can it handle different rules per department?
Yes. Rules can depend on department, request type and amount, and you can change thresholds without new development.
Can approved requests flow into accounting?
Often, yes, depending on the accounting system you use. We check what it allows before promising a connection.
Sounds like your week?
Tell us how the work happens today. A person from NOVA reads every brief and answers.
