Custom workflows
The platform's rules on approvals and budgets always hold. Everything above them is yours to shape.
Order approvals, budget commitments and the guards on a purchase order are platform rules, and they stay that way — otherwise a buyer could configure its way past its own signature policy. A workflow sits above them, tracking where a requirement or an order has got to inside your company. The two never contend for the same decision.
Stages are connected by routes, and only a declared route can be taken. Skipping legal review because the stage after it looked available is refused by the database, not by a screen — so it holds however the move arrives.
A route can require a permission, resolved through the same check as everything else. If your company has taken order approval away from members, the award step refuses them too, without anyone remembering to update the workflow.
Every move writes an append-only event with its actor, its note and its timestamp. A status column tells you where something is; this tells you how it got there, which is the question an auditor actually asks.
Give a stage an SLA and work sitting there too long is marked late. Nothing blocks — the point is to surface the requirement stuck in review for nine days while there is still time to move it.
Controls that live in the database, so they apply whether the order came from the app, an integration, or someone in a hurry.
Read morePut demand in front of the right suppliers and let competition do the work, without losing the audit trail that makes the award defensible.
Read moreMost audit logs record what happened. This one can also demonstrate that the record has not been edited since.
Read more