Operations

Extract Contract Information with AI

Parties, effective date, term, payment, termination notice, governing law — key terms into a contract register, with "unknown" marking every gap loudly.

Overview

Contract review at register scale is an extraction problem: every agreement needs the same key terms on file. This setup pulls parties (every name in the preamble, exactly as written), effective_date in ISO format, term_length and termination_notice as durations with their units, payment_amount as a bare number, and governing_law — under the strictest settings on the tool: no inference at all, and missing values returned as the literal "unknown" so a human reviewer sees every gap instead of skimming past a null. Legal text punishes guessing; this prompt forbids it.

Workflow

Generate and run per agreement
One contract per call; the preamble guidance tells the model where parties and defined terms live.
Read the "unknown"s first
Return Unknown turns every gap into a visible flag — the missing termination clause is the finding, not a blank.
Keep durations as written
term_length and termination_notice keep their units ("24 months", "30 days") — no unit math, no conversion errors.

Why This Works

Strict no-inference policy matches the cost asymmetry of legal data
"Unknown" beats null when a human must notice what the contract never says
Preamble-aware guidance finds parties where contracts actually put them

Best for

Legal-ops teams filing many agreements into one register
Renewals tracking driven by effective dates and term lengths
Reviews where a visible "unknown" must trigger a human read

Not for

Legal interpretation — what a clause means is a lawyer's question, not an extraction
Clause-by-clause analysis — this extracts register fields, not the whole document

Use cases

Building a contract register with the same key terms per agreement
Flagging agreements where the termination notice was never stated
Extracting party names exactly as the preamble writes them

Customize This Resource

Opens this setup in Extraction Prompt Generator. Generate to get the full extraction prompt — then adjust the fields, missing-data behavior, and ambiguity policy.

Open in Extraction Prompt Generator

Prompt Template

TASK
Extract key terms from the agreement in the input for our contract register.

SOURCE
The input is a contract or legal agreement.
Reading guidance: Party names appear in the preamble; defined terms are capitalized; dates and amounts are often written out in words.

FIELDS TO EXTRACT
- parties (required): All parties named in the preamble
- effective_date (required): Date the agreement takes effect
- term_length (optional): Duration of the agreement
- payment_amount (optional): Recurring or total payment amount
- termination_notice (optional): Notice period required to terminate
- governing_law (optional): Jurisdiction named in the governing-law clause

EXTRACTION RULES
- parties: List every party named; use the organization or person name exactly as written.
- effective_date: Use ISO format (YYYY-MM-DD) when the date can be determined; otherwise extract it as written.
- term_length: Extract the duration as stated, including its unit (e.g. "30 days").
- payment_amount: Extract the numeric value only — no currency symbols or thousands separators.
- termination_notice: Extract the duration as stated, including its unit (e.g. "30 days").
- Extract values from the source text only — do not use outside knowledge to fill fields.
- Do not summarize or interpret the document — return only the fields listed above.

MISSING DATA
- If a field is not found in the source, return the literal string "unknown".
- Use "unknown" only for genuinely absent information — never as a shortcut for skimming the text.
- Never invent or guess a value for a missing field.

AMBIGUITY POLICY
- Extract only information explicitly stated in the source text — do not infer values.
- If a value is implied but not stated, treat the field as missing.

OUTPUT FORMAT
Return the extracted data as a single valid JSON object using the field names below.

EXAMPLE OF A VALID EXTRACTION
{
  "parties": [
    "Acme Corp",
    "Borealis GmbH"
  ],
  "effective_date": "2026-06-10",
  "term_length": "24 months",
  "payment_amount": 1840.5,
  "termination_notice": "30 days",
  "governing_law": "Germany"
}

OUTPUT RULES
- Return only the JSON object — no text before or after it.
- Do not wrap the output in markdown code fences.
- Use the field names exactly as defined — no renaming, no extra fields.

Related Resources

Explore more resources that work well with this one.