> 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/jurisphere-guide/handbook/how-to-read-this-handbook.md).

# How to read this handbook

Every chapter follows the same three sections. 

{% stepper %}
{% step %}

### Practice Area Overview

A bird's-eye view of what work looks like, and where Jurisphere comes into play. This is where you confirm whether your current work flow matches what our team is solving for.
{% endstep %}

{% step %}

### Stage-by-Stage Workflow

How a typical matter moves through the team, broken into the five or six stages most teams recognise. Each stage details the exact tools that can be leveraged as well as a sample run of tasks in that stage.
{% endstep %}

{% step %}

### Capability Matrix

A table that maps each sub-tasks of the practice area against the Jurisphere tool that handles each one, with a tier showing how much lawyer input the output still needs, and a description of what you actually get
{% endstep %}
{% endstepper %}

***

### The Lawyer-Input *spectrum.*

Four tiers describe how much application of mind each Jurisphere output still needs from the lawyer. The same tool lands in different tiers depending on the task. 

{% hint style="success" %}
**Minimal**

Light verification only. Clerical tasks and grunt work.
{% endhint %}

{% hint style="info" %}
**Moderate**

Lawyer reviews and adjusts the first cut. Automation completes over 70% of the task.
{% endhint %}

{% hint style="warning" %}
**Substantial**

Lawyer materially develops the content. Tools require handholding and guidance.
{% endhint %}

{% hint style="danger" icon="user-hair" %}
**Lawyer-led**

Tools act as ancillaries only. Task requires application of mind and judgement calls.
{% endhint %}

Translation and a chronology are mechanical; verification is enough. But if the document has handwritten text or is largely illegible, the burden of verification increases. 

Research sits in the middle and shifts by practice: arbitration and taxation are fact-heavy and settle at moderate, while compliance and advisory work runs into grey areas that need substantial or partner-led input.

In this guide, each task that forms a stepping stone in a practice area measures the above metrics, so you can estimate Jurisphere's benefits in each cycle. 


---

# 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/jurisphere-guide/handbook/how-to-read-this-handbook.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.