---
title: "Obligation Management"
canonical: "https://help.agiloft.com/space/SD/237240328/Obligation+Management"
format: markdown
---
For AI-driven obligation management, use Astra with Agiloft CLM. When you evaluate a contract with an Agiloft community Obligation Management screen, AI automatically finds obligations and extracts them to your KB where you can create tasks and generate reports for tracking them. This article describes how to use the obligation management feature out-of-the-box as well as how to customize Obligation Management screens and update your KB to support the customizations.

> ℹ️ Astra must be deployed before you can set up or use the obligation management feature. For information, see [Setting Up Astra for Agiloft CLM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/570261517).

# Out-of-the-Box Setup

Out-of-the-box, the following Obligation Management screens are set up to identify and extract several types of obligations. The screens are standards-based playbooks designed by Agiloft’s team of Legal Knowledge Engineers, who have deep experience with contracts as former practicing attorneys:  

- **Obligations – Delivery**: Extracts delivery-related obligations that may be found in general commercial contracts.
- **Obligations – Service Levels**: Extracts service level-related obligations that may be found in service level or service level-related contracts.
- **Obligations – Insurance**: Extracts insurance-related obligations that may be found in general commercial contracts.
- **Obligations – Confidentiality**: Extracts confidentiality-related obligations that may be found in general commercial contracts.
- **Obligations – General Commercial Agreements**: Compiles into a single screen the obligations from the Delivery, Insurance, Confidentiality, Payment, Termination, and Regulatory screens.
- **Obligations – SaaS Agreements**: Extracts SaaS-related obligations that may be found in SaaS contracts.
- **Obligations – Payment**: Extracts payment-related obligations that may be found in general commercial contracts.
- **Obligations – Termination**: Extracts termination-related obligations that may be found in general commercial contracts.
- **Obligations – Regulatory**: Extracts regulatory-related obligations that may be found in general commercial contracts.
- **Obligations – Data**: Extracts data-related obligations that may be found in data processing contracts.
- **Obligations – Statements of Work**: Extracts SOW-related obligations that may be found in statements of work.

## Add the Screens to Your Workspace

To set up your KB so you can initiate obligation extraction with the click of a button in Contract records, simply add the Obligation Management screens to your Astra workspace:

1. Log in to Astra with Agiloft CLM and go to [Community Screens](https://www.screens.ai/community).
2. Locate the screens under Obligation Management.
3. Click Get Screen for each screen you want to add to your workspace.

Once the screens are in your workspace, you can use them to extract obligations with a [Screen Run action](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/120553719) button on the Obligations tab in Active Contract records. For details, see [Extract Obligations](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44433413).

# Obligation Extraction and Processing

This section describes the extraction and processing of obligations and the relationships between Astra and obligation management-related records in Agiloft CLM. 

## Data Extraction

Each question in an Obligation Management screen represents one obligation that might be found in a contract. Unlike questions in other community and custom screens where answers are returned in a free text field, questions in Obligation Management screens return answers in a set of [Structured Data fields](#structured_data_fields). The structured data fields are key to the generation of meaningful Obligation records in Agiloft CLM. When you evaluate a contract with one of the screens, Astra extracts the structured data fields and additional metadata for each question to a Screen Result record in your KB.

![Diagram showing data extracted from Screens to a Screen Result](media://a020e669-c41e-4336-a69e-118d93652c92)

Screen Result records include the Element Name, which is the Question Title in a screen, and Element Definition, the Question Text. The Result Extraction field stores the extracted structured data fields and their responses. The language from the contract where AI found the answer to the question is stored in Pinpoint Citation. Pinpoint Citation is empty when the document doesn’t contain the answer, meaning that obligation isn’t found in the contract.

### > Macro (anchor)

Structured Data Fields 

Questions in the out-of-the-box screens prompt AI to return values for each of the following structured data fields. Some fields are required for generating a useful Obligation record in your KB and others are optional.

| **Field** | **Required?** | **Description** |
| --- | --- | --- |
| Summary | Required | The answer to Question Text in the screen. Maps to Answer in Obligation records. |
| Summary Standardized | Required | The meaningful value from the answer in Summary. This is the key value, like a law or regulation, penalty or remedy, timeframe, or date, that you might want to use for filtering, automation, or reports after the obligation is extracted.<br>> ℹ️ Since responses from Astra are in text format, they’re human readable but not interpretable by the system. For example, Summary Standardized could return values like “January 10, 2026” or “30” to represent days. One value looks like a date and the other a number, but they’re text and can’t be used in reports on obligation deadlines. To use the Summary Standardized value in operations like filtering or reporting, it needs to be processed to a typed field, such as a date or integer. The [Metadata Type record](#) defines which type of field to process Summary Standardized to.<br>> ⚠️ In addition to being a key field for operations after the obligation is extracted, this field is also key for triggering the out-of-the-box processes that generate Obligation records. For the best results, always include this field in the list of fields you return. When a question won’t produce a value, you can prompt AI to return “null.” For example, some Summary Standardized prompts in the out-of-the-box screens are “Always null” because the question won’t return a value for the field. |
| Consequence | Required | A description of the penalty or remedy for failing to meet the terms of the obligation. |
| Consequence Standardized | Required | The specific consequence, such as a fixed amount or percentage.<br>> ℹ️ Like Summary Standardized, this field holds a key value that you might want to use for operations after the obligation is extracted. It should also be processed to a typed field. |
| Obligation Type | Required | Describes the type of obligation. Maps to Topic in Obligation records. The out-of-the-box types are Confidentiality, Data, Delivery, Financial, Insurance, Performance, Regulatory, and Termination.<br>> ⚠️ With the out-of-the-box setup, an Obligation record won’t be created if Obligation Type is missing. |
| Responsible Party | Optional | The company name or description of the party responsible for the obligation. |
| Trigger | Optional | The event or condition that triggers the obligation. |
| Trigger Type | Optional | The type of trigger. The out-of-the-box types are Event-based, Time-based, and Ongoing. |

> 📝 When there isn’t a response for a structured data field, the out-of-the-box screens prompt AI to respond "null." This ensures all structured data fields are extracted for each question.

## > Macro (anchor)

Metadata Type Record Creation

Each Screen Result record links to a Metadata Type record. Out-of-the-box, a Metadata Type record exists for each question in the Obligation Management screens. Element Name in the Screen Result maps to Metadata Type in the Metadata Type record (Question Title in the screen).

![Diagram showing the relationship between Screen Results and Metadata Types](media://cd5ece0a-896f-4879-95c6-6676313f757d)

You can create or update a Metadata Type record from a Screen Result by clicking the Convert to Metadata Type button in the Screen Result. When a new Metadata Type record is added, Metadata Type ID is pulled back into the related Screen Result.

Metadata Type records define how to process the values in the Summary Standardized and Consequence Standardized fields after they’re imported to an Obligation record from the Screen Result ([Processing Target Fields](#processing_target_fields)). They also define which of the standard fields to display in the Obligation record (Standard Fields Visibility).

### > Macro (anchor)

Processing Target Fields

In a Metadata Type record, the Processing Target Field defines which types of fields to process the Summary Standardized and Consequence Standardized values to in an Obligation record. In the out-of-the-box screens, prompts for the standardized structured data fields always instruct AI to format responses according to the type of fields the values might be processed to. The table below lists the target field options and their data types, the standardized field the value is pulled from, and the format to prompt for.

| **Target Field** | **Data Type** | **Structured Data Field** | **Response Format** |
| --- | --- | --- | --- |
| Amount | Floating Point | Consequence Standardized | Number with a decimal point |
| Currency | Link to selected fields from other table: Currency | Summary Standardized | 3-letter currency code |
| Data Processing | Choice: Lawful Basis, Data Minimization, or Purpose Limitation | Summary Standardized | One of the Choice values |
| Date | Date (Due Date field in Obligation) or  
Integer (Due in Days field) | Summary Standardized | A specific date or number (without a decimal point) that represents the number of days in the future |
| Incoterms Code | Multi-Choice: EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DPU, DAP, DDP, Other | Summary Standardized | A value from the Multi-Choice list or multiple values separated by semicolons |
| Law/Regulation | Link to single field from other table: Law/Regulation | Summary Standardized | A code from the Laws/Regulations table or multiple codes separated by semicolons |
| Minimum Coverage Amount | Floating Point | Summary Standardized | Number with a decimal point |
| Penalty/Remedy | Link to selected fields from other table: Penalty/Remedy | Summary Standardized | Text describing the penalty or remedy for obligation breach |
| Recurrence Frequency | Choice: Weekly, Bi-Weekly, Monthly, Bi-Monthly, Quarterly, or Annually | Summary Standardized | One of the Choice values |
| Timeframe | Integer | Summary Standardized | Number without a decimal point |
| Timeframe Units (Displayed if Timeframe is selected) | Choice: Hours, Days, Weeks, Months, Quarters, Years, or Percentage | Summary Standardized | One of the Choice values |

> ℹ️ **Example**
> ℹ️ 
> ℹ️ Below is a snippet from the Summary Standardized prompt for the Payment Terms question in the Obligations – Payment screen:
> ℹ️ 
> ℹ️ “If the Summary field is a certain time period after receipt or date of an invoice, (for example, invoice will be due and payable within thirty (30) days, within 30 days, or similar), convert the output from the Summary field into a number of days and output as a number (integer).”
> ℹ️ 
> ℹ️ The prompt instructs AI to return a timeframe as an integer that represents a number of days. The Metadata Type record for Payment Terms includes Timeframe as a processing target field, with Days selected as the Timeframe Unit.
> ℹ️ 
> ℹ️ The Consequence Standardized prompt for the same question asks for an amount as a number with two decimal places and possibly a percent sign:
> ℹ️ 
> ℹ️ “If the Consequence field contains a fixed currency amount, output only the exact amount as a number with two decimal places. If the Consequence field specifies a benchmark rate (such as the base rate, prime rate, or applicable rate) without an additional uplift or margin, output only the named benchmark rate as it appears. If the Consequence field contains a penalty amount that is expressed as a margin above or below a benchmark rate, output the benchmark rate together with the margin in the format benchmark rate+/-number with two decimal places%.”
> ℹ️ 
> ℹ️ In the Metadata Type record, Amount is also selected as a processing target field.

When multiple processing fields are selected, the system populates the appropriate target field based on the extracted text. 

For more information, see [Metadata Types Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050).

## Obligation Record Creation

In a Screen Result record, if Result Extraction includes Obligation Type and Pinpoint Citation isn’t blank, a rule with an import action is triggered. The action generates an Obligation record from the Screen Result. The diagram below shows how fields are mapped from Screen Results to an Obligation.

![Diagram showing how Obligation records are created from Screen Results](media://9368e902-7dfa-4de7-b446-e6236432ea72)

The Obligation record also includes settings from the Metadata Type record, which are used to process the extracted data. 

## Obligation Record Processing

The creation of an Obligation record triggers rules in the Obligation table that process the data in the record. The diagram below shows how the values in Summary Standardized and/or Consequence Standardized are processed to typed fields according to the [Processing Target Fields](#processing_target_fields) selected in the Metadata Type record.

![Diagram showing how data is processed in an Obligation record](media://bac7b36e-61ef-4fe5-b80a-79caa45f0bf9)

Obligation records link to the related Screen Result, Screen Run, Contract, and Attachment records for the contract that was evaluated. When Summary Standardized is processed to Currency, Law/Regulation, or Penalty/Remedy fields, those values are also links to the related table. For existence checks, or Yes/No obligations, the Obligation Exists field is set to Yes or No based on the value in Summary Standardized or Consequence Standardized. 

Obligation records have a Create Task button so you can create a [Task](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434285) that links to the Contract record for the contract that includes the obligation. For tracking whether the AI-generated obligations have been reviewed by a human, Obligation records also include a Review Status field. New records from AI extractions are assigned a Review Status of Not Reviewed. When a user reviews the record, they can change the status to Needs Review if they want another person to review it, Reviewed if they approve the record, or Edited if they made changes to the record.

For more information, see [Obligations Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/570163248).

# Customizing Obligation Management Screens

You can build custom screens by using the Agiloft Obligation Management screens as templates. You can directly edit the screens you added to your workspace or create copies to modify. 

To copy a screen:

1. Go to the Screens page in Astra.
2. In the list of available screens, click the menu icon for the screen you want to copy and select Duplicate Screen.

> ℹ️ For general information on working with screens, see [Using Astra with Agiloft CLM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/570327053) in the Help Guide.

Each Agiloft Obligation Management screen includes an Obligation Template at the bottom of the screen. To add a question, copy the template to the screen and then modify the copy.

To copy the template, click the menu icon on the top right and select Copy to screen. Then select the destination screen and click Copy to screen again.

![Menu for the Obligation Template with Copy to Screen highlighted](media://7f7efe32-5748-499f-aae5-58b5ddbb4e13)

You can duplicate the template in the screen as many times as you’d like. You can also edit or delete any of the existing questions in the screens. The template provides user guidance with customization notes, sample question types, and placeholders that guide you in writing questions and prompting for responses. For additional help, review the details of the other out-of-the-box questions in the screen.

When adding or editing questions, follow the user guidance in the template and keep the following high-level notes in mind:

- The capitalized instruction at the top of the template prevents AI from creating a false obligation from the template. Remove that instruction when adding your question.
- To keep things working as expected, it helps to minimize changes to the template as much as possible. Ideally, replace only the [[placeholder]] text and keep the same structured data fields as the template.
- Always include responses for the required [structured data fields](#structured_data_fields). To ensure all fields are extracted, prompt AI to respond "null" if no answer is found.
- All questions in a screen don’t necessarily result in an Obligation record. An Obligation record is created only if AI finds that obligation in the screened contract.

The table below describes what happens when you run an Obligation Management screen with various types of customizations. It includes guidance on what changes to make when an obligation is found in a contract but an Obligation record isn’t generated or doesn’t include the data you expect. 

| **Type of Customization** | **Result** | **Suggested Change** |
| --- | --- | --- |
| A new question is added. It includes responses for all of the structured data fields in the template. | If the obligation is found in a contract, an Obligation record is generated. If there isn’t a Metadata Type record for the new question, Subtopic is blank in the Obligation record. | If Subtopic is blank, click Set Subtopic in the Obligation record to create a new [Metadata Type](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050) record and populate Subtopic with that metadata type.<br>If the new question includes Summary Standardized and/or Consequence Standardized values that you want to use in reports or other operations, set the Processing Target Fields in the Metadata Type record and run the screen again to generate an Obligation record with typed fields. |
| An existing question is edited. The prompt in Question Details is changed, but the possible response values and output format in the structured data fields remain the same. | An obligation record is generated as expected. | N/A |
| An optional structured data field is removed from a question. | An Obligation record is generated, and the deleted field is blank in the record. | You can hide the empty field from the Obligation record by deselecting that field under Standard Fields Visibility in the Metadata Type record. |
| All required structured data fields are removed from a question. | A Screen Result record is created but an Obligation record isn’t generated. | Add the required structured data fields to the question and rerun the screen to generate an Obligation record. |
| All required structured data fields except Obligation Type are deleted from a question. | An Obligation record is generated, but it’s essentially a clone of the Screen Result record and can’t be used for reporting or automation. In addition, Obligation Exists is set to No. | Add the required structured data fields to the question and rerun the screen to generate a usable Obligation record. |
| A new structured data field is added to a question, or an existing field is renamed. | The new field is extracted to the Screen Result record, but it isn’t represented in the Obligation record. | To include the field in the Obligation record:<br>1. Add the new field to the [Obligations](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/570163248) table.
2. Update the T:Create Obligation import action in the [Screen Results](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434110) table to map the result to the new field in the Obligations table. |
| A question that has a non-structured, free text response is added. | A Screen Result record is created for the question, but an Obligation record isn’t. Note that the out-of-the-box filter for Screen Results History – Questions in the Contract record excludes this type of Screen Result record. It won’t be listed in the Contract record but can be seen in the Screen Results table. | Make sure all questions in an Obligation Management screen return the required structured data fields. |
| A question returns an Obligation Type that isn’t a preconfigured choice. | An Obligation record is generated, but the Topic field is set to the default value of “Choose one.” | Edit the Topic field in the [Metadata Types](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050) table to add the new value to the list. Then update the Obligation record and select the Topic. |
| The Summary Standardized response includes a penalty or remedy that doesn’t match a value in the Penalties/Remedies table. | The Penalty/Remedy field in the Obligations table allows loose links, so the Penalty/Remedy value in the Obligation record is text instead of a link. | Add the new value as a record in the [Penalties/Remedies](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/217743409) table. |
| The Summary Standardized response returns a law or regulation that doesn’t match a value in the Laws/Regulations table. | The Law/Regulation Codes field in the Obligations table does not allow loose links, so Law/Regulation Codes will be blank in the Obligation record. | Add the new value as a record in the [Laws/Regulations](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/217743382) table. Then update the Obligation record to select the Law/Regulation Codes value. |

For more information about the obligation management-related tables, see the articles below.

- [Obligations Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/570163248)
- [Metadata Types Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050)
- [Screen Results Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434110)
- [Penalties/Remedies Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/217743409)
- [Laws/Regulations Table](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/217743382)