After submitting a self-serve contract request, a contract document is generated based on the contract template and contract template rules. A workflow for reviewing and finalizing a self-serve contract document might progress as follows:

1. The contract user reviews the contract document.
   • If no changes are required, the contract user submits the document for signature.
   • If changes are necessary, the contract user submits a change request to the contract fulfiller and the process continues.
2. An email notification with the details of the change request is sent to the contract fulfiller.
3. The contract fulfiller updates the document and creates a document revision.
4. Contract fulfiller gets ad-hoc approval from the stakeholders.
5. Contract fulfiller sends the contract document back to the contract user.
6. An email notification is sent to the contract user that the document has been updated.
7. The contract document can shared with stakeholders and on finalizing can be sent for signature.
8. If additional changes are required, the contract user submits the change request again and this process continues until the document is acceptable and can be sent for signature.