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.

Use Case: Ad hoc Task Management within a Contract

  • The administrator has enabled the Adhoc Tasks feature flag in CLM Feature Management setting.
  • The administrator has enabled the new UI feature flag.
  • You have access to contract records.
  • Contract is in an eligible status (for example, Authoring, Signing, Activated, Amendment, Renewal).
  • You have permissions to create and manage tasks.
  • The intended assignee exists as a user or user group.

Standard Statement

This use case provides an example of how to create and manage an actionable task that is linked to a contract within the CLM application.

Business Context

Contract execution often requires actions that fall outside predefined workflows—such as clause reviews, internal approvals, document verification, follow-ups, or escalations. Traditionally, these actions are tracked using emails or spreadsheets, leading to poor visibility and audit gaps.

The Ad hoc Task Management capability enables Contract Managers to create, assign, track, and complete contract-specific tasks directly within the CLM application. All task activities remain contextual to the contract, auditable, and integrated with notifications—ensuring accountability, compliance, and operational efficiency throughout the contract lifecycle.

Actors
  • Primary Actor: Contract Manager / Contract Owner
  • Secondary Actors:
    • Task Assignee (User or User Group)
    • CLM System
    • Platform (Notifications, Audit, Attachments)

Trigger

A Contract Manager identifies a contract-related action that must be tracked and fulfilled outside the standard workflow.
Note:
  • Tasks from the original contract are not copied.
  • Tasks are created and managed only within the current contract version.
  • Tasks from a parent contract are not copied to amended or renewed versions.
New tasks must be created in the cloned contract. Tasks are created and managed only within the amended/renewed contract version. No task inheritance from parent contract. Separate task lists maintained per contract version.
.
  1. The Contract Manager opens a contract record.
  2. The Contract Manager clicks the More icon () on the Contracts Details page and selects Tasks.
    This opens the Tasks listing page.
  3. The Contract Manager clicks New Task.
  4. The Contract Manager fills in the required task fields.
  5. The Contract Manager selects Actionable as the task type.
  6. The Contract Manager chooses whether to publish immediately, or delay publishing until contract activation.
  7. The Contract Manager clicks Create Task.

    The system saves the task in:

    • In Draft status if delayed publishing is selected, or
    • Not Started status if published immediately.

    The system associates the task with the contract and makes it visible within the contract.

  8. The Assignee receives notifications based on task assignment and due-date rules.
  9. The Contract Manager or Assignee uploads supporting documents, if required.
  10. The Assignee reviews the task and updates its status as work progresses: Not Started → In Progress → Completed.
  11. The Contract Manager or authorized users may:
    • Cancel the task.
    • Reassign the task.
    • Update or extend the due date.
    • Return the task to the creator.
  12. Comments and additional attachments may be added at any stage.
  • The actionable task is executed and completed within the contract.
  • Task progress and completion are visible to authorized users.
  • Notifications are sent for assignment, reassignment, status changes, and due-date reminders.
  • The task lifecycle concludes when the task is completed or cancelled.

All task actions, including creation, updates, reassignment, comments, attachments, and status changes, are captured in an audit trail. Audit logs are available to compliance users through reports or dashboards.

Tip:
Best Practices:
  • Use actionable tasks only when follow-up or execution is required.
  • Assign realistic due dates to avoid unnecessary reassignment.
  • Attach relevant documents to avoid rework.
  • Use Comments to capture context.