An approval process can move into software and still behave like a confusing email chain. Requests sit with the wrong person, managers approve without enough context and nobody can explain which version was accepted. Automation has moved the delay rather than removed it.
Design the decision rules before automating the route. The system should make responsibility and evidence clearer, while handling ordinary follow-up work consistently.
Define the decision and the authority
Start with one approval type, such as a purchase request, campaign budget or publication. Identify who can request it, who can approve it and which conditions require an additional review.
Write the rule precisely enough to implement. If approval depends on value, department or project, define the relevant field and how exceptions are handled. Avoid relying on a developer to infer authority from job titles.
Separate preparation from approval where the organisation's controls require it. Decide who can delegate and what happens during an approver's absence. A workflow that depends on one unavailable person will still stall.
Require the information needed to decide
A request should contain the purpose, amount or scope, supporting evidence, relevant dates and the version being submitted. Keep the form focused on the actual decision rather than collecting every possible detail.
Make missing information visible before submission. If a request is returned, record the reason and preserve the history. The requester should know what to correct, not merely see a status labelled “rejected.”
If the request changes materially after approval, define whether it must be reviewed again. Approval of an earlier amount or document should not silently cover a different final version.
Make the system enforce the rules
Permission checks must protect the server action, not only the interface. A person should not be able to approve another team's request by changing a record identifier or calling an endpoint directly. OWASP recommends denying access by default and checking authorisation on every request.
Keep an audit record of the requester, approver, decision, timestamp and approved version. Protect that record from ordinary editing. Log corrections as new actions rather than rewriting the history to make it look clean.
Use clear status transitions. A request should not move from draft to completed merely because a notification was sent. Sending, receiving, approving and executing are separate events.
Automate reminders with restraint
Notify the responsible person when action is required, then send reminders according to an agreed schedule. Escalate overdue work to a defined role. Do not copy the entire organisation every time a deadline is missed.
Keep sensitive details out of lock-screen notifications where possible. The alert can direct the authorised person to sign in and review the request securely.
Give users a clear view of outstanding actions. Notifications help draw attention, but the work queue should remain the authoritative place to see what needs a decision.
Test exceptions before launch
Test a returned request, a changed approver, a duplicate click, an expired session and an attempted action by an unauthorised user. Check what happens if the notification provider fails while the approval itself succeeds.
Ensure that repeated submissions do not create duplicate approvals or repeated downstream actions. Confirm the behaviour when a browser closes midway through the process.
Pilot the workflow with real users and review the first cases. Measure time spent waiting, reasons for returns and the number of exceptions requiring manual intervention. These signals show where the process needs improvement.
Automation is useful when it makes a well-defined process more reliable. If authority, evidence or exception handling remains unclear, faster routing only delivers unclear decisions sooner.
Design and implement an approval workflow with Zero Impulse.
Technical reference: OWASP authorisation guidance.




