---
title: "Obligations Table"
canonical: "https://help.agiloft.com/space/SD/570163248/Obligations+Table"
format: markdown
---
The Obligations table stores the obligations that AI extracts when you evaluate a contract with an Obligation Management screen. For details, see [Obligation Management](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/237240328).

# Record Creation

Users don’t typically create Obligation records. They’re automatically generated from [Screen Results](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434110) when obligations are extracted from contracts. Obligation records link to the related Screen Result, Screen Run, Contract, and Attachment records for the document that was evaluated. They also list the Topic (Obligation Type) type and Subtopic (Metadata Type).

The sections below describe the main features, action buttons, and fields in Obligation records.

## Set Subtopic

The Set Subtopic button is displayed if Subtopic is blank. This indicates the obligation was created from a screen result for a new or modified question, and there isn’t an exact match for Element Name in the Screen Result (Question Title in the screen) and a [Metadata Type](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050) record. 

You can click Set Subtopic to create a new Metadata Type record and populate Subtopic with that metadata type.

## Create Task

The Create Task button is always displayed. Clicking the button creates a [Task](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434285) record with a Task Category of Obligation and partially populates the new record with values from the Obligation. The new task is linked to the Contract the obligation is for. 

## Details and Metadata

The Details tab shows the Review Status of the Obligation. All AI-generated Obligation records are assigned a status of Not Reviewed. Once 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.

The rest of the obligation details and metadata fields are the responses to the prompts in the associated Obligation Management screen. The Metadata Type record for the obligation controls which of the standard fields are displayed. 

# Views

The out-of-the-box Obligations table includes the [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574). The Default View shows the Edit icon, View, ID, Contract ID, Obligation Exists, Topic, Subtopic, Question, Answer, Pinpoint Citation, Responsible Party, and Review Status fields. 

![Default View for the Obligations table](media://a3430157-976a-45d5-b3d4-3d2e51069fb0)

The table also includes a Related Table View that is used to display obligations in Contract records.

# Related Tables

The diagram below shows the default incoming table relationships and linked fields in the Obligations table.

![Diagram of the default table relationships for the Obligations table](media://df493e95-05f0-4662-9068-31a41fc4ab39)

# Fields

In addition to the [standard fields](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434023), the out-of-the-box Obligations table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Amount - Fixed | Floating Point | If Amount Type is Fixed, this field lists the fixed amount. |
| Amount - Percentage | Floating Point | If Amount Type is Relative, this field lists the amount as a percentage. |
| Amount Type | Choice: Fixed, Relative | The type of amount. Set by a rule.<br>- Fixed means an explicit amount was extracted from the contract.
- Relative means a proportional amount specified as a percentage was extracted from the Contract. |
| Answer | Text | The response to the question prompt in the screen. The value comes from the Summary field in the structured data output. |
| Attachment ID  
Attachment Title | Link to selected fields from other table: Attachments | The linked Attachment record. |
| Company Name  
Contract Amount  
Contract Title  
Contract Type  
Contract ID | Link to selected fields from other table: Contract | Lists details from the linked Contract. |
| Consequence | Text | The response to the Consequence prompt in the screen. It’s generally a summary of the consequence for failing to comply with the obligation terms. |
| Consequence Standardized | Short Text | The response to the Consequence Standardized prompt in the screen. Generally, this field contains the specific consequence, like a monetary amount or percentage. |
| Create Task | Action button | Creates a Task record and partially populates the new record with values from the Obligation record. The new task is linked to the Contract the obligation is for. |
| Currency Code  
Currency ID | Link to selected fields from other table: Currencies | The extracted currency code and ID. |
| Date Type | Choice: Fixed, Relative | The type of date. Set by a rule.<br>- Fixed means an explicit due date was extracted from the contract.
- Relative means the due date is specified as a timeframe, such as 30 days after the contract end date or 24 hours after a data breach. |
| Due Date | Date | If Date Type is Fixed, this field lists the obligation due date. |
| Due in Days | Integer | If Date Type is Relative, this field lists the number of days until the obligation is due. |
| Incoterms Codes | Multi-Choice: EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DPU, DAP, DDP, Other | The International Commercial Terms codes found in the contract. |
| Law/Regulation Codes | Link to single field from other table: Law/Regulation | The law and regulation codes found in the contract. |
| Mark Edited | Action Button | Changes the Review Status to Edited. |
| Mark Reviewed | Action Button | Changes the Review Status to Reviewed. |
| Minimum Coverage Amount | Floating Point | The minimum coverage amount identified in the contract. |
| Obligation Exists | Choice: Yes, No | Indicates whether the obligation exists. Managed by a rule that sets the value based on Summary Standardized and Consequence Standardized.<br>- The flag is set to No if both standardized fields are blank or if Summary Standardized explicitly returns No.
- In all other cases, the flag is set to Yes.<br>A hidden value of N/A is available in case you want to reconfigure the rule to avoid false positives. |
| Obligation Title | Compound | The name of the obligation. The title is set by combining the Contract ID, Topic, and Subtopic values. |
| Penalty/Remedy  
Penalty/Remedy ID | Link to selected fields from other table: Penalty/Remedy | The penalty or remedy identified in the contract. |
| Percentage Basis  
Percentage Basis ID | Link to selected fields from other table: Replacement Variable | The proportional reference point used to identify and interpret relative value expressions in the contract. |
| Processing Obligation Tag | Multi-Choice: Lawful Basis, Data Minimization, Purpose Limitation | If Subtopic Processing Target Fields includes Data Processing, this field lists the extracted obligation tag. |
| Question  
Screen Result Element Name  
Screen Result ID  
Pinpoint Citation  
Screen Status | Link to selected fields from other table: Screen Result | These fields display information from the Screen Result record for the obligation. |
| Related Tasks | Related Table: Tasks  
Saved Search: | Lists any Task records that are related to the obligation. |
| Reporting Frequency | Choice: Weekly, Bi-Weekly, Monthly, Bi-Monthly, Quarterly, Annually | If Subtopic Processing Target Fields includes Recurrence Frequency, this field lists how often the obligation recurs.<br>If you need additional options, you can change the prompt in the screen and edit or add to the choice list values. |
| Responsible Party  
Responsible Party ID | Link to selected fields from other table: Companies | The response to the responsible party prompt in the screen. |
| Review Status | Choice: Not Reviewed, Needs Review, Edited, Reviewed | Indicates whether a user has reviewed the obligation record. AI-generated Obligation records are assigned a status of Not Reviewed. Once a user reviews the record, they can change the status to Needs Review if they want another person to review it, Edited if they changed the record, or Reviewed if they approve the record. |
| Review&nbsp;Status | Link to single field from other table: HTML Status | This field is used for aesthetic purposes in Obligation table views to display HTML-formatted labels for Review Status values. |
| Review Needed | Action Button | Visible when Review Status is Not Reviewed. Changes the Review Status to Needs Review. |
| Reviewed/Edited By  
Reviewer ID | Link to selected fields from other table: Employee | Lists the name of the person who reviewed or edited the record. |
| Run Data Processing | Choice: Yes, No | System-managed flag that triggers a rule that processes the Summary Standardized and Consequence Standardized values into target fields. |
| Screen Run ID  
Screen Name | Link to selected fields from other table: Screen Run | Identifies the Screen Run record linked to this Obligation. |
| Set Subtopic | Action Button | Visible when Subtopic is empty, meaning there isn’t an exact match for the Element Name in the Screen Result (Question Title in a screen) and a Metadata Type record. Clicking the button creates a new Metadata Type record and populates Subtopic in the Obligation record. |
| Subtopic  
Subtopic ID  
Subtopic Processing Target Fields  
Subtopic Standard Fields Visibility  
Subtopic Timeframe Units | Link to selected fields from other table: Metadata Type | These fields display information from the Metadata Type record for the obligation. |
| Summary Standardized | Short Text | The response to the Summary Standardized prompt in the screen. Generally, this field contains the succinct version of the answer in Summary, such as Yes or No. |
| Timeframe | Floating Point | The timeframe extracted from the contract. |
| Timeframe Unit | Choice: Hours, Days, Weeks, Months, Quarters, Years, Percentage | If Subtopic Processing Target Fields includes Timeframe, this field lists the unit of time for the timeframe. |
| Topic | Choice: Confidentiality, Data, Delivery, Financial, Insurance, Performance, Regulatory, Termination | Describes the type of obligation. This value maps to the Obligation Type in the structured data output from Astra. If you want to extract a new type of obligation, you can update the Topic field in the [Metadata Types](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/511148050) table to add the new type to the choice list. |
| Trigger Type | Choice: Time-based, Event-based, Ongoing | If Subtopic Standard Fields Visibility includes Trigger Type, this field displays the response to the trigger type prompt in the screen. |

# Automation

This section describes the rules that are implemented for the out-of-the-box Obligations table. For details about rule configuration options, see [Rules](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714473) in the Help Guide.

- **Create: All Obligation Create actions (web, API)**: This rule runs when an Obligation record is created and performs the following actions:
  - Refreshes links to the related Screen Results and Metadata Type records.
  - Sets the Obligation Exists flag:
    - If Summary Standardized is No, it’s set to No.
    - If Summary Standardized and Consequence Standardized are “null” or empty, it’s set to No.
    - In all other cases, it’s set to Yes.
  - Sets the Number of Active Extracted obligations in the contract.
  - Sets the Run Data Processing field to Yes to trigger the Create/Edit: Run Data Processing rule.
- **Create/Edit: Run Data Processing (web, API)**: This rule runs when Obligation records are edited or created. It finds records where Run Data Processing is Yes and performs the following actions:
  - If Consequence Standardized isn’t null and Subtopic Processing Target Fields contains Amount, it sets the appropriate Amount Type and Amount - Percentage or Amount - Fixed values.
  - If Summary Standardized isn’t null and Subtopic Processing Target Fields contains Date, it sets the appropriate Date Type and Due in Days or Due Date values.
  - Sets the Processing Obligation Tag, Incoterms Codes, Law/Regulation Codes, Minimum Coverage Amount, Penalty/Remedy, Reporting Frequency, Timeframe, or Timeframe Unit values according to the Subtopic Processing Target Fields and Summary Standardized value.