> 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/the-client-handbook.md).

# The Client Handbook

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><h3>12 practice areas</h3></td></tr><tr><td><h3>350+ pre-built workflows</h3></td></tr><tr><td><h3>200M+ documents indexed</h3></td></tr></tbody></table>

Each chapter looks at one practice area and answers three questions: **how work typically moves through your team**, which Jurisphere tools apply at each step, and how much lawyer input they still need.

{% hint style="info" %}
Use this handbook as a starter-kit to understand how your team can benefit the most from Jurisphere.
{% endhint %}

Jurisphere is built around a simple idea: ***legal AI is most valuable when it fits naturally into the workflow lawyers already follow***. Across twelve practice areas, this handbook maps the practical application of Jurisphere tools to the day-to-day realities of legal work, from data-room review and commercial contracting to arbitration strategy, regulatory advisory, capital markets filings, and title diligence.&#x20;

Rather than treating AI outputs as standalone answers, the platform is designed to operate inside the lawyer's existing drafting, review, and research process.

{% hint style="success" %}
The objective of this handbook is straightforward: to give your team a clear operational understanding of how Jurisphere fits into live legal work, where it meaningfully reduces friction, and where strategic legal judgment continues to remain firmly with counsel.
{% 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/jurisphere-guide/handbook/the-client-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.