Creating a Clause-Level Rule

The CongaAIPLATAdminPermission permission group has been added to your user profile to access Conga Redline related configuration. For more information, see User Management. Ensure that the following object permissions are included in the permission group:

RedlineDocumentMap
RedlineDocumentMapping
RedlinePlaybook
RedlinePlaybookDocumentMap
RedlinePlaybookRuleMap
RedlineRule

A clause-level rule restricts the scope of validation to a single clause within the contract document.

Clause-level rules allow you to define how Redline should identify and evaluate specific clauses in third-party documents. When creating a clause-level rule, you choose between two approaches depending on whether the clause you want to track already exists in your organization's clause library.

If the clause is part of your standard library, you can select it directly and the clause's standard position acts as the baseline against which third-party language is compared.

If the clause is not in your clause library but are expected in third party documents, for example, a clause that commonly appears in vendor or counter-party paper, you can create a custom clause rule.

Best practices for creating rules

Use the info icon (tool tip) in the UI for in-product best-practice guidance.
Specify the rule name in Clause Name_Identifier format, closely matching the clause name for accurate identification.
Make the description and sample text for custom clause rules as accurate and representative as possible.
Use bullet-point format for favorable and unfavorable conditions.
Avoid duplicative rule names. Each rule name must be unique across the rule library.
Give each rule in a clause a distinct name.

In Conga Advantage Platform (Modern UI), go to AiMe Settings > Solution Setup.
Click View Settings in the Redline tab.
Click Rules Library tab.
A list of existing rules is displayed.
Click + Create Rule.
Click Clause Level tab.
To add a rule on a clause from the clause library, select or search a clause from the list.
1. Rule Name is auto-populated based on the clause selected. Edit it if needed.
To add a rule on a custom clause, Define New Clause.
1. Specify the Clause Name.
2. Specify the Rule Name.
3. Specify a description for clause in Clause Description.
4. Provide the clause content in Sample Clause
If you selected a clause from the clause library, the clause content is displayed in the Standard Clause Text field.
Under the Acceptable Match Range, select the acceptable percentage overlap between your standard clause language and the language found in the received document.
In the Favorable Position, define the language or terms that are acceptable per your organization's standards. To auto-extract favorable conditions from the clause text, click Scan Clause Text. Review the extracted conditions and edit, add, or remove items as needed. Favorable position is optional for clause-level rules. If only favorable conditions are present and the match score meets the configured threshold, the clause is marked compliant and no recommendations are generated.

In the Unfavorable Conditions enter unfavorable language or terms in the appropriate risk tier sub-section:

Option	Description
High Risk	Enter conditions that are deal-breakers or require immediate escalation.
Medium Risk	Enter conditions that are negotiation points needing attention.
Low Risk	Enter conditions that represent minor concerns or preferences.

Note: Redline uses Favorable Position and Risk Conditions for generating recommendations. Specifying these settings is optional when creating a rule. If you do not configure either condition, the clause is validated only against Gate 1 criteria.

Click Create.

The rule is added to the Rule Library.

You can add the rule to a playbook.

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.

Creating a Clause-Level Rule

Footer Section

Explore