> For the complete documentation index, see [llms.txt](https://help.paxton.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paxton.ai/help/prompt-library/pull-out-key-information.md).

# Pull Out Key Information

<details open>

<summary><strong>Extract Parties, Roles, and Obligations</strong></summary>

Map who's bound to do what under any contract, order, or multi-party document.

{% code overflow="wrap" %}

```
Identify each party named in the attached document and map their obligations, rights, and restrictions, including any obligations that are conditional, mutual, or triggered by another event. Flag any party whose obligations are vague, internally inconsistent, or unenforceable as drafted. If the document leaves any party's role undefined, identify that rather than inferring it.
```

{% endcode %}

{% hint style="info" %}
Great for kicking off a contract review or making sense of a multi-party agreement.
{% endhint %}

</details>

<details open>

<summary><strong>Extract Key Dates and Deadlines</strong></summary>

Pull a clean, chronological list of every date that matters out of a document so nothing slips.

{% code overflow="wrap" %}

```
Identify every meaningful date and deadline in the attached document, including ambiguous, conditional, or triggered dates that could create a missed-deadline risk. For each, give the date or triggering event, what happens, who is responsible, and the source location. If the document contains relative deadlines you cannot fully resolve, note them rather than guessing.
```

{% endcode %}

{% hint style="info" %}
Especially useful for trial calendars, contract lifecycle tracking, and any document that drives a deadline.
{% endhint %}

</details>

<details open>

<summary><strong>Extract Defined and Technical Terms</strong></summary>

Build a working glossary from any document so you can read the rest of it without losing the thread.

{% code overflow="wrap" %}

```
Identify the defined terms and terms of art used in the attached document, including any used inconsistently or in ways that depart from typical legal usage. Where a term is defined, give the definition; where it is not, explain it in plain English. If any term is critical to interpreting the document, note why.
```

{% endcode %}

{% hint style="info" %}
Read the glossary first, then read the document — you'll move twice as fast.
{% endhint %}

</details>

<details open>

<summary><strong>Build a Narrative Chronology</strong></summary>

Turn the events, communications, and actions in a document into a clean narrative timeline you can read like a story.

{% code overflow="wrap" %}

```
Build a narrative chronology of the events described in the attached document — written as a readable timeline, not a bare list. For each entry, give the date, what happened, who was involved, and the source location. Note gaps in the timeline and flag any place where two sources describe the same event differently. End with a one-paragraph read on the overall arc.
```

{% endcode %}

{% hint style="info" %}
Use on deposition transcripts, correspondence, investigation files, or anything where the sequence of events matters more than the dates themselves.
{% endhint %}

</details>

<details open>

<summary><strong>List the Key Dates</strong></summary>

Quickly pull every important date out of a document.

{% code overflow="wrap" %}

```
List every important date in this document. Include what each date is and who it applies to.
```

{% endcode %}

{% hint style="info" %}
For a more detailed result, see [Extract Key Dates and Deadlines](#extract-key-dates-and-deadlines).
{% endhint %}

</details>

<details open>

<summary><strong>Build a Timeline</strong></summary>

Turn a document or set of documents into a chronological timeline of events.

{% code overflow="wrap" %}

```
Build a chronological timeline of events from this document. For each entry, include the date, what happened, and who was involved.
```

{% endcode %}

{% hint style="info" %}
For a more detailed result, see [Build a Narrative Chronology](#build-a-narrative-chronology).
{% endhint %}

</details>

<details open>

<summary><strong>Pull the Key Parties and Obligations</strong></summary>

Identify who's involved and what each party is on the hook for.

<pre data-overflow="wrap"><code><strong>Identify every party in this document and list each party's obligations, rights, and roles. Note any party whose obligations are unclear.
</strong></code></pre>

{% hint style="info" %}
For a more detailed result, see [Extract Parties, Roles, and Obligations](#extract-parties-roles-and-obligations).
{% endhint %}

</details>

<details open>

<summary><strong>Build a Document Index or Exhibit Table</strong></summary>

Creates a clean index, appendix, or exhibit table from a set of documents.

{% code overflow="wrap" %}

```
Review the attached documents and build a clean exhibit index. For each document, include: an exhibit number or label, the document title or type, the date, the source or author, and a one-line description of what it shows or supports. Present the result as a table.
```

{% endcode %}

{% hint style="info" %}
Works for trial exhibit lists, appendices, statement-of-facts tables, and discovery indices. Add documents to the matter or attach them before running.
{% endhint %}

</details>

<details open>

<summary><strong>Build a Fact, Issue, or Evidence Matrix</strong></summary>

Turns documents into a structured matrix connecting issues, evidence, witnesses, and gaps — a table to build from, not a verified record.

{% code overflow="wrap" %}

```
Build a fact, issue, or evidence matrix from the attached materials. Organize by issue, element, claim, defense, witness, exhibit, date, and source as appropriate, and present it as a table. Distinguish facts from inferences, include document references where available, and flag missing proof or contradictions that need follow-up.
```

{% endcode %}

{% hint style="info" %}
Use when you want a chart, issue matrix, or proof table rather than prose. Works best when the source documents are in the matter or attached.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.paxton.ai/help/prompt-library/pull-out-key-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.