A built-in approval gate on documents: before a document is confirmed, it can require a reviewer to sign it off. It is the second pair of eyes, woven into the lifecycle, that keeps commitments and spending controlled.
- Where the verify step sits in the lifecycle
- How approve, reject and resubmit work
- When to switch verification on
The verify step
Between draft and confirmed, a document can pass through Verify, where a reviewer (typically a superior) looks at it and records a verdict: accepted, pending, or rejected. An accepted document moves on to be confirmed; a rejected one goes back to draft, carrying the reviewer's reason so the author knows what to fix.
A shared, optional gate
Verification is the same gate on documents across the system, an order, an invoice, a payroll batch, a purchase, and it is optional: where review is switched on, documents must be approved before they confirm; where it is off, they go straight through. So you add control exactly where you want it, without changing how anything else works.
Good practice
- Switch it on where commitment matters – large orders, payments, anything you want a second sign-off on.
- Give a reason on rejection; it travels back to the author and saves a round of guessing.
Related
- Reference: Document Lifecycle
- Reference: Users and access (who can approve)