Skip to main content

Obligation Properties

!

Release: Currently, there are eight default properties. With the July release, additional properties are being added and will be live on July 23rd. To learn more about the features included in our July release, refer to What's New in Ironclad: July 2026.

Summary

This article provides an overview of obligation properties. Obligation properties are the data points you use to create, track, and filter obligations throughout their lifecycle. Ironclad includes a variety of predefined obligation properties, and you can create additional properties in Data Manager when you need to track more information.

Use Case

At Classics Inc., a legal operations manager wants to track post-signature work in a consistent way. They use obligation properties to capture key details such as the obligation name, owner, due date, and related contract. This helps the team organize obligations, filter the dashboard, and review the right details at the right time.

Prerequisites

Features

Obligations, Data Manager

Permissions

What are obligation properties?

Obligation properties are the pieces of information you want to collect and track for each obligation. You use them when you create obligations, monitor them over time, and filter or sort them.

Some properties describe the obligation itself, such as its name or description. Others help you manage the work, such as the assignee, due date, and status. The Type property groups obligations into categories, which makes them easier to search, filter, sort, and manage in saved views.


How do obligation properties work with obligation types?

Obligation properties define which information is collected for an obligation type.

When you add properties to an obligation type, those properties become the fields users use when they create or manage obligations in that category. This helps you collect the right information for each type of obligation instead of using the same set of fields for every obligation.

For example, one obligation type might need a due date and assignee, while another might also need additional custom fields. For each obligation type, you can add and remove properties. While there are out-of-the-box properties, you can also create additional properties in Data Manager when the predefined set does not cover what you need to capture.


Out-of-the-Box Obligation Properties

Each obligation type includes a set of standard default properties. These standard properties no longer appear on the type configuration page, which now displays only type-specific properties. Refer to the tables below for a list of the standard default properties:

Field

Required

Description

Name

Yes

A short, recognizable title for the obligation. Ironclad recommends something unique and easy to identify.

Type

Yes

The category the obligation belongs to, such as Payment or Renewal Notice. Type controls which additional properties apply and makes obligations easier to search, filter, and group.

Contract

Yes

The contract the obligation is associated with.

Description

No

More detail about what the obligation requires.

Assignee

No

The person responsible for tracking the obligation.

Trigger

Yes

How the obligation occurs: One time, Recurring, Conditional, or Perpetual. This determines which trigger-specific fields apply.

Status

Yes

Where the obligation stands, such as Not Started, In Progress, or Completed.

Due date

No

The date the obligation needs to be completed.

Completed date

No

The date the obligation was completed or fulfilled.

Responsible party

No

Which side is responsible for performing the obligation: your company or the counterparty.

Trigger-Specific Properties

When Trigger = Recurring

Field

Required

Description

Frequency

Yes

How often the obligation repeats: Daily, Weekly, Monthly, or Yearly. Use Repeat every to set the interval, for example every 2 months.

Start date

Yes

The date the recurring schedule begins.

Ends

No

When the schedule stops generating obligations: After a number of occurrences, On a specific date, or at Contract end.

Due date offset and due date offset anchor

No

When each occurrence is due relative to its period, for example “5 days before the end of the quarter.”

When Trigger = Conditional

Field

Required

Description

Condition description

Yes

A description of the event or condition that creates a new obligation.

Due date after condition is met

No

When the obligation is due once the condition occurs.

Resources

Explore articles, courses, and support options to get the most out of Ironclad.

Help Center

Academy

  • No relevant resources at this time.

Support

Did this answer your question?