The obligation register: 5 attributes an entry cannot work without
In short
An obligation register is a list of commitments a business has to perform or enforce, and a line on it is only workable if it carries 5 attributes: who owes it, what triggers it, whether the deadline is absolute or relative to an event, who inside the business owns delivery, and what counts as evidence it was done. Missing any one turns the entry back into a clause summary.
Key takeaways
- A register holds commitments to perform, not summaries of clauses; the difference is whether a line can be worked.
- 5 attributes make an entry actionable: obligor, trigger, deadline basis, internal owner, evidence of performance.
- Deadlines are absolute, relative to an event, or recurring, and the 3 need different fields and different alerts.
- Conditional obligations fail silently because nothing in the estate records the trigger that should start them.
An obligation register is the list of commitments a business has to perform or enforce under its contracts. It is not a list of clauses, and the distinction is practical: a clause summary says what the agreement says, while an obligation entry tells a named person what to do, by when, and what proves they did it.
5 attributes carry that difference. An entry missing any of them is a sentence someone will have to re-read the contract to act on, which is the exact work the register was built to remove.
The 5 attributes, and what fails without each
| Attribute | The question it settles | What fails without it |
|---|---|---|
| Obligor | Which party owes this, us or them | Our duties and our rights sit in one list, so neither gets worked |
| Trigger | What starts it: a date, an event, or a condition | The entry exists but nothing ever fires it, and it is discovered at breach |
| Deadline basis | Absolute date, offset from an event, or a recurring interval | A stored date silently detaches from the event it came from |
| Internal owner | Which named role performs or enforces it | Legal holds a list nobody outside legal has agreed to act on |
| Evidence of performance | What closes it, and where the artefact is filed | Closure records an intention, and cannot be shown to an auditor |
Obligor looks trivial and is not, because the counterparty on the page and the legal entity in your systems are often different records — the resolution problem in one counterparty appearing under 9 names. A duty owed by a subsidiary since sold is a different exposure from one owed by the group.
One-off, recurring and conditional are 3 different records
- One-off. A single act with a single deadline: deliver the implementation plan within 30 days of commencement. The deadline is an offset, so the register keeps the anchor date as well as the result — why effective, execution and commencement dates cannot be one field.
- Recurring. A repeating act on an interval: a quarterly service report, an annual insurance certificate. The entry needs a schedule and a horizon, and each occurrence its own closure and evidence — a single closed flag on the parent hides 3 missed quarters.
- Conditional. An act owed only if something happens: notify within 5 business days of a security incident, seek consent before subcontracting. There is no date until the condition occurs, which is why this shape fails differently from the other 2.
Conditional obligations fail because nothing records the trigger
A missed one-off obligation shows up as an overdue line. A missed conditional obligation shows up as nothing at all, because the register is waiting for an event no system told it about. The failure is not in the tracking; the trigger has no observer.
- Name the system that would know. For each conditional obligation, write down which system of record — the incident tool, the procurement system, the payroll ledger — would first learn the condition occurred.
- Wire the observable ones. Where a system knows, take the event from it rather than asking a person to remember that a contractual duty attaches.
- Attest the rest on a cadence. Where nothing knows, turn the condition into a periodic question to the owner: has this happened since we last asked. Weaker than an event feed, far stronger than silence.
- Review the never-fired. A conditional obligation that has not fired since creation is either dormant or unwired, and only a person can tell which. Put that list to the owner quarterly.
What closing an entry actually requires
Closure needs a state and an artefact. The states worth distinguishing are performed, waived, superseded by amendment, and expired with the agreement — because 3 of those 4 mean the duty ended without anyone doing anything. The artefact is whatever you would produce if the counterparty said it never arrived: the report, the certificate, the sent notice.
Two upstream facts shape the entries before the register sees them. Obligations arrive from a family of documents rather than one file, so an entry has to know which instrument in the parent, the child and the amendment it belongs to. And the obligation you end up with is whichever rung was accepted, which is why fallback ladders inside a negotiation playbook map onto the register's future contents.
A register that cannot say who owes it, what starts it, who does it and what proves it was done is an index of the contract, not a record of the business.
The build implication is small and unglamorous: model the 5 attributes as required fields, model recurrence as occurrences rather than a flag, and refuse to let an entry close without an artefact reference. That is ordinary MVP and product build work. This page sits in contract lifecycle and obligations, part of legal technology software.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is an obligation register in contract management?
It is the list of commitments a business must perform or enforce under its contracts, held as workable entries rather than clause summaries. Each line names the party that owes the duty, what triggers it, how its deadline is derived, which internal role delivers it, and what artefact closes it. Anything less sends the reader back to the contract.
What is the difference between a recurring and a conditional obligation?
A recurring obligation has a schedule and comes due whether or not anything happens; a conditional one has no date until a triggering event occurs. They fail differently: a missed recurring obligation appears as an overdue occurrence, a missed conditional one appears as nothing, because no system told the register the condition had happened.
Why does an obligation need an owner inside the business?
Because legal negotiates the commitment and rarely performs it. Delivery sits with the team that runs the service, holds the insurance or files the report, and an entry without a named internal role is a list legal maintains and nobody has agreed to act on. Name a role rather than a person, so the entry survives the individual leaving.
What counts as evidence that an obligation was performed?
Whatever you would produce if the counterparty said it never happened: the delivered report, the insurance certificate, the acknowledgement of a notice, the signed acceptance. A closure flag without the artefact records an intention. Distinguish performed from waived, superseded and expired too, since 3 of those 4 mean nobody did anything.
- obligation register
- contract management
- data model
- compliance
The work behind this page
Builds from our portfolio that this page draws on.
Brief Forge
Contract review AI for solo lawyers and small firms — extract, score, and redline contracts in minutes.
Legal TechAI Lease Management
AI-powered commercial real estate lease management for multi-brand operators — automates lease data extraction, obligation tracking, and portfolio intelligence.
Real EstateAskVault
An AI internal knowledge-search platform that answers employee questions from your own docs — grounded in citations, with knowledge gaps surfaced and deflection tracked.
Productivity AIRead next
- Auto-renewal: alert on the notice deadline, not the renewal dateThe date printed in the contract is the last date anything can be done about it. The date worth diarising sits 3 subtractions earlier.definition
- Three dates a contract record keeps confusing, and what each one governsA repository with one date field has already chosen which of three questions it can answer, usually without noticing that it chose.definition
- Contract families: the parent, the child, and the amendment on bothA parent field expresses one relationship of one kind at one moment. Real contract families need directed edges carrying a type, a date and a scope.definition
- Everyone knows the agreement exists and search will not return itA known agreement that will not surface has one of four causes, and re-indexing the estate fixes exactly one of them. Four probes, in order, tell you which.diagnostic
- One counterparty, nine records, and never the whole relationshipAsk what you have with a supplier group and the repository answers with half of it. Some near-duplicate records are typing errors; some are different legal persons.diagnostic
- The renewal alert fired on time and the notice window had already closedThe alert was accurate, timely and useless. It counted back from the wrong date, and it treated a decision that takes six weeks as something a person does on the morning they are told.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation