A contract obligation is a duty that a party must perform, refrain from performing or satisfy under an agreement. It may concern payment, delivery, service, notice, confidentiality, compliance or another promised outcome.
What information defines an obligation?
- Responsible party and beneficiary
- Required action or restriction
- Trigger, due date or frequency
- Conditions, dependencies and evidence
- Remedy or consequence for nonperformance
- Amendment, expiry or survival treatment
How should obligations be managed?
Extract obligations from the governing version, assign accountable owners and connect each one to tasks and evidence. Monitor changes so an amended term replaces rather than competes with the prior obligation.
Obligation vs. deliverable
A deliverable is a specific output to be provided. An obligation is broader and can include ongoing conduct, payment, cooperation or restrictions. Delivering a file may satisfy one obligation while service-level or confidentiality duties continue.
What counts as evidence?
Evidence can include an accepted deliverable, payment record, notice receipt, service report or approval. The evidence should show the relevant version, party, date and scope rather than merely indicate that someone marked a task complete.
