The right approvers, in the right order, every time.
Set approval rules once: a vendor contract above $50,000 needs legal, then finance, then a director; an NDA on the standard template needs nobody. Krujinfosoft routes each contract by value, type, entity, department and deviations found in review, and keeps a record of who approved what and when.
Legal, then finance, then director. Approved in 2 days, not 2 weeks.
What Approval Flow covers.
Rule-based routing
Route by value, contract type, entity, department, currency or the presence of non-standard clauses.
Sequential and parallel steps
Run finance and tax together, then send to the director only when both have approved.
Deviation-triggered approval
If a fallback clause is used, add the legal head automatically. Standard drafts skip the extra step.
Reminders and escalation
Approvers get reminders by email, and a step that waits too long is escalated to a named backup.
One-click approve from email
Approvers see a summary with key terms and findings, and approve or return with a comment.
Approval record
Every approval is stored with the approver, time, version approved and any condition attached.
How it runs, step by step.
Agreed text is frozen
The final version from negotiation is locked for approval.
Rules pick the route
Value, type and deviations decide who approves and in what order.
Approvers act
Approve, return with comments or approve with conditions.
Ready to sign
Once the last approval is in, the contract moves to E-Sign.
The details, in writing.
Asked about Approval Flow.
Can approval limits differ by entity?
Yes. Each group company can have its own thresholds and approvers.
What if an approver is on leave?
Set a delegate for a date range. The approval record shows both the delegate and the original approver.
Can a contract change after approval?
Any change after approval sends it back through the affected steps, so signed text always matches approved text.