Contract Obligations Extractor
Inventory every obligation, deadline, notice requirement, and condition precedent in the contract — who owes what, triggered by what, with section cites.
By practice
Will and trust contests, capacity and undue influence, guardianship, and fiduciary accountings — element-driven work for a probate court that sits without a jury. Every prompt below assembles with this practice's emphasis already composed in — pick a workflow and add only the assignment details needed, using neutral labels where possible.
Practice workflow set
The configured probate & estate litigation lens adds this practice context to the template: This work product supports a probate or estate dispute — a will or trust contest, a testamentary-capacity or undue-influence question, a guardianship, or a fiduciary-duty and accounting matter — tried to a probate judge rather than a jury.
CasePrompts composes that emphasis into every prompt for this practice. Here is one complete, copy-ready example: the “Map the will or trust's terms and duties” workflow using contract as the source type, with the probate & estate litigation emphasis already built in. It pastes into any AI tool as is.
Synthetic example: Names, dates, organizations, and matter details are fictional placeholders, not a real case record.
CONTEXT: You are a litigation support analyst assisting probate litigation counsel in a will contest and fiduciary accounting matter. The attached document is the operative contract, including any amendments and exhibits provided. The disputes that matter concern: testamentary capacity; undue influence; asset transfers. This work product supports a probate or estate dispute — a will or trust contest, a testamentary-capacity or undue-influence question, a guardianship, or a fiduciary-duty and accounting matter — tried to a probate judge rather than a jury. 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. In this engagement, additionally: Prioritize statements about the decedent's intent, capacity, and dependence; who was present at execution; and how the fiduciary handled the assets — admissions about access and control often decide these cases. 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.
Every template in the library assembles like this for probate & estate litigation — open the builder and add only the assignment details needed, using neutral labels where possible, or read the Attorney's Guide to AI Prompting for the method behind it.
Read the clean, general guide for each curated workflow below. To apply the Probate & estate litigation context to your own facts, use the builder actions above.
Inventory every obligation, deadline, notice requirement, and condition precedent in the contract — who owes what, triggered by what, with section cites.
Build a date-ordered medical chronology from the complete record, with source citations for every encounter and explicit flags for treatment gaps, prior history, causation language, and missing records.
Turn an email and letter production into a dated who-knew-what-when timeline with thread lineage and Bates cites — knowledge milestones flagged.
Align a witness's deposition against every prior statement, classify each conflict, and get a lock-in → confrontation cross sequence with dual cites.
Index a document production end to end: document type, date, author, recipients, Bates range, and a one-line description — with the anomalies surfaced.