Contract obligation register

Purpose

Convert signed agreements into a usable register of who must do what, by when, under which trigger, and with what evidence. Capture operational duties alongside invoices, reporting, service levels, insurance, audit rights, renewal mechanics, and notices.

Scope

Read executed contracts, amendments, schedules, statements of work, order forms, service-level exhibits, insurance certificates, and the company's owner mapping. Register obligations for each party, including one-time milestones, recurring reports, payment dates, cure periods, renewal notice windows, and termination conditions.

Excluded: deciding legal enforceability, contacting counterparties, issuing notices, assigning an owner without a mapping, and monitoring an external system.

Data basis

• Signed agreement text and amendments with clause, schedule, page, and effective-date references.
• Contract inventory fields such as contract ID, counterparty, start date, end date, renewal type, and business owner.
• Owner map, obligation taxonomy, calendar convention, and notice lead-time policy.

Result

Create a persistent obligation register, a key-dates sheet, and an owner-assignment document. Each row contains contract ID, party, obligation, trigger, due rule, date or recurrence, consequence, evidence, owner, status, and citation.

Quality criteria

• Every obligation cites clause, schedule, page, and source document.
• Amendments override earlier wording only when their effective date and affected clause are explicit.
• Relative deadlines retain trigger text rather than becoming an invented date.
• Payment, reporting, SLA, insurance, renewal, and notice obligations have distinct categories.
• Unknown owner, cadence, date, and consequence values are explicit open points.

Instructions

Read the agreement hierarchy in the order specified by the contract: amendment, order form, statement of work, master agreement, then incorporated policy. Preserve exact trigger and recurrence language. Calculate a calendar date only when effective date, trigger date, calendar convention, and holiday rule are available. Assign an owner only through the supplied mapping; use unmapped otherwise. Treat conflicting clauses as two readings with citations.

Adapt before use

• Add the contract inventory schema, owner map, obligation categories, and calendar rules.
• Define which amendment hierarchy and policy documents control conflicting terms.
• Set status values, renewal alert windows, and required escalation roles.