Skip to content
Extract key testimonyContract

Contract Obligations Extractor

Inventory every obligation, deadline, notice requirement, and condition precedent in the contract — who owes what, triggered by what, with section cites.

Report a correction

Worked example · Synthetic fictional details

Sample prompt

Synthetic example: The names, dates, case details, and issues below are fictional CasePrompts sample values, not client data or evidence from a real matter. They demonstrate the prompt format, not the accuracy of any AI model's output.

Preview the complete sample prompt
Customize in builder
CONTEXT:
You are a litigation support analyst assisting in-house counsel in a commercial construction dispute matter. The attached document is the operative contract, including any amendments and exhibits provided. The disputes that matter concern: delay damages; change-order approval; termination for convenience.

INSTRUCTIONS:
Inventory the instrument completely:
1. OBLIGATIONS — every promise to perform: who owes it, to whom, the performance required, and any stated standard.
2. DEADLINES — every date or period: what is due, when, and how the period is computed if the contract says.
3. NOTICE REQUIREMENTS — every provision requiring notice: trigger, deadline, required form and content, and the address or method specified.
4. CONDITIONS PRECEDENT — events that must occur before a duty arises, and whose duty they condition.
5. TERMINATION & REMEDY PROVISIONS — rights to terminate, cure periods, and stated consequences of breach.
Use the contract's own defined terms, capitalized as defined. Where provisions cross-reference each other, follow the chain and note it.

TEMPLATE — format your output exactly as follows:
## Obligations
| # | Obligor → Obligee | Performance required (verbatim key language) | Standard / qualifier | Cite |
|---|---|---|---|---|
## Deadlines & periods
| What is due | When / period | Computation notes | Cite |
|---|---|---|---|
## Notice requirements
| Trigger | Deadline | Form & content required | To whom / method | Cite |
|---|---|---|---|---|
## Conditions precedent
| Condition | Whose duty it conditions | Cite |
|---|---|---|
## Termination & remedies
Bullet list with cites.

EVIDENCE REQUIREMENTS:
For every finding, cite the exhibit or Bates number and page; if neither exists, cite the PDF page number. Quote operative language verbatim wherever a duty, deadline, or condition turns on wording. Do not interpret ambiguous provisions — flag them under a final heading "Ambiguous — attorney review" with both readings. If a referenced exhibit or amendment is not attached, list it as missing rather than assuming its contents.

If the provided record does not support a requested finding, write "not found in the record." Do not infer or fill gaps from outside knowledge.
The scope is limited to the requested task, stated issues, and provided record. Do not introduce outside subjects or sources.
A human reviewer must verify every material statement and citation against the source record before relying on or sharing the output.

AI output is a starting point, not work product. Verify every citation against the record before you rely on it, file it, or send it.

What you'll fill in

  • 01Your role
  • 02Case typee.g., "trucking liability," "first-party property," "medical malpractice"
  • 03Key issue(s) — 1 to 3e.g., "vehicle speed at impact; brake maintenance; visibility"

Pro tip Sort the deadlines table chronologically and it doubles as your breach timeline scaffold.