> 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/capital-calls.md).

# Capital Calls

Capital Calls is where you collect capital that investors have already committed. You issue each call as a percentage of every commitment and track it until it closes.

This screen lists calls across every vehicle, and each deal also has a Capital Calls section in its Investors tab.

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

1. **Total capital calls** Counts the capital calls issued across every vehicle.
2. **Status filters** Filter calls by stage: Draft, Open, Closed, or Canceled.
3. **Search** Finds a call by typing any part of its name.
4. **Toolbar** Lets you refresh the list or issue a new capital call.
5. **Column headers** Sort the table by any of its seven columns when selected.
6. **Call Percentage** Sets the share of each investor's commitment that the call draws down.
7. **Amount** Shows the total the call percentage produces across the whole vehicle.
8. **Due Date** Shows when investors must pay, with the date the call was created beside it.

### A call is set as a percentage

You set one percentage and the platform calculates each investor's share. For example, an investor who committed $200,000 owes $100,000 on a 50% call.

> **Check the percentage before you issue a call.** Entering 50 to mean $50,000 calls half of every commitment, so confirm the Amount the platform calculates before you send.

### Four statuses

* **Draft:** The call is created and ready to issue.
* **Open:** The call has been issued and investor payments are on their way.
* **Closed:** The call is complete and every commitment has been received.
* **Canceled:** The call was withdrawn and stays on record.

> Sort Open calls by Due Date to see which payments to follow up first.

### Naming a call

Give each call a name with a vehicle prefix, the year, and a number, such as ALLOC-2025-01. Search finds calls by name, so a consistent name keeps the list easy to read.


---

# 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/capital-calls.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.