--- sourceDocument: Australia Employee Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/employee-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Employee Service Management ft:clusterId : - emplsm bundleId : - emplsm workflow : - Employee --- # Obligation form # Obligation form {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read The obligation form provides the details to create or modify an obligation record in Obligation Management. {#cncore-obligation-form__table_jb1_f2v_rcc__entry__2} | Field | Description | |-|-| | Number | An auto-generated unique number for the obligation record. | | Contract | Unique number of the contract repository record. | | Name | Name of the obligation. | | Category | Category of the obligation. The available values are: * Operational or service delivery * Legal * Commercial * Compliance * Governance {#cncore-obligation-form__ul_imq_bjs_2dc} | | Subcategory | Subcategory of the obligation. The available values depend on the selected category. | | Active | Option to activate the obligation. If a recurring schedule has been defined for obligation tasks, activating the obligation creates obligation tasks based on the defined schedule. | | Approver group | Group whose members have appropriate permissions to approve or reject an obligation task. | | Approver | Member of the approver group assigned to approve the obligation tasks. | | Task assigned to | User to whom the obligation tasks will be assigned by default. This value can be overridden by assigning a user once the obligation task is created. A notification email is sent to the assigned user. | | Start date | Date from which the obligation will be in effect. | | End date | Date on which the obligation ends. | | Instructions | Actions that must be performed as part of the obligation. | | Description | Extract from the contract that describes the obligation. | | Schedule type | Schedule type of the obligation tasks. Adhoc : Obligation must be fulfilled once or at irregular intervals. You must create obligation tasks manually. Recurring : Obligation must be fulfilled regularly at a defined interval. Obligation tasks are automatically created based on the interval specified in the Repeats field and according to the value in the Task creation lead time (days) field. | | Repeats | This field appears only when Recurring is selected from the Schedule field. Note: For monthly or yearly repeats, the first obligation task is due on the selected date and recurring obligation tasks are due on the same day of the month or year as the initial value. For example, if you select 2024-08-10 as the Due date value, the first obligation task will be due on the 10th of August 2024 and the subsequent tasks will be due on the 10th day of the month in the specified interval or on that date every year. If you select the 31st day of a month as the Due date value, the obligation tasks for months with less than 31 days will be due on the last day of that month. The available values are: * Daily - Obligation tasks are created daily and are due every day between the start date and end date of the obligation record. * Weekly - Obligation tasks are created every week. The value in the Repeats field that appears when this value is selected determines the days of the week when the obligation tasks should be fulfilled. * Monthly - Obligation tasks are created once a month and are due on the day of the month specified in the Due date field that appears when this value is selected. * Every three months - Obligation tasks are created every three months and are due on the day of the month specified in the Due date field that appears when this value is selected. * Every six months - Obligation tasks are created once a month and are due on the day of the month specified in the Due date field that appears when this value is selected. * Yearly - Obligation tasks are created once a year, with the first obligation task being due on the selected date and recurring obligation tasks due on the same date every year. {#cncore-obligation-form__ul_usq_vhv_cdc} | | Task creation lead time (days) | This field appears only when Recurring is selected from the Schedule field. It determines the number of days before the task's due date when the obligation tasks should be automatically created. | [Table 1. Obligation record form] {#cncore-obligation-form__table_jb1_f2v_rcc} **Related concepts** * [Contract Management Pro glossary](https://www.servicenow.com/docs/nu5AY2cfCyiW9R2SChx_lg#contract-management-pro-glossary "Learn about the terms and concepts used in Contract Management Pro.") **Related reference** * [Components installed with Contract Management Pro](https://www.servicenow.com/docs/KgVuwhJbpy90XDqjViR~6g "Several types of components are installed with activation of the Contracts Core application that includes the components for Word Document Templates, including tables and user roles.") * [Components installed with Contract Workspace](https://www.servicenow.com/docs/rF153GaFzXx6xtcGOdukkw "User roles are installed with activation of the Contract Workspace plugin.") * [Components installed with Analytics Pack for Contract Management Pro](https://www.servicenow.com/docs/0Qen9j3lDlxRnWT0ZU7dlA "Several types of components are installed with activation of the Analytics Pack for Contract Management Pro plugin, including user roles and scheduled jobs.") * [Contract request State and Contract document status in Contract Management Pro](https://www.servicenow.com/docs/Q828Fv9YqdZ5hRU64nL_lg "Contract requests follow a specific life cycle and move through a series of states in Contract Management Pro. The contract request state and the contract document status are displayed in the State and the Contract status fields on the request record.") * [Signatory roles](https://www.servicenow.com/docs/iR83A81eN5IQkswsnqahvA "Signatory roles define how each participant interacts with a contract document during the signature workflow.") * [Clause Variation form](https://www.servicenow.com/docs/Zp98kOGZWiQraEX2eMAz_w "Use the Clause Variation new record form to create or modify a clause variation.") * [Contract Configuration form](https://www.servicenow.com/docs/u1t3HrYPiEDosw0f5Rg6FA "Use the Contract Configuration New Record form to create or modify a contract configurations.") * [Properties installed to configure expiry notifications](https://www.servicenow.com/docs/x0rLZLg17nk~phgz_g3rKQ "There are several properties related to Contracts Core that can be used to configure the number of days before which expiry notification should be sent and the generation of audit certificate.") * [Properties installed to configure contracts integrations](https://www.servicenow.com/docs/FNJFK1dQcV1WleM8jS1GUQ "There are several properties that you can use to configure integrations for Contract Management Pro.") * [Expiring Contracts Condition form fields](https://www.servicenow.com/docs/SQD6iQOyowP76sjMmhWHdQ "The Expiring Contracts Condition form is used to create a rule or update an existing rule.") * [Action assignment form](https://www.servicenow.com/docs/wKTKudUZPnfE3MgbjTGYxw "Learn about the fields of the Action Assignment form. Use this form to add the New action button to your workspace.") * [UFX Add on Event mapping form](https://www.servicenow.com/docs/gvsivMFRgB4W43svB~o8kw "The UFX Add on Event mapping form to configure the display of declarative action in your application.") * [Obligation Management notifications](https://www.servicenow.com/docs/efv0aYTNkLewTgFgjJimAg "Obligation Management uses email notifications to notify obligation fulfiller and obligation users when an obligation task is created, assigned, submitted, approved, or rejected.") * [Contract Management solutions](https://www.servicenow.com/docs/OhibclvKMo3sMhnSqNEnCA "Explore the differences between the different contract management solutions offered in ServiceNow - ITAM Contract Management, (Deprecated) Legal Simple Contracts, and Contract Management Pro (CM Pro)")