> 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/understand-a-document.md).

# Understand a Document

<details open>

<summary><strong>Analyze This Document</strong></summary>

A quick read of what the document means and where the issues are.

{% code overflow="wrap" %}

```
Analyze this document. Tell me what it is, what it argues or decides, and any issues, gaps, or risks worth my attention.
```

{% endcode %}

{% hint style="info" %}
For a more detailed result, see [Analyze a Document](#analyze-a-document).
{% endhint %}

</details>

<details open>

<summary><strong>Identify Causes of Action and Theories of Liability</strong></summary>

Pull every legal theory advanced in a document and the elements each one requires to prevail.

{% code overflow="wrap" %}

```
Identify every cause of action or legal theory advanced in the attached document, the party asserting each and against whom, the elements required to prove it, and a short read on how the document alleges or argues each element is met. For each, note any obvious weaknesses, missing elements, or affirmative defenses that jump off the page. Flag overlapping or alternative theories and how they relate.
```

{% endcode %}

{% hint style="info" %}
Works on complaints, motions, demand letters, and any filing that asserts or attacks a legal claim.
{% endhint %}

</details>

<details open>

<summary><strong>Break Down a Court Order</strong></summary>

Get a clean, actionable read on what a court order says, what it requires, when, and from whom.

{% code overflow="wrap" %}

```
Analyze the attached court order and identify the holding in plain English, the reasoning, every directive (who must do what, by when), any conditions or contingencies, and the practical impact on the matter. Extract dates into a clean list and identify open issues the order leaves unresolved. Flag anything in the order that is ambiguous or could be read more than one way.
```

{% endcode %}

{% hint style="info" %}
Works on standing orders, scheduling orders, discovery orders, and rulings on motions.
{% endhint %}

</details>

<details open>

<summary><strong>Analyze a Deposition</strong></summary>

Pull the substance out of a deposition transcript — admissions, inconsistencies, follow-up areas — without reading every page.

{% code overflow="wrap" %}

```
Analyze the attached deposition transcript and identify the most important admissions and testimony, any inconsistencies with prior testimony or documents, areas where the witness was evasive or hedged, and topics warranting follow-up. Organize by topic rather than chronologically and quote with page and line cites. End with the three or four pieces of testimony most likely to matter at trial or in dispositive motions.
```

{% endcode %}

{% hint style="info" %}
Best on full transcripts; for excerpts or one-topic reads, use a topical summary instead.
{% endhint %}

</details>

<details open>

<summary><strong>Analyze Discovery Responses</strong></summary>

Distill written discovery responses into what was admitted, denied, objected to, and produced — with a punch list of follow-up issues.

{% code overflow="wrap" %}

```
Analyze the attached discovery responses. For each request, identify what was admitted, denied, objected to, or evaded, and whether any objection is substantive or boilerplate. Flag responses that are non-responsive, incomplete, or worth challenging in a meet-and-confer or motion to compel. Identify the responses containing the most useful admissions. If anything is ambiguous in effect, flag it rather than assuming.
```

{% endcode %}

{% hint style="info" %}
Works on interrogatory responses, requests for admission, or responses to requests for production — the structure carries across.
{% endhint %}

</details>

<details open>

<summary><strong>Analyze Arguments and Reasoning</strong></summary>

Stress-test the logic, authority, and unstated assumptions behind any brief, memo, or position paper.

{% code overflow="wrap" %}

```
Analyze the arguments made in the attached document. For each, identify the position, the supporting reasoning and authority cited, and the strongest counterarguments — including any limiting, distinguishing, or contrary authority the author did not address. Assess which arguments are strongest and which are most vulnerable. If any reasoning relies on unstated assumptions, name them.
```

{% endcode %}

{% hint style="info" %}
Excellent for prepping a response to a motion or pressure-testing your own draft before sending.
{% endhint %}

</details>

<details open>

<summary><strong>Analyze a Document</strong></summary>

Get a tight, two-minute overview of any document so you know what's in it before diving deeper.

{% code overflow="wrap" %}

```
Analyze the attached document and identify its purpose, the parties involved, the most material provisions or findings, and anything unusual or noteworthy in light of standard practice for documents of this type. If any provisions are ambiguous or open questions remain after your review, identify them rather than working around them.
```

{% endcode %}

{% hint style="info" %}
Works on contracts, court orders, statutes, memos, depositions — anything you'd want to triage quickly.
{% endhint %}

</details>

<details open>

<summary><strong>Identify Risks and Red Flags</strong></summary>

Surface the provisions that create exposure or shift risk, prioritized by severity.

{% code overflow="wrap" %}

```
Analyze the attached document for provisions that create meaningful risk, exposure, or unfavorable terms, including any limits, carveouts, or counterbalancing language that may mitigate them. Rate severity for each and explain why. Flag any risk you cannot fully assess from the document alone rather than overstating or understating it.
```

{% endcode %}

{% hint style="info" %}
The severity ratings make this easy to triage — read the highs, skim the rest.
{% 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/understand-a-document.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.