Use Case: Completing Obligation Fulfillment on an Agreement
- The agreement has been activated and obligation fulfillment records with a status of Pending Fulfillment have been created automatically by the CLM system.
- An assignee and a reviewer are selected for the obligation fulfillment record. As an assignee, you have received a notification that you have been assigned an obligation with a status of Pending Fulfillment.
- In-app or email notifications are configured for obligation assignment.
Business Context
Once an agreement is activated, tracking whether each party has fulfilled their contractual commitments is critical to managing risk and maintaining compliance. Without a structured fulfillment workflow, assignees have no clear path to confirm completion, reviewers have no mechanism to verify submissions, and contract managers have no auditable record of whether obligations were met on time. The Obligation Fulfillment workflow in Conga CLM provides a process, from assignment and submission through review and final status, ensuring that every obligation is tracked, verified, and resolved within the system.
Overview
This use case demonstrates the end-to-end obligation fulfillment workflow, from the moment fulfillment records are created upon agreement activation through assignee submission, reviewer verification, and final resolution of the obligation status.
Scenario
A contract manager activates a Master Service Agreement that includes a Payment obligation and a Compliance obligation. Upon activation, the CLM system automatically creates fulfillment records for both obligations and notifies the respective assignees. Each assignee completes their task, uploads supporting documents, and submits the fulfillment record for review. The reviewer verifies the submission and assigns a final fulfillment status. For obligations that are no longer applicable, the contract manager waives the fulfillment record, removing it from the active workflow.
Actors
Contract Manager: Monitors obligation fulfillment progress across the agreement and waives obligations that are no longer applicable.
Assignee: Receives notification of obligation assignment, completes the required task, uploads supporting documents, and submits the fulfillment record for review.
Reviewer: Receives notification of the fulfillment submission, verifies the supporting information, and assigns a final fulfillment status.
CLM System: Creates fulfillment records upon agreement activation, sends notifications at each stage, and updates obligation status based on reviewer and contract manager actions.
- Navigate to the Agreement Obligations section in the Related tab of the agreement, open the obligation record, and access the Agreement Obligation Fulfillments related tab.
- Upload supporting documents in the Notes & Attachments section and specify the fulfillment date.
- Change the fulfillment status to Pending Review and click Save to submit the record to the reviewer.
- The reviewer receives a notification, opens the fulfillment record, verifies the submission, and updates the fulfillment status to Fulfilled On Time, Fulfilled Late, Not Fulfilled, or Pending Fulfillment based on the completeness and accuracy of the submission.
- If the submission is rejected, revise the supporting information and resubmit the fulfillment record.
- If an obligation is no longer applicable, change the fulfillment status to Waived to remove it from the active fulfillment workflow.