> 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/regulatory-advisory-and-compliance/overview.md).

# Overview

Regulatory advisory is where [Research](https://jurisphere.gitbook.io/jurisphere-guide/research/overview-of-the-research-tool) carries the chapter. The five-agent retrieval, the multi-jurisdictional database coverage, the click-to-source verification on every citation, and the ability to build out the answer in an editable drafting pane all run through Research. Stale citations and hallucinated authorities don't survive Partner review. The Research tool is built to survive that review.

## The shape of the work

A regulatory query is fundamentally a research workflow. [Research](https://jurisphere.gitbook.io/jurisphere-guide/research/overview-of-the-research-tool) runs five specialised agents (Master, Web Search, Judgement Search, Legislation Search, Final Research Note) across a database of over 200 million primary-source documents spanning nine jurisdictions. The internal database updates in parallel as regulators publish on their websites, so the law a lawyer cites today is the law the regulator published this morning.

* Every assertion is anchored to an in-line citation.
* Click any citation to open the highlighted passage in the source.
* Follow-up questions let the lawyer steer the agent toward the operative question.

[Drafting on Document Review](https://jurisphere.gitbook.io/jurisphere-guide/drafting-on-document-review) moves the answer into an editable canvas with version control. Advisory work is where lawyer input is heaviest: cross-statute interpretation, grey-area positions, and the conservative-aggressive call all sit with the partner. Jurisphere accelerates retrieval and structured drafting, but the view stays with the lawyer.

## How the work moves

A mandate moves through the stages below. The detailed walkthrough — with the tools each stage uses and the call the lawyer still owns — is on the next page.

<table data-view="cards"><thead><tr><th>Title</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Issue Framing</strong><br>Frame the regulatory question and the applicable instruments.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#issue-framing">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#issue-framing</a></td></tr><tr><td><strong>Primary Research</strong><br>Select the relevant database(s); attach client documents for context.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#primary-research">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#primary-research</a></td></tr><tr><td><strong>Secondary Research &#x26; Follow-ups</strong><br>Up to thirty follow-ups per thread, contextually aware.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#secondary-research-follow-ups">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#secondary-research-follow-ups</a></td></tr><tr><td><strong>Synthesis &#x26; Opinion</strong><br>Enable Drafting on Research to render the answer in an editable drafting pane.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#synthesis-opinion">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#synthesis-opinion</a></td></tr><tr><td><strong>Output &#x26; Reference</strong><br>Export the structured note as .docx with citations as hyperlinks.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#output-reference">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#output-reference</a></td></tr></tbody></table>

{% hint style="success" %}
**The shape of the time saved.** From question to defensible note in a single working day. Every authority cited is current to today's RBI position. Every assertion opens to its source.
{% 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/regulatory-advisory-and-compliance/overview.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.