Everything your contracts require of you, and the exact words that require it.

ClauseClock reads your vendor agreements and finds the deadlines, rights and money buried in them. Every finding shows the clause it came from. When a contract doesn't support an answer, it says so instead of guessing.

Upload a contract See it working →

What it catches

Nine kinds of contract terms ClauseClock watches.

Most of these never make it onto a calendar, because nobody re-reads a signed agreement until something has already gone wrong.

Renewal and non-renewal deadlinesAuto-renewal dates and the last day to stop one
Notice requirementsHow much warning is owed, in what form, to whom
Price increasesScheduled uplifts, indexation, and caps on them
Termination rightsWhen you may exit, for cause or for convenience
Fees and penaltiesLate charges, early-exit costs, minimum commitments
Rebates and refundsMoney owed back to you, and the window to ask
WarrantiesCoverage periods and what voids them
Service creditsCredits owed after service failures, and the window to claim them
DisputesEscalation steps and the time limits on each

A finding

Every date traces back to the sentence that produced it.

Nothing below is summarised or restated. The clause is quoted as written, and each value is derived from it.

Vendor Services Agreement — Meridian Supply Co. · § 4.1 Term and Renewal · page 3

“This Agreement shall commence on December 1, 2025 (the “Effective Date”) and shall continue for an initial term of three (3) years. This Agreement shall automatically renew for successive one (1) year terms unless either party provides written notice of non-renewal not less than sixty (60) days prior to the end of the then-current term.”

Effective date: December 1, 2025
Initial term: 3 years
Term ends: November 30, 2028
Renews: December 1, 2028
Notice counts back from: End of term
Notice period: 60 days
Notice deadline: October 1, 2028

The anchor is classified from the quoted phrase, then the date is computed in Python from that anchor. It is not inferred by a language model. ClauseClock asks you to confirm a finding before it starts tracking the date.

How it works

Nothing gets tracked until you have seen where it came from.

Upload your agreementsVendor contracts, amendments, and the signed versions of both
Findings surface with their sourceEach one carries the clause, the page, and the derivation
You verify before anything is trackedConfirm, correct, or dismiss — ClauseClock does not act on its own reading
The Action Center shows what is requiredWhat is owed, to whom, in what form, and by when
You log the action and attach evidenceThe notice you sent, fingerprinted when it is filed
The outcome is recordedA closed record of what the contract required and what you did

Why the dates hold

A wrong date is worse than no date.

Dates are computed, not estimated.Once the anchor and the notice period are read from the contract, the arithmetic runs in Python. The same inputs always produce the same date.
Every finding carries its source.The clause is stored verbatim and matched against the document it came from, so you can check any value against the page it was read from.
Unclear contracts get a refusal, not a guess.If the effective date is missing, or the language does not establish what the notice period counts back from, ClauseClock declines to produce a deadline and tells you what it needs.

See a refusal in the worked example →

Start with one contract.

Upload a vendor agreement and see what ClauseClock finds in it — and what it will not claim to know.

Upload a contract

ClauseClock is not a law firm and does not provide legal advice. All data and examples on this page are synthetic demonstration values.