> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/errors-and-faqs/document-review-output-feels-incomplete.md).

# Document Review output feels incomplete

Sometimes, users feel that the **Document Review** tool has not fully considered all parts of the selected document(s), or that certain sections appear to be missing from the response. In most cases, this is expected behaviour based on how document review works and the nature of the input.

This does not usually mean the tool skipped content intentionally or malfunctioned.

***

#### Why this can happen

There are a few common reasons why a Document Review output may feel incomplete.

<details>

<summary>1. Document size and scope</summary>

When very large documents are selected, or when multiple documents are reviewed together, the system focuses on the **most relevant and representative portions** of the material rather than reading every word line by line.

For example:

* Reviewing several large documents together
* Reviewing a single document running into hundreds of pages

In such cases, the output reflects a reasoned review of the material, not an exhaustive page-by-page reproduction.

{% hint style="info" %}
Document Review is designed for insight and analysis, not verbatim coverage of every line.
{% endhint %}

</details>

<details>

<summary>2. Non-OCR or scanned content</summary>

If parts of the document are scanned documents, handwritten text, or poorly OCR’ed, those sections may not be readable by the system.

This commonly affects:

* Old scanned PDFs
* Documents with stamps, seals, or handwritten notes
* Image-heavy annexures

If the text is not machine-readable, it cannot be reviewed reliably.

</details>

<details>

<summary>3. Overly broad or generic instructions</summary>

Some prompts are too wide in scope to be meaningfully answered.

For example:

* Selecting a 700-page compilation of judgements and asking, *“Summarise every case”*
* Asking for a single output that covers every clause, issue, and fact in detail

In such cases, the response will necessarily be high-level or selective.

</details>

{% hint style="success" %}
Clear, focused instructions lead to more complete and useful outputs. Larger tasks are best broken down into multiple steps or tranches to leverage the tool best.
{% endhint %}

***

#### How to get better results

To improve the quality and completeness of Document Review outputs:

* Break large reviews into **smaller, focused questions**
* Narrow the scope (for example, specific sections, clauses, or issues)
* Ensure documents are **properly OCR’ed** before upload
* Use follow-up questions to drill deeper into specific areas
* Toggle deep mode for improved depth and analysis

You can [use the prompt enhancement feature](/document-review/overview-of-the-document-review-tool.md#prompt-enhancement) or [visit our Prompting Guide](/resources/prompting-guide.md) to know more.

***

{% hint style="info" %}
Document Review prioritises **useful analysis over exhaustive reproduction**. The goal is to help you understand, assess, and work with documents efficiently, not to replicate the document in full.

If a section feels missing, it is often best addressed by refining the question or narrowing the scope rather than rerunning the same prompt.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://help.jurisphere.ai/resources/errors-and-faqs/document-review-output-feels-incomplete.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.