How to Extract Key Dates, Obligations and Amounts From a Contract (Free)

Extracting key terms means pulling the operative facts out of a contract, the effective date, the term and renewal window, payment amounts and due dates, milestones, caps, notice addresses, governing law, and putting them somewhere you can actually track: a spreadsheet, a tracker, a calendar. A signed contract sitting in a folder protects nobody. The one thing almost everyone gets wrong: they extract what is easy to find, a bolded "Effective Date" field, a rupee figure in a payment clause, and miss what is phrased indirectly, an obligation buried in a sentence starting "The Provider shall..." three pages later, or a date that is never written as a date but has to be computed from another clause. This guide (published by Adira, which makes contract review and CLM software that does exactly this extraction automatically, so we have a commercial stake in you finding it useful, but the method works whether or not you use our product) gives you the manual checklist, the AI-assisted method with its verification pass, and a runnable test to prove your tracker is actually right.

Why extraction is harder than a Ctrl+F

A contract is not a form. The eight or ten facts you actually need to run the deal, when it started, when it ends, who owes what and by when, are scattered across defined terms, cross-references, schedules, and conditional clauses, not laid out in one table. Three things make plain keyword search unreliable on its own:

1. Obligations are phrased as duties, not lists. A payment obligation rarely says "Amount: Rs 5,00,000." It says "the Client shall pay the Fees set out in Schedule 1 within thirty (30) days of invoice," and the number lives in a schedule, referenced, not repeated.
2. Dates are often computed, not stated. "Within thirty days of Effective Date" is a formula. You will not find "15 October 2026" anywhere; you have to calculate it, and if the Effective Date is itself conditional (signature plus a deposit), the starting point moves.
3. Defined terms hide the real subject. A clause might say "the Supplier shall deliver the Deliverables by the Milestone Dates," and none of those capitalised terms mean anything until you chase their definitions, usually in a schedule.

A naive extraction, by a person skimming or a tool doing a shallow keyword match, reliably catches the obvious fields and reliably misses the conditional ones. That gap is where costly slips happen, most often a missed non-renewal notice date, which is why it gets its own section below.

The manual checklist: what to hunt, and the exact words to search for

Work through the contract once for each category below. Use Ctrl+F (or Cmd+F) with these search terms, and for each hit, note the clause number, not just the fact, so you can trace back later.

Effective date and parties Search: "Effective Date", "commencement", "shall commence", "dated as of". The Effective Date sometimes differs from the signature date, especially where the contract is conditional on a later event (an approval, a deposit, a third signature).

Term, renewal, and the notice-to-avoid-renewal deadline Search: "Term", "renew", "auto-renew", "evergreen", "expiry", "notice of non-renewal". This is the single highest-value search in the whole exercise. Do not just note the renewal date, note the notice window before it, since that earlier date is the one that actually controls your exit. Our guide on the auto-renewal (evergreen) clause walks through why the notice window, not the renewal date, is the trap.

Payment amounts and due dates Search: "shall pay", "Fees", "invoice", "due", "net 30" (or whatever number), "within [X] days". Amounts are frequently in a schedule, not the body, so search the schedules separately. If your counterparty is a registered micro or small enterprise, the payment term cannot lawfully exceed 45 days regardless of what the clause says, under Section 15 of the MSMED Act, 2006, covered in our MSME 45-day payment guide.

Milestones and deliverables Search: "Milestone", "Deliverable", "delivery date", "acceptance", "completion date". Milestones are often tied to a schedule with its own numbering, separate from the main clause numbers, so track both references.

Caps and thresholds Search: "aggregate liability", "shall not exceed", "cap", "liquidated damages", "penalty". A cap is one of the few numbers that genuinely matters as a standalone figure, so verify it appears exactly once; contracts amended by email sometimes carry two different cap figures in different places.

Notice addresses and method Search: "Notices", "shall be delivered to", "in writing to". This clause decides whether your non-renewal notice, or any other notice, actually counts. An email to the wrong address, or the right address by the wrong method (registered post only, for instance), can mean a notice was never validly given at all.

Governing law and dispute resolution Search: "governed by", "governing law", "jurisdiction", "arbitration", "courts of". Note both the governing law (which country's or state's law interprets the contract) and the forum (where a dispute is actually heard); they are sometimes different.

AI extraction, with a verification pass

Do the manual checklist once, by hand, on one contract first, so you know what "done well" looks like. From there, AI extraction is a legitimate speed-up for volume, not a replacement for that first pass.

A workable prompt: "List every date, payment amount, and obligation in this contract. For each item, give the exact clause number and quote the sentence it is based on. If a date or amount is computed from another clause rather than stated directly, show the calculation. If you are not confident an item is complete, say so instead of guessing."

That last instruction matters most. An AI extraction tool, like a person skimming, is tuned to find what looks like the field it expects, and will confidently return a term it half-found rather than say "not stated." Verify every AI-extracted row the way you would a junior colleague's first draft: open the clause it cites and confirm the sentence actually says what the tool claims, at minimum for every row involving money or a deadline.

The runnable test: build a one-row obligations table

Before you trust any tracker, whether built by hand or by AI, run this test on a single row.

Pick one payment obligation from the contract. Build a table with these columns: Obligation | Amount | Due date | Clause number | Exact quoted sentence. Fill in every column, then check each cell against the clause it claims to come from. If the amount cell says "Rs 5,00,000" but the clause only says "the Fees set out in Schedule 1," your tracker has a broken link, the real number lives in the schedule, and the row is one reference short of being checkable. Fix the chain until every cell traces to an actual sentence. Do this once, properly, for one obligation, and you will see immediately whether the rest of your extraction is trustworthy or just looks tidy.

Why a missed date is the costliest slip

Of everything on this checklist, the notice-window deadline before an auto-renewal is the single most common expensive miss, because it does not look like a deadline. The renewal date itself is easy to find and calendar. The date that actually matters, 30, 60, or 90 days earlier, when your right to say no expires, is buried inside the renewal clause's own sentence, and reviewers routinely catalogue the renewal date while skipping the window that precedes it, which is backwards: by the time the renewal date arrives, the window has already closed. See our auto-renewal notice-window guide for the mechanics.

The Indian position: why some dates and amounts will never show up in a search

Two provisions of the Indian Contract Act, 1872 explain why a chunk of the important facts in a contract are structurally invisible to a keyword search.

Section 46 governs what happens when a contract does not specify a time for performance:

"Where, by the contract, a promisor is to perform his promise without application by the promisee, and no time for performance is specified, the engagement must be performed within a reasonable time." Source: Section 46, Indian Contract Act, 1872 (Indian Kanoon)

The explanation adds that what counts as "reasonable" is a question of fact in each case. A contract can validly impose a real deadline without ever writing a date, and no Ctrl+F will surface it, because there is no string to find. When your checklist turns up an obligation with no stated timeframe, do not record it as having no deadline; record it as governed by Section 46's "reasonable time" standard, and flag it for a person to judge, since a tracker field that says "none" is actively misleading.

Section 29 does the equivalent job for amounts:

"Agreements, the meaning of which is not certain, or capable of being made certain, are void." Source: Section 29, Indian Contract Act, 1872 (Indian Kanoon)

The section's own illustrations are instructive here: a sale of "one thousand maunds of rice at a price to be fixed by C" is not void for uncertainty, because the price is capable of being made certain, even though no rupee figure appears in the clause. A payment clause that says "Fees shall be as set out in the applicable Order Form" behaves the same way: legally certain, extraction-wise invisible, because the number lives one document away. Section 74 covers the flip side, a stated ceiling on damages: it entitles the non-breaching party only to "reasonable compensation not exceeding the amount so named," so even a cap stated as a number is a ceiling, not an automatic payout. Source: Section 74, Indian Contract Act, 1872 (Indian Kanoon). The lesson for a tracker: a fee or cap defined by cross-reference or formula is not a gap, it is a deliberately certain-but-indirect term, and your extraction has to follow the reference rather than stop at the sentence with no number in it.

Red flags in your own extraction

Normal	Red flag	Why it matters
Every row in your tracker has a clause number you can point to	A row has an amount or date with no clause reference	You cannot verify, or defend, a fact you cannot trace back to the document
Obligations phrased as "shall pay / shall deliver / shall provide" are all captured	Only headline clauses (Payment, Term) were searched, sentences inside other clauses were skipped	Real obligations routinely sit inside indemnity, warranty, or general clauses, not just the clauses named for them
A "reasonable time" or formula-based amount is flagged for human judgement	It is recorded as "no deadline" or "amount not specified"	Section 46 and Section 29 both treat these as legally real, just not literally written; marking them blank hides a live obligation
The renewal notice-window date is calendared separately from the renewal date itself	Only the renewal or expiry date is tracked	The notice window, not the renewal date, is when your exit right actually expires
Defined terms (capitalised words) are chased to their actual definitions	Capitalised terms are read at face value without checking the definitions clause	A term like "Confidential Information" or "Deliverables" can be defined far more narrowly, or broadly, than its plain English reading
Every schedule and annexure was searched, not just the main body	Only the numbered clauses were checked; schedules were skimmed or skipped	Amounts, milestone dates, and price lists are routinely moved into schedules precisely so the main body reads cleanly

Bad extraction row → better extraction row

Bad: "Payment: Rs 5,00,000, due within 30 days."

What is wrong: no clause number, so nobody can verify it; states a fixed number even though the actual clause may reference a schedule that could later be amended; and "30 days" with no anchor, from signature, from invoice, from delivery, is meaningless without knowing what it counts from.

Better: "Payment obligation (Clause 4.1, amount per Schedule 2, Row 3): Client shall pay Rs 5,00,000 (per Schedule 2) within thirty (30) days of the date of the Provider's invoice (Clause 4.1, second sentence). Invoice trigger: delivery of Milestone 2 (Clause 6.2). Verified against document on [date]."

What changed: every fact carries a clause reference; the 30-day period is anchored to a specific trigger (invoice date) instead of left ambiguous; the chain from milestone to invoice to payment is shown, not assumed; and a verification date shows when the row was last checked, since contracts get amended.

Privacy: where you do this extraction matters

Most contracts you extract terms from are confidential, an NDA, a vendor deal, an employment agreement. Pasting the full text into a public AI tool, or uploading it to a random online extraction service, sends that document to a third party's servers, sometimes for training, depending on its terms. Do the manual checklist pass locally, in whatever reader you already have. For the AI-assisted pass, prefer a tool with a clear no-training commitment, and check its data-handling terms before pasting anything sensitive. You can also do the highlighting and clause-by-clause markup entirely in the browser, without uploading the file anywhere, using Weave.

Track it forward, not just once

A one-time extraction is only half the job; the real value is tracking these dates and obligations forward so a notice window or milestone surfaces as a reminder before it lapses, not after. See our companion guide on tracking contract obligations and renewals for turning a static extraction table into an ongoing calendar.

FAQ

Can I trust an AI tool to extract dates and amounts without checking its output? No. Verify every row involving money or a deadline against the exact clause it claims to cite. AI extraction tools are tuned to find the field type you asked for and often return a confident best guess rather than say a term is not stated, so an unverified table can look complete while quietly being wrong.

Why does a date sometimes not appear anywhere in the contract even though a deadline clearly exists? Under Section 46 of the Indian Contract Act, 1872, a contract can validly require performance "within a reasonable time" with no date stated at all. That standard is enforceable even though no keyword search will surface it, so treat an obligation with no stated timeframe as needing a person's judgement, not as having no deadline.

My contract's payment clause has no rupee figure in it. Is that a problem? Not necessarily. Under Section 29, an amount "capable of being made certain," a price set by a formula, a schedule, or a third party's determination, is legally certain even without a number in that sentence. Follow the cross-reference to where the figure lives instead of treating the clause as incomplete.

What is the single highest-value item to extract first if I only have time for one thing? The non-renewal notice deadline, if the contract has an auto-renewal clause. It is the date most commonly missed, because reviewers naturally track the renewal date instead of the earlier window that controls whether renewal can be stopped at all.

Should I extract terms from a scanned or image-only PDF the same way? Run OCR first so the document is searchable text; a Ctrl+F checklist does nothing against an image. See our guide on turning a scanned contract into searchable text first.

This guide gets you to a method for extracting and verifying the operative facts in a contract. It does not tell you whether a specific clause's amount or deadline is enforceable as you have read it, that depends on the exact wording and the facts of your situation, and is not legal advice. Talk to a lawyer before you rely on an extracted figure or date in a live, high-value contract.