> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/the-overview-tab.md).

# The Overview tab

Overview is the first tab you see when you open a deal. It summarizes the raise and links to the tab that holds each detail.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/xPlJRPER0VkBg3uXe1gl/Unknown%20image)

1. **Tab row** Moves between the deal's 13 tabs, with an arrow at the left that brings the earlier tabs back into view.
2. **Raise progress** Shows committed, contributed, and goal, with the target close date and the days remaining.
3. **Progress bar** Draws contributed and committed as two segments against the goal, each with its percentage.
4. **Complete deal basics** Tracks the same eight basics as Setup, and each outstanding item links to the screen that resolves it.
5. **Investors preview** Shows the first few investors and the total, with a link to the full list.
6. **Banking** Shows the account provider, the current balance, and when it was last synced.
7. **Activity** Lists recent signings on the deal, newest first.
8. **Assets** Lists each holding with its type, location, and valuation.

### The tab row

A deal has 13 tabs, so scroll the row or use the arrow at the left to reach them all.

Overview · Setup · Investors · Banking · Closing · Invest · Data Room · Files · Pledges · Updates · Financials · Brokerage Account · Support

### Raise progress

* **Funds contributed:** The money received so far, with the number of investors it came from.
* **Funds committed:** The money investors have signed for, with its own investor count.
* **Funds goal:** The target for the raise, with the amount still remaining below it.
* **Target close:** The planned closing date, with the days remaining shown beside it.

> **Compare the three figures.** If committed is below the goal, the raise needs more investors. If contributed is below committed, investors have signed and their money is still on its way.

### Complete deal basics

The tracker shows how many of the eight basics are complete and lists each item still outstanding, with a link to the screen that completes it.

### Using Overview to review a deal

Read the screen in this order for a quick review of a deal:

1. The status beside the deal name, which shows whether the deal is waiting on you or on Allocations.
2. Complete deal basics, for any item that still needs your action.
3. The gap between contributed and committed, which shows whether to focus on fundraising or collection.
4. The days remaining, because a gap needs faster follow-up close to the target date.
5. The Banking sync time, before you rely on the balance.


---

# 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://docs.allocations.com/why-allocations/the-overview-tab.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.