Compliance Obligation

Definition identifies the catalog duty; Tasks represent its occurrences and Registrations hold resulting identifiers. Subject is currently text. Generates Task is a stored flag and does not itself prove an automation creates tasks. The collection workflows do not implement compliance scheduling.

Use and boundaries

Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.

Related guide · All entities

Fields

Field	Storage	Source, options or boundary
Obligation #	Auto number	Generated by Airtable.
Subject	Text	Text reference; not a linked record.
Definition	Linked records	Compliance Definition
Requirement Source	Text	Stored value.
Cadence	Single select	Daily, Weekly, Biweekly, Monthly, Quarterly, Annual, On Demand
Start Date	Date	Stored value.
Achieved Date	Date	Stored value.
Priority	Single select	Urgent, High, Medium, Low
Compliance Status	Single select	Not Started, In Progress, Compliant, Expired, Waived, Not Applicable
Jurisdiction	Text	Stored value.
Evidence	Attachments	Stored value.
Applicability Evidence	Text	Text reference; not a linked record.
Generates Task	Checkbox	Stored value.
Registrations	Linked records	Registration
Tasks	Linked records	Task
Documented By	Linked records	Content
Tags	Linked records	op:tags · optional labels from the Core Tags catalog; classification only.

Example and maintenance

Illustrative example: one organization must renew a license, with a linked definition and supporting requirement source.

Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.