Approval can be a single decision button or a multi-step workflow with conditions, delegation, evidence, and escalation. Estimate the work by the business decision and its failure paths, not only the number of screens.
Basic approval scope
A simple flow needs requester, approver, item, decision, time, reason, and notification. Define what happens when an approver is unavailable, the item changes, or the request is withdrawn.
Rules and roles
Cost increases with thresholds, departments, sequential or parallel steps, delegated approval, separation of duties, tenant scope, and field-level permissions. The document approval cost guide helps identify common evidence and routing work.
Evidence and audit
Budget for attachments, comments, version, source, changed values, decision reason, audit trail, search, export, and retention. Keep sensitive information visible only to authorized reviewers.
Notifications and escalation
Include in-app, email, or other channels, reminders, due date, fallback owner, failure handling, preference, and quiet hours. Preserve the approval state when a notification is missed.
Security and accessibility
Scope authorization on every transition, protected links, tenant isolation, keyboard behavior, focus, mobile layout, clear status, and safe error recovery.
Maintenance cost
Allow for policy changes, new roles, workflow versioning, stale approvals, reporting, access review, data retention, support, and rollback. Assign an owner for each approval rule.
Approvals happening in email and spreadsheets without evidence? Ask Vertinus to scope decisions, notifications, and auditability together.