Approvals that don't stall on someone's desk
Most approval failures are not policy failures. The request is sitting unopened in an inbox, the approver is on a flight, the stand-in has no authority to sign, and the requester has no way to find out — so the work happens anyway and the paperwork catches up afterwards. NOWORX makes the route explicit, keeps it moving while people are away, and leaves a record that still makes sense long after everyone involved has moved on.
If this keeps happening
Nobody knows whose desk it's on
A request goes out by email or chat and simply disappears. Three days later the requester asks in a group thread, and someone eventually finds it below the fold in an inbox. The delay was never a decision — it was invisibility.
The approver is away and there is no formal stand-in
Leave, travel and off-days are not reflected in the route, so requests either queue behind an absent person or get waved through verbally by whoever happens to be in the room. Neither outcome survives a question three months later.
Rejected, with no reason attached
The document comes back with one word and no explanation. The requester guesses, edits and resubmits, and the same document circulates three times before anyone states what was actually wrong with it. Each round costs a day.
The same spend approved twice, in two places
One approval happens as a chat message so the order can go out today; another happens on the form a week later so the file is complete. Finance sees both and cannot tell which one was real, and reconciling that takes longer than the approval ever did.
Proving what was approved, months later
A lender, an auditor or a newly arrived manager asks who authorised something in the spring. The answer is distributed across a mailbox, a spreadsheet, a printed signature and a departed colleague's chat history — and assembling it is a week of someone's life.
How the work runs in NOWORX
Tap an app name in any step to see what it does.
- 1
Draft it in the right form, with the numbers already in it
Half of all rework starts with a document that was incomplete when it was sent. form-builder turns each of your request types into a form with the fields that actually matter, so a requester cannot submit a purchase request with no vendor or no delivery date. Where the request is a priced document, quote-docs produces it from the same data instead of a re-typed attachment, and expense-insight pulls in what has already been spent against the same budget line so the approver sees position, not just amount. Requesters who live in a grid can still work in sheets and attach the result.
- 2
Route: sequence, parallel review, and cover while people are away
approval-dashboard holds the route itself: who reviews, who signs, what runs in sequence and what runs in parallel, and which thresholds pull in an extra approver. Because the route is a rule rather than a habit, an amount that crosses a band picks up the additional signature automatically instead of depending on the requester's discretion. team-calendar and attendance-board tell the route when someone is away, so a delegate takes it on with recorded authority and a defined period rather than an informal nod — and the record shows they signed as acting, not as themselves.
- 3
Review, return and resubmit — with the reason attached
A return in approval-dashboard carries the reason and points at the field or the figure in question, so the second version fixes the actual problem. The department agent does the first pass before a human ever opens it: comparing the request against previous ones of the same type, flagging the line that is four times the usual, noticing the missing attachment. What is waiting on whom becomes a card in task-board rather than a nagging thought, and notice-digest tells the requester what happened in plain language instead of leaving them to refresh a screen.
- 4
An approval has to become something
An approval that stops at 'approved' just moves the re-typing downstream. Approved spend posts to ledger and lands in expense-insight against the right budget line. A signed agreement goes to contract-vault with its term and renewal date, so the next decision about it arrives before the auto-renewal does. Approved allowances and adjustments feed payroll-ledger at the cut-off, and issued or received documents are reconciled in tax-invoice-view rather than in a parallel spreadsheet nobody else can open.
- 5
The record, and what it tells you
Every step keeps who did what and when, so producing a history for an auditor or a new finance lead is a query rather than an excavation — data-browser answers it directly. anomaly-watch reads the flow rather than the individual document: requests that are consistently submitted just under a threshold, one approver who returns everything twice, a category creeping upward month after month. daily-briefing gives each approver their queue in priority order at the start of the day, and daily-report keeps the throughput visible so 'approvals are slow' becomes a number instead of a complaint.
Frequently asked questions
Can routes differ by document type and by amount?
Yes — that is the normal case. Each document type has its own route, and bands within a type can add reviewers or change who signs. Reviews can run in parallel where two departments need to look at the same thing, and a department can have rules that apply only to it. The point is that the rule is written down once instead of being re-decided by whoever is drafting.
What happens when an approver is on leave or travelling?
Authority is delegated for a defined period, and the delegate signs as acting — visible as such in the record. You can also set what happens when nothing moves at all: after a set time the item escalates rather than sitting silently. The common failure mode is not the wrong decision, it is no decision, and that is what this closes.
Half our approvals are urgent. Won't a formal route slow us down?
Formality is not what slows approvals — searching for the document does. Approvers get the item on a phone with the context already attached, so the decision takes the thirty seconds it should. For genuinely urgent items you can define a short route with a named signer and a mandatory reason, which is far better than the alternative: a verbal yes that finance has to reverse-engineer later.
Does the AI agent approve anything by itself?
No. The agent prepares and checks — completes the draft from prior documents, verifies that required fields and attachments are there, compares against similar past requests, chases the person holding it up. Sign-off remains a person's act, and the record shows a person's name against it. An organisation cannot delegate accountability to a piece of software, and we don't design as if it could.
Can we keep our existing document formats?
Your formats become forms rather than attachments. The layout your organisation is used to can be reproduced, but the fields become data — which is what makes an approval post to the ledger, or a spend total answerable without opening forty documents. Where a genuine attachment is required, it travels with the request.
How far back can we look, and can we hand a record to an auditor?
Every submission, return, delegation and approval is timestamped against a person, and the history is queryable rather than archived out of reach. You can produce the trail for one document, one approver or one category and share it as a read-only view, so the auditor sees what happened without being given access to everything else.