Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Obligation Fulfillment

You can manage and track the completion of obligations from the Obligation Fulfillment page. Once a contract is activated, fulfillment records are created for all the active contract obligations. The Obligation Fulfillment page displays a list of contracts having obligations for fulfillment. Clicking the contract link displays all the obligation fulfillment records created for the contract. You can track the obligation fulfillment through its status.

The assignee and reviewer for an obligation are selected at the time of creating an obligation. The assignee can submit an obligation for fulfillment by providing necessary information, which then triggers a review process. The reviewer can accept or reject the submitted fulfillment based on its completeness and accuracy. If required, the contract managers can waive an obligation from fulfillment.

For an active contract, when a contract manager assigns or delegates an obligation to a user (assignee or reviewer) or delegates an obligation to another user, if the selected user does not already have access to the contract, the system displays a confirmation prompt during assignment. Contract access is granted only if the contract manager confirms. If the contract manager declines, the obligation is still assigned, but the user does not receive access to the contract. A notification is sent to the newly assigned user informing them of the assignment. All future notifications and reminders are directed exclusively to the new assignee. The previous assignee stops receiving all notifications and reminders for the obligation fulfillment.

Email notifications are sent to the obligation assignee seven days before the obligation due date.

The reviewer also receive notifications for the following events:

  • When the assignee submits an obligation for fulfillment
  • When the reviewer accepts or rejects an obligation sent for review by the assignee
  • When the contract manager delegates an obligation fulfillment record to another user for an active contract, the old reviewer and the new reviewer receive an immediate notification. All the future notifications are sent to the new reviewer and the previous reviewer stops receiving notifications for the obligation fulfillment.
The assignee receives notifications for the following events:
  • When the reviewer accepts or rejects an obligation.
  • When the reviewer accepts or rejects an obligation sent for review by the assignee
  • When the contract manager delegates an obligation to another user, the old assignee and the new assignee receive an immediate notification. All the future notifications are sent to the new assignee and the previous assignee stops receiving notifications for the obligation fulfillment.

Obligation Fulfillment Lifecycle

In the Obligation Fulfillment lifecycle, fulfillment records are generated for active obligations when a contract becomes active and are tracked through defined statuses to ensure timely completion and compliance. Typically, a fulfillment record progresses from Pending Fulfillment to Pending Review, and ultimately to a final status such as Fulfilled on Time, Fulfilled Late, Waived, Canceled, or Rejected.

The lifecycle also aligns with contract status changes. If a contract is terminated or expired, any associated fulfillment records that are still in pending states are automatically updated to Canceled. Similarly, when an obligation is inactivated during an amendment, its pending fulfillment records are updated to Canceled upon activation of the amended contract. Fulfillment records that have already reached a final status remain unchanged, ensuring accurate historical tracking and lifecycle integrity.