> 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/circle-ups/overview-of-circle-ups.md).

# Overview of Circle Ups

**Circle Ups** helps capital markets teams streamline the process of identifying and marking disclosures across transaction documents.

For capital markets teams, reviewing transaction documents can involve reviewing hundreds of pages, identifying disclosures that need to be circled up, checking the same information across multiple sections, and repeating the process through several rounds of revisions.

Circle Ups automates the first-pass identification of potential disclosures, allowing you to focus your time on reviewing and validating the results rather than manually searching through the entire document.

### How Circle Ups works

Once you upload a document, Jurisphere:

1. **Identifies potential circle ups automatically**\
   Jurisphere reviews the document and identifies sections that may require a circle up.
2. **Groups the results into review categories**\
   The identified circle ups are organised into categories, making it easier to work through the results systematically.
3. **Takes you directly to the relevant sections**\
   Select a circle up to navigate directly to the corresponding section of the document and review it in context.
4. **Lets you review, retain, or discard suggestions**\
   Review each identified circle up and decide whether it should be retained or removed from the final document.
5. **Generates a final marked-up document**\
   Once your review is complete, download the document with the circle ups you have retained.

### Documents you can use with Circle Ups

Circle Ups is particularly useful for **long-form transaction and offering documents** where teams need to identify and review disclosures across multiple sections

#### **Examples include:**

* DRHPs (Draft Red Herring Prospectuses) - Identify potential circle ups across the document during IPO preparation and review.
* RHPs (Red Herring Prospectuses) - Review disclosures before finalisation and filing.
* Offering Circulars - Identify disclosures that may need to be highlighted for review.
* Information Memorandums (IMs) - Review transaction-related disclosures across lengthy information memorandums.
* Placement Memorandums - Assist with identifying potential disclosures in private placement documentation.
* Prospectus Supplements - Review new or amended disclosures introduced in subsequent versions.
* Transaction documents - Review relevant disclosure sections across documents prepared as part of a capital markets transaction. 
* Draft Letter of Offers - The Takeover Code compliant offer document, which can be used by the Public M\&A team as well. 

{% hint style="success" %}
Circle Ups can be especially useful when the same document goes through multiple drafting and review rounds. Instead of manually going through hundreds of pages each time, you can run Circle Ups on the latest version and use the results panel to quickly identify, navigate to, and review potential disclosures.
{% endhint %}

> For example:
>
> IPO workflow: A capital markets team receives a revised DRHP containing several hundred pages. Instead of manually scanning the entire document for potential disclosures, the team runs Circle Ups, reviews the identified results, retains the relevant circle ups, discards the irrelevant suggestions, and downloads the final marked-up version.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.jurisphere.ai/circle-ups/overview-of-circle-ups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.