> 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/pledges.md). # Pledges Pledges tracks soft commitments before investors sign. The board shows how much sits at each stage. A pledge records an investor's interest before they sign. ![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/SENcFFxc3mSua2LOQhz0/Unknown%20image) 1. **Header** Shows the number of pledges in the pipeline and their combined value. 2. **Stages** Group pledges into five columns, each with its own count and dollar total. 3. **Drop here** Marks where to drop a pledge when you drag it into a new stage. 4. **Pledge** Creates a new pledge directly in that stage of the pipeline. 5. **WIRED** Holds pledges whose money has arrived, as the last stage of the pipeline. ### Stages Drag a pledge to move it between the five stages. * **DRAFT:** The pledge is recorded for your own planning, before you contact the investor. * **DISCUSSION:** The pledge is in conversation, and the amount is still being agreed. * **INVITED:** The investor has been sent the deal to review. * **SIGNED:** The investor has signed and the pledge has become a commitment. * **WIRED:** The money has arrived. > Each stage shows how many pledges it holds and their total value ### Pledges and the Investors tab Signed and wired investors also appear on the Investors tab. > **Treat the Investors tab as the record.** Moving a card on the Pledges board updates the pipeline only, and the investor's record and money stay on the Investors tab. ### Reporting pledges > When you report to investors, quote the committed figure from Raise progress on the Overview tab and treat pledges as pipeline. --- # 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/pledges.md?ask=&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.