Is anyone utilizing an approval workflow (based on dollar amount/requesting location) for service agreements in the Requester/RSS "Contract Change Order" feature? We have rolled out the "propose a contract" feature in RSS to allow requesters/leaders to propose a new service agreement, and have an automated workflow that mirrors our requisition feature (based on the requesting location and dollar amount, the contract proposal is routed through appropriate leaders before final sign off and activation by a supply chain administrator).
Along with that, we are utilizing the "contract change feature" to help in requests to change existing contracts (line additions, dollar amount changes, contract renewals, etc.). We do not utilize any approvals for this process at the time, but are seeking to bring that in.
Curious if anyone else has built a workflow for the contract change order feature? If so, how are approvals handled for minor budget adjustment to contract lines that result in larger budget shifts over the life of the contract (example: a relatively minor $0.94 budget change to a line resulted in >$10,000 change to contract; potentially requiring an approval workflow to be triggered). Just wondering if there are best practices out there from other organizations.
Thanks!
