Obligations

A signature starts the obligations, it does not end them. Docshark tracks what every signed agreement commits you to. Deliverables due, renewals approaching, deadlines that turn into breaches if nobody is watching.

What an obligation is

An obligation is a dated commitment tied to an agreement:

• Deliverables. Reports due monthly, milestones, submissions.
• Renewals. Auto-renewal windows, notice periods, contract end dates.
• Deadlines. Payment terms, SLAs, cure periods.
• Anything dated. A contract clause with a calendar consequence.

Each obligation records what is owed, when, and which agreement it came from. Linked back to the sealed document and its certificate.

Creating them

• From a completed envelope. Add obligations to any signed agreement: the deliverable, its date, who owns it.
• From Mako, the AI copilot reads a signed agreement and proposes its dated commitments, renewal windows, notice periods, recurring deliverables. As suggested obligations you confirm.

Watching them

Obligations surface before they bite:

• Due soon. Approaching deadlines land in the Inbox and fire OBLIGATION_DUE_SOON to webhooks.
• Overdue, missed dates are flagged as overdue, not silently passed, OBLIGATION_OVERDUE fires and the item stays red until resolved.
• The obligations view. Every tracked commitment across agreements, filterable by status and date.

States

Why it matters

The most expensive contract failures are not bad terms. They are missed renewals, silent auto-extensions, and deliverables nobody tracked. Obligations turn the signed PDF from a filing-cabinet artifact into a living list of what you owe and are owed.