Contract obligations management is the part of the register that a summary never carries. A contract commits the company to deliverables, reports, notices, insurance certificates, audit rights and payments, each with a date and an owner, and a missed one is a breach whether or not anyone noticed. Contract compliance tracking is the same work seen from the other side: proving that the obligations were met, on time, when a counterparty or an auditor asks. Small legal teams keep obligations in an email thread or not at all. This page is about what obligation management records, why the obligations belong beside the contract they come from, and what the free legal contract lifecycle management sheet on this site does with them.
What an obligation is, and what has to be recorded
An obligation is anything the contract requires the company or the counterparty to do by a date: deliver, report, notify, insure, pay, allow an audit. The record for each is the contract it comes from, the clause, the party who owes it, the owner inside the company, the due date, and whether it was met. Contract obligation management is keeping that list current; contract obligations that live in the PDF are met by luck. On the worked example a contract carries 8 obligations and 2 are overdue, which is 25%, a figure the general counsel can raise with the owner this week rather than discover at renewal.
Why obligations belong on the contract register
Obligations management kept in a separate tracker drifts from the contract that created it: the contract is amended, the obligation is not; the contract expires, the obligation keeps generating reminders. On the register the obligation is a row under the contract, with the contract's own dates around it, so when the term ends or the renewal changes the value, the obligations move with it. That is also what makes contract compliance management answerable: the proof that an obligation was met sits beside the clause that required it.
The contract compliance checklist, and contract compliance tracking
A contract compliance checklist for a small legal team is short: are the obligations listed with owners and dates; is each one marked met, overdue or waived; is the evidence attached; are the counterparty's obligations to us tracked as well as ours to them; and is the overdue share read weekly. Contract compliance tracking is running that checklist on a schedule and keeping the answers. The free lifecycle sheet on this site takes the obligations a contract carries and how many are overdue and returns the share; the paid register keeps each obligation with its owner, date and evidence.
Questions people ask about contract obligations management
Whose obligations should be tracked, ours or the counterparty's?
Both. Ours are the ones a missed date turns into a breach; theirs are the ones that give the company a remedy it will never use if nobody noticed. The register holds each obligation with the party who owes it.
How often should obligations be reviewed?
Weekly for the overdue and the due-this-month, and at every amendment or renewal for the whole contract, because those are the moments obligations change. A fixed day and a short list is the whole process.
Does the free sheet on this site track obligations?
It takes the count carried and the count overdue for one contract and returns the share, beside the contract's own deadlines. Keeping each obligation with its owner, date and evidence is Clauselane Pro.