Approval workflows that leave a trail
Purchase requests, time off, discounts, and anything else that needs a yes. Routed to the person who decides and recorded where you can find it later.
Approval means an email thread and a hope.
A request goes out as an email and then it is gone. Nobody knows whether it is waiting on finance or on a manager who is on leave. The invoice waits on a signature nobody can find, so someone forwards the thread again with a question mark. When a director asks who approved the spend, the answer lives in three mailboxes.
Every request is a row with a status.
Appvise builds a request form, a queue for approvers, and a status on every row. The person who raised it can see where it sits without asking. The approver opens one list of what is waiting on them, and roles make sure that list is theirs rather than everyone. Each decision is written onto the record with who decided and when.
What gets built
Questions
How soon can people start submitting requests?
Describe the form and the stages and you have a working queue the same day. Publish it on a URL with HTTPS, give the people who raise and approve an account, and refine the fields once real requests are coming through.
Can one request need two approvals?
Yes, if you describe it that way. The usual shape is a status that moves through stages with an approver recorded per stage, so the request is only done once both decisions exist. Sketch the rule in plain words first, because it is much easier to change than to guess.
What gets recorded when someone approves?
The decision lands on the request itself, with the account that made it and the time it happened. Open that request months later and it still says who said yes, without anyone searching a mailbox.
